The salary is the number everyone sees.
When an organisation decides to hire a Project Manager, the conversation usually starts and ends with a figure. A salary band is agreed, a job description is written, and the cost is entered into a budget as a clean, manageable line. The assumption, rarely examined, is that this number represents what the hire will actually cost.
It doesn’t. Not even close. The salary is the start of the cost, not the sum of it. And for organisations that hire project managers regularly, particularly at senior or programme level – the gap between what they budget and what they actually spend is significant enough to change how they think about resourcing entirely.
What the salary doesn’t include
Start with time to hire. For a senior Project Manager or Programme Lead, a realistic recruitment timeline, from approval to signed offer, is eight to twelve weeks. During that period, the project the role was created to lead is either stalled, running on borrowed resource, or being managed by someone whose primary job is something else. None of that cost appears in the salary budget, but all of it has a cost.
Then there’s the agency fee, if external recruiters are used. For a permanent hire at senior level, that’s typically 15 to 20 per cent of first year salary. This sometimes appears in a separate recruitment budget, but it’s rarely factored into the true cost-per-hire when the decision is made.
Add onboarding. Even an experienced project manager new to an organisation needs time to understand the environment, the stakeholders, the politics, the systems, the culture. Realistically, a new senior PM is operating at full effectiveness somewhere between six weeks and three months after they start. The salary clock starts on day one. The value delivery does not.
The real cost of a permanent PM hire is typically 1.5 to 2x the advertised salary once you account for recruitment, onboarding, and the gap before they’re effective. Almost no business case includes this calculation.
The timing problem
There’s a second issue that sits alongside cost, and it’s arguably more damaging: timing. Projects don’t wait for recruitment cycles. The moment a delivery gap is identified, a programme needs a lead, a departing PM leaves a gap, a new initiative is approved, the clock starts. The project has a start date. The stakeholders have expectations. The budget has been allocated.
A twelve-week recruitment process in that context isn’t just expensive. It’s a structural incompatibility. Something has to give. Usually it’s the quality of what fills the gap in the interim, or the timeline of the project itself, or both.
Organisations that recruit permanent PMs for every delivery need are effectively accepting this incompatibility as a recurring feature of how they work. Most of them haven’t named it as such. If they did, the resourcing conversation would look different.
The permanency risk
There’s a third dimension that rarely surfaces in the recruitment discussion: what happens between projects? Senior project managers are a significant overhead when there’s no project to run. Organisations that carry permanent PM headcount through quiet periods are paying for capability they’re not using, or finding ways to keep people occupied that don’t reflect the seniority they were hired for.
This creates its own set of problems. Good project managers who aren’t leading meaningful work start looking elsewhere. The investment in hiring, onboarding, and embedding them walks out the door. The recruitment cycle begins again.
Permanent headcount makes sense when demand is consistent and predictable. Project delivery is rarely either. The cost of carrying permanent resource through low-demand periods is another number that rarely appears in the budget conversation.
The flexibility calculation
When you lay out these costs honestly, recruitment timeline, agency fees, onboarding ramp-up, bench cost between projects, attrition risk, a different model starts to look more attractive.
Flexible resourcing for project leadership means the organisation has access to experienced delivery capability at the point it’s needed, without the overhead of permanent employment and without the structural delay of a recruitment process. The day rate is higher than the equivalent day rate of a salaried employee. That’s the number people react to. It’s also not the right number to react to.
The right comparison is total cost: recruitment, onboarding, and the cost of the gap, set against the cost of experienced resource deployed on the first day of the project at full effectiveness, with no long-term commitment when the project ends.
For many organisations, particularly those with variable project pipelines, specialist programme needs, or critical delivery timelines, that comparison is considerably closer than the salary line suggests. For some, it points clearly in the other direction.
The calculation worth doing
The honest truth about the cost of recruiting project managers is that most organisations haven’t done the full calculation. They’ve looked at the salary line and made a decision. The rest of the cost, the timing risk, the ramp-up period, the recruitment overhead, the bench cost, is absorbed quietly in other budgets or in delivery delays that nobody formally prices.
Before the next PM recruitment is signed off, it’s worth doing the maths properly. The answer might be the same. It might not be.
Stoneseed’s PMaaS provides experienced project and programme management resource without recruitment timelines, onboarding gaps, or long-term headcount commitments. stoneseed.co.uk