69 — Product Roadmap Story
Status: CANONICAL · Commercial OS
Owner: Founder (product)
Last verified: 2026-07-21
Truth source: docs/STRATEGIC_BUILD_PLAN.md (execution sequencing) — this document is how we talk about the roadmap externally, and the rules for doing so safely.
Purpose
The roadmap as narrative: what we tell customers, prospects, analysts, and investors about where the product goes — themed, honest, and commitment-disciplined. A startup roadmap conversation is a trust exercise; this document keeps us trustworthy.
Target audience: Sales/CS (roadmap questions in deals), founder (briefings), analysts and Enterprise buyers (under NDA).
1. The Roadmap Grammar (themes, not features; sequence, not dates)
Public roadmap talk uses four standing themes with a strict now / next / later grammar — never dated feature lists (dates we miss cost trust; themes we advance build it):
| Theme | Now (shipping/hardening) | Next | Later |
|---|---|---|---|
| Deeper benches (the wedge, perfected) | CS workbench end-to-end on HubSpot; signal quality iteration (v1 noisy → v4 good, said openly) | Salesforce parity; meeting/QBR prep depth | Vertical bench variants |
| More benches (the expansion architecture 46 V3) | Sales + RevOps benches in design-partner use | Exec bench; Finance/Service compositions | Custom bench composition tooling |
| Deeper trust (the governance lead, extended) | TruthLayer + approval lifecycle GA-hard; audit polish | SSO/SCIM, policy customization (Enterprise tier 30); SOC 2 milestones (42 §3) | Region pinning; advanced policy authoring |
| Wider fabric (connected capability) | 70+ connectors; governed writebacks on the wedge stack | Marketplace listings (49); handoff adapters (n8n/Zapier) | IW-Continuity-Bridge GA — gated by distribution doctrine, stated exactly that way |
The narrative through-line (say it in every roadmap conversation): "Everything on this roadmap deepens one loop — humans and Twins doing governed work over owned truth. We don't add adjacent products; we make the loop wider and deeper." This is also the internal triage test (44 §5 feedback routing): a request that doesn't deepen the loop is a no, kindly.
2. Commitment Discipline (the rules that keep trust)
- Three tiers of language, used precisely: shipped (demo it) · building (in design-partner hands, honest state) · exploring (no commitment implied — say "exploring").
- Dates only in contracts, only for items we control (32 §4 / 43): scoped Enterprise commitments, nothing else.
- No roadmap promises to close a deal. A deal that needs a promised feature is a deal at the wrong time — offer the design-partner path instead (influence, not promises).
- The public changelog is the roadmap's receipt: launches per PMM tiering (20 §3); build-logs tell the honest journey (56 T4).
- Roadmap regret protocol: when we kill or delay something we discussed, affected customers hear it from us first, with the why. (47 no-surprise rule applies to product too.)
3. Audience Renderings
| Audience | What they get |
|---|---|
| Prospect (in-deal) | The themes table verbatim + "which theme matters most to you?" (discovery, not promising) |
| Customer (QBR) | Themes + their requests' honest status + you-said-we-shipped notes (44 §5) |
| Enterprise buyer | NDA roadmap session: next-tier depth on Deeper Trust theme; contractual items separated explicitly |
| Analyst (66) | Themes + the honest slide (what's unproven) — candor is the AR strategy |
| Investor (67 §8) | Themes mapped to milestones the raise buys; the build plan's 180-day spine |
KPIs: zero missed public date commitments (by having ~zero public dates) · roadmap-promise deals = 0 · you-said-we-shipped notes delivered each quarter to every design partner · theme advancement demonstrated in every QBR cycle.
Related: 20 PMM Guide · 44 CS Playbook · 42 Security FAQ · Strategic Build Plan: ../../STRATEGIC_BUILD_PLAN.md