The start of a new financial year is when most founders plan their hiring. Headcount feels like strategy. A bigger team feels like progress.
And sometimes it is, but more often than founders realise, hiring is the most expensive answer to a problem that has a cheaper solution.
There is a moment most service-based businesses arrive at, usually somewhere between 5-15 staff, where the obvious answer to most problems starts to be "we should hire someone." Things are stretched. The team is busy. The founder is busier. So the next logical step is more people.
This post is about the audit worth doing before you hire, why most hires are not actually fixing the problem founders think they are, and what to do instead.
The Most Expensive Way to Solve a Process Problem
A hire is not just the salary. The full cost of a hire, once you include onboarding, training, the slowdown to existing staff, the management overhead, and the time it takes for the new person to be productive, is usually two to three times the headline number for the first year.
That is real money. It is also worth it when the hire is the right answer.
It is not the right answer when the underlying problem is operational. If the team is stretched because the processes are inefficient, hiring more people into the same inefficient processes does not fix the stretch. It scales it. You now have more people doing the same broken work, with more coordination overhead, more communication channels, and more places for things to fall through.
This pattern is so common that I think of it as the default. Most founders, faced with operational stretch, hire first and fix processes later. The order is almost always wrong.
The Audit Worth Doing Before You Post the Job
Before you hire, run this audit. It takes about a day, and it is the cheapest insurance you will buy this quarter.
Step one. List the work the new hire would do. Be specific. Not "marketing support." What would they actually do on a Monday? On a Wednesday? On a Friday afternoon?
Step two. For each task, ask three questions. Could this be eliminated without anyone noticing? Could this be done more efficiently with a small process change? Could this be done more efficiently with a tool you already have?
Step three. Count what is left. Whatever survives those three questions is real work. That is what the new hire would be doing. If the volume of real work is enough to justify the role, the role makes sense. If it is not, you have a process problem, not a capacity problem.
This audit reliably reveals that 20 to 40 percent of an imagined role is not actually new work. It is existing inefficiency that the hire would absorb, but that could be removed for free with a process change.
When Hiring Is the Right Answer
There are absolutely times when hiring is the right call. The audit is not designed to prevent hiring. It is designed to make sure the hire is solving the right problem.
The clearest signs that a hire is the right answer:
The work is genuinely new, not existing work being done inefficiently. A new service line, a new function the business has not had before, a capability gap rather than a capacity gap.
The work is full-time, ongoing, and at a level of consistent volume. Not a once-a-quarter project that has been frustrating.
The processes the new hire would inherit are reasonably documented. They will not spend their first six months trying to reconstruct how things work because nobody wrote it down.
The economics make sense, accounting for the real cost of the hire, not just the salary.
If all four are true, hire. The audit will have confirmed it, and the new hire will succeed faster.
An Example
A six-person professional services firm was about to hire their seventh team member, a "client services coordinator" to manage the growing administrative load that the practice manager could no longer absorb on her own.
The audit revealed three things.
First, about a quarter of the imagined role was scheduling work that could be substantially automated using a feature in the booking system they already paid for. Second, another quarter was follow-up communications that could be templated, with the practice manager triggering them rather than writing them from scratch. Third, about a third was triage of incoming enquiries, which had grown beyond the practice manager's capacity, and was genuine new work that needed someone to own it.
The result was that the firm hired a part-time coordinator focused on enquiry triage and intake, not the full-time generalist role they had been about to post. The total cost of the role was less than half what the full hire would have been. The practice manager got her capacity back. The new hire was set up to succeed because their role was focused and the processes were documented before they started.
One day of audit work changed the shape of the hire, and the outcomes for everyone involved.
What to Do Instead of Hiring
If the audit reveals that the work is mostly inefficiency rather than genuine new capacity needs, here is the order of operations.
First, eliminate. Remove anything that is not adding value, even if it has always been done.
Second, automate. Apply the three criteria: repeated, mechanical, cheap to test. The fixes are usually small and pay back quickly.
Third, document. Make sure existing processes are written in a way that lets the team move without asking the founder every five minutes.
Only then, if the work still exists after eliminating, automating, and documenting, hire.
Most founders skip the first three steps and start at the fourth. That is what the audit is designed to interrupt.
Next Steps
If you are planning a hire in the next quarter, an Operations Review is the audit, structured. We map the work, identify what could be removed or automated, and tell you what the genuine capacity gap is before you commit to a role.