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.

Founders, product managers and 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.

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.

What happens after a feature ships?

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

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.

The product intelligence system for teams that ship daily.

Get started free →See how it works ↓

Lives in your stack — natively, via MCP

CursorClaude CodeGitHubSlack

The bottleneck moved

The slow part isn't building anymore. It's deciding what to build. Circuit is the intelligence layer between feedback and shipped code.

Discovery

Know what to build next.

Explore Discovery →

Collect messy feedback from every channel — ranked by impact, re-ranked the moment something changes.

Priorities · ranked by impact11 active

From: 247 Slack · 89 Transcripts · 12 calls→ 11 priorities

01P99 latency spikes on large context windows18 usersShipped

02SDK missing parameters block onboarding12 usersBuilding

03Managed prompt store with analytics9 usersNew

04API rate limits cause 429s at peak7 usersNew

05SSO for enterprise tier5 usersNew

Re-ranked 3m ago+ 6 more

Delivery

Ship the right thing, codebase-aware.

Explore Delivery →

Specs grounded in your repo and the customer threads that asked for it. Pulled into Cursor and Claude Code on demand.

PRD-0214 · Building23 customers waiting

Grounded in: 14 Slack threads · 9 GitHub issues · 3 calls · your repo→ spec

PRD-0214

API rate limits — proper 429 headers

Customer impact

23 asking · 4 enterprise

Done when

Retry-After + X-RateLimit-Remaining returned on every 429.

Codebase context

src/api/rate-limit.ts
src/middleware/headers.ts
tests/rate-limit.test.ts

Status

Building

Pulled into Cursor · just now09:14:21

Native MCP integration·Specs pulled into Cursor and Claude Code on demand·Zero context-switch

Intelligence

The longer you run it, the more it knows.

Explore Intelligence →

Patterns and risks surfaced from the whole record — every customer, every signal, every shipped outcome. Reasoning across the graph, not a single thread.

Instinct · surfaced this week14 signals

Reasoning across: 248 customers · 1,243 signals · 90 days→ patterns

Riskjust now

Rate limits raised twice this quarter. Enterprise customers still hitting the ceiling.

Pattern2d ago

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

Signal4d ago

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

Reasoning across 1,569 nodes+ 11 more

Built for the team that reads feedback one day and ships it the next.

"I run Circuit on Circuit. My customers hear back the moment something ships — and they know I'm listening."

Catherine Williams-Treloar · Founder

The category

Autonomous product intelligence.

Behind every Circuit feature is the product intelligence graph — a connected record of every customer who ever asked, every signal they sent, every priority it shaped, every spec it produced, every outcome that shipped. Every release sharpens the graph.

How autonomous product intelligence works →

Customers

248

Signals

1,243

Priorities

Specs

Shipped

Product intelligence graphLive · 1,569 nodes

Start free. Scale as the product grows.

See pricing →Talk to the team

The thinking behind autonomous product intelligence.

All writing →

ThinkingWhy autonomous product intelligence compounds8 min read PracticeHow to prioritise a product backlog without a meeting7 min read PracticeHow to write a PRD from customer feedback — and why AI does it faster12 min read EssayThe bottleneck moved8 min read

Listen. Decide. Ship. Repeat.

The longer you run it, the more it knows.

Get started free →Talk to the team