The Roadmap in the Sales Room: Selling the Present

The most expensive feature I’ve ever seen shipped was promised in a sales call I wasn’t in. A prospect — large, logo-worthy, loud — said they’d sign if we committed to a custom approval workflow by end of quarter. The AE said yes, the CEO backed it, and the roadmap bent. The feature shipped six weeks late, consumed the quarter’s best engineers, and served exactly one customer — who churned fourteen months later anyway, for reasons that had nothing to do with approvals. The full price only became visible later: the two validated roadmap themes that got bumped, the second prospect who’d been told about those and went quiet, and the sales team’s updated belief — confirmed by experience — that the roadmap was negotiable if the deal was big enough. One yes, four costs, and only the first one was ever attributed to the deal.

The discipline that prevents this is a single sentence: in a sales room, the roadmap is evidence of trajectory, not a menu. Its job is to derisk the buyer’s future — to show that the product is going somewhere and that the vendor decides deliberately — never to become the thing being purchased, because a customer who buys your roadmap has bought something that doesn’t exist from a team that no longer controls it. This is the third post in the roadmap run: the build manual, then the investor room, and now the room where roadmap talk has the most immediate money attached and therefore the strongest gravitational pull on your priorities.

Sequence: the roadmap enters late or not at all

The sales conversation has an order, and the roadmap belongs at the end of it. Early calls are discovery — and genuinely so, not discovery-themed pitching. The same rules from the discovery post apply with the stakes raised: past behavior over hypotheticals, the prospect’s problem in the prospect’s words, and no leading the witness. What does their current process actually look like? What breaks? What have they already tried? A rep who can’t answer those three questions about a prospect isn’t ready to demo, let alone to discuss futures.

The demo, when it comes, sells the present product against the problem discovery surfaced — April Dunford’s Sales Pitch structure is the one I point teams at: establish the market context (your positioning, spoken aloud), the alternatives and their tradeoffs honestly stated, then your differentiated value against that map. The roadmap appears only after the present product has been judged sufficient — as a closing reassurance, directions not dates, themes not features. Shown early, a roadmap does something subtle and destructive: it reframes the entire evaluation from what you have to what you lack, and every subsequent question becomes a gap question. You handed the prospect the deficiency list yourself.

And enterprise buyers screenshot. Whatever roadmap artifact enters a procurement process will resurface in a renewal negotiation eighteen months later with commitments read into it that you never made. The sales-facing roadmap view — derived from the internal artifact like the investor view, never the artifact itself — contains themes, direction, and recent shipping velocity. No dates. The changelog of what you have shipped is more persuasive than any forward promise anyway, because it’s the only part that’s verifiable. Selling the future instead has a long and expensive record — the Osborne effect and its modern heirs is that record written out.

The three-tier answer

“Is X on the roadmap?” is the most common question in any technical sale, and winging it is how promises get born. The hands-on fix is a standard vocabulary, agreed between product and sales, with exactly three tiers:

1. Shipped or in flight — “yes, and here’s how it works.” Demo it or show the Now column. Nothing else counts as yes.
2. Committed direction — “it’s in our near-term plan; I can say this quarter-ish, and I won’t give you a date, because we don’t give dates we haven’t started.” Said plainly, this builds trust — buyers have been burned by vendor dates before, and the refusal reads as the discipline it is.
3. Exploring / not planned — “that’s in discovery” or, crucially, “no, and here’s why not.” The confident no is the most underrated sales move I know: “we’re built for X, not Y — if Y is the core need, we’re the wrong tool” loses deals you’d have lost anyway at renewal, and visibly raises the credibility of every yes you’ve said before it.

What makes the tiers work is that they map one-to-one onto the internal roadmap from the build post — tier one is the Now column, tier two is Next items marked validated, tier three is everything else. Sales isn’t improvising product truth; they’re reading a shared artifact aloud. That alignment, maintained in a monthly thirty-minute product-sales sync, is the actual mechanism; the vocabulary is just its interface.

When the commitment is genuinely on the table

Sometimes the ask is real: strategic account, reasonable request, deal-blocking. The discipline isn’t “never commit” — it’s pricing the commitment honestly before saying yes, against the four costs from the story up top: the displaced validated work, the precedent it sets with the sales team, the credibility spent if it slips, and the one-customer-feature risk. Three tests, in order:

• The segment test: would this serve the target segment from your strategy kernel, or this account only? A feature for the segment that one account happens to need first is a roadmap item arriving early — fine. A feature for one account is custom development, and should be priced, scoped, and contracted as exactly that, not smuggled through the roadmap.
• The evidence test: does the ask corroborate something discovery already suggested? The best sales asks are free discovery signal — a second, paying source for a hypothesis you were already tracking. Log every roadmap ask against the deal, segment, and problem it came from; reviewed monthly, that log is the highest-signal discovery input you own, and it feeds the roadmap review as learning, not as a queue.
• The contract test: if it goes in writing, it goes in as scope with acceptance criteria and its own price — never as a dated side-letter promise attached to a standard subscription. Side letters are where roadmaps go to be litigated.

The failure modes are the story in generalized form: the feature-promise treadmill (each promise teaches sales to extract the next, until the roadmap is an order book and the flat-backlog disease returns wearing a quota); selling the gap (roadmap-heavy demos that convert your evaluation into a deficiency review); and the silent yes — the vague “that’s coming” that the buyer records as a commitment and you record as nothing.

Put it to work

1. Write the three-tier vocabulary down — one page, with live examples from your actual roadmap for each tier — and run the monthly product-sales sync that keeps it current. The artifact takes an hour; the habit is the mechanism.
2. Start the ask log this week. Every roadmap question from every deal: what, who, which segment, what problem underneath. Review it in the monthly roadmap meeting as discovery input. Three months of this typically finds at least one theme the roadmap had wrong.
3. Price your last roadmap commitment retroactively — the four costs: displaced work, precedent, credibility, single-customer risk. Write the number down and bring it to the next “they’ll sign if we commit” conversation. The argument goes differently when the yes has a visible invoice.

Further reading

• April Dunford, Sales Pitch — positioning translated into an actual sales narrative structure; the best treatment of selling the present product honestly.
• Rob Fitzpatrick, The Mom Test — the discovery-questioning discipline, and it applies to sales calls even more than user interviews, because the incentives to hear yes are stronger. I’ve annotated a worked example of the same interview run twice.
• Pete Kazanjy, Founding Sales — early-stage selling mechanics, including how product truth and sales motion stay aligned before there’s a sales org.
• Bruce McCarthy et al., Product Roadmaps Relaunched — the external-audience roadmap views, including what to show buyers without handing procurement a contract.