01 · 7 questions
About Circuit
What Circuit is, who it's for, and how it fits with the tools you already use.
Autonomous product intelligence. Customer signal becomes scored priorities and codebase-aware specs — then flows into Cursor and Claude Code via MCP. When a feature ships, customers who asked for it hear back automatically. Without being asked.
Founders, product managers and engineers at growth and scaling companies. If you're the person who reads customer signal on Monday and ships by Wednesday — Circuit was made for you.
Other tools sort feedback into dashboards. Circuit generates specs to ship — scored by revenue impact, grounded in your codebase, delivered to Cursor and Claude Code via MCP. The full feedback-to-spec pipeline, automated.
Yes. Specs flow via MCP with file paths and context from your GitHub repository. Pull priorities, fetch specs and start coding without leaving the editor.
An embed for your site that captures feedback directly from your customers. Five surface types — Bubble, Embed, Banner, Thumbs and Trigger. All feed the same priority pipeline.
Circuit works alongside the tools you already have. It reads from Slack, spreadsheets, support threads — wherever feedback already lives — and generates what comes next: scored priorities and codebase-grounded specs.
A codebase-aware brief, generated automatically from the priority. It includes real file paths read from your GitHub repo, acceptance criteria written against your testing patterns, the customer's exact words quoted as context, and a done-when definition. Delivered to Cursor and Claude Code via MCP — ready to act on.
Most teams find the Circuit spec replaces the work that used to happen between "this is a priority" and "the engineer can start building." What teams keep using PRDs for — stakeholder alignment, strategic context, the why behind the what — stays where it always lived.
02 · 4 questions
How it works
From a connected source to a ranked backlog to a shipped feature.
Connect a source and the first batch processes in 15-20 minutes. After that, new feedback scores in real time. Most teams have a ranked backlog within the hour.
Connect GitHub. Circuit reads 9 signals — file signatures, .cursorrules, testing patterns, directory structure, open issues, recent PRs, tech stack, CI config and README. Every spec includes real file paths and follows your team's coding conventions. An AI product spec generator grounded in your codebase.
Yes. The Priority Engine scores across 6 lenses — volume, urgency, revenue impact, positive sentiment, negative sentiment and feature demand. Set a goal and every priority re-ranks to match. A feature prioritization framework that reflects what the team cares about today.
Mark it shipped. Circuit emails the customers who asked for it — their original feedback quoted back. New feedback on the same theme feeds a V2 spec automatically. The loop continues.
03 · 7 questions
Features
The named pieces — Priority Engine, Instinct, Share Back, Projects, Ask Circuit, the MCP and transcripts.
Circuit's scoring system. Every feedback theme scores across 6 lenses — volume, urgency, revenue impact, positive sentiment, negative sentiment and feature demand. Set a goal (growth, retention, quality) and every priority re-ranks to match. Switch lenses and the list reflects the new view. Revenue is weighted by customer tier automatically, so enterprise feedback counts more than free-plan feedback.
Circuit's learned understanding of how your team builds. It remembers what shipped, which classifications got corrected and which patterns appear across feedback. Priorities that match your shipping history get flagged. Specs reference what you've built before. Classifications get sharper every cycle. You don't configure Instinct — it builds itself from your work.
The close-the-loop layer. Mark a feature shipped and Circuit emails every customer who submitted related feedback, with their original words quoted back. Notifications are branded to look like they came from you. Recipients are managed automatically — no list-building, no manual follow-up. Email and in-widget banners both supported.
Separate workspaces for separate products or teams. Each project keeps its own feedback, priorities, specs and integrations — same account, isolated context. Useful for teams running multiple products, or for separating B2B from B2C feedback. Pro and Max plans support multiple projects.
An in-app AI assistant that searches across your feedback, priorities, specs and help articles. Ask in plain language — "what are enterprise customers asking for?", "which priorities mention onboarding?" — and get answers grounded in your data, with citations back to the source.
Four tools delivered to Cursor and Claude Code via the Model Context Protocol: circuit.priorities (ranked list with scores), circuit.spec (full spec for any priority), circuit.act (ship a feature, submit feedback, mark corrections, park priorities) and circuit.ask (search across everything). Install circuit-mcp from npm. No tab-switching, no copy-pasting.
Yes. Upload recordings or transcripts from Otter, Fireflies, Grain or Whisper. Circuit extracts only the product-relevant moments and scores them alongside other feedback — small talk and off-topic sentences are skipped. A 45-minute call typically yields 15-25 scored items, each counting as one feedback item against your plan.
04 · 9 questions
Pricing & plans
Plans, seats, feedback limits and what happens at the edges.
No. Free plan, no card needed. Starter, Pro and Max require a card — cancel anytime.
Yes. Upgrade or downgrade at any time — changes take effect at the start of your next billing period. Downgrading to Free is always available.
Every priority generates a spec. There's no cap — generate, regenerate and edit as many times as you need. Specs are included on every plan.
The main difference is feedback volume per month and team size. All plans include every integration, unlimited specs and the full AI pipeline. Free is for solo exploration. Starter fits solo founders. Pro fits small product teams. Max fits larger orgs or teams with multiple products.
No. GitHub context makes specs more specific (real file paths, tech stack awareness), but Circuit works without it.
Each piece of customer feedback: a widget submission, a Slack message, a CSV row, a manual entry. Duplicates are removed on import and don't count.
A team member who can edit priorities, generate specs, export them and configure integrations.
On paid plans (Starter, Pro, Max): top up ($9 for 100 items) to process them now, or they'll carry forward and process automatically when your next monthly plan starts. On the Free plan, upgrade to a paid plan to continue processing. Existing priorities and specs remain accessible in the meantime.
Data is retained for 30 days after cancellation. Reactivate within that window and everything is where you left it. After 30 days, all data is permanently deleted.
05 · 4 questions
Security & data
Where your data lives, who can access it, and what we do with it.
No. Circuit uses AI for classification and spec generation but customer data is never used to train models. Feedback stays within the processing pipeline and is not shared with third parties for training purposes.
Data is stored on encrypted infrastructure with Supabase (Postgres). All connections use TLS. Backups are encrypted at rest.
No. Circuit reads 9 specific signals from your GitHub repository — file signatures, testing patterns, directory structure and a few others. It does not clone, store or index your full codebase. Read-only access, scoped to what specs need.
Only authenticated team members with the roles you assign. Circuit supports email-based 2FA. No Circuit staff access customer data without explicit permission.
Still have questions?
The fastest way to see if Circuit fits is to connect a source and watch the first batch process. Free plan, no card required.
Get started