What a Product Strategy Consultant Costs (and Why the Day Rate Is the Wrong Number)

A while back I emailed a bid to a prospective client and they wrote back and said I was too expensive. I was fine with that. But after a few hours of thinking about it, I began to wonder whether my bid was inaccurate, so I wrote back and asked what their budget was and what the goals were. Turns out they needed about five hours of help a week and I had bid twenty. Once I understood what they were actually looking for, we scoped the work and agreed on a monthly number that worked for both of us.

Neither of us was wrong about the rate. We were wrong about the job.

That's most of what goes sideways when someone starts pricing product strategy help, so before the numbers, the honest framing: the day rate is the cheapest number in this decision, and it's the one everyone comparison-shops.

What the market actually charges

Real published ranges, from people who sell into this market:

A fractional CPO runs $10,000 to $20,000 per month on a typical three-to-six-month engagement. A separate rate survey puts the same role at around $200 an hour, roughly $8,000 to $16,000 a month.

A product strategy consultant bills $250 to $500 an hour, with a six-to-eight-week engagement landing somewhere around $40,000 to $80,000.

A full-time CPO costs $300,000 or more per year fully loaded, before you count the three to six months it takes to hire one and the ramp after that.

Two caveats on those numbers, and they matter. All three sources sell into this market, so read them as published market rates rather than neutral research. And ranges that wide usually mean the category is doing more than one job, which is the actual problem here.

The three gaps, and which one you have

The useful question isn't what these cost. It's which of three problems you're solving, because they have genuinely different answers.

A capacity gap means you know what to build and you don't have enough hands. Hire a PM. Don't pay strategy rates for throughput; it's the most common mis-purchase I see and it's expensive in a quiet way, because the strategy person will do the capacity work, competently, and you'll have bought a very good execution hire at a consultant's rate.

A direction gap means the roadmap keeps changing shape and nobody can say why this quarter's bets are the right ones. That's ongoing, it's entangled with your org and your stakeholders, and it wants somebody embedded – a fractional leader who's in the room week over week.

A decision gap is narrower and sharper: one hard question you can't answer internally and can't afford to get wrong. Which market. Whether the enterprise tier is real. Whether the thing you're about to spend two quarters building is worth building. That's project-shaped, not retainer-shaped, and it's the one where an outside answer is worth the most, because the value is concentrated in a single call.

If you can't tell which you have, that's diagnostic information on its own, and it usually points at the direction gap.

The number nobody quotes

Here's what makes the fee comparison mostly beside the point.

Set the engagement cost against what it costs to build in a direction nobody validated. Two quarters of a five-person product team is a large multiple of any of the numbers above, and that's just the payroll – it doesn't count the opportunity cost of the thing you didn't build, the market position you didn't take, or the fact that you now have a live feature to maintain, support, and eventually deprecate.

Eric Brown puts the scarce thing well: what's rare now is knowing "which work is worth doing, what not to build, and where the model is confidently wrong enough to cost you six months if you believe it." He adds the part I've watched play out repeatedly – plenty of clean, expensive analysis gets produced perfectly and answers a question nobody should have asked.

A cheap yes leads to an expensive no. The yes is cheap because nobody made it pay for itself up front; the no arrives two quarters later with a codebase attached. Against that, the spread between one engagement quote and the next one you're weighing it against is noise.

How to tell judgment from capacity before you sign

Brown's test is the best single question I know for this, and I'd use it on me: ask them where they'd tell you not to use it.

Anyone selling capacity will keep selling. The person worth hiring will have a list, because they've watched this stuff fail, and they'll walk you through the parts of your plan that are a bad idea before you've signed anything.

A few more that work:

Ask what would make them tell you to stop. If there's no answer – no evidence that would end the engagement early with a recommendation not to proceed – you're buying activity.

Ask who is actually doing the work. In a traditional firm the partner sells and the juniors deliver. Ask by name, and ask how many other engagements that person is on.

Ask what you keep. A deliverable you can't operate without them is a dependency, not an asset.

Ask what they won't do. I'll say mine plainly: the strategy work I do produces personas, a problem inventory, and a thematic roadmap. That's enough for a team to write epics and stories. It is not enough for engineers to estimate against – nobody estimates a theme, and that's three or four weeks further on, once stories exist. Anyone promising you estimable work out of a strategy engagement is selling you something that doesn't exist.

Why the ranges are so wide

It's worth saying why published rates vary by a factor of two or more, because the spread isn't sloppiness – it's the category doing several different jobs under one label.

Some of it is scope. An engagement that ends in a written recommendation prices differently from one where somebody sits in your leadership meetings for six months, and both get called "product strategy." Some of it is seniority, and the gap between a person who has made these bets with their own name on the outcome and a person who has read about them is real, hard to assess from a website, and reflected in the rate.

And some of it is risk transfer. A fixed-scope project prices the risk into the number; an hourly arrangement leaves the risk with you. Neither is wrong, but you should know which one you're buying, because the cheaper-looking option is frequently the one where overruns are your problem.

When you shouldn't hire any of this

If you have a capacity gap, hire. If the decision is genuinely reversible and cheap to unwind, just make it and watch what happens – that's faster and cheaper than any engagement and you'll learn more. If the real problem is that two executives disagree and neither will say so, an outside consultant becomes a very expensive way to avoid a conversation, and I've been hired into that room more than once. The deliverable doesn't fix it. It just gives everyone something neutral to argue about for another quarter.

And if nobody internally can articulate what a good answer would even look like, start there. That's a free afternoon with a whiteboard, and it occasionally dissolves the whole question.

I'm not going to publish my rate here, because a number on a page becomes an anchor and it'd be out of date by spring. But I'll tell you the one on the other side of the email: ask what the budget is and what the goals are. That question has saved me more engagements than any bid I've ever written.