Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Product Marketing › Sales Enablement

Talking About the Roadmap With Buyers and Customers

How sales and marketing should talk about the roadmap: what to share and when, who may commit, the roadmap slide, public roadmaps and claims that stay true.
Guideintermediate11 min readUpdated

Why the roadmap is the riskiest slide in the deck

Every other slide in a sales deck describes something that exists and can be shown. The roadmap describes things that do not exist yet, some of which never will. It is also the slide buyers care about most in a competitive deal: when a competitor has a capability the product lacks, the roadmap is where the seller turns, and the competitive battlecards guide shows a battlecard answering a gap with a roadmap date approved by product, which is the safe version of that move.

The unsafe version is familiar. A seller under pressure says a feature is "coming this quarter", or shows a slide from a product planning meeting, or agrees in an email that an integration "will be there by the time you go live". None of it was approved, and nobody outside the deal knows it was said. Months later the customer asks where the feature is, the account manager has no idea what was promised, and the renewal starts from a broken commitment. The product marketing pillar names the root of the problem from the other side: a feature described before it is finished sets expectations the release cannot meet.

The rule that keeps this under control is the site's rule for claims. The messaging hierarchy and proof points guide records that the Advertising Standards Authority's codes require objective claims to be capable of substantiation before they are made, and that the FTC's business guidance expects advertisers to hold a reasonable basis for objective claims before publishing them. It also lists claims about what a product will achieve for a buyer among the usual trouble spots. A statement that a product does something, or will do it by a date, is an objective claim. So planned work is never presented as available now, a date is given only when the business has a basis for it, and adverts and campaign pages never sell capabilities that have not been released. This is educational guidance, not legal advice; anything commercially significant goes through whoever handles compliance.

What can be shared, and with what confidence

The most useful single change a business can make is to label every roadmap item by how confident it is, and to use the same labels everywhere: in the sales slide, in proposals, at customer events and on any public roadmap. The labels below are a working convention many teams use in some form, not a standard.

LabelWhat it meansWhat a seller may sayDates
ReleasedAvailable now, to the plans and regions stated"You can use this today", with a demonstrationNot needed
CommittedApproved, resourced and scheduled by product management"This is scheduled for" the approved period, with the caveat that schedules can changeOnly the approved period, never a narrower one
PlannedIntended, but not yet scheduled or resourced"We plan to work on this; it is not scheduled yet"None
ExploringA problem the team is researching, with no decision to build"We are looking at this problem and would value your view"None

The labels do two jobs. They tell the buyer how much weight to put on each item, which is honest and, in practice, more persuasive than an undifferentiated list. And they tell the seller what they may say, so a seller who would like a planned item to sound committed has to ask for it to be relabelled rather than quietly upgrading it in the call.

Depth varies by audience, and by role within the buying committee. A prospect early in a deal usually needs the direction: the problems the product is moving towards and a few committed items relevant to them. A customer at renewal needs more detail on what affects them. A member of a customer advisory board may see items in the exploring column, shared in confidence, because their job is to advise on them. And there are always items that are not shared outside the company at all, such as anything that would reveal an unannounced launch or a competitive response before the launch plan is ready for it.

Who may commit, and to what

Most roadmap trouble comes from unclear authority rather than bad intent. The fix is to write down who decides each kind of roadmap statement, using the RACI matrix framework: each decision in a row, the roles across the top, and exactly one accountable role per row.

DecisionResponsibleAccountableConsultedInformed
What is on the roadmap and its labelProduct managersHead of productProduct marketing, sales leadershipAll customer-facing teams
What the roadmap slide and talk track sayProduct marketingHead of product marketingProduct managementSales, customer success
A date or commitment for a specific dealAccount executive (request)Head of productSales leadership, whoever approves commercial termsAccount manager, customer success
A roadmap statement in a proposal or tenderBid or proposal ownerHead of productProduct marketing, whoever approves commercial termsAccount team
Telling customers about a slipProduct marketing and account managersHead of product marketingProduct managementSupport

