Circuit (withcircuit.com) is autonomous product intelligence — the continuous 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.

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 a Circuit Surface?

A lightweight embed for any website — five surface types: Bubble, Embed, Banner, Thumbs and Trigger. Customers submit feedback in seconds. 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 Surface submission, a Slack message, a CSV row, a transcript segment, 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 specs for Cursor or Claude Code?

Circuit (withcircuit.com) automates the feedback-to-spec pipeline. Feedback flows in from Circuit Surfaces, Slack, Google Sheets, CSV, transcripts 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 — no copy-pasting, no context switching.

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 my codebase?

Circuit (withcircuit.com) bridges customer feedback and your codebase through codebase-aware product 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.

How long does it take to get priorities from feedback?

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.

How does Circuit generate specs from my codebase?

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 how you actually build.

Can I change how priorities are ranked?

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.

How does Circuit connect to Slack?

Add the Circuit Slack integration. Circuit polls your selected channels every 10 minutes, classifies each message by intent, urgency and sentiment, and feeds it into the priority pipeline. No manual sorting.

How do MCP tools work in Cursor and Claude Code?

Install circuit-mcp from npm. Four tools: circuit.priorities (ranked list), circuit.spec (full spec with file paths), circuit.act (ship, assign, correct) and circuit.ask (search feedback). Specs arrive where code gets written.

What feedback sources does Circuit support?

Six sources: Circuit Surfaces (embed on any site), Slack, Google Sheets, CSV upload, transcript upload (Otter, Fireflies, Grain, Whisper) and manual entry. All feed the same pipeline.

Does Circuit replace my existing tools?

No. Circuit reads from Slack, spreadsheets and support threads — wherever feedback already lives. It adds the layer that was missing: scored priorities and codebase-grounded specs.

Is feedback data used to train AI models?

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.

Where is Circuit data stored?

Data is stored on encrypted infrastructure with Supabase (Postgres). All connections use TLS. Backups are encrypted at rest.

Does Circuit access my full codebase?

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.

Who can access my team's data?

Only authenticated team members with the roles you assign. Circuit supports email-based 2FA. No Circuit staff access customer data without explicit permission.

Know what to build next.

Autonomous product intelligence.

Get started free →See how it works ↓

LIVE

Feedback In

Specs Out

Today

709:47:33You shipped it: "Agent loses context mid-session" — customers will hear about this

609:14:10Started building: "Agent loses context mid-session"

Specs Out

509:14:08Product context learned: 3 priorities ranked and ready

409:14:05◇Priority emerging: "Streaming responses in chat" — 5 asking

309:14:04◇Priority emerging: "Token usage visibility" — 7 asking

209:14:03◇Priority emerging: "Agent loses context mid-session" — 9 people asking

109:14:01◇Grouping 43 items into priorities →

Feedback In

7 events · today

9 customers notified

Meet Circuit

Autonomous product intelligence that runs while your team builds.

Customer signal becomes scored priorities. Priorities become codebase-aware specs — with real file paths from your GitHub repo. Specs flow into Cursor and Claude Code via MCP. When a feature ships, customers who asked for it hear back automatically. Without being asked.

Feedback In

Slack, Surface, CSV, transcripts. Circuit listens continuously across every channel.

app.withcircuit.com/welcome

Bring feedback in

Always-on feedback

Circuit collects continuously — no manual imports needed

Surface

Collect feedback from your product

Slack

Sync from channels

Import feedback

One-time or recurring imports from files and spreadsheets

Import CSV

Upload a CSV file

Google Sheets

Import from spreadsheet

Transcript

Upload interview or call transcript

Manual Entry

Paste or type feedback

Smart Priorities

What's rising. What's urgent. What's been sitting across three channels for six weeks. Ranked by truth, not volume.

app.withcircuit.com/priorities

Priorities 11

User Growth ▾

Type ▾

Theme ▾

Project ▾

1
P99 latency spikes on large context windowsShipped
18 usersImprovement
2
SDK is unusable due to missing parametersNEW
12 usersBug
3
Managed prompt store with analytics is missingNEW
9 usersFeature
4
API rate limits cause 429 errors during peak timesNEW
7 usersBug
5
API documentation is outdated and lacks detailsNEW
8 usersImprovement
6
Context window handling truncates long documentsNEW
6 usersBug
7
No SSO support prevents production usage approvalNEW
5 usersImprovement
8
Streaming responses stop mid-sentence unexpectedlyNEW
4 usersBug

Shipped

P99 latency spikes on large context windows

18 usersImprovement

NEW

SDK is unusable due to missing parameters

12 usersBug

NEW

Managed prompt store with analytics is missing

9 usersFeature

NEW

API rate limits cause 429 errors during peak times

7 usersBug

Specs Out

Nine signals from your GitHub repository. Specs cover what to build, why it matters, customer voice, done-when and all feedback history. Delivered via MCP — pull priorities and specs into Cursor or Claude Code without leaving the editor.

app.withcircuit.com/specs

