Intelligence Suite

The product world model.

Every signal, priority, spec and outcome connects into one product intelligence graph. Ask it questions, watch it track change over time, and let it learn from everything you ship. The longer it runs, the more it knows.

01 · Ask

Stop scrolling dashboards. Ask.

A question in plain language, an answer from your own data — with the rows behind it.

Circuit
AskNew conversation
What did we deprioritise last month, and why?
Three priorities dropped out of Next in April. The biggest was Version history — dismissed on Apr 4 after two enterprise accounts churned and the evidence score fell below threshold. The full reasoning opens beside this chat.
Has it come back since?
Yes — 5 new signals this week, across 2 accounts. Radar flagged it under Coming back on Monday.
Ask anything…
Enter to send · Shift+Enter for a new line
Ask in natural language.

“Which accounts have asked about export the longest?” “What did the enterprise accounts say about pricing last quarter?” Circuit answers from your signals, priorities, briefs and customer records.

Every answer is cited.

Each claim links to the source rows behind it. You can click through to the feedback, the priority or the spec — the answer is auditable, not generated from thin air.

One search across everything.

Signals, priorities, briefs, specs, outcomes, accounts and memory — one search box, by meaning rather than keyword. “Can’t export” finds “bulk download missing.”

— Also includes
Saved questions.
Re-run the same question on a schedule and get the answer in your inbox.
Search by meaning.
Semantic search across the whole graph, not keyword-matching per page.
Source-typed results.
Every result shows whether it’s a signal, a spec, an account or a memory.
02 · Trajectory

A rank without a trajectory is only half the picture.

Every priority carries a direction over time, so you know whether something is climbing toward the top or already on its way out.

Circuit
Priorities58Ready 58Building 2Shipped 12
1
AI rewrite collides when two people edit a block
18 signals · 5 accountsBugRising
2
Presence cursors freeze on large canvases
12 signals · 4 accountsBug
3
Let AI summarise a long thread into a shared docNEW
9 signals · 3 accountsFeature
Heating or cooling, at a glance.

Each priority shows a state — warming, hot, cooling, dormant — driven by signal velocity, account-spread change and sentiment shift. A sparkline sits on every row.

Volume spikes, flagged the day they happen.

A theme that triples in a day surfaces as an alert at the top of the inbox, not a surprise in next quarter’s review.

Sentiment flips, caught before churn.

When a previously-loved feature turns negative, Circuit flags the reversal — the early signal of an account at risk.

— Also includes
Topic drift detection.
When “export” starts splintering into “CSV export” and “scheduled export,” Circuit proposes the split.
Cross-source corroboration.
The same theme in Slack, Reddit, email and a call within 30 days raises a “heard everywhere” flag.
Anomaly digest.
One email when something changed enough to matter.
03 · Accounts

Whose voice is shaping the roadmap.

The customer graph runs both directions — priorities know their accounts, accounts know their priorities — so you can weight the roadmap by who’s asking.

Circuit
Customers3
Name
Email
Company
Revenue
Last seen
SSimon
Northwind
Enterprise
2d ago
BBen
Helio
Mid-market
1w ago
CCatherine
Meridian
Starter
3w ago
Accounts behind every priority.

For any priority, see the accounts whose signals make it up — sorted by revenue, engagement, churn risk or recency.

Priorities behind every account.

For any account, see every theme they’re driving across the list. One click answers “what is Northwind shaping?”

Influence, not just volume.

Circuit scores each account by how many ranked priorities they appear in, weighted by rank. You see who shapes the roadmap most — a more useful number than ticket count.

— Also includes
Churn-risk lens.
Re-rank by which priorities most reduce churn risk, in one click.
Revenue lens.
Money-weighted ranking, transparent and toggleable.
Lens reports.
Send the engineering or executive view to the team on a schedule.
04 · Memory

Your past decisions stop being lost.

Every outcome — shipped, parked, deferred — is recorded. Future briefs stand on the memory of every old one.

Circuit
Memory

What Circuit remembers about co-edit

Tandem·9 outcomes recorded·since Jan
Past shipsWhat you closed here, and how it landed.
  • Co-edit conflict fix
    Shipped Apr · 14 people notified · no regressions since
    co-edit.ts
  • Presence cursors for shared blocks
    Shipped Feb · 6 accounts asked · still the most-used view
    Canvas.tsx
  • AI thread summary
    Deferred to next quarter · reason and history kept
CorrectionsThe changes you made that Circuit carried forward.
  • You renamed “Realtime” → “Collaboration”
    Re-clustered 31 signals · the new name carries into briefs
  • You re-ranked block locking above export polish
    Circuit weights co-edit work higher here now
Related contextWhat bit last time you touched this ground.
  • Locking the block briefly broke presence cursors
    Last co-edit change · Simon caught it · watch this path
    usePresence.ts
  • Ben flagged merge order on queued edits
    Replay the queue after the rewrite lands, not before
    co-edit.ts
  • Catherine asked for a shipped-note on this one
    Close the loop with the 14 who reported the conflict
Context from what happened before.

When a new brief touches an area you’ve worked in, Circuit surfaces the relevant past outcome before you start. “Last time we touched billing, the edge case was annual plans.”

Risks from evidence, not guesswork.

The risk section is populated from past outcomes and signal patterns — “three accounts asked for this and the opposite, scope risk” — instead of invented caveats.

Patterns across what ships.

Circuit surfaces what kinds of work succeed: “briefs that included transcript signals shipped faster.” You learn from your own shipping history.

— Also includes
“We’ve touched this before” nudge.
New priorities in a known area surface with the prior outcome attached.
Win/loss tagging.
An honest record of what moved the needle.
Outcome cohorts.
Compare how different kinds of briefs performed.
— Compound

The graph is the moat.

Voice, priorities, specs, outcomes and accounts compound into one record that no team without it can catch up to. A team running Circuit for twelve months is deciding with everything they shipped, every correction they made, and every customer who responded. The longer it runs, the more it knows.

one graphcited answerslearns from every outcome
See the full discipline →
Questions

Asked and answered.

What can I ask Circuit?

Q1

Anything grounded in your data — which accounts asked for what, what shipped recently, where sentiment is heading, why a priority ranks where it does. Answers come back with the source rows attached.

How is this different from analytics?

Q2

Analytics tells you what happened inside your product. Intelligence tells you what your customers are saying and what to do about it — and connects it to the accounts, specs and outcomes behind each signal.

What is the product intelligence graph?

Q3

The accumulating record of every customer who asked, every signal they sent, every priority it shaped, every spec it produced and every outcome that shipped. It’s the asset that compounds — the longer Circuit runs, the more it knows.

How does Circuit learn?

Q4

From outcomes, not just inputs. Every shipped, parked or deferred brief, every correction you make, every theme you rename feeds back in — so what surfaces next matches how your team decides.

Does it work if I only use part of Circuit?

Q5

Yes, but the graph is more useful the more of the loop runs through it. Discovery fills it with voice, Delivery records what shipped, Intelligence is where it compounds.

Intelligence is on all plans.
See pricing →

The system that gets sharper as you ship.