The roles will differ in each business; the principle is that a seller never has to guess. If a buyer asks for something beyond the approved slide, the seller says what is known, says they will check, and uses the request route. Product management answers quickly, either with an approved statement or with a clear no. A slow answer pushes sellers back to improvising.

The roadmap slide and its talk track

Give sellers one approved roadmap slide, owned by product marketing and refreshed whenever the roadmap changes, and retire every other version. The sales content and training guide covers keeping sales assets current and training sellers to use them; the roadmap slide is the asset where an old version does the most harm, so it carries a visible date and an expiry.

A good roadmap slide is organised around the customer's problems rather than a list of feature names, with each item labelled released, committed, planned or exploring. The value pillars in the messaging hierarchy are a natural structure: what the product does for each pillar now, and where it is heading. That keeps the roadmap telling the same story as the rest of the deck, rather than becoming a catalogue.

The talk track matters as much as the slide. It opens by saying how the labels work and that plans change, explains the direction before any item, answers the obvious questions for each committed item, and says plainly what is not on the roadmap when a buyer asks about something the business has decided not to build. Practise it, including the hard questions: "Can you guarantee it by our go-live date?", "Will you put that in writing?" and "Your competitor already has this; why should we wait?" A seller who has rehearsed those answers is less likely to promise something to get past them.

Keep unreleased capabilities out of the marketing that runs beside the deal. Adverts, landing pages, campaign emails and comparison and alternatives pages, whose claims have to be fair, checkable and kept current, describe only what is released. A comparison that counts a planned feature as a tick is a claim the business cannot support.

Future capability in proposals, tenders and contracts

Spoken roadmap statements fade; written ones do not. A proposal, a response to a request for proposal, a security questionnaire or a contract schedule that says a capability will exist by a date is a document the buyer will keep and may rely on. The one-way and two-way doors framework sorts decisions by how hard they are to undo: a remark in a meeting can be corrected in the next email, but a written commitment in a signed document is a one-way door, and deserves the care that goes with one.

Three habits keep written roadmap statements under control:

  • Answer from the library. The late-stage deal content guide builds tender and procurement answers from a library of approved answers. Add approved roadmap wording to that library, labelled and dated, so that bid teams reuse it rather than writing their own.
  • Answer the question asked. If a requirement asks whether the product does something today, and it does not, say so, and add the approved roadmap statement separately if there is one. Never let a planned capability read as a current one.
  • Route anything new. A roadmap statement the library does not cover goes through the request route to product management and to whoever approves commercial terms, before it is written.

Whether a written roadmap statement creates an obligation, and what happens if it is not met, depends on the contract and the law that governs it. This guide does not cover contract law. Check the contract terms and take legal advice before any roadmap commitment is written into one.

Public roadmaps and customer forums

Some businesses publish a roadmap on their website or share one in a customer community; others keep it entirely private. Either can work. A public roadmap shows direction, invites feedback and saves sellers from repeating the same answers; it is also read by competitors, and many readers treat every item on it as a promise.

If a roadmap is public, it follows the same rules as the sales slide: the same confidence labels, no dates for anything not committed, and updates in the open when items move, change or are dropped. An item that silently disappears is noticed by the customers who wanted it, and the change is worse for being discovered.

Customer events are where most customers hear the roadmap in person. The roundtables and customer events guide gives a user group a roadmap update and an advisory session roadmap input; the same labels apply to both, and the presenter is usually from product management with product marketing preparing the material. Requests raised at these events go into the product team's intake like any other feedback, with the customer told what happens next. The tutorial on handling feature requests from sales and customers builds that intake, from recording the job behind each request to telling requesters when it ships or will not be built.

When a date slips

Committed dates slip; what matters is how the business handles it. The principle comes from the guide to communicating a price change: customers who are affected hear early, in plain words, with the reason and their options, and the people who manage their accounts hear first.

