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.

DELIVERY SUITE

Specs that ship themselves.

Delivery turns ranked priorities into build-ready specs, lands them in Cursor or Claude Code, watches the PR, and tells customers when their feedback shipped.

Get started free →Watch the loop close ↓

Codebase-aware PRDs. Native MCP. Tested-and-shipped detection. Customer notification on ship.

Delivery is the half of the loop most product tools never reach. Once a priority is ranked, Circuit writes the spec in your conventions, hands it to your build environment, watches the PR through, and closes the loop with the customer who asked.

01 · Spec

Codebase-aware PRDs

Specs that know your stack, your patterns, your naming. Not generic. Grounded in the repo. Build-ready before standup.

02 · Hand off

Native MCP → Cursor & Claude Code

One handshake. Specs land in your build environment as a context window your agent already understands.

03 · Close the loop

Customer notification on ship

The PR merges. Tests pass. The customers whose voice is on that priority get the email. Loop closed.

circuit / delivery · spec → cursor → shiplive

→ circuit ship priority/02 --to=cursor  reading priority #02 · sdk missing parameters in /v2/embeddings  source signals · 11 customers · 4 channels · 3 weeks  scanning codebase · 1,247 files · stack: typescript / fastify / postgres  ✓ spec generated · grounded in /api/v2/embeddings.ts:142  ✓ handshake → cursor:agent · context window loaded   watching pr #2841 · author: agent-cursor  ── 14m later ──  ✓ tests passing · 47/47 · ci green  ✓ merged to main · v2.14.3 deployed   → notifying 11 customers · "you asked, we shipped"  ✓ loop closed · 18m start to ship

v2.14.3 · 18m start to ship11 customers notified

PLUS FOUR MORE CAPABILITIES, EVERY CYCLE

04

Spec versioning tied to git

Every spec has a commit. Every commit has a spec. Roll back the design decision, not just the code.

05

"Done when" detection

Circuit watches the PR through review, CI, deploy. Knows when shipped means shipped — not when merged means merged.

06

Spec library, indexed

Every spec generated lives in a searchable archive. The decision-record your team forgot to write.

07

Changelog auto-write

The shipped feature gets a customer-facing release note in your voice. You approve, it sends.

A scenario

Specs written in Notion, translated by hand into Cursor prompts, version unknown. Discovery ranks the priority, Delivery writes the spec, Cursor builds it. Eighteen minutes from priority to deployed. The customer who filed the bug gets notified before standup.

What it replaces

×The PRD-in-Notion bottleneck
×Hand-pasting specs into Cursor
×"Did we ship that?" Slack threads
×Manual customer "we built it" emails
×Changelog Mondays

Delivery is available on all plans.

See pricing →

The build is the fast part. Make the spec match.

Get started free →Then: Intelligence →