"We can't roll this out to the team without single sign-on."
⚙ SAML/SSO Fernwood & Co · $5,000/mo
Linked to 1 feature · 1 account · counted in Demand below · Example data
Product · Insights & Prioritization
Feedback in. Priorities out.
Every request, review, survey answer, and support thread lands in one feed — linked to the feature it's about and the customer who said it. Then the roadmap argument ends: features rank by requests and the revenue behind them, scored in the framework your team already speaks.
Every source named on this page is live today, with real sync.
AIOInsights
AI that earns its seat — with receipts
The product copilot you open with ⌘I from anywhere. Click through what it actually does — every answer cited to your own data.
A copilot grounded in your product
Ask a product question and get an answer with citations to your own records.
- Every cited answer links the records it read
- Reads the same spine — feedback, usage, revenue
Simple questions, zero token bill
- Revenue, demand and open work compute from your records
- No model call, no hallucination, instant
Invest, fix or deprecate
- A verdict on every feature, argued from usage
- Demand weighed by revenue at stake, not raw votes
Meetings write their own tasks
- Calls transcribe themselves
- Action items land on your board as drafted tasks
Example data · grounded in your product
One feed
All of it. One place. No tabs.
Feature requests, app-store reviews, survey answers, research notes, design comments, community threads, error reports, support chats — unified into one feed the moment a source is connected.
-
Canny · Productboard · Featurebase
-
Typeform · Dovetail · Notion
-
App Store · Google Play
-
Discord
-
Support chat · Manual capture
Capture anything by hand. Heard it in a call? Add it as an insight in seconds — same feed, same links, same scoring.
Chat becomes feedback. Threads from the support widget land on the feed as insights — not in a separate inbox silo.
Webhooks out. Every captured insight can fire an outbound webhook, so the rest of your stack reacts to new signals.
The feed fills per connector you switch on. No email-forwarding channel yet — feedback arrives via connectors, the chat widget, or manual capture.
Linked, not piled
Every insight knows its feature — and its customer.
A feed you can't act on is a junk drawer. Here, each insight links to the feature it's about and the account that said it — so feedback carries revenue, and revenue carries into every ranking on this page.
- ✓Tag any insight with a customer account — their plan and revenue come with it.
- ✓Link insights to features, and demand accumulates where decisions happen.
- ✓The same links surface on the customer's 360 page — feedback next to what they pay.
Demand
Ranked by who's asking — and what they pay.
The Demand view lists every feature with two numbers next to it: how many customers asked, and the revenue those customers represent. The loudest request and the most valuable request are rarely the same row.
-
Requests, counted
Every linked insight increments the feature it points at. No more re-reading threads to remember who wanted what.
-
Revenue, summed
Linked accounts bring their subscriptions. A feature's demand line reads in dollars, not just votes.
-
ROI, per feature
Demand over effort — a clear return figure on each row, so the trade-off is visible before the meeting starts.
Score it your way
Five frameworks. Your call, per product.
Prioritization stops being a vibe when the scoring is explicit. Pick the framework each product runs on — the demand and revenue data underneath stays the same.
- RICE
Reach × Impact × Confidence ÷ Effort. Reach defaults from revenue-weighted demand, so the math starts from real asks.
- WSJF
Weighted Shortest Job First — cost of delay over job size, for teams that ship in flow.
- Value-Effort
The classic 2×2, with scores instead of sticky notes. Quick wins surface themselves.
- MoSCoW
Must / Should / Could / Won't — when the conversation is scope, not sequence.
- Kano
Basics, performance, delighters — score how a feature lands, not just how loud the ask is.
- PER PRODUCT
Set in product settings, next to your methodology. A B2B product can run WSJF while the consumer app runs Kano — same workspace.
AI on the feed
AI that tidies the data and argues the call.
Two real capabilities, grounded in your records — no theatre. One keeps your feature taxonomy clean; the other gives every feature a recommendation you can interrogate.
Three names, one feature. Merged.
When your event stream reveals the same feature under different keys, the AI suggests a canonical name and merges them. Now demand and usage count toward one row, not three.
export-csv · csv_export · exportCSV
↳ merge suggested
CSV export — one feature, one history
From your product events · Example data
An invest / fix / deprecate / watch verdict on every feature.
The AI reads each feature's usage, signals, and open work, then returns a confidence-scored recommendation — argued from the numbers, not from whoever spoke last.
SAML/SSOINVEST · 86%
Session replayWATCH · 71%
Legacy importerDEPRECATE · 74%
From usage + signals + open work · Example data
- The feed fills per connector — connect a source and its history syncs in; nothing pretends to be there before that.
- No email channel yet. Feedback arrives through connectors, the chat widget, and manual capture — forwarding an email into the feed isn't built.
- Support chat is human-answered. Threads land as insights automatically, but no bot replies to your customers.
Early access
Stop arguing in roadmap meetings.
Connect a feedback source and Stripe, and within the walkthrough you'll see your own demand ranked by revenue — scored in your framework.
FAQ
Questions, answered
Which feedback sources can I connect?
Canny, Productboard and Featurebase for feature requests; Typeform, Dovetail and Notion for surveys and research; App Store and Google Play reviews; Discord; plus support chat and manual capture — all flowing into one feed.
How does revenue-weighted prioritization work?
Every piece of feedback links to the account it came from, so demand is ranked by the revenue behind the ask, not just the number of votes. The loudest request and the most valuable one stop being the same thing.
Which prioritization frameworks are supported?
RICE, WSJF, Value-Effort, MoSCoW and Kano, chosen per product. In RICE, Reach even defaults from revenue-weighted demand, so the math starts from real asks.
Does feedback link back to features and accounts?
Yes — each item links to the feature it concerns and the account it came from, so you can trace a shipped feature back to the customers (and revenue) that asked for it.
How is this different from a standalone feedback tool?
Standalone tools capture feedback in a silo. Here it's on the same spine as your accounts, revenue and roadmap, so prioritization runs on real customer value — connected, not consolidated.