Back to blog
We have been part of roadmap reviews where the third line down had been on the slide for two planning cycles running. Sprint number, release date, owner's name. When we asked which segment it was meant to win, the product lead paused, looked at the sales lead, and said, "it's next in the backlog." Nobody in the room disagreed. That was the justification. Not a market, not a timing bet, not a reason it came before or after the line above it. Just where it sat in the queue.
That's the pattern behind most commercial product roadmaps. What gets shown at the planning offsite is a delivery plan wearing a strategic label. Features, releases, a date everyone's nervous about. Ask which commercial bet each line represents, and the room goes quiet in exactly the way ours did.
Why the roadmap defaults to delivery
The roadmap as a format grew up inside product and engineering. It answers "what gets built, and when," a question release planning is genuinely good at. Nobody redesigned it to answer a different question: which market moves happen, in what order, and why now rather than later. The format stayed. The content shifted slightly. Most organisations ended up with a document that looks commercial because it sits next to the strategy deck, while it functions exactly like the engineering backlog it was built from.
Portfolio work is often where the confusion starts. Product Portfolio Management covers this from the other side: the push, pull, and exit calls get made properly, which products earn investment, which get sustained, which get retired. Then there's a gap. Nothing translates those calls into a sequence, this segment first, that channel second, a pricing move once the first shows traction, so good portfolio thinking sits upstream of a roadmap that never picks it up. The decisions were right. They just never became a plan anyone could act on in order.
What a commercial roadmap actually is
It helps to place the roadmap where it sits in the wider architecture. Business strategy sets the ambition. Commercial strategy decides where to compete and how. The portfolio decides what earns investment. The roadmap turns those choices into a sequence of commercial commitments, before any of it becomes an individual initiative. This is the layer What Is a Commercial Agenda touches only briefly, as a roadmap that predates the strategic choices sitting above it. It's worth spelling out properly.
That sequencing is the whole job. A commercial roadmap states which segment gets the go-to-market push in quarter one, which pricing change follows once that segment shows traction, and which market gets resourced once the specifier channel in the first has matured. None of that is a delivery date. It's a bet, placed in order, for a stated reason.
This isn't an argument against product roadmaps. Delivery planning matters and shouldn't be diluted with strategic language it was never built to carry. The two documents can coexist perfectly well. What doesn't work is asking one to do the other's job, which is what happens when the only roadmap in the room is the engineering one with a commercial cover slide.
What breaks without it
Skip this layer and the damage shows up downstream, which is why it's easy to miss at first. The same translation problem shows up at the strategy level too. How to Implement a Strategy That Actually Sticks makes the case that strategy has to be translated all the way down to the metrics that govern daily decisions. A missing commercial roadmap is that same translation gap, one layer up, before the metrics even get set.
Product and commercial each build their own version of sequence, independently, because nothing forced agreement on which came first. Targets get set against initiatives that were never sequenced against each other, so the numbers look ambitious and connect to nothing underneath. Funding defaults to whichever initiative argued loudest that quarter, because there's no commercial sequence to fund against. Only a list.
"A roadmap that lists everything in equal weight has sequenced nothing."
The portfolio prioritisation work holds up fine on its own. It's the layer between portfolio and initiatives that goes missing, and that's precisely where a commercial roadmap is supposed to sit.
"It's a bet, placed in order, for a stated reason. Not a delivery date."
Where to start
Take the current roadmap and go through it line by line, the way we did in that review. For each item, ask what commercial bet it represents and why it sits where it does in the sequence, not just when it ships. Where the honest answer is "it was next in the backlog" rather than naming a segment, a timing, a reason, that's the gap. Closing it doesn't take a rebuild. It takes making every line answer a question the format was never built to ask.
Key takeaways
A commercial roadmap and a product roadmap answer different questions. Most organisations only have the second, labelled as the first.
Good portfolio decisions about what to push, pull, or exit don't automatically become a sequence anyone can act on. That translation is the roadmap's job, and it's the layer most often skipped.
The test for any roadmap line isn't when it ships. It's which segment, market, or pricing move it represents, and why it comes before or after the item next to it.
A roadmap where every item carries equal weight hasn't sequenced anything. It's a list with dates attached.
Closing the gap doesn't require a new planning process. It requires asking each existing roadmap line to justify its position, not just its deadline.
FAQ
What is a commercial roadmap?
A commercial roadmap sequences the commercial bets that follow from portfolio decisions, which segment gets resourced first, which pricing or go-to-market move follows, and in what order, before those bets become individual delivery initiatives.
How is a commercial roadmap different from a product roadmap?
A product roadmap sequences what gets built and when. A commercial roadmap sequences which market moves happen and why one comes before another. Most organisations only build the first and call it both.
Why do commercial roadmaps usually turn into delivery plans?
Because the roadmap format was built inside release planning, where "what ships, and when" is the natural question. Nobody redesigned it to sequence market bets instead, so the format persisted while the underlying question quietly changed.
Does a business need both a product roadmap and a commercial roadmap?
Yes. They answer different questions and neither replaces the other. The problem isn't having a product roadmap. It's having only one and treating it as if it were commercial.
What's the first step to building a genuine commercial roadmap?
Take the existing roadmap and ask, line by line, which commercial bet each item represents and why it's sequenced where it is. Items that can only be justified by their delivery date, not their commercial reasoning, are the ones to fix first.
