Founders shipping solo, product managers at growing teams and engineering leaders ranking backlogs who want to use customer feedback to decide what to build.

Does Circuit work with Cursor and Claude Code?

Yes. Circuit (withcircuit.com) connects to Cursor and Claude Code through the Model Context Protocol (MCP). Pull priorities, fetch specs with file paths and context from GitHub, and start coding without leaving the editor.

What is the Circuit Widget?

A lightweight embed for any website. Customers submit feedback in seconds with a simple form. One line of code to install. Themed to match any brand. Feedback flows straight into Circuit for classification and scoring.

What if we already have a feedback tool?

Circuit reads from where feedback already lives. Slack, spreadsheets, support threads. It doesn't replace existing tools. It generates what comes next: scored priorities and build-ready specs for Cursor and Claude Code.

What counts as a feedback item?

Each piece of customer feedback: a Circuit Widget submission, a Slack message, a CSV row, a manual entry. Duplicates are removed on import and don't count toward the limit.

Do I need to connect GitHub to use Circuit?

No. GitHub context makes specs more specific (real file paths, tech stack awareness), but Circuit works without it. Specs are still generated with the what, why, customer voice, implementation notes and done criteria.

How do I prioritize features by revenue impact?

In Circuit (withcircuit.com), link customer revenue data (customer name and revenue or SKU) and every feedback theme scores by revenue impact alongside urgency and sentiment. Set the Priority Engine to Revenue Growth and the list re-ranks to surface what drives the most revenue. No spreadsheets, no manual scoring.

How do I turn customer feedback into build specs?

Circuit (withcircuit.com) automates this. Feedback flows in from Circuit Widget, Slack, Google Sheets, CSV or manual entry. Circuit classifies it by intent, urgency and sentiment, groups it into priorities and generates build specs in seconds. Connect GitHub and every spec includes real file paths, tech stack context and naming conventions. Specs flow to Cursor and Claude Code via MCP.

How do I notify customers when features ship?

In Circuit (withcircuit.com), mark a priority as shipped. Circuit automatically emails every customer who submitted related feedback, with their original feedback quoted back. No manual follow-up. New feedback on the shipped feature flows in automatically for V2 specs.

How do I integrate product management with Cursor?

Circuit (withcircuit.com) connects to Cursor through the Model Context Protocol (MCP). Use MCP tools from inside Cursor: circuit.priorities to fetch ranked priorities, circuit.brief to pull a full spec with file paths, circuit.ask to search feedback and circuit.act to mark a priority as shipped. Specs include GitHub codebase context.

How do I use Claude Code for product management?

Circuit (withcircuit.com) connects to Claude Code via MCP. Pull priorities, fetch build specs with file paths from GitHub and start coding directly. Circuit handles feedback collection, AI scoring and spec generation upstream. Claude Code handles the building. The two work together — Circuit decides what to build, Claude Code builds it.

Feedback in.
Specs out.

Name: Circuit
Price: 19 USD

AI agents build fast. Circuit guides what to build.

See how it works

Keyboard shortcuts

Ready

Customer Voice

"I'd love keyboard shortcuts for faster navigation"

Files to Touch

src/hooks/useKeyboardShortcuts.tsNEW

src/components/App.tsxMODIFY

Meet Circuit

Circuit is the AI product system that turns customer feedback into scored priorities and build-ready specs for Cursor and Claude Code. The full loop — from feedback to shipped feature — automated.

Circuit gets smarter the more team and agents build.

Read the story →

Circuit 01

Feedback flows in

Circuit collects customer feedback from 5 sources: Circuit Widget, Slack, Google Sheets, CSV and manual entry. Connect Slack and feedback is scored by morning.

Circuit Widget

What would make this product better?

I'd love to see keyboard shortcuts for faster navigation...

Submit feedback

Circuit Widget

Connected

Slack

Connected

Circuit 02

Priorities surface

Circuit groups feedback into themes, each scored and ranked by urgency and sentiment. Add customer revenue data and priorities also rank by revenue impact. Set a goal (growth, retention, quality) and the Priority Engine re-ranks the list to match. Review in 5 minutes, not 5 meetings.

Priorities

3Ready

1Building

2Shipped

Keyboard shortcutsNEW

47 usersFeature12%

CSV export

31 usersFeature8%

Dark mode

24 usersEnhancement3%

Circuit 03

Specs, ready

Connect GitHub and every spec knows your codebase — file paths, tech stack and naming conventions. 5 sections: what to build, why, customer voice, relevant files and done criteria. Specs flow to Cursor and Claude Code via MCP. No dashboard to interpret. No copy-pasting between tools.

