When Every Rise in Workload Needs Another Hire

The tolerated pain

Volume rises, queues grow and the immediate answer is another person. That can work, but if the underlying work is repetitive coordination, re-keying, chasing, reconciliation or status administration, each growth step permanently raises the cost base.

The pattern is easy to miss because every individual hire is reasonable. The order desk is behind, so a coordinator is added. Supplier queries are piling up, so an administrator joins finance. Customer onboarding is slow, so operations gains another pair of hands. Each decision solves a visible backlog. Taken together, they describe a business whose administrative capacity can only grow by adding salaries.

Why businesses tolerate it

Hiring is familiar, quick to approve and easy to explain. A new employee can start relieving pressure within weeks, while redesigning a process means stopping to understand how the work actually moves, which systems hold which data and where effort is being wasted. Under pressure, the hire wins.

There is also a measurement gap. Most businesses track headcount and payroll, and many track volume, but few divide one by the other for a specific process. Without that ratio, nobody can see whether the business is getting more efficient as it grows or simply bigger. The problem is often described as a capacity shortage when it is really a design limitation, which is the pattern explored in why growth breaks systems that worked when the business was smaller.

Operational consequence

When people are the only scaling mechanism, the process inherits every weakness of manual work:

• Coordination load rises faster than headcount. More people handling the same flow means more handoffs, more messages asking for status and more meetings to keep everyone aligned.
• Knowledge fragments. Workarounds live in individual heads, so quality depends on who handled the transaction.
• Errors scale with volume. Re-keying data between systems produces a roughly constant error rate, so more transactions mean more corrections, credit notes and customer queries.
• Management capacity is consumed. Every new team member needs supervision, training and performance management, pulling experienced staff away from the work itself.
• Response to demand is slow. A recruitment cycle takes weeks or months, so backlogs build before the new capacity arrives and linger while the new person learns.

Financial consequence

The primary mechanism is operating leverage. If transactions grow 20% and the process needs roughly 20% more labour to remain stable, the business is scaling activity rather than capability. Recruitment, management, training and error-handling costs compound the payroll increase.

labour cost per transaction = total loaded labour cost for the process ÷ completed transactions

Track this over time. A healthy redesign should allow volume to rise without equivalent growth in administrative labour. If the figure is flat or rising while volume grows, the process has no leverage.

Loaded cost matters here. Salary is only part of what each hire costs. In South Africa, SARS sets the employer Unemployment Insurance Fund contribution at 1% of remuneration, capped at R177.12 a month for employees earning above R17,712, and the Skills Development Levy at 1% of total salaries for employers whose annual payroll is expected to exceed R500,000. Retirement contributions, equipment, software licences and workspace then sit on top.

A worked cost model

The following model is entirely illustrative. Every input is an assumption chosen to show the arithmetic, not a benchmark. Replace each one with your own figures.

Today: 4 × R32,657.12 = R130,628.48 a month. Divided by 6,000 transactions, labour cost per transaction is about R21.77.

Growth by hiring: volume rises 20% to 7,200 transactions. At today's productivity that needs 4.8 coordinators, and because people are hired whole, the business adds a fifth. Monthly cost becomes R163,286.40 and cost per transaction rises to about R22.68. A second 20% step to 8,640 transactions needs 5.76 people, so a sixth is hired: R195,943.68 a month, still about R22.68 per transaction. Volume has grown 44% and unit cost has not fallen at all.

The one-off cost of each hire: assume an illustrative recruitment cost of R30,000, a new hire working at half productivity for two months (R32,657.12 of unproductive cost) and an experienced colleague spending 20% of their time training for those two months (about R13,062.85). Each hiring cycle costs about R75,719.97 before the new person is fully effective, or about R151,439.94 for the two hires.

Growth after redesign: now assume an illustrative finding that 35% of coordinator time goes on re-keying, chasing and status updates that integration and routing could remove. The same four people could then handle about 9,231 transactions a month (6,000 ÷ 0.65), so both growth steps are absorbed without hiring. At 8,640 transactions, cost per transaction falls to about R15.12.

The difference between the two paths is two loaded salaries, about R783,770.88 a year, plus roughly R151,439.94 in one-off hiring costs. That figure is before the cost of the redesign, which must be estimated honestly and set against it. It is the arithmetic of the example, not a promise of savings.

Secondary consequences

The cost does not stop at payroll. Each extra person adds identity accounts, devices and licences to manage. Larger teams need more management layers. And because labour is a largely fixed cost once hired, a business that scaled through people carries that cost even if volume later falls, which weakens margin in a downturn exactly when protection matters most.

Commercial urgency

The urgency is highest at three moments: when a growth plan or budget assumes headcount will rise with volume; when a team asks for another hire for work it describes as admin, chasing or capturing; and when margin is falling despite revenue growth. Each is a point at which the next salary commitment can still be questioned. As IBM describes business process automation, the aim is to reduce reliance on manual processes so that workflows become easier to manage and scale. The cheapest time to test that is before the next recruitment cycle starts, not after it.

The same pattern appears from different angles in why revenue growth requires more admin staff and why routine admin expands as the business grows. Before the next hire is approved, it helps to establish how much of the team's time goes on coordination and re-keying, and how to find the manual work nobody is measuring offers a practical way to start.

Sources and further reading

• Unemployment Insurance Fund - South African Revenue Service (last verified 10 October 2026)
• Skills Development Levy - South African Revenue Service (last verified 10 October 2026)
• What Is Business Process Automation? - IBM (last verified 10 October 2026)

Related Mellorca reading

• When Every Process Problem Becomes Another Software Purchase
• The Cost of Retyping Customer Details into Every System
• Predictable Appointments Still Carry a Cost When Staff Arrange Every Slot

Do not automate judgement

The objective is not fewer people at any cost. Separate work requiring expertise, relationships and decisions from work caused by poor handoffs, duplicate entry, manual routing and fragmented systems.

What better looks like

Standard work is visible, routine routing is automated where appropriate, data is captured once, exceptions are explicit and people spend more time on decisions than administrative movement.

Practical actions

1. Measure transaction volume, cycle time and labour hours for the process.
2. Classify steps as judgement, exception, coordination, data entry or waiting.
3. Remove unnecessary steps before automating.
4. Integrate systems where re-keying creates recurring labour.
5. Track labour cost per transaction after each change.

Bottom line

Headcount growth is not inherently inefficient. Headcount that must rise in lockstep with repeatable administrative volume is a warning that the operating model has weak leverage.