A business owner I talked to last year was about to hire a second office manager. The workload had grown, things were slipping, and the obvious answer was another person.

Before she posted the job, we spent 45 minutes looking at what her current office manager actually did. Scheduling, follow-up emails, invoice tracking, data entry, reporting. Of the 40 hours a week in that role, roughly 28 were tasks that could be automated or handled by AI.

She did not hire. She automated the 28 hours, shifted her existing person to higher-value work, and saved about $55,000 a year.

That is not a story about replacing people. It is a story about asking the right question before making a major decision.

The Five Questions

Before you post any job, work through these:

1. What specific tasks are creating the need to hire?

Get granular. "Things are falling through the cracks" is not an answer. List the actual tasks. If you cannot list them, you are not ready to hire — you are just reacting to stress.

2. Of those tasks, which ones are repetitive and rule-based?

Repetitive and rule-based means it follows a pattern. The same steps, the same inputs, the same expected output. Data entry. Sending follow-up emails. Generating weekly reports. Scheduling. These are candidates for automation.

3. What does the remaining work actually require?

What is left after you separate out the repetitive tasks? Judgment calls, relationship management, problem-solving, things that require context and nuance — that is what humans are for. Is there enough of that remaining work to justify a full-time hire?

4. What would it cost to automate the repetitive parts?

A Zapier subscription is $20-100/month. A VA handling overflow is $500-1,500/month. A full-time employee is $40,000-80,000/year plus benefits, onboarding time, and management overhead. The math is usually not close.

5. Is the problem actually a process problem, not a capacity problem?

Sometimes businesses are not short on people — they are short on process. Adding another person to a broken workflow just gives you two people doing things the slow way. Fix the process first.

When You Should Actually Hire

This is not an argument against hiring. Some work genuinely requires a person. When the task demands relationship, judgment, creativity, or accountability — hire.

But hire for that work specifically. Not to absorb the administrative volume that should have been automated two years ago.

The businesses that get this right hire fewer people and pay them better. The people they do hire are doing work that matters, not filling in for systems that should have been built.

One More Thing

The expensive mistake is not always hiring when you should have automated. Sometimes it is automating when you needed a person — and now you have a system that produces the wrong outputs at scale, with no one accountable for fixing it.

If you are genuinely uncertain, it is worth getting a second perspective before you commit either way. That decision — hire or automate — is exactly what the Hiring Audit is designed to answer.