Do You Actually Need to Hire? (Hire, Outsource, or Automate)

A guy who runs a 14-person landscaping company called me last spring, frustrated. His office manager had quit, the phones were a mess, and he'd already written a job posting. He wanted my help screening candidates.

I asked him one question before we touched the posting. "What did she actually do all day?"

He went quiet. Then he started listing tasks. Answering phones. Scheduling crews. Sending invoices through software he'd bought two years ago and never fully turned on. Filing paperwork that, when I pushed, he admitted nobody ever looked at again.

By the end of that call, he didn't need to hire an office manager. He needed to turn on the invoicing automation he'd already paid for, hand the scheduling to his lead foreman who wanted more responsibility, and use a part-time answering service for the phones. He saved himself a $48,000 salary plus benefits, and he solved the actual problem in about a week.

The Problem: You Feel Pain, So You Post a Job

In my 25 years training small-business owners to hire, I've watched the same reflex play out over and over. Something breaks. Someone quits, sales spike, a process falls apart, and the owner feels the pain in their gut. The very next move is to write a job posting.

That reflex is expensive. When you add a permanent employee, you sign up for far more than one salary. You take on that salary every year, plus payroll taxes, plus benefits, plus the time you'll spend managing that person, plus the cost of replacing them if it doesn't work out.

Here's a number worth keeping in your head. For private-industry workers, benefits add roughly 30 percent on top of wages, according to the U.S. Bureau of Labor Statistics (December 2025 data) (BLS, 2026). So a "$50,000 hire" is really a $65,000-plus commitment before you've factored in your own time. A full-time hire is the heaviest, most permanent, most expensive tool in your toolbox. Reaching for it first, every time, is like buying a dump truck because you need to move a wheelbarrow of dirt.

And the stakes go up when you rush. Gallup found that companies pick the wrong person for management roles 82 percent of the time (Gallup, 2018). Most of those misfires start way upstream, when nobody stopped to define what the role actually needed to be. A bad hire doesn't just cost you the salary. It costs you the real damage of a wrong hire and the full price of replacing that person when it falls apart.

So before you write a single word of a job posting, you have to prove the role is real.

The Framework: Prove the Role Before You Post It

This is Phase 1 of my 10-Phase Hiring System. I call it Evaluate the Need, and it's the phase almost everybody skips. Get this one right and the other nine get easier. Skip it and you'll feel it for years.

Here's how I walk owners through it.

Step 1: Write Down the Actual Work

Not the job title. The work. Forget "office manager" or "sales rep" and list every concrete task that needs doing, with rough hours per week next to each one.

When you do this honestly, two things usually happen. You find tasks that don't need a human at all anymore. And you find that what felt like a full-time job is actually 15 real hours of work surrounded by habit and busywork.

Step 2: Ask the Three Questions

For every cluster of tasks on that list, ask:

Does this need to be done at all? Some of it is leftover. A report nobody reads. A process built for a problem you no longer have. Kill it and the "need" shrinks.

Does this need to be done by a new person? Or does someone on your team already want to grow into it? Promoting from within is faster, cheaper, and you already know the person.

Does this need to be done by a person at all? A lot of repetitive work (invoicing, appointment reminders, follow-up emails, payroll) is now handled by software you may already own.

Step 3: Walk Through the Alternatives, In Order

A full-time hire is the heaviest tool you have. Run the cheaper options first and see if any of them solve the problem.

Fix the broken process. Half the time the pain comes from a broken workflow, not a missing person. A messy process creates chaos and makes you feel understaffed. Adding a body to a broken process just gives you a more expensive version of the same mess.

Redistribute the work. Can two people each take on a few hours of high-value work they'd actually enjoy? This works when the total new workload is small and your team has capacity.

Use overtime for a short spike. If the pain is temporary (a busy season, one big project), paying overtime for a few weeks is far cheaper than a permanent salary you'll be carrying in the slow months.

Bring in a contractor or fractional pro. Need bookkeeping, marketing, or HR help but not 40 hours of it? A fractional or part-time contractor gives you the skill without the full salary, the benefits, or the long-term commitment. This is the right call when the work is specialized but not constant.

Automate it. If the task is repetitive and rule-based, software does it cheaper and more reliably than a person ever will. Look hard at the tools you already pay for before you buy anything new. Like my landscaper, you may already own the solution.

Step 4: Look For the Signals That You Genuinely Do Need a Hire

Sometimes the answer really is yes, hire. Here's what that looks like:

The work is full-time, ongoing, and not temporary. It's still there in your slow season.

The work requires judgment, relationships, or presence that a contractor or software can't give you. Think a salesperson who owns client relationships, or a foreman who runs a crew on site.

Redistributing it would burn out your best people or pull them off higher-value work.

The cost of leaving it undone is climbing every week. When a role sits empty too long, the damage compounds. I wrote about the hidden cost of leaving a role open, and it's real.

When you hit those signals, you hire with confidence, because you've proven the need instead of guessing at it.

The Action: What to Do Monday

1. Pull out a blank sheet and list every task the "needed" role would cover. Put estimated weekly hours next to each one. Be honest, not aspirational.

2. Cross off everything that doesn't need doing anymore. Watch the role shrink.

3. Mark each remaining task with one of four letters: P (a person on your team could take this), C (a contractor or fractional pro fits), A (automate it), or H (this genuinely needs a new full-time hire).

4. Tally the H's. Add up the real weekly hours that landed in that column. Under 25 hours? You probably don't need a full-time hire yet. Look at part-time or contract.

5. Check the software you already own before buying anything. Log in, read the feature list, call their support. You've likely paid for tools you never switched on.

6. If you still land on "hire," run the math out loud. Salary, plus 30 percent for benefits and taxes, times the years you'll carry it. If the number still makes sense, you've earned the right to post the job. Our bad-hire calculator can show you what the downside looks like if you get the person wrong.

The Thread: This Is Where Good Hiring Starts

Here's why I make every owner I work with do this first. The most expensive hiring mistakes don't happen in the interview. They happen before it, when you commit to a role you never proved you needed and then go shopping for a person to justify it.

That's how desperation hiring gets started. You feel the pain, you skip the diagnosis, you post the job, and three weeks later you're hiring the first warm body who applies because the pressure won't let up. Then you're paying the replacement cost a few months down the road.

Evaluating the need is Phase 1 of my 10-Phase Hiring System for exactly this reason. Every phase after it (writing the role, sourcing, screening, interviewing, checking references) only pays off if the role itself is real. Build on a shaky foundation and the whole hire wobbles.

I cover all of this in depth in The Naked Interview, but you don't need the book to start. You need a blank sheet of paper and the discipline to ask one question before you ever write a job posting: do I actually need to hire?

Most of the time, when you really look, the answer surprises you. And the times the answer is a clear yes, you'll hire from a position of strength instead of panic. That's the whole game.