How to price fractional product management

Fractional product work gets priced like an hourly contractor when it's closer to a leadership hire. Here's how to price the decisions rather than the days.

What you're actually selling

A team that builds the right thing. The roadmap, the specs, and the rituals are visible outputs; the product is a company not spending six months on something nobody wanted.

Why product managers get this wrong

The valuable work in product management is deciding what not to build, and it produces almost no visible artefacts. Price by the day and you'll be paid for running ceremonies and writing tickets, while the decision that saved a quarter of engineering time is bundled in free.

How to work out your number

  1. Anchor to what a wrong roadmap costs

    A team building the wrong thing for a quarter is an enormous, quantifiable amount of money. That's the number your fee sits against — not the hours you spend in refinement.

  2. Define the outcome for the engagement

    Validated roadmap, shipped launch, a discovery process the team can run without you. A defined end state lets you price the engagement rather than rent yourself by the day.

  3. Set capacity and decision rights up front

    Days per week, which meetings you're in, and what you can decide versus recommend. Fractional product roles expand faster than any other, because every stakeholder wants your input on everything.

  4. Price interim leadership above delivery work

    Acting as head of product — hiring, strategy, board-facing work — is a different job from writing specs for one squad, and it should carry a different number.

Pricing models that fit product managers

Think twice about: Fixed project fee

Product work is discovery — the scope is supposed to change as you learn. Fixing a fee against a scope you're contractually meant to challenge sets up a conflict.

Mistakes that cost you money

  • Pricing at contractor day rates for work that's closer to a leadership hire.
  • Leaving capacity undefined and being pulled into every meeting in the company.
  • Taking accountability for outcomes without authority over the roadmap.
  • Charging the same for writing specs as for owning product strategy.

Ask these before you quote

  • What's the engineering team costing per month, and what are they building?
  • Am I owning the roadmap, or executing someone else's?
  • Which decisions are mine, and which need sign-off?
  • Is this covering a gap, or building a function that outlasts me?

Product Managers: frequently asked questions

How do fractional product managers charge?

#

Usually a monthly retainer for a defined slice of capacity — two days a week, named meetings, agreed decision rights — rather than an hourly rate. It matches how the work runs and keeps the price attached to judgement rather than attendance.

How much should a fractional head of product charge?

#

More than a delivery-focused product contractor, because strategy, hiring, and board-facing work is a different job. Anchor the fee to the engineering spend you're directing and the cost of that spend going to the wrong roadmap.

Should product managers use fixed project fees?

#

Generally no. Good product work changes the scope deliberately as you learn, so a fee fixed against an initial scope puts you in conflict with your own job. Retainers and defined-outcome engagements fit better.

How do I stop a fractional product role expanding?

#

Write down the days per week, the meetings included, and the decisions you own before you start. Product roles attract requests from every function, and without a stated capacity a two-day engagement becomes a five-day one at two days' pay.

Get the deep dives

Worked examples and scripts for every pricing model. No spam.