Guide
Product strategy for founders
Most founders don't have a strategy problem. They have a page that was never written. This is the page — what product strategy actually is, what belongs on it, and how to tell whether yours is real.
Written from twenty-five years of building products and sitting with founders at the point where the roadmap stops explaining itself.
In short
Product strategy is the set of choices explaining what you're building, who it's for, how you'll win, and what you're deliberately not doing. It sits between vision and roadmap: vision is where you're going, strategy is what you'll trade to get there, the roadmap is only the order of work. A founder's strategy fits on one page and answers six things: the problem, the specific customer, the exclusions, the one advantage, the assumptions, and the signals you'd act on.
What product strategy is
Product strategy is the set of choices that explains what you're building, who it's for, how you'll win, and what you're deliberately not doing.
It sits between vision and roadmap. Vision is where you're going. Strategy is what you'll trade to get there. The roadmap is only the order of work — and if the strategy is clear, most roadmap arguments end before they start.
The test is simple: can two people on your team, asked separately, describe the same problem, the same customer and the same thing you've chosen not to build? If not, the strategy exists in your head, which means it doesn't exist.
The six things a founder's strategy needs
One page. Six answers. Everything else is supporting material.
01
The problem you're actually solving
One sentence, defensible, written down. If two people on the team say it differently, you don't have a strategy yet — you have a shared hope.
02
Who it's for, specifically
Not a market. A person with a bad Tuesday. Strategy gets easier the moment the customer stops being plural.
03
What you will not do
A strategy without exclusions is a wish list. The value is in what the roadmap loses, not what it gains.
04
How you'll win
The one advantage that compounds — distribution, insight, speed, trust. Pick one. Two is a hedge, three is a hope.
05
The assumptions you're betting on
Write down what must be true. Price each assumption by what it costs to be wrong, and test the expensive ones first.
06
How you'll know it's working
One or two signals you'd act on. If a metric wouldn't change a decision, it's decoration.
What a good one sounds like
Three worked examples. Note how short they are, and how much they refuse.
B2B SaaS, pre-revenue
"We help operations managers at 20–100 person manufacturers stop rebuilding the same spreadsheet every month. We win on setup speed — live in a day, not a quarter. We will not build reporting until 20 teams ask for it."
Marketplace, early traction
"We make it normal for independent trainers to fill their last three seats. We win on supply trust, not demand volume. We will not chase enterprise buyers this year."
Internal platform
"We cut the time from idea to deployed experiment from three weeks to three days. We win on removing steps, not adding tools. We will not own anything a team can own itself."
Five mistakes that cost the most
- 01
Confusing a roadmap with a strategy. A roadmap is a schedule; a strategy is a set of choices that makes the schedule obvious.
- 02
Writing strategy as a vision statement. Vision is where you're going; strategy is what you'll trade to get there.
- 03
Letting the loudest customer set the direction, then calling it customer-led.
- 04
Treating a demo as evidence. A demo proves it can be built, not that it should be.
- 05
Never writing it down — which means it quietly changes every week and nobody notices.
Common questions
What is product strategy?
Product strategy is the set of choices that explains what you're building, who it's for, how you'll win, and what you're deliberately not doing. It sits between your vision and your roadmap: the vision says where you're going, the strategy says what you'll trade to get there, and the roadmap says in what order.
What's the difference between product strategy and a roadmap?
A roadmap is a sequence of work. A strategy is the reasoning that makes that sequence obvious. If you can't explain why an item is on the roadmap without referring to a meeting, you have a schedule rather than a strategy.
How do I create a product strategy as a founder?
Start by writing the problem in one sentence you'd defend in front of a customer. Name the specific person it's for. List what must be true for it to work, and price each assumption by the cost of being wrong. Choose one advantage you'll compound. Then write down what you will not do this year. That page is your strategy.
How long should a product strategy be?
One page. If it doesn't fit on a page, it isn't a set of choices yet — it's a summary of everything you've considered. A strategy you can't hold in your head won't survive a busy week.
How often should product strategy change?
The choices should hold for six to twelve months; the evidence behind them should be reviewed monthly. Change it when an assumption is disproven, not when a quarter ends.
Do early-stage founders need a product strategy?
Yes — earlier than most expect. Before product-market fit, strategy is mostly about which assumption to test next. It's cheaper to be clear on one page than to discover the same thing after two quarters of building.
Where to start
If you're not sure whether your strategy is real, the fastest check is the Founder Clarity Score — ten questions, two minutes, across problem clarity, customer proximity, roadmap discipline, decision hygiene and shared language. If you'd rather just talk it through, the first twenty minutes are free.
Related reading: how to validate a product idea · the roadmap is a story, not a schedule · every prototype is tuition · founder frameworks
Want the one-page strategy template?
Leave an email and I'll send the template behind this guide, plus one lesson a month. No newsletter, no offers.