Customer Facing Roadmap Template
Three documents and two sheets that audit what your team actually told customers against the confidence tier each feature held that day.
Free download · No account needed
Internal to External Mapping
Before a Tier Is Assigned
Every open roadmap item, ready for its status, its tier, and whether a signed contract backs it.
| Feature | |
|---|---|
| Internal Status | |
| Confidence Tier | |
| Contractually Committed | |
| Allowed External Language |
Committed is never assigned by confidence alone. Only a signed date, in writing, earns that tier.
Page one for customer-facing roadmaps agrees on the shape: hedge with High, Medium and Exploratory confidence labels, add a safe-harbor disclaimer, avoid a specific date unless it is truly locked. That system protects a written roadmap page. It does nothing for a QBR call, a sales deck slide, or a hallway comment, the channels where most actual promises get made. A specific, dated promise can become part of a contract's basis of the bargain whether or not anyone meant it that way, and a scheme that only governs one page never checks the other three.
Marlstone, a fictional B2B analytics company, splits 22 open roadmap items into four tiers: one Committed, backed by a signed side letter naming a customer and a date, 9 High, 7 Medium, and 5 Exploratory. Commitment Register audits 41 statements logged across two quarters against the tier each feature held that day. Nine overstated their tier, most often a Medium-tier item given a specific ship date in a QBR call, and four of those nine have already slipped without a correction.
All four unresolved slips sit in front of a customer now inside their own renewal window, $612,000 of combined ARR renewing within eleven weeks. Delay Comms Template exists for exactly this moment: log the exact words that were said before drafting anything new, and never restate an old date with a fresh coat of confidence. A product launch creates the next batch of roadmap promises the moment it ships, and the onboarding content that gets a new account to value is where those promises get tested first.
What's in the pack
External Roadmap
The actual customer-facing page, written using only the language each item's tier allows, with contractually committed items left off entirely.
Commitment Guidance
The four tiers and why Committed is a contract rather than a confidence level, with the one legal citation worth knowing before promising a date.
Delay Comms Template
The internal alert for the day a slip is confirmed, and the customer message that follows once there is an honest answer to give.
Internal to External Mapping
Every open item's real status, its tier, whether a contract backs it, and the exact words that tier allows someone to say out loud.
Commitment Register
Every external statement logged with its date and channel, audited against the tier that was actually true that day, not the tier it is today.
How to use it
- 1
Send your roadmap and your contracts, or take it blank
Open the pack in River and send your backlog export plus any signed agreements naming a feature and date, or download the Word documents and CSV sheets and tier it yourself.
- 2
Every item gets a tier, and Committed means a contract
River tiers each item by engineering status, then checks it against any signed order form or side letter, since only a contract earns the Committed tier.
- 3
Every statement gets audited against its tier that day
Send whatever record exists of what was said to customers, and River checks the language against the tier that item actually held on that date, not today's tier.
- 4
A slip gets a delay message before it gets a repeat
Once a promised window closes without a ship, Delay Comms Template drafts the internal alert first, so the next customer conversation corrects the record instead of restating it.
Frequently asked questions
Is this template free?
Yes, with no account, no card and no email gate on the download. Edit with AI is the optional half: send River your own roadmap and any signed commitments, and it builds your own tier mapping and audits your own statements. Every pack sits in the template library.
What format are the downloaded files?
Three Word documents and two CSV sheets, in a zip. The documents open in Word, Pages and Google Docs. The sheets open in Excel, Numbers and Sheets, as real spreadsheets rather than tables flattened into a page.
Why does a verbal QBR promise matter if nothing was signed?
Because a signature is not what creates the risk. Under UCC 2-313, a specific affirmation of fact or promise about goods can become part of the basis of a bargain without anyone using the word warrant or intending to make one. A dated promise said out loud to close a renewal carries that same shape.
Isn't a confidence-tier system enough on its own?
It is most of the job, and this pack keeps the four tiers rather than inventing new ones. What a tier scheme alone will not catch is drift: a rep using stronger language than an item's tier allows in a live call, which is exactly what produced 9 of 41 overstated statements on this pack's own worked register.
Is this the same as the pricing change communication plan?
No. The pricing and packaging launch pack is for changing a number on accounts you already have. This pack is for what gets said about a feature before it ships, to any customer, in any channel, well before a price is involved.
What does Edit with AI actually do?
It installs this pack as a private workspace and asks for your roadmap export and any signed commitments. It tiers every item, and once you share what has actually been said to customers, it audits that language against the tier each item held on the day it was said.
Find out what your team already promised
Send your roadmap export and any signed commitments. River tiers every item, then audits what was actually said to customers against the tier it held that day.
Edit with AI