What a product management consultant costs — and how to read a day rate

Almost nobody in this market publishes a rate, and the reason is boring rather than sinister: the number genuinely depends on scope, days per week, duration and how much accountability comes with it. A quoted figure without those four things attached is noise.

What is publishable is the structure — and if you know the structure, you can read any quote you’re given and tell whether it’s reasonable. That’s more useful than a number anyway.

The three ways this gets priced

Day rate. You pay per day worked, invoiced monthly. The default for interim and fractional work. Advantages: it flexes, and you stop paying the week you stop needing it. Disadvantage: it invites both sides to count days rather than outcomes.

Monthly retainer. A fixed monthly fee for an agreed level of availability — “two days a week” — regardless of exact days used. Better for fractional arrangements, because it prices availability rather than attendance, and it stops the awkward conversation about whether a 40-minute call counted as a day.

Fixed scope. A price for a defined deliverable: a validated product strategy, a discovery programme, a shipped launch. Best when the outcome is genuinely definable, and it’s the only model where the supplier carries the efficiency risk. Ask for it when you can name the deliverable — if the supplier resists a fixed price for something well-defined, that’s information.

Most consulting work is priced the third way. Most interim and fractional work is priced the first or second, because holding a role isn’t a deliverable.

The arithmetic that makes a day rate comparable

The comparison people instinctively make is day rate × 220 days vs. salary, and it’s wrong in both directions. Here’s the version that isn’t.

Step 1 — the true cost of the permanent hire. Take the gross salary and add:

• Employer social contributions (in Germany, roughly 20–21% on top of gross)
• Recruitment fee, if agency — commonly a fifth to a quarter of first-year salary
• Equipment, tooling, desk
• Paid holiday and sick leave, which you’re funding inside the salary

Step 2 — divide by actual working days. Not 260. A German employee has roughly 30 holiday days plus public holidays plus some sick leave, which lands you near 220 productive days — and for the first two to three months of those you’re paying full cost for partial output while they ramp.

Worked through with an illustrative €120,000 salary — the figure is an example, not a market claim:

Gross salary	€120,000
+ employer contributions (~20%)	€24,000
+ agency fee (20%, one-off)	€24,000
Year-one cost	€168,000
÷ 220 working days	≈ €764 per productive day

Step 3 — now compare. That per-day figure is what you actually pay a permanent hire in year one, and it’s usually a lot closer to a consultant’s day rate than people expect.

What’s in a day rate that isn’t in a salary

The gap between those two numbers is buying specific things, and it’s worth being explicit about them:

• No notice period. If it isn’t working, it ends in weeks. A permanent mis-hire in Germany is a months-long process at best.
• No ramp. You’re paying for output from week one. The ramp is the consultant’s problem, and they’ve done it before.
• No recruitment cost or delay. Two to three weeks to start, against four to six months for a search.
• No equity, no bonus, no severance, no pension.
• The risk sits on their side. Their unpaid holiday, sick days, quiet months, insurance and pension all come out of that rate. A contractor bills maybe 140–180 days a year, not 220 — the rest is sales, admin and gaps.

That last point is the one buyers most often miss. A day rate is not a salary expressed differently; it’s a business’s revenue per billable day.

What drives the number

Up:

• Accountability. Holding a role costs more than advising on one. It’s the single biggest driver.
• Fewer days per week. One day a week costs more per day than four — context-switching is real and the supplier can’t fill the gaps efficiently.
• Short duration. A three-week engagement prices higher per day than a six-month one.
• Urgency, and on-site requirements.

Down:

• Longer commitment with a signed end date.
• Remote, with occasional travel.
• A clearly scoped problem. Ambiguity is priced, because ambiguity is risk.

What “cheap” actually costs

The failure mode I’d warn about most is buying on rate. Three ways it goes wrong:

You buy advice when you needed a decision. A consultant is cheaper per day than an interim precisely because they don’t hold accountability. If your actual problem is that nobody can say no, a cheaper supplier who also can’t say no has changed nothing — you’ve paid for a diagnosis you already had.

You buy too few days. Someone holding a role at one day a week when it generates three days of decisions becomes the bottleneck. The team waits. You’ve paid for a slower version of the problem.

You buy a junior at a senior price point. The market has a wide range and the titles don’t sort it. The test is the work sample: ask what they’d do in your first month, and see whether the answer is a plan or a template.

How to ask

Four questions that get you a real number quickly:

1. “What’s your day rate at [N] days a week for [M] months?” — all four variables in one sentence, so the answer is comparable.
2. “What’s included that I’d be invoiced separately for elsewhere?”
3. “What would make this cost more than we’ve discussed?”
4. “What’s the smallest useful version of this?” — the answer tells you a lot about whether they’re sizing to your problem or to their pipeline.

Any supplier worth engaging will give you a number in the first conversation. A rate that only appears after three meetings and a proposal is a rate that’s being calculated from how much they think you’ll pay.

---

For what it’s worth, that’s how I’d rather do it too: you’ll get a number from me on the first call rather than in a document afterwards. If the honest answer is that you need six weeks of project work rather than an interim engagement, that’s a much smaller number and I’d rather say so — see how the engagements differ.