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.

Works with your stack

Circuit connects where feedback lives and where code ships.

Where AI specs go

Cursor and Claude Code via MCP

Circuit connects to Cursor and Claude Code through the Model Context Protocol. Pull priorities, fetch specs, search feedback and update build status from inside your coding tool.

See how specs are generated →

Setup

•Cursor: Add Circuit MCP to your Cursor config
•Claude Code: Run claude mcp add circuit
•First run opens a browser for OAuth authentication
•Token cached locally for 30 days

View circuit-mcp on npm →

4 MCP tools

circuit.prioritiesRanked priorities ready to build

circuit.briefFull spec for any priority with all 5 sections

circuit.askSearch feedback and priorities for context

circuit.actUpdate build status (start building, mark as shipped)

Example: asking for priorities in Cursor

> What should I build next?

circuit.priorities → 3 results

Keyboard shortcuts — Score: 87
mentions · urgency: high · revenue: $18k MRR

CSV column mapping — Score: 71
mentions · urgency: medium · revenue: $12k MRR

Dark mode — Score: 64
mentions · urgency: low · revenue: $9k MRR

GitHub. Codebase context for every spec

Connect your repo and Circuit reads the codebase to generate specs that reference real files. Without GitHub, specs are useful but generic. With it, every spec includes actual paths marked as new or modify. Naming conventions followed. Open issues accounted for.

What Circuit reads

README, directory structure, tech stack, recent commits, open and merged PRs, open issues, relevant source files, testing patterns, contributing guide, config files and GitHub Actions workflows. 13+ contextual signals from your repo.

What specs include

Actual file paths marked as new or modify, awareness of naming conventions and context from open issues and PRs. Create GitHub issues directly from any spec.

Where feedback comes from

Slack. Automatic feedback collection

Connect your workspace and Circuit monitors selected channels with no manual forwarding. OAuth connection with AI-suggested channel selection. Polled every 10 minutes. Messages parsed for customer metadata and revenue band.

Google Sheets. Bulk import

Connect Google Drive, select a spreadsheet, review the auto-detected column mapping and import. Useful for historical feedback or tools that export to Sheets.

CSV. Drag and drop

Upload any CSV. Circuit auto-detects delimiter, encoding and headers. Map columns, review and import.

Widget. Embed on your site

A lightweight, adjustable feedback form for your website. Optional rating selector, screenshot capture and URL capture. Public endpoint, no authentication needed for submitters.

Manual entry

Paste feedback from anywhere. Email threads, support tickets, meeting notes. Processed through the same AI pipeline as every other source.

Automation and events

Webhooks. Connect anything else

Send events to any HTTP endpoint, Slack channel, Linear, GitHub or PagerDuty.

Available events

•Spec generated
•Build status changed (ready → building → shipped)
•New priority created
•Priority volume spike (>20% increase)
•New feedback received

Test any hook before going live with full execution history, timestamps and status codes. All integrations included on every plan.

See pricing →