The job description usually gets written on a Sunday. Third attempt, and the list of duties keeps growing, because it has stopped being a description of a role and turned into a list of everything that has been getting dropped. Answer the phone. Chase the outstanding quotes. Keep the spreadsheet up to date. Put the figures together at month end. Somewhere near the bottom, almost as an afterthought, help with the actual work.
What the duties list is telling you
Read it again and put one question to every line. Would you interview anybody for this? Would you shortlist on it, ask about it at the table, check a reference against it?
Nobody interviews for retyping a quote out of an email and into a system. Nobody checks a reference on keeping a spreadsheet current. Those lines are there because the work exists and has nowhere to go, not because they describe somebody worth hiring.
The lines you would genuinely interview for are the role. Everything else is the job you are about to pay somebody to inherit, and it is worth asking why that work is not already where it needs to be before the advert goes out.
Capacity and friction are different problems
Hiring solves a capacity problem. There is more work than there are hours, the work needs a person to do it, and the only way through is another pair of hands.
Friction is a different shape. Everybody is busy, the week is full, and the amount of real work that comes out of it is thin. The hours are going somewhere, but not into anything a customer would pay for. When people are visibly flat out and the output does not match, a new person joins the same friction, and you get a fraction of them back.
The three places the hours go
Handling. The quote that arrives by email and gets retyped into the system. The form that comes in as a PDF and gets keyed in by hand. The same address typed four times in one job.
Waiting. Work that cannot start until somebody replies, sitting in a queue nobody can see. The job that sat four days because one answer was outstanding and nothing flagged it.
Redoing. Work done twice because the first version went missing, or because the figures moved after it was finished. The report rebuilt from scratch every month because it was never set up to update itself.
None of the three feels like waste while you are doing it. All of them feel like working.
What a new person inherits
A new hire arrives into whatever is already there. For the first stretch they are slower than the person training them, and the training comes out of that person’s week. If most of the list is work you would never have interviewed for, you have taken on a salary so that the same information can be moved by hand, slightly faster, by somebody who also now has questions.
That is not an argument against hiring. It is an argument for knowing which of the two problems you are solving before you commit to a wage.
When hiring is the right answer
Often. Where the work needs judgement, a relationship, a pair of hands on site or somebody physically present, no amount of software covers it. Where demand has genuinely grown and the process underneath is already clean, you need people.
We say this more often than people expect. Somebody arrives convinced they should automate their way out of a hire, and the honest answer after looking at the work is that the process is fine and they are simply at capacity. Automation does not help there, and saying so is cheaper for everybody than finding out in month three.
The half you can take back first
Start with the task that happens most often, not the one that takes longest. The hour-long monthly job is satisfying to fix and barely moves your week. The four-minute job that happens eleven times a day is the one quietly eating the afternoon.
For that one task, answer four questions.
- What starts it? Something has to trigger it: a form, an email, a date in the calendar.
- What information does it need? Every field, including the ones somebody has to go and look up.
- Where does that information already live? If the answer is a system you already pay for, this is the easy case.
- What comes out at the end? A record, a document, a message to somebody.
If all four have a clean answer, the task is a candidate. If one of them comes back as “it depends who picks it up”, the problem is not the tooling yet. That one is a decision rather than a purchase, and it is the step most people skip.
What changes, and what does not
When this works, the handling goes and the judgement stays. The phone still gets answered by a person. The quote still gets priced by somebody who knows the job. What stops is the retyping, the chasing for information that already exists somewhere in the business, and the monthly rebuild of the same report.
The week does not get emptier. It gets less fragmented, which is the thing that actually decides how much comes out of a day.
Where our audit comes in
Our AI audit is a structured look at how work arrives and what happens to it afterwards. We map where the hours go, say where automation would pay for itself and where it would not, and tell you plainly when the answer is a person rather than a system.
It starts with a free discovery call. Answer five questions about how your business works, and we will come back with what we would look at first.
