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.

Memory

Using Circuit·

4 min read

Memory

Circuit learns from what you ship. The longer you use it, the sharper it gets.

How Memory Works

Every time the team ships a brief or corrects a classification, Circuit records it. Over time, these records form a picture of how the team makes decisions: which themes get prioritised, which customer segments matter most and how specs are structured.

This isn't configuration. It happens automatically as the team works.

Ship Memories

When you mark a brief as shipped, Circuit writes a memory. It records:

Theme of the shipped feature
Volume of feedback at time of ship
Customer segment that drove the priority

These memories accumulate. After a few ships, patterns emerge.

Classification Corrections

Correct a category on a priority and Circuit remembers. The correction applies to future feedback on the same theme. Even when new feedback arrives, the corrected category sticks.

This means less time fixing classifications and more time building. The system adapts to how the team thinks about its product.

What Briefs Remember

After a few ships, briefs show what Circuit remembers: previous ships, corrections and related context. If the team has shipped something similar before, the brief surfaces it.

This helps avoid duplicate work and gives the builder context on past decisions.

What Circuit Knows

Go to Settings → Account to see what Circuit has learned: ship count, category breakdown (e.g. Bug 65%, Feature 23%) and any classification corrections. This data is used automatically to improve briefs and priority scoring.

Blind Spot Detection

After 3 or more ships with a strong segment bias, a challenge banner appears at the top of the Priorities page. For example: "You've been focused on Enterprise. 4 SMB items are waiting." Dismiss it and it reappears after 7 days.

Shipping History on Priorities

Priorities flag when they match your shipping history. If a priority aligns with themes the team has shipped before, it's marked. This gives a quick signal: has the team seen this pattern before?

Memory in MCP

Memory enriches the MCP tools too. When pulling priorities or briefs from Cursor or Claude Code:

Priorities flag when they match your shipping history
Briefs include past context from related ships

Ask your coding tool: "Have we shipped anything like this before?" to surface memory directly.

The Compounding Effect

Each ship makes the next cycle sharper. Priorities align closer to how the team actually makes decisions. Briefs reference what's been built before. Classifications get it right the first time.

The loop tightens with every cycle.

Memory

Memory

How Memory Works

Ship Memories

Classification Corrections

What Briefs Remember

What Circuit Knows

Blind Spot Detection

Shipping History on Priorities

Memory in MCP

The Compounding Effect

Related articles