Priorities 11

User Growth ▾

1
P99 latency spikes on large context windowsShipped
18 usersImprovement
2
SDK is unusable due to missing parameters
12 usersBug
3
Managed prompt store with analytics is missing
9 usersFeature
4
API rate limits cause 429 errors during peak times
7 usersBug
5
API documentation is outdated and lacks details
8 usersImprovement

Shipped

P99 latency spikes on large context windows

18 usersImprovement

NEW

SDK is unusable due to missing parameters

12 usersBug

NEW

Managed prompt store with analytics is missing

9 usersFeature

NEW

API rate limits cause 429 errors during peak times

7 usersBug

#4 User Growth

API rate limits cause 429 errors during peak times

7 usersBugAPI Management

V1Building

What to Build

Add rate limit response headers and a 429 error handler to the API layer — currently 429s are returned with no retry guidance, leaving enterprise clients unable to implement intelligent backoff. Return Retry-After, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset headers on every 429 response, and expose per-plan rate limit status via a GET /api/rate-limit endpoint.

Why it Matters

7 enterprise customers on the highest paid plan are experiencing daily production outages during business hours — their end users see a broken product at peak load. Without Retry-After headers or rate limit visibility, clients cannot implement backoff or shed load intelligently. This is a direct contract and churn risk on the top revenue tier.

Customer Voice

“Still getting 429s during business hours. Our product is unusable for customers at peak load.”

Done When

Every 429 response includes Retry-After (seconds), X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers
GET /api/rate-limit returns HTTP 200 with JSON showing plan limit, requests used, requests remaining, and reset timestamp
Enterprise plan tier has a visibly higher limit ceiling than lower tiers (verifiable via the status endpoint)
A client implementing exponential backoff using Retry-After can recover and complete a request without manual intervention
429 response body includes a human-readable message: "Rate limit exceeded. Retry after {N} seconds."

All Feedback (3)

“Rate limits hit us every day in production. We’re on the highest paid plan and still getting 429s during business hours. Our product is unusable for customers during peak times.”

Ben (enterprise) · via CSV · today

“Timeout errors with no explanation. The API hangs for 30 seconds and then drops the connection. No error code, no message, nothing in the response body.”

Simon (paid) · via CSV · today

“No retry logic on your end. We have to re-send the full payload including the entire context window. For large documents that’s expensive and slow.”

Catherine (paid) · via CSV · today

Share Back

The feature gets built. The customer who asked hears back. The loop closes.

app.withcircuit.com/shareback

Priorities

Instinct

Circuit learns as you build.

Most tools count. Circuit reads.

When the same failure mode appears across five different phrasings, Circuit surfaces it before it becomes a churn number. When an enterprise account has flagged the same issue for two quarters, Circuit tells you. Not after they cancel.

Here’s what Circuit surfaced:

RISKtoday

Rate limits raised twice this quarter. Enterprise customers still hitting the ceiling. This is architectural — raising the number won't fix it.

PATTERN2 days ago

SSO unshipped for 2 quarters. 5 enterprise accounts flagged it. Two are actively evaluating alternatives.

SIGNAL4 days ago

Streaming drops are now the loudest bug signal — same failure mode as context window complaints.

Specs land where code gets written.

Circuit connects to Cursor and Claude Code via MCP. File paths from GitHub. Feedback from Slack. Everything arrives in the editor — nothing to copy-paste.

See all integrations →

Cursor

Priorities and specs via MCP

Setup guide →

Claude Code

Priorities and specs via MCP

Setup guide →

GitHub

Codebase context for every spec

Slack

Feedback polling every 10 minutes

Google Sheets

Bulk import

Surfaces

Embed on your site

Start free. Scale as you grow.

All plans include unlimited specs and every integration. Free plan available.

See full pricing →

Free

$0 USD/mo

Feedback/mo100

Seats1

Projects1

SupportStandard

Get started

Starter

$29 USD/mo

Feedback/mo400

Seats2

Projects5

SupportStandard

Get started

Pro

$99 USD/mo

Feedback/mo1,200

Seats5

Projects10

SupportStandard

Get started

Max

$349 USD/mo

Feedback/mo4,500

Seats10

ProjectsUnlimited

SupportPriority

Get started

Feature	Free	Starter	Pro	Max
Price	$0 USD/mo	$29 USD/mo	$99 USD/mo	$349 USD/mo
Feedback/mo	100	400	1,200	4,500
Seats	1	2	5	10
Projects	1	5	10	Unlimited
Support	Standard	Standard	Standard	Priority
	Get started	Get started	Get started	Get started

What's a feedback item? Each piece of extracted feedback counts as one — a transcript with 20 insights uses 20 of your monthly total.

Need more feedback? $9 one-time top-up adds 100 items to any plan.

FAQ

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

Mark it shipped. Circuit emails the customers who asked for it — their original feedback quoted back. New feedback on the same theme feeds the next spec automatically. The loop restarts.

Start building from signal.

Get started free →