Circuit (withcircuit.com) is the AI product system that turns customer feedback into build-ready specs. Feedback in, priorities scored, specs generated for Cursor and Claude Code, customers notified when features ship. The full loop, automated.

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

How is Circuit different from other feedback tools?

Other tools sort feedback into dashboards. Circuit (withcircuit.com) generates specs to ship — scored by revenue impact, updated as conditions change, delivered to Cursor and Claude Code via MCP. It covers the full pipeline: feedback to priorities to codebase-aware specs to customer notification.

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.

How long until we see results?

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

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 connect customer feedback to engineering?

Circuit (withcircuit.com) 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. The customer voice is preserved in every spec — what they asked for, why it matters, which files to touch.

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.

Working with Priorities

Using Circuit·

6 min read

Priorities5

3 1 1

User GrowthTypeTheme

1

Bulk CSV importNEW

142 usersFeature24%

2

Slack thread replies

87 usersFeature12%

3

Dashboard load time

74 usersBug8%

4

Dark mode for widgetNEW

61 usersFeature31%

5

Export to PDF

53 usersFeatureStable

Working with Priorities

Priorities are groups of similar feedback, ranked by importance. There is no artificial cap on priorities. More feedback creates more priorities.

How Priorities Are Created

Assess - Each feedback item is assessed for meaning
Group - Similar feedback is combined automatically
Score - Importance metrics are calculated across six dimensions
Rank - Priorities sort by your chosen focus

Website-Aware Classification

Connect your website and Circuit classifies feedback in your product's language. Urgency levels and category themes use your domain terminology instead of generic labels.

Circuit picks this up automatically when you sign up: your email domain is used to find your website and scrape context in the background. To change or add a URL manually, go to Settings → Account → Your product.

Category Corrections

If a priority is categorised wrong, correct it. Circuit remembers the correction and applies it to future feedback. Even when new feedback arrives on the same theme, the corrected category sticks.

Priority Engine

Each priority is scored across six dimensions. Use the dropdown at the top of the Priorities page to sort by the one that matters most right now.

Focus	Categories	Best For
User Growth	All	What most users want
Revenue Growth	All	Enterprise needs
Retention Risks	Complaint, Bug, Friction	Fix what's hurting
Delighters	Praise	Enhance what works
Bug Fixes & Quality	Bug, Friction	Critical issues first
New Features	Feature	Roadmap input

Priority Indicators

Indicator	Meaning
NEW badge	First detected within 7 days
↑ arrow	Volume up >10% vs last week
↓ arrow	Volume down >10% vs last week
Category badge	Bug, Feature, Friction, Praise, Complaint
Competitor mentions	Names on the card, context in the brief. How often and whether users are comparing or switching
Refresh badge	Brief is stale. New feedback has changed the scope since the brief was last generated

Competitor Mentions

When customers mention competitors in their feedback, Circuit surfaces it on the priority card and includes context in the brief. You see which names come up, how often and whether users are comparing features or actively switching.

Filtering Priorities

Click a category badge on any priority to filter by that type (Bug, Feature, Friction, Praise, Complaint)
Use ⌘K / Ctrl+K for quick semantic search across feedback, priorities and briefs

Batch Actions

Select multiple priorities to act on them at once. Checkboxes appear on hover.

Action	What it does
Change status	Set Ready, Building or Shipped on all selected
Assign	Assign to a team member
Export	Download as markdown. Individual briefs or a batch

Setting Your Product Focus

Go to Settings → Account to set your product focus area. This helps Circuit generate more relevant briefs.

Next Step

Click any priority to see its brief and start building.

Working with Priorities

Working with Priorities

How Priorities Are Created

Website-Aware Classification

Category Corrections

Priority Engine

Priority Indicators

Competitor Mentions

Filtering Priorities

Batch Actions

Setting Your Product Focus

Next Step

Related articles