How to price project management

Project management is invisible when it works, which makes it the hardest service to justify by the hour. Here's how to price the outcome instead of the meetings.

What you're actually selling

Projects that land — on time, in budget, without the client discovering problems too late to fix them. When you're doing it well, nothing dramatic happens, and that's the thing you're being paid for.

Why project managers get this wrong

Billing hours puts you in an impossible position: the better you run the project, the fewer crises there are, the fewer hours you bill, and the more your fee looks like it's for attending meetings. Nobody pays well for a calm status update.

How to work out your number

  1. Price against the cost of the project going wrong

    Slipped launches, blown budgets, and idle delivery teams are expensive and quantifiable. A fee that's a fraction of the overrun you're preventing is an easy case to make, and it's the right frame for the conversation.

  2. Scope the engagement by project or by month

    A defined fee for a defined project, or a monthly fee for ongoing delivery oversight. Both keep the price attached to the outcome rather than to how many hours the chaos generated.

  3. Be explicit about authority

    You can't be accountable for a delivery date without the authority to change scope, timeline, or resourcing. Write down what you can decide and what you can only recommend, because it changes what you can promise.

  4. Define capacity, not availability

    Fractional project management drifts into being permanently on call. State the number of days or hours a month, the meetings included, and the response times you're committing to.

Pricing models that fit project managers

Think twice about: Hourly rate

It pays you most when the project is on fire and least when you've prevented the fire. The incentive points the wrong way and the value is invisible.

Mistakes that cost you money

  • Billing hours, so competence quietly reduces your income.
  • Accepting accountability for a deadline without authority over scope or resourcing.
  • Leaving the number of days a month undefined and becoming permanently on call.
  • Quoting for the delivery phase and absorbing the discovery and planning that made it possible.

Ask these before you quote

  • What does a month of delay cost this business?
  • Can I change scope, timeline, or resourcing, or only flag issues?
  • Who are the stakeholders, and how many need to agree on decisions?
  • Is there an existing plan and budget, or does that need building first?

Project Managers: frequently asked questions

How should a freelance project manager charge?

#

By the month or by the project, not by the hour. Hourly billing means a smoothly run project earns you less than a chaotic one, and it reframes your value as attendance rather than delivery.

How do I justify project management fees?

#

Compare your fee to the cost of the project slipping — idle delivery teams, missed launch windows, budget overruns, rework. Those numbers are usually far larger than your fee, and they're the ones the client is really weighing.

What should a fractional project management retainer include?

#

A stated number of days or hours a month, named meetings and reporting, and defined response times. Without those, a fractional arrangement drifts into full-time availability at part-time pay.

Should I take responsibility for delivery dates?

#

Only where you have the authority to protect them. If you can't change scope, timeline, or resourcing, you can be accountable for visibility and escalation but not for the date itself — and your contract should say so.

Get the deep dives

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