---
title: "How Do I Communicate the Roadmap to Customers Without Dates?"
description: "Communicate the roadmap to customers in three tiers and never in dates. The four commitments to refuse, the message when an item is dropped, two numbers to watch."
topic: "Playbooks & Operations"
author: "Raj Bheda, Co-founder, GainTrace"
audience: "Customer Success Manager, Head of Customer Success"
published: 2026-09-18
modified: 2026-09-18
source: https://gaintrace.com/explore/playbooks/communicate-the-roadmap-to-customers
---

# How Do I Communicate the Roadmap to Customers Without Promising Dates?

*The forward-looking half of expectation setting*

**Short answer:** Communicate the roadmap to customers in three tiers and never in dates: shipped, committed this quarter, and direction only. Name the tier out loud every time, put it in the customer's thread the same day, and give one date, the day you will next bring news. Roadmap talk damages a renewal when a tier is skipped, not when the news is bad.

**Key takeaways**

- Three tiers carry every roadmap answer: shipped, committed this quarter, direction only. Say which tier an item sits in and the customer can plan without a ship date.
- The only date a CSM should ever give about the roadmap is the date of the next update, because that is the one date the CSM controls.
- Write the roadmap conversation back to the customer the same day, in your own words. In our review corpus the damage shows up months later, as a customer repeating a sentence a vendor no longer remembers saying.
- When an item is dropped, message every customer who was told about it before the release notes do, and name the replacement in the same message.
- Two numbers make this measurable: roadmap exposure, the share of account ARR resting on an unshipped item, and tier slip rate, the share of committed items that moved.

Communicate the roadmap to customers badly and nobody tells you for two quarters, until a renewal call opens with a feature the customer has been waiting for and nobody on your side remembers promising. The sentence that caused it was usually harmless at the time. Someone said a thing was coming, the customer wrote it down, and the two records drifted apart from that moment on.
This page is for the CSM or the Head of CS who fields roadmap questions every week and has been burned by an answer that aged badly. It gives the three tiers to speak in, the four commitments to refuse, the message to send when an item is dropped, and two numbers that tell you whether any of it is working on your own accounts.

## How much of the roadmap can a customer be told?

A customer can be told everything that has already shipped, the themes committed for the current quarter, and the direction beyond that, with no date attached to anything past the first group. The limit is not secrecy. The limit is certainty: you may share any item whose status you are willing to restate, in writing, to that customer every month until it ships or dies.

> **The next-news date:** The next-news date is the only date a CSM can safely give a customer about the roadmap: the day you will come back with news, not the day the feature ships. It costs nothing to keep, it sits entirely inside your control, and it turns an open question into a scheduled one. A customer holding a next-news date stops asking, and you stop guessing.

Roadmap talk is rare in public review text and lopsided when it appears. Of the 4,978 public reviews of customer success platforms in our corpus, 46 mention a roadmap (0.9%), and 30 of those 46 sentences sit in the reviewer's dislikes or problems field rather than the likes field. What those 30 describe is almost never anger about priorities. It is a customer holding a sentence they were given months earlier and checking it against what shipped.

> "Our CSM tells us new product enhancements are coming soon, and things like Gantt charts are on the roadmap."
>
> — Small-Business reviewer, public G2 review

That review carries 1.5 stars out of 5, and the sentence above is the reviewer's evidence. Nobody lied to them. A CSM said something true on the day, with no tier attached and no date to come back on, and the customer carried it for a year. Roadmap communication fails in that gap, not in the decision itself, which is why the fix is a naming habit rather than a policy about what is confidential.

> "I do feel that we talk about a lot of great things coming on roadmap, but slow to materialize and MVPs are not up to usability."
>
> — Mid-Market reviewer, public G2 review

## Which three tiers should I use to communicate the roadmap to customers?

Three tiers cover every roadmap question a customer can ask: shipped, committed, and direction. Each tier has a different level of evidence behind it, so each tier gets a different sentence, and the sentence names the tier out loud. A customer who hears the tier can decide whether to wait, build around it, or escalate, which is the only decision they were ever trying to make.

| Tier | What has to be true | Use when | The sentence |
| --- | --- | --- | --- |
| Shipped | Code is in production and this customer can turn it on today, on their plan, without a services project | The customer's problem is already solved and nobody told them | "That is live now. I can switch it on for you this week and walk your admin through it." |
| Committed | An owner, a written spec and engineering time booked inside the current quarter | The customer is deciding whether to wait for you or build around you | "It is committed for this quarter. I will come back on the 15th either way, and the same day if it moves." |
| Direction | A theme the company intends to invest in, with no spec, no owner and no booked time | The customer is asking where the product is going, usually inside a business review or a [renewal](/blog/saas-renewal-management) conversation | "That is the direction we are going. There is nothing built behind it yet, so plan as though it does not exist." |

