Most product roadmaps fail for a boring reason: nobody wrote down what the roadmap is actually for. Not "grow revenue" — that's a goal, not a filter. A roadmap needs a filter that tells you why the third item is above the eighth item, and most teams don't have one, so the roadmap becomes a queue of whoever asked most recently. Product strategy is the work of building that filter before you build the list.
Prioritisation that survives contact with sales
Every scoring framework — RICE, ICE, weighted value-vs-effort — collapses into the same underlying question: what do we believe about impact, and how confident are we in that belief? The framework matters less than the discipline of writing the belief down before you build, so you can check it against reality afterward. RICE (Reach × Impact × Confidence ÷ Effort) is popular because the Confidence term forces you to admit when you're guessing. A feature with huge assumed impact but 20% confidence should lose to a feature with modest impact and 90% confidence, and most teams get this backwards because the big swing is more exciting to plan.
Before ranking anything, sort requests into reversible and irreversible. A UI tweak is reversible — ship it, watch the data, revert if wrong. A pricing model change, a data migration, or a public API contract is a one-way door. One-way doors deserve more scrutiny and a slower decision process than the scoring framework alone will give them; don't let a RICE score wave through an irreversible bet.
Build vs. buy vs. partner
The build-vs-buy decision gets framed as a cost comparison and that's the wrong lens for most of it. The real question is whether the capability is core to your differentiation or table stakes for being in the category. Billing, authentication, email deliverability, and search are table stakes for almost every SaaS product — customers don't buy you for your billing system, so buying Stripe or WorkOS instead of building it is close to a free decision. The capability worth building in-house is the one your customers would specifically choose you over a competitor for. If two vendors solve the same underlying problem and your pitch doesn't depend on how you solved it, buy it and spend the engineering time on the part that does.
Vendor lock-in is a real cost that shows up two years later, not on the signing date. Before adopting a third-party dependency for a core workflow, write down what migrating away would look like and roughly how long it would take. If the answer is "we don't know," that's the real price of the decision, not the monthly invoice.
Positioning the product does the selling
Positioning is not a tagline exercise — it's deciding which category you're competing in and which comparison you're forcing the buyer to make. A product with weak positioning makes the sales team invent a different pitch for every prospect, which means every deal takes longer and every rep sells a slightly different product. Strong positioning answers three things concretely: who is this for (and, just as importantly, who is it explicitly not for), what alternative are they using today, and what is true about you that isn't true about that alternative. If the honest answer to the third question is "we're basically the same but cheaper," that's not positioning, that's a discount strategy wearing a marketing site.
Roadmap communication as a trust mechanism
A public or semi-public roadmap is a promise, and broken promises compound faster in a small customer base than in a large one — every enterprise buyer who was told a feature was "coming next quarter" and watched two quarters pass without it becomes a harder renewal conversation. The fix isn't to stop communicating roadmap; it's to communicate confidence bands honestly. "Committed, shipping this quarter" and "exploring, no committed date" are different categories, and mixing them on the same public roadmap page erodes trust in both once the exploratory item slips.
Wrapping up
A SaaS product strategy is not a longer roadmap, it's a sharper filter: a stated basis for prioritisation, a clear build-vs-buy line drawn around what's actually core to your differentiation, and a positioning statement specific enough that sales doesn't have to reinvent the pitch per prospect. Get the filter right and the roadmap mostly writes itself; skip it and you'll ship a long list of individually reasonable features that don't add up to a product anyone can describe in one sentence.
Independent software engineer in Nairobi specialising in Acumatica customisations, Laravel backends, and tax fiscalisation integrations across East and Southern Africa.