Product strategy consulting
Roadmap, prioritisation and discovery practice grounded in evidence.
- Engagement
- Fixed-fee, optional quarterly re-run
- Typical timeline
- 3–4 weeks
- Starts with
- Introductions to three customers, one of whom left you.
Next quarter’s roadmap is whatever your largest customer asked for last month. Two features shipped this year are used by fewer than five accounts, and nobody has looked at what the other four hundred do all day.
A roadmap the team believes in and can defend.
What we build
Concrete artefacts, handed over and documented.
An evidence pack: interviews with customers who stayed, churned and nearly bought, set beside what usage data actually shows
A scoring model your team can run again without us, with the weights argued over once and then fixed
A prioritised roadmap where every item names the outcome it is meant to move
A written not-now list, so a refusal can be pointed at instead of relitigated
Kill criteria per bet: the result, and the date at which you would stop
What changes
Prioritisation arguments end with a score sheet rather than with seniority
Engineering effort moves towards features more than a handful of accounts will use
Saying no becomes possible, because the refusal is written down and shared with sales
How it runs
- Week 1
01Evidence
Eight to twelve customer conversations, the support queue, and the actions your product analytics show people repeating.
- Weeks 2–3
02Score and sequence
Candidates scored in the open, then ordered, with the trade-off each ordering forces made visible.
- Week 4
03The no list
What you are not doing and why, presented to product and sales in the same room so that it holds afterwards.
Chosen per project. Named here so you can see the shape of it.
- Dovetail
- PostHog
- Notion
- Linear
- Miro
Questions we get asked
Related work
Tell us the outcome, not the tooling.
Send us the situation you are in. We will tell you which discipline it belongs to, what we would do first and what it costs, including when the answer is to wait.