> "I don't pretend to know what we will build six months from now. The next few weeks can be specific. The next quarter can have themes. Anything beyond that is direction, not a promise."
>
> — r/CustomerSuccess, 2026

That is a product manager describing the same three tiers from the inside, in a thread read by CSMs in 2026. The tiers are not a CS invention layered on top of product; they are the states the work is already in. The failure is translating all three into one customer-facing word, which is almost always "soon". A fourth state exists, the item you have decided against, and it needs its own conversation: [a feature request that will not be built](https://gaintrace.com/explore/playbooks/feature-request-that-will-not-be-built) covers that one.

## What do I say when a customer asks for a roadmap date?

Give the date you control instead of the date you do not: name the day you will next bring news about the roadmap item, and say plainly that the ship date is not yours to give. Most date questions are not requests for a date at all. The customer has a decision to make about their own plan, and a ship date is the shortcut they reached for.

1. **Name the tier before you answer anything.** "That one is in the direction tier for us" or "that is committed this quarter". Six words, said first, and the rest of the conversation runs on a shared footing.
2. **Ask what they will do with the answer.** "If it lands in March, what changes for you? If it lands in September?" The answer tells you whether they need a date or a decision, and the two need different help.
3. **Give the next-news date, not the ship date.** "I cannot give you a release date and I will not guess one. I will tell you where it stands on the 15th of every month until it ships or we drop it."
4. **Offer the bridge for the gap.** Name what they can do between now and then: a workaround, an integration, a services piece, or an export. A bridge with a cost beats a promise with none.
5. **Write it back to them the same day.** Three lines in the thread they already use: the item, the tier, the next-news date. Your version becomes the record both sides check against later.
6. **Put the next-news date in your own calendar with the account name on it.** A next-news date you miss is worse than the date you refused to give. Missing it twice teaches the customer that nothing you say about the roadmap has a clock on it.

> "The tempting move is to say "yes, that's on the roadmap" and hope product can catch up. But that gets ugly fast. The demo becomes half product, half promise."
>
> — r/startups, 2026

That founder is describing the pre-sale version of the same move, and the CS version is harder to spot because it arrives as generosity. A CSM under pressure hands over a date to make a tense call end well. The date costs nothing that day and everything in the quarter it is missed. [How do I stop sales from overpromising to customers](https://gaintrace.com/explore/onboarding/stop-sales-from-overpromising-to-customers) handles the pre-signature side; this page handles the calls you own after the deal.

## Which four commitments should never appear in a roadmap conversation?

Four commitments do the damage in roadmap conversations, and all four get made by accident by people trying to be helpful. Each one converts a company-level intention into a customer-level entitlement, and the customer is right to treat it that way. The replacement column below keeps the goodwill and drops the liability.

| What gets said | What the customer writes down | Say this instead |
| --- | --- | --- |
| "That is coming soon." | A quarter, usually the current one. Soon is read as a date by everyone who has ever been told it. | "That is in the direction tier. No build behind it yet, and I will tell you the day that changes." |
| "It is on the roadmap." | Someone is working on it now. The roadmap sounds like a queue with a front, and the customer assumes their item entered it. | "It is logged with the ARR behind it. It has not been picked up. Here is how I will know when it is." |
| "I will push for it." | A CSM with influence is now the owner of the outcome. The renewal conversation will treat your effort and the result as the same thing. | "I will put it in the next prioritisation round with your use case and the revenue attached, and send you what came back." |
| "We can build that for you." | A bespoke commitment, priced at nothing, owed to them specifically. Enterprise buyers escalate on this one first. | "That is a services scope, not a roadmap item. I can get it costed this week if you want the number." |

> "Don't get me wrong, I understand not all wishess will be fullfilled and we do not decide on the roadmap as customers."
>
> — Enterprise reviewer, public G2 review

Typos and all, that sentence is the most useful line in the roadmap half of our corpus, and it comes from a 2-star review. Customers do not expect to win the prioritisation argument. They expect to be told where they stand so they can plan. The four commitments above fail because each one implies the customer did win it, which sets up a grievance later out of a conversation that went well at the time.

## What do I tell customers when a roadmap item is dropped?

A dropped roadmap item needs a message from you before the customer notices its absence, and that message names what changed, why, and what they get instead. The order matters. A customer who hears it from you keeps a working relationship with a disappointing product; a customer who works it out for themselves has learned that your updates only carry good news.

| What changed | What you owe the customer | When | Who sends it |
| --- | --- | --- | --- |
| Cancelled: it will not be built | A named reason, the alternative you can offer, and an open door to argue the decision with product | Within five working days of the decision, before any release note or public log change | The CSM, by name, in the thread where the original promise was made |
| Deprioritised: pushed out of the committed tier | The tier change in plain words, the new next-news date, and what they should assume in the meantime | At the next-news date at the latest, sooner if they have a decision pending on it | The CSM, in the monthly update they already expect |
| Descoped: shipping, but smaller | What is in and what is out, checked against the use case they described when they asked | Before the release, so they are not surprised by a version that misses their case | The CSM, with the product manager copied if the customer wants to push back |
| Delayed: same scope, later | The new quarter and a note on whether the slip is one-off or a pattern at your company | At the next-news date. A delay does not need a same-day message | The CSM, or an automated product update if the account is in a digital tier |

> "How do you balance showing directionality, while managing expectations? What about times when roadmap changes and a customer was hoping for something that's no longer there?"
>
> — r/CustomerSuccess, 2025

**Before you mention an unshipped item to any customer**
- [ ] You can name the tier it sits in without checking with anyone.
- [ ] You know who owns it in product, by name.
- [ ] You have a next-news date and it is in your calendar against this account.
- [ ] You know the bridge: what the customer does between now and then.
- [ ] You know what happens to this account's renewal if the item never ships.
- [ ] You are willing to repeat the same sentence to this customer every month until it resolves.
- [ ] The item and its tier are written in the account record, not only in your head.
- [ ] If sales or support already told this customer something different, you have reconciled the two before you speak.

## How do I know the roadmap conversation is working on my accounts?

Two numbers make roadmap communication measurable: roadmap exposure and tier slip rate. No trustworthy public benchmark exists for either, and the figures circulating for roadmap or forecast accuracy come from consultancy posts with no survey, no sample and no method behind them, so measure your own and compare it only to your own last quarter.

**Roadmap exposure**

```
Roadmap exposure = ARR of accounts told an unshipped item is coming ÷ Total account ARR × 100
```

Where:
- Accounts told: any account where you, sales or support named an unshipped item in a call, an email or a deck, whether or not a date came with it
- Unshipped item: anything not in production for that customer today, including a feature that exists but is not enabled on their plan
- What good looks like: under 10% of account ARR, on our own working threshold. Above 25%, the upcoming renewals are carrying a product forecast, and one slipped quarter becomes a retention event

**Tier slip rate**

```
Tier slip rate = Items that moved to a weaker tier after a customer was told ÷ Items communicated in that tier × 100
```

Where:
- Moved to a weaker tier: committed down to direction, or direction down to cancelled. Movement the other way, direction up to committed, is not a slip
- Items communicated: count each item once per quarter, not once per customer, or one popular item will swamp the number
- What good looks like: under 20% for committed items, on our own working threshold. Above 40%, stop using the committed tier with customers until product forecasting improves

> **Worked example:** A 90-account portfolio carrying $2.4M ARR. Over one quarter the CSM named an unshipped item to 14 accounts holding $610,000 of ARR between them, so roadmap exposure is 610,000 ÷ 2,400,000 × 100 = 25%. Of the 9 items communicated as committed that quarter, 3 dropped back to direction and 1 was cancelled, so tier slip rate is 4 ÷ 9 × 100 = 44%. Read together, the two numbers say the wording of the conversation is not the problem: committed means nothing at this company yet. The CSM stops using the committed tier for a quarter, speaks only in shipped and direction, and exposure falls to 8%. These figures are illustrative; run both on your own accounts. If you want the revenue at stake behind the exposure number, the [cost of churn calculator](https://gaintrace.com/tools/cost-of-churn-calculator) will size it.

Size the stakes with a figure you can cite. Median gross revenue retention for private B2B SaaS was 91% in SaaS Capital's September 2025 retention brief, a median across more than 1,000 self-selected private B2B SaaS respondents. Gross revenue retention is revenue-weighted, so it says nothing about how many logos leave. What it does say is that around 9% of last year's revenue has to be won back before growth starts, and roadmap exposure tells you how much of next year's is sitting on something nobody has built yet.

## How does GainTrace keep roadmap commitments next to the account?

GainTrace reads the calls, emails and tickets on an account and keeps what was said about unshipped work attached to that account, so the sentence a CSM used in March is still findable in October when the renewal opens. [Triage](https://gaintrace.com/platform/triage) surfaces the accounts where an open commitment is sitting against a renewal date, and [renewal forecasting](https://gaintrace.com/solutions/renewal-forecasting) shows the ARR resting on items that have not shipped. Nobody has to keep a second spreadsheet of what was promised to whom.

## Frequently asked questions

### Can I show a customer our internal product roadmap?

Show a customer-facing version, never the internal board. The internal board carries ticket names, engineering estimates and competitor reasoning, and customers read estimates as dates. Publish three tiers instead: what shipped in the last quarter, what is committed for this quarter, and the themes beyond that with no timing at all. Same information, no implied entitlement, and it survives a screenshot landing in a procurement email.

### What do I say when a customer asks when a feature will ship?

Name the tier, refuse the ship date, and give the next-news date instead. "That is committed this quarter. I cannot give you a release date and I will not guess one, but I will tell you where it stands on the 15th of each month until it ships." Then ask what changes for them depending on timing, because the answer usually reveals they need a decision rather than a date.

### We told a customer something was coming and it got cut. What now?

Message them within five working days of the decision, before any release note or public changelog does it for you. Name what changed, give the real reason, and bring the alternative in the same message: a workaround, a services scope, an integration, or a partner. Offer a call with the product manager if they want to argue the decision. Then log the cancellation against the account so the renewal conversation is not a surprise.

### How much roadmap can I share with a customer under NDA?

An NDA changes what you may show, not what you may promise. Under NDA you can share the committed tier in more detail and name the themes behind the direction tier, which is worth doing with design partners and reference accounts. The tier language stays identical, because the risk was never disclosure. The risk is a customer planning their year around a quarter you cannot hold.

### Should the CSM or the product manager communicate the roadmap to customers?

The CSM owns the standing relationship and the next-news date; the product manager joins for the decisions the customer wants to argue. A CSM who hands every roadmap question to product teaches the customer to route around them, and a CSM who never brings product in ends up defending decisions they did not make with reasons they cannot give. One monthly update from the CSM, one product session per quarter for the accounts that ask.

### Is there a benchmark for how often roadmap commitments slip?

No trustworthy public benchmark exists for roadmap slip or renewal forecast accuracy. The ranges you will find quoted come from vendor and consultancy posts with no survey, no sample size and no stated method, several of them repeating each other in identical wording. Measure your own tier slip rate for two quarters and compare it to itself. Your own trailing number is more useful than any figure you can cite from elsewhere.

## How this was researched

We searched a corpus of 4,978 public G2 reviews of five customer success platforms, covering 29,027 sentences, for roadmap language: 46 reviews mention a roadmap (0.9%), 30 of them in the dislikes or problems field, and 9 use the phrase "on the roadmap" directly. We then searched 33,600 posts from r/CustomerSuccess, r/SaaS, r/sales and r/startups published between May 2024 and September 2026, of which 163 mention a roadmap (0.5%), and read the threads where CSMs and product managers describe the problem in their own words. The retention figure is SaaS Capital's September 2025 research brief, a median across more than 1,000 self-selected private B2B SaaS respondents. The three tiers, the four refused commitments, the next-news date, both formulas and the thresholds inside them are our own; the worked example uses illustrative figures.

## Sources

- [r/CustomerSuccess: CSMs, what is an effective strategy to communicate the roadmap with your customers?](https://reddit.com/r/CustomerSuccess/comments/1ommx8b/)
- [r/startups: How do you sell around a roadmap gap without promising something that doesn't exist?](https://reddit.com/r/startups/comments/1v06l6t/)
- [r/CustomerSuccess: I've worked in product for 10 years. I got better when I stopped doing most of what makes a PM look busy.](https://reddit.com/r/CustomerSuccess/comments/1vn6j4o/)
- [r/CustomerSuccess: CS folks, what do PMs do that drives you absolutely nuts?](https://reddit.com/r/CustomerSuccess/comments/1swcb0y/)
- [SaaS Capital, 2025 B2B SaaS Retention Benchmarks (Research Brief 32, September 2025)](https://www.saas-capital.com/wp-content/uploads/2025/09/RB32WS1-2025-B2B-SaaS-Retention-Benchmarks.pdf)

## Next steps

Pick one account this week, name the tier on every open item, and send them a next-news date. [Start free](https://app.gaintrace.com/auth/login) or [book a demo](https://gaintrace.com/booking).