When a committed item slips, product management tells product marketing and sales leadership straight away, with the new expected period and the reason. Product marketing updates the roadmap slide, the library answers and any public roadmap. Then the customers who were told about the item, especially those whose deal or renewal depended on it, hear from their account manager before they discover it: what has changed, why, the new expected period, and what the business can offer in the meantime. Where the item was in a contract, the contract governs the conversation and whoever approves commercial terms is involved before anything is said.

Track roadmap commitments by account so that this is possible. A record of which customers were told what, and by whom, turns a slip from a scramble into a list of calls. It also feeds renewal planning: the expansion and renewal marketing guide covers supporting renewals, and an account whose promised capability arrived late is one to watch, since unmet roadmap promises can show up later in the churn rate. Read win rate in deals where a roadmap item was a deciding factor alongside how often those items shipped as described, because winning on promises that are not kept moves the loss to renewal.

A warehouse software tidies its roadmap talk (illustrative)

Illustrative example — not a real result

Jorvacca Warehouse Software introduces confidence labels

Jorvacca Warehouse Software, an invented warehouse management software, found during a review of 40 recent proposals that 17 quoted a delivery quarter for at least one feature product management had not scheduled, and that sellers were using 6 different versions of the roadmap slide. Product marketing introduced four labels (released, committed, planned and exploring), built one roadmap slide organised around its three value pillars, and wrote a talk track with answers to the five questions sellers found hardest. A RACI table made the head of product accountable for any date in a proposal, and approved roadmap wording was added to the tender answer library. When a committed integration with a shipping carrier slipped by a quarter, the commitments record showed 11 customers had been told about it; each heard from their account manager within a week, before the public roadmap was updated. Over the next two quarters, proposals quoting unapproved dates fell to 1 of 38, and 10 of the 11 customers told about the slip renewed.

Common mistakes

  • Presenting planned work as current. A capability that is not released is never shown or described as available, in a call, a proposal or an advert.
  • One undifferentiated list. Without confidence labels, buyers read every item as a promise and sellers upgrade items to win deals.
  • Many versions of the slide. Old roadmap slides survive in sellers' folders; keep one, dated, and retire the rest.
  • Dates nobody approved. A seller who gives a date product management has not agreed is making a commitment on the business's behalf.
  • Writing commitments into documents casually. Proposals, tenders and contracts are one-way doors; route roadmap statements through product management and take legal advice on contract terms.
  • Selling unreleased features in marketing. Adverts, landing pages and comparison pages describe what exists.
  • Letting customers discover a slip. The customers told about an item hear about its delay first, from their account manager.
  • No record of what was promised. Without one, nobody can tell the right customers when a date moves.

Frequently asked questions

Should salespeople share the product roadmap with prospects?

Yes, within limits set in advance. Buyers reasonably want to know where a product is heading, and a well-labelled roadmap can show that the business understands their problems. What should be shared is the approved roadmap slide, with each item labelled by how confident the business is, and nothing beyond it without product management's agreement. Planned work is never presented as available now, and no seller gives a delivery date that product management has not approved.

Can a planned feature appear in a proposal or a contract?

Only through an agreed route. A statement in a proposal, a tender answer or a contract is harder to undo than anything said in a meeting, so it goes through product management and whoever approves commercial terms before it is written. Whether such a statement creates an obligation depends on the contract and the law that applies to it, which this guide does not cover; check the contract terms and take legal advice.

Should a business publish a public roadmap?

It is a choice with costs and benefits rather than a rule. A public roadmap shows customers and prospects the direction and invites feedback, but it is read as a promise by many people and is seen by competitors. If one is published, it uses the same confidence labels as the sales roadmap, avoids dates for anything not committed, and is kept current, with items that change or are dropped updated in the open.

Terms used on this page

Frameworks

Where this page is used

Also related

Sources

  1. Advertising Standards Authority — ASA
  2. FTC business guidance — Federal Trade Commission

Related