Keyboard shortcuts

Ready

Customer Voice

"I'd love keyboard shortcuts for faster navigation"

Files to Touch

src/hooks/useKeyboardShortcuts.tsNEW

src/components/App.tsxMODIFY

Done When

•Keyboard shortcuts work for top 5 actions
•No conflicts with browser defaults
•Shortcut hints visible in tooltips

Feedback in. First spec in minutes.

Circuit 04

The loop doesn't close. It restarts.

Ship a feature and Circuit emails the customers who asked for it, with their original feedback quoted back. New feedback on shipped features flows in automatically. V2 specs generate as new patterns emerge.

Customer notification

You shared this feedback with us:

"I'd love to see keyboard shortcuts for faster navigation"

We built what you asked for.

Keyboard shortcuts for common actions

Priorities stay current

New feedback is classified and grouped as it arrives. Themes update. Scores shift. Stale specs get flagged. A weekly digest shows what moved, what's new and what dropped off.

The list reflects today, not last week. The only decision left: ship or wait.

Each ship teaches Circuit how the team decides. Which categories matter. Which segments drive revenue. How specs should read. The next list is sharper than the last.

Specs land where code gets written

Circuit connects to Cursor and Claude Code via MCP to deliver specs with file paths directly in the editor. Feedback from Slack is polled every 10 minutes. Codebase context from GitHub. Everything connected, nothing to copy-paste.

See all integrations →

Cursor

Priorities and specs via MCP

Claude Code

Priorities and specs via MCP

GitHub

Codebase context for every spec

Slack

Feedback polling every 10 minutes

Google Sheets

Bulk import

Circuit Widget

Embed on your site

How specs reach your editor

Feedback scored

Priorities update in Circuit

→

Spec generated

With file paths from GitHub

→

Pull from editor

Via MCP in Cursor or Claude Code

Straightforward pricing

Starter at $19/mo, Pro at $79/mo, Max at $249/mo. All plans include unlimited specs and every integration. 14-day free trial on any plan.

See full pricing →

Starter

$19 USD/mo

Feedback/mo200

Seats2

SupportStandard

Pro

$79 USD/mo

Feedback/mo1,500

Seats5

SupportStandard

Max

$249 USD/mo

Feedback/mo5,000

Seats10

SupportPriority

Feature	Starter	Pro	Max
Price	$19 USD/mo	$79 USD/mo	$249 USD/mo
Feedback/mo	200	1,500	5,000
Seats	2	5	10
Support	Standard	Standard	Priority

FAQ

The AI product system that turns customer feedback into build specs. Feedback in. Priorities scored. Specs generated for Cursor and Claude Code. Customers notified when features ship.

Founders shipping with a team under 10. Product managers at growing startups. Engineers ranking backlogs. If customer feedback drives what you build, Circuit is for you.

Other tools sort feedback into dashboards. Circuit generates specs to ship — scored by revenue impact, updated as conditions change, delivered to Cursor and Claude Code via MCP.

Yes. Specs flow via MCP with file paths and context from GitHub. Pull priorities, fetch specs and start coding without leaving the editor.

A simple embed for your site. Customers submit feedback in seconds. It flows straight into Circuit for scoring.

Connect a feedback source and priorities appear within minutes. Specs generate in seconds. Most teams have a ranked backlog on day one.

Circuit reads from where feedback already lives. Slack, spreadsheets, support threads. It doesn't replace your tools. It generates what comes next: scored priorities and build-ready specs.

Feedback flows in from Circuit Widget, Slack, Google Sheets, CSV or manual entry. Circuit classifies it, groups it into priorities and generates build specs in seconds. Connect GitHub and every spec includes real file paths and tech stack context. Specs flow to Cursor and Claude Code via MCP.

Circuit bridges customer feedback and engineering through codebase-aware specs. Feedback is collected, scored and grouped into priorities. Specs are generated with file paths from GitHub. Engineers pull specs directly into Cursor or Claude Code via MCP.

Feedback in.Specs out.

AI agents build fast. Circuit guides what to build.

Meet Circuit

Feedback flows in

Priorities surface

Specs, ready

Keyboard shortcuts

The loop doesn't close. It restarts.

Priorities stay current

Specs land where code gets written

Cursor

Claude Code

GitHub

Slack

Google Sheets

Circuit Widget

Straightforward pricing

Starter

Pro

Max

FAQ

Listen. Decide. Ship.Repeat.

Feedback in.
Specs out.

Listen. Decide. Ship.
Repeat.