Home/Services/Product Strategy
Product & Portfolio
Product Strategy Consulting for Companies That Have to Choose
Product strategy is the decision about where a product competes and on what basis it wins, expressed as a sequence rather than a list. A roadmap says what will be built. A strategy says why those things and not others, in what order, and what would prove the choice wrong.
Most roadmaps we are shown are agreeable and unusable. Everyone has signed them and nobody can act on them, because no bet has been named and no order of attack has been stated.
- Senior-led engagements
- Written recommendation first
- Reply within two working days
When companies call us
The conversation that keeps restarting
Portfolio
“Three teams are building for three different customers.”
Adoption
“The roadmap is four quarters of features with no stated order.”
Pricing
“We keep saying yes to everything and shipping slowly.”
Sequence
“We cannot explain why we build what we build.”
And usually
“We have been going round this for months and keep starting the argument again.”
And usually
“We have been going round this for months and keep starting the argument again.”
The engagement
What we look at, and what you keep
What we analyse
- Real demand, segmented by who actually buys and who merely evaluates
- Positioning against the alternatives your customers genuinely consider, not the ones you track
- Where you win on evidence rather than on assertion
- Dependencies between the bets, and what has to be true first
- The indicators that would tell you the strategy needs revisiting
What you receive
- A written strategy with each bet named and costed
- A four-quarter sequence with dependencies made explicit
- The wedge — the one segment to win before widening
- A falsification test written into the plan
- One page a new joiner can act on without a briefing
How long it takes
Two-week diagnostic, or 8–12 weeks embedded with your product team.
Who it is for
Companies past first revenue where the product organisation has grown faster than the clarity about what it is for.
A strategy that cannot be proven wrong is not a strategy. We write the test in.
Related services
Common questions
Product Strategy, in practice
What is the difference between a product roadmap and a product strategy?
A roadmap is a schedule of what will be built. A strategy is the reasoning that decides what goes on the roadmap and in what order. If you can remove the strategy document and the roadmap still looks the same, you had a schedule and not a strategy.
How do you connect product strategy to the P&L?
By costing each bet and stating what it is expected to return. Every roadmap is a plan for allocating capital, and treating it that way makes the trade-offs visible to the board and to the product team in the same language.
How long does it take?
Two weeks to a written recommendation. Eight to twelve weeks if we work through the sequence and the metrics with your team.
Do you write the strategy for us or with us?
With you. Strategies written for a team are read once. The ones that survive are argued through with the people who will have to act on them.
Tell us the decision you are facing.
A short paragraph is enough. Where another firm would serve you better, we will say so and suggest one.
- Senior-led engagements
- No model or software resale
- Reply within two working days