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.

Get started

Quick Start Guide to Circuit

Feedback inImportPrioritiesRankSpecsGenerateShip + Close the loopNotify

Quick Start Guide to Circuit

What is Circuit?

Circuit is the product intelligence layer between customer feedback and your codebase. It collects feedback from wherever your customers talk — Slack, your website, support transcripts, CSV exports — groups it into ranked priorities and writes codebase-aware product specs for each one. Specs reference your actual codebase, so engineers know exactly what to build and where.

When you ship, Circuit notifies the customers whose feedback drove the feature. Their next message starts the next spec.

Why it helps

Most teams already have the feedback. The problem is what happens to it: buried in Slack threads, spread across spreadsheets, lost between support and product. Turning it into a decision takes days. Turning a decision into a spec takes hours. Circuit compresses both into minutes.

Feedback from 6 sources flows into one ranked list
Priorities scored by volume, urgency, sentiment and revenue impact
Specs generated with real file paths from your codebase
Customers hear back when their request ships

The loop closes automatically. New feedback on a shipped feature starts a V2 spec.

How to get started

Feedback in → Priorities → Specs out → Ship → Share back

Feedback flows in from your channels (Slack, Surfaces, CSV, Google Sheets, transcripts, manual entry)
Circuit groups it into themes and ranks them by volume, urgency, sentiment and revenue impact
A build spec generates for each priority — 5 sections, codebase-aware if you connect GitHub
You ship. Circuit notifies the customers whose feedback drove it
New feedback on that theme starts the next cycle automatically

Step 1: Set up your account

During onboarding you will be asked:

Your role — Founder, Product Manager, Engineer or Designer
How you found Circuit — optional, just curious
Your product in a sentence — if you don’t have a public website for Circuit to scrape, describe your product in one sentence. Circuit uses this to generate relevant specs. You can also set or update this in Settings → Team & Account at any time.

Step 2: Connect GitHub (recommended)

Without GitHub, specs are generated but the Files to Touch section is omitted.

Go to Settings → Integrations → GitHub
Click Connect and select your repository

Circuit reads 9 signals from your repo — all read-only. Specs immediately start referencing real paths and following your team’s coding conventions.

Step 3: Bring feedback in

Pick at least one source. You can add more later. Minimum 10 items for meaningful priorities.

Always-on sources

Circuit collects continuously once connected — no manual imports needed.

Slack

Go to Settings → Integrations → Slack
Click Connect and authorize
Select channels (e.g. #customer-feedback, #support)

Circuit polls every 10 minutes. Forwarded emails are parsed automatically.

Surfaces

Go to Settings → Integrations → Surfaces
Choose a surface type (Float is the quickest to set up)
Copy the embed code and paste before </body> on your site

Feedback arrives in real time.

Import sources

One-time or recurring imports from files and spreadsheets.

CSV

Go to Settings → Integrations → Import
Upload a .csv file with a feedback text column
Map columns, preview, import

Good for: NPS exports, support ticket exports, survey responses.

Google Sheets

Go to Settings → Integrations → Google Drive
Click Connect and authorize
Select a spreadsheet and map the feedback column

Good for: Support exports in Sheets, NPS data, bulk historical feedback.

Transcripts

Go to Settings → Integrations → Import
Click Upload transcript
Paste content or upload from Google Drive

Supports Otter.ai, Fireflies, Grain and Whisper formats. Up to 25 feedback segments extracted per call.

Manual entry Click + Add in the top nav and paste feedback directly. Good for one-offs or testing.

Step 4: See your priorities

Once feedback is imported, Circuit classifies and groups it automatically. Go to the Priorities page.

Priorities are ranked by the User Growth lens by default
Switch lenses (Revenue Growth, Retention Risks, Bug Fixes, etc.) using the dropdown
Each priority shows volume, type, trend and a NEW badge if it appeared in the last 7 days
Click any priority to open its spec

Step 5: Read a spec

Every spec has 5 sections:

Section	What it contains
What to Build	One clear task statement
Why It Matters	Who's affected and revenue context
Customer Voice	Real quotes from feedback
Files to Touch	Suggested file paths from your codebase (requires GitHub)
Done When	Exit criteria

Click Copy to grab the full spec and paste into Cursor, Claude Code or any editor.

Step 6: Connect Cursor or Claude Code (optional)

Pull priorities and specs directly into your editor without copy-pasting.

Cursor — run once:

npx circuit-mcp setup

Claude Code — run once:

claude mcp add circuit -- npx circuit-mcp

First run opens a browser for OAuth. Then ask: "What are my top priorities?" or "Get the spec for [priority name]."

Step 7: Ship and close the loop

When a feature is done:

Open the spec and click Mark as Shipped
The Share Back dialog opens — review the recipient list (customers whose email is on file from any feedback source)
Choose a channel: email, surface banner, or both
Send

Customers get notified. The spec moves to Shared. New feedback on that theme feeds into a V2 spec automatically.

What's next

Add your team — Settings → Team → Invite
Set up more channels — Slack, Surfaces, Transcripts, API
Connect MCP — work from Cursor or Claude Code without leaving the editor
Questions? Email support@withcircuit.com

Docs

Quick Start Guide to Circuit

Quick Start Guide to Circuit

What is Circuit?

Why it helps

How to get started

Step 1: Set up your account

Step 2: Connect GitHub (recommended)

Step 3: Bring feedback in

Always-on sources

Import sources

Step 4: See your priorities

Step 5: Read a spec

Step 6: Connect Cursor or Claude Code (optional)

Step 7: Ship and close the loop

What's next

Related docs