What’s shipping now, next, and later.
A public, opinionated roadmap. Items in Now are committed for the current quarter. Items in Next are likely to ship in the following quarter. Items in Later are on the roadmap but not yet committed — they may move, change shape, or be replaced by something better. We update this page when reality changes, and we say so when items slip. The companion log of what already shipped lives in the changelog.
Three columns. Confidence drops left to right.
Each card includes the customer signal that surfaced it. Confidence is our best read of whether the item is going to ship as described, not a promise.
- Frame-aware search
Search by what was on screen, not just what was said. Run a query like “the frame where the legacy admin tool was on screen” and jump straight to the timestamp.
High·12 customer interviews; voted #1 in Q1 trust portal poll. - Conversation-aware Slack digests
Channel-routed digests that respect quiet hours, group artifacts by team, and summarise the day’s decisions instead of dumping every push.
High·Replaces the 0.8.3 first-pass implementation; design review complete. - SOC 2 Type II audit window
Observation period closes mid-Q3. Type II report available under NDA in early Q4. Continuous control monitoring already in production.
High·Tracked publicly on /compliance; auditor engaged.
- Live transcription for ongoing meetings
Connect a live meeting (Zoom, Meet, Teams) and get the evidence layer building in real time. Useful for sales and CS playback during a call.
Medium·Prototype validated in two design partner workspaces; needs work on speaker stability under packet loss. - Structured outputs for CRMs
Native pushes to Salesforce and HubSpot — call summaries become typed activities, not unstructured notes. Maps to your existing object model.
Medium·Design partner enablement Q3; GA target Q4. - Public webhooks v2
Per-tenant fair-share, exponential backoff with jitter (already shipped internally), now exposed with a richer event taxonomy and a verified signature header.
High·Spec drafted; backwards-compatible with v1.
- Multi-recording synthesis
Ask a question across an entire research project, sales quarter, or release cycle. Citations span recordings; provenance preserved per claim.
Exploring·Architecture review in progress; storage cost model is the open question. - Customer-managed encryption keys (BYOK)
Bring your own KMS-managed root key for tenant data. For Enterprise customers with strict crypto governance.
Exploring·Two Enterprise design partners have signed up to co-design. - Workflow rules engine
If a recording produces an artifact tagged X, push to Y, notify Z, and create a calendar follow-up. No-code, in-product.
Considering·Asked for in 30+ tickets; prioritisation pending. - Mobile capture app
Quick voice memo + screenshot capture on iOS / Android, ingested into a workspace as a lightweight recording.
Considering·Useful for field research and on-call ops; not on a current quarter plan.
The last five releases, at a glance.
Each links to the full entry on the changelog with tags, breaking-change details, and rollout notes.
Things we’re explicitly not building.
A roadmap is also the things you say no to. Each item below has had real customer pull at some point, and we’ve declined for a stated reason.
We won’t replace your inbox with a different kind of unread. Citesvue surfaces evidence in the tools you already use; one more digest channel is not the answer.
We won’t score participants by talk-time, sentiment, or “engagement.” Recordings are evidence, not surveillance.
We won’t ship an ungrounded answer mode. If the copilot can’t point to evidence, it says so. This is non-negotiable for the product to mean what it says.
We won’t monetise Citesvue with advertising or sale of customer data. The business model is subscriptions, period.
Four principles that decide what goes where.
- 01Honest dates over heroic ones
Quarters not months. Items move when reality moves; we say so when they do.
- 02Evidence drives priority
We weight signals from interviews, support tickets, and design partners over activity metrics. The loudest customer is rarely the most representative.
- 03Trust ships at the same cadence as features
Compliance, security, and reliability work appears on this roadmap alongside product features. They are products too.
- 04Public, not exhaustive
This page covers the work most likely to matter to customers. Internal platform work, refactors, and continuous improvements are not all listed.
Tell us where the gap is. Real signal moves items left.
The clearest votes come from customers who tell us the workflow they’re trying to run, the friction they hit, and what would change in their week if it were solved. We read every one.