What does product strategy and roadmap work include?

A written answer to who you are for, what you will win on, and what you are therefore not doing, followed by a roadmap where every item traces to that answer in one sentence. The strategy half is a small number of decisions: the segment, the wedge, the thing you will be measurably better at. The roadmap half is the part teams recognize, and it is worth less than it looks unless the decisions above it are explicit. A roadmap with no stated strategy is a queue.

What does customer discovery include?

A structured interview program, run by the consultant rather than delegated back to you, large enough that no single loud voice can determine the outcome. In a serious engagement that means 60–80 customer and prospect interviews across current customers, churned accounts, closed-lost prospects and the segment you do not yet serve. The output is not a transcript library. It is a set of named patterns with counts attached, and a cadence your team keeps running after the engagement ends, so the evidence base ages forward instead of freezing.

What does a prioritization system include?

A written rule, visible to everyone, that produces the same ranking regardless of who is in the room. Most companies at this stage have a scoring spreadsheet nobody trusts and a real process that runs on seniority. The work is replacing the second with something defensible: explicit criteria, explicit weights, a standing forum where the ranking is challenged with evidence, and a documented answer to what happens when a large customer disagrees. The test is whether a PM can decline a request without escalating to the founder.

What does product org design include?

Deciding how many product people you need, at what levels, split along which lines, and in what order to hire them. Below $15M ARR this is usually a smaller answer than founders expect: one accountable leader and a small number of PMs owning outcomes rather than feature areas. The workstream also covers the boundaries nobody writes down, which is where most friction lives: who owns pricing, who owns onboarding, and whether design reports into product. A structure that requires the founder to arbitrate is not a structure. The hiring end of this workstream is covered in hiring a head of product for your SaaS company.

What do metrics and instrumentation include?

Choosing the small set of numbers the product is actually managed by, then making sure they exist and are trusted. Activation, time-to-value, feature adoption by segment, expansion and churn reason codes carry most of the load at this stage. The unglamorous half is instrumentation: agreeing definitions, fixing the events that were never implemented, and getting one source everyone quotes. A metric two teams compute differently is not a metric, and every prioritization argument built on it is unresolvable by design.

What does go-to-market alignment include?

Closing the gap between what the product does and what sales says it does. In practice: a positioning statement product and sales both use, a shared definition of the qualified deal, a loop that gets closed-lost reasons back into prioritization, and launch mechanics so a release reaches customers rather than only the changelog. This is the workstream founders skip and then misdiagnose later, because a product problem and a sales problem look identical from the revenue line. Separating them is covered in the guide to telling a product problem from a sales problem.

• Strategy and roadmap: one segment, one wedge, every item traceable in a sentence
• Customer discovery: 60–80 interviews, patterns with counts, a cadence that outlives the engagement
• Prioritization: a written rule that outranks seniority in the room
• Org design: the smallest structure that does not require founder arbitration
• Metrics: one trusted definition per number, instrumented and agreed
• Go-to-market: shared positioning, closed-lost reasons feeding the roadmap

How many workstreams can run at once?

Two or three, on a 20–25 hour monthly retainer. Anyone offering all six simultaneously at that level is describing a team, and the price should reflect it. The sequencing matters more than the count: discovery almost always runs first because the other five are unresolvable without evidence, and metrics usually runs alongside it because the arguments in month three are settled with numbers that have to exist by month two. Product management consulting for B2B SaaS is the category name for this work; a fractional CPO is the engagement model that carries accountability for the outcome of it rather than the quality of the recommendation.

Sivan Kadosh, a fractional Chief Product Officer for B2B SaaS companies between $2M and $15M ARR, runs these on a $8,000 monthly retainer with a 3 month minimum. What each model costs is set out in the guide to product management consulting cost, and the broader buyer's view is in product management consulting for B2B SaaS.

Six workstreams make up product management consulting services, and a senior operator runs two or three of them at a time on 20–25 hours a month. Discovery is the one to start with in almost every case, because the other five inherit whatever assumptions you skip. Buy the sequence, not the catalogue.