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.spec 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.

Docs

Feedback in

Surface Analytics

Each widget has its own analytics dashboard. Open it from Settings → Integrations → Widget by clicking a widget name.

Metrics

Metric	What it shows
Total responses	All-time submission count for this widget
Responses this week	Submissions in the current 7-day window
Positive / Neutral / Negative	Breakdown by sentiment (thumbs up, neutral, thumbs down)
Average rating	Mean score across all rated submissions (1–5 scale)
Bug reports	Submissions classified as bug reports
Feature requests	Submissions classified as feature requests
Revenue tier breakdown	Responses split by Enterprise, Paid, and Free users (where email is captured)

Each metric card shows a 30-day trend chart.

Feedback Table

Below the metrics, the feedback table shows each submission with:

Feedback text
Submission date
Submitter email (if provided)
Rating
Screenshot (if captured)
Linked priority (if routed)
Intent type (bug, feature request, praise, other)

Filters: Rating, intent type, status. Combine filters to narrow results.

Export: Click Export CSV to download the current filtered view.

Filtering by Surface or Context

If you use data-context on Inline, Thumbs, or Bar surfaces, each submission carries that tag. Filter the feedback table by context to see per-feature or per-flow responses.

Example contexts:

feature:dark-mode — which users thumbed-up or down after trying dark mode
flow:checkout-complete — post-checkout bar responses
help-article:api-docs — inline feedback on a specific help article

Notification Branding

Emails sent when you close the loop use your workspace branding. Configure in Settings → Integrations → Widget → Notification branding:

Company name
Logo URL
Accent colour (hex)
Footer text
Sender display name

API Key Management

Your widget API key authenticates submissions. To regenerate:

Go to Settings → Integrations → Widget
Click Regenerate API Key
Update data-api-key in every embed snippet that uses the old key

Regenerating immediately invalidates the previous key. Submissions from old keys will fail until the snippets are updated.

Can't find what you're looking for?

Contact support

Docs

Surface Analytics

Surface Analytics

Metrics

Feedback Table

Filtering by Surface or Context

Notification Branding

API Key Management

Related docs