Adding Another PM vs Deploying an Intelligence System: What the Real Cost Comparison Looks Like

What Does It Actually Cost to Add Another Senior PM in NZ?

Most PMC principals think about this as a salary decision. The Hays Salary Guide FY25/26 puts senior project managers and senior contract administrators in the $130,000-$180,000 range in New Zealand, depending on experience and location. That is the number that goes into the budget.

The real number is higher. Once you add KiwiSaver contributions, ACC levies, health insurance, professional memberships (NZIQS, NZIS, RICS, or similar), laptop and software, and professional development, on-costs typically add 18-25% to base salary. On a $160,000 base, that is an additional $28,000-$40,000 before anyone has done a day's work.

Then there is the recruitment cost. Using a specialist recruiter for a senior PM role in NZ typically costs 15-20% of first-year salary. On a $160,000 appointment, that is $24,000-$32,000 paid upfront. If you hire directly and advertise widely, the cost is lower but the time investment of shortlisting, interviewing, and assessing candidates is still substantial.

And then there is ramp-up. A new senior PM on a NZS 3910 project does not hit full productivity in week one. They need to learn your firm's processes, understand your existing client relationships, get across the contract and its special conditions, and build trust with the principals and contractor teams they will be working with. Realistically, this takes three to six months. During that period, a more experienced colleague is spending time supervising, reviewing work, and answering questions. That cost does not appear on the invoice, but it is real.

When you add recruitment, on-costs, ramp-up management time, and the operational overhead of managing an additional person, the true annual cost of a senior PM hire commonly sits in the $180,000-$250,000 range. That is the number you should be comparing against alternative investments in capacity.

Where Does That PM's Time Actually Go?

Before comparing the two options, it is worth being clear about what you are actually buying when you hire a senior PM. You are buying their professional judgement, their commercial instinct, their ability to read a contract and spot risk before it becomes a claim. You are not buying a spreadsheet maintainer or a compliance tracker.

The problem is that a significant portion of what senior PMs do on NZS 3910 projects is exactly that: maintaining spreadsheets, tracking obligations manually, compiling reports from multiple sources, chasing documentation, and updating registers that should update themselves. Industry experience and the RICS 2025 survey consistently point to around 14 hours per week per senior PM spent on tasks of this kind.

That is more than a third of a 40-hour week. Spent on work that requires consistency and completeness, not professional expertise. Work that a well-configured system can handle more reliably than a human doing it manually under time pressure.

This matters for the hiring comparison because it means the new PM you bring in will also spend 14 hours a week on admin. You are not adding 40 hours of advisory capacity. You are adding, at best, 26 hours of it, with the other 14 going to the same administrative overhead that is already consuming your existing team.

As explored in detail in our article on why your best PMs are doing $50/hour work, the administrative burden is a structural problem, not an individual one. Hiring more people into the same structure amplifies the problem as much as it solves it.

How Does an Intelligence System Compare on Capacity Returned?

An intelligence system deployed on your firm's infrastructure handles the repeatable, structured work that currently occupies 14 hours of each PM's week. Obligation tracking, deadline monitoring, CCA payment claim windows, special conditions flagging, daily priority briefings, reporting compilation. The system does not require supervision. It does not need ramp-up time. It does not take annual leave.

The capacity return is calculable. If a senior PM is currently managing two to three contracts and spending 14 hours per week on admin, recovering most of that time means they can add one to two more contracts to their portfolio. The advisory time per contract does not decrease. The administrative overhead per contract drops sharply because the system is tracking it.

Across a team of six senior PMs, recovering 10 hours per person per week returns 60 hours of capacity. That is the equivalent of one and a half additional full-time senior advisors, every week, without a hire, without recruitment fees, and without a three-month ramp-up.

The capacity recovery is also higher quality than the capacity you get from a new hire. The existing PMs know your clients, your processes, and your contracts. When you give them back 10 hours per week, that time goes directly into advisory work on projects they already understand. A new hire's first two months of capacity goes predominantly to learning.

The Comparison Table

Factor	Add a Senior PM	Deploy an Intelligence System
Annual cost	$180K-$250K fully-loaded (salary, on-costs, recruitment, ramp-up)	One-time build fee plus modest annual maintenance retainer (value-based, contact for details)
Time to value	3-6 months to full productivity. Advisory capacity builds slowly during ramp-up.	8-12 weeks to deploy and train. Capacity returns from first operational month.
Capacity gained	~26 hrs/week of advisory capacity (40 hrs minus 14 hrs admin overhead)	10-14 hrs/week per existing PM recovered, multiplied across the team
Quality floor	Depends on the individual. Varies by experience, familiarity with your contracts, and workload.	Consistent across all contracts. System tracks everything regardless of who is on leave or overloaded.
Scaling path	Each new contract requires proportionally more staff. Cost increases linearly with revenue.	System covers additional contracts at marginal cost. You hire selectively, for real gaps.
Exit cost	Redundancy, notice periods, PI tail cover, knowledge lost when person leaves	System stays on your infrastructure. You own it. No access cutoff, no data loss.
Key person risk	Added person becomes a dependency. Their knowledge walks out the door if they leave.	System holds the obligation register, the deadlines, the contract knowledge. Survives any individual departure.
Biggest risk	Wrong hire, slow ramp-up, or departure before value is recovered	Team adoption. System only returns value when PMs use it consistently.

