{"slug":"strategy/business-strategy/69-product-roadmap-story","title":"69 — Product Roadmap Story","section":"strategy","sectionLabel":"Strategy","status":"unclassified","type":"document","path":"strategy/business-strategy/69-product-roadmap-story.mdx","bytes":6940,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\nStatus: CANONICAL · Commercial OS\nOwner: Founder (product)\nLast verified: 2026-07-21\nTruth 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.\n\n---\n\n## Purpose\n\nThe 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.\n\n**Target audience:** Sales/CS (roadmap questions in deals), founder (briefings), analysts and Enterprise buyers (under NDA).\n\n---\n\n## 1. The Roadmap Grammar (themes, not features; sequence, not dates)\n\nPublic 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):\n\n| Theme                                                                                                  | Now (shipping/hardening)                                                                       | Next                                                                                                                                                          | Later                                                                               |\n| ------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- |\n| **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                                                             |\n| **More benches** (the expansion architecture [46 V3](../08-customer-success/46-expansion-strategy.md)) | Sales + RevOps benches in design-partner use                                                   | Exec bench; Finance/Service compositions                                                                                                                      | Custom bench composition tooling                                                    |\n| **Deeper trust** (the governance lead, extended)                                                       | TruthLayer + approval lifecycle GA-hard; audit polish                                          | SSO/SCIM, policy customization (Enterprise tier [30](../05-value-pricing/30-pricing-strategy.md)); SOC 2 milestones ([42 §3](../07-sales/42-security-faq.md)) | Region pinning; advanced policy authoring                                           |\n| **Wider fabric** (connected capability)                                                                | 70+ connectors; governed writebacks on the wedge stack                                         | Marketplace listings ([49](../09-gtm/49-marketplace-strategy.md)); handoff adapters (n8n/Zapier)                                                              | IW-Continuity-Bridge GA — _gated by distribution doctrine, stated exactly that way_ |\n\n**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](../08-customer-success/44-customer-success-playbook.md) feedback routing): a request that doesn't deepen the loop is a no, kindly.\n\n## 2. Commitment Discipline (the rules that keep trust)\n\n1. **Three tiers of language, used precisely:** _shipped_ (demo it) · _building_ (in design-partner hands, honest state) · _exploring_ (no commitment implied — say \"exploring\").\n2. **Dates only in contracts, only for items we control** ([32 §4 / 43](../05-value-pricing/32-licensing-strategy.md)): scoped Enterprise commitments, nothing else.\n3. **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).\n4. **The public changelog is the roadmap's receipt:** launches per PMM tiering ([20 §3](../04-product-marketing/20-product-marketing-guide.md)); build-logs tell the honest journey ([56 T4](../11-marketing/56-content-strategy.md)).\n5. **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](../08-customer-success/47-renewal-strategy.md) applies to product too.)\n\n## 3. Audience Renderings\n\n| Audience                                     | What they get                                                                                                                        |\n| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |\n| Prospect (in-deal)                           | The themes table verbatim + \"which theme matters most to you?\" (discovery, not promising)                                            |\n| Customer (QBR)                               | Themes + their requests' honest status + you-said-we-shipped notes ([44 §5](../08-customer-success/44-customer-success-playbook.md)) |\n| Enterprise buyer                             | NDA roadmap session: next-tier depth on Deeper Trust theme; contractual items separated explicitly                                   |\n| Analyst ([66](66-analyst-relations.md))      | Themes + the honest slide (what's unproven) — candor is the AR strategy                                                              |\n| Investor ([67 §8](67-investor-narrative.md)) | Themes mapped to milestones the raise buys; the build plan's 180-day spine                                                           |\n\n**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.\n\n---\n\n**Related:** [20 PMM Guide](../04-product-marketing/20-product-marketing-guide.md) · [44 CS Playbook](../08-customer-success/44-customer-success-playbook.md) · [42 Security FAQ](../07-sales/42-security-faq.md) · Strategic Build Plan: `../../STRATEGIC_BUILD_PLAN.md`\n"}