When Is Hiring Still the Right Answer?

This is the part of the comparison that matters most, because the answer is not always the same.

Hiring is the right answer when your current PMs are already running at full advisory capacity and the gap is genuinely about project count and geographic coverage. If your team is well-supported, spending 80% of their time on advisory work, and you have more projects on the table than they can cover even with that efficiency, you need another person. The system cannot be in two places at once, and a client relationship requires a human contact.

Hiring is also the right answer when you need specific expertise that does not exist in your current team. A specialist in alliance contracting, or someone with deep FIDIC experience for an international project, or a senior QS who can run a commercial function that your current team cannot cover. These are capability gaps, not capacity gaps. Systems do not fill capability gaps.

And hiring is the right answer when your growth trajectory is clear enough that you need to build bench depth. A firm that is going to double its project portfolio in 18 months needs to start hiring now, not after the projects land. That is a strategic decision about the business, not a response to a current capacity crunch.

If the reason you are considering hiring is "we are stretched and things are getting missed," that is a systems problem, not a headcount problem. Adding another person into a firm where things are getting missed because of poor tracking and administrative overhead does not fix the system. It adds another person to the same broken system.

When Is the System the Better Answer?

The system is the better answer when your current PMs are capable but consumed by administrative work. When they are managing two or three contracts each but spending a third of their week on tracking and reporting instead of advising. When the quality of their output on each project would be higher if they had more time to think rather than time to type.

It is the better answer when the capacity crunch is cyclical rather than structural. Construction project loads are not linear. A firm might be at capacity for six months and then have gaps. Hiring a senior PM on a $180K salary to cover a cyclical peak is a commitment you carry through the trough. A system scales with the portfolio.

The system is also the better answer when your PI exposure is a consideration. Every additional person adds a point of failure for obligation tracking. A junior PM who misses a claim notice deadline under a special condition that tightened the standard NZS 3910 timeframe can generate a liability that exceeds the firm's fee on the entire engagement. The system tracks every obligation, every modified timeframe, every special condition, across every contract in the portfolio. That consistency does not waver when someone is overloaded or on leave.

As discussed in our article on scaling a PMC firm with AI project intelligence, the firms that build durable capacity advantages are the ones that invest in the infrastructure to support their people, not just the headcount itself.

What About the Hybrid Approach?

The most effective approach for most PMC firms is the hybrid: deploy the system, recover capacity, then make a hiring decision based on what is still genuinely outstanding after the system is running.

Here is why this sequence matters. When you hire before deploying the system, the new PM joins a firm where 14 hours per week of everyone's time still goes to admin. They inherit the same overhead. You have spent $180K-$250K per year and recovered 26 hours of advisory capacity. When you deploy the system first, you recover 10-14 hours per existing PM per week. With a six-person team, that is a substantial capacity return in weeks, not months. You then hire based on what is genuinely needed after the system is running, which is usually a smaller hire, a more targeted one, or a hire you make six months later when the business is in a stronger position.

The hybrid approach also changes what you hire for. Once the system is handling the administrative overhead, you can hire specifically for advisory capacity, business development, or specialist expertise. You are not hiring to cover the same administrative functions that the system now handles. The quality of the hire improves because the role is clearer.

How Do You Make the Call?

Three questions will clarify this for most PMC directors:

First: where is your current team's time actually going? If you tracked a week of each PM's activity, what percentage is genuine advisory work versus administrative overhead? If the answer is below 60% advisory, you have a systems problem that hiring will not fix. See our diagnostic on why your best PMs are doing $50/hour work.

Second: what is the nature of the capacity gap? Is it that your existing PMs cannot take on another project because their advisory time is fully committed? Or is it that they are overloaded but still managing because they are working longer hours to cover the admin? The first is a headcount gap. The second is a systems gap with overtime as the band-aid.

Third: what is your risk tolerance on quality consistency? A new hire brings capability uncertainty. A system brings consistency. On a $60M NZS 3910 project, the cost of a missed obligation, a misdirected notice, or a lapsed deadline can be measured in hundreds of thousands of dollars. The system eliminates the category of error where an obligation was simply not tracked. The new hire does not.

The PMC firms that are growing without proportionally increasing headcount are not doing it through heroic effort from their existing team. They are doing it by building the infrastructure that lets their existing team work at full advisory capacity, on more projects, with a higher quality floor and lower PI exposure than their competitors.