Hire, Augment, or Automate: The Decision Most CEOs Make Backward

For a long time, a capability gap and a headcount gap were one and the same. Something needed doing, nobody had time to do it, so you wrote a job description. The logic held because no other option cleared the bar.

Two other options clear it now. You can automate the work, or you can borrow the expertise for a few months instead of hiring it permanently. AI made both cheaper and faster in about two years. Hiring stayed exactly as slow and as permanent as it has always been, and most leaders still reach for it first.

Telling the three apart before you commit to one is the skill worth building. The signals are clearer than you might expect.

Most Gaps Get Described as a Person, Not a Problem

Leaders can answer “who are we hiring” in one sentence. Ask what that person fixes in their first six months and the answer takes noticeably longer to arrive. That second answer decides whether you need a person at all.

“Historically, it’s just been a role. I need a front-end developer. I need a QA person,” said Chris Howard, President at Slingshot. “We’d get much further if they walked us through the problem they were trying to solve.”

A job title is a solution wearing the costume of a request. It shows up pre-answered, which is why it clears a leadership meeting so quickly. Nobody argues with a req. The fix here is nearly free. Describe the gap as work rather than as a person, and all three options stay live long enough to compare.

“When you write out a job description, you’re documenting what the tasks of that job actually are,” said Doug Compton, Director of AI Engineering at Slingshot. “That’s the same starting point you need if you want to make somebody more efficient instead.”

So the document itself was never the problem. Write it early, read it as an inventory of the work, and it tells you what you could automate and what you could hand to an outside team. Leave it until last, and it just tells HR what to post.

The Real Cost of a Hire Starts Long Before Day One

Two clocks start when you approve a req, and neither one starts on the new hire’s first day. The first runs from the decision to the signed offer. The second runs from that offer to when the person actually starts the work.

“The hiring process itself takes months before anyone even starts,” Doug said. “Then the first two weeks, they’re just learning the system, the product, the business logic. It’s usually three to six months before they know the ins and outs of what they’re working on.”

If you decide in January that you need a senior developer and you won’t start seeing meaningful output until somewhere in the back half of the year. Payroll, meanwhile, started months earlier, and Chris puts benefits and everything else a company provides at roughly 30% on top of salary.

The harder cost is what those same months buy you if you chose wrong.

“When you hire somebody, it’s probably the most important move you make as a company,” Chris said. “If you make the wrong move, it takes several months, maybe a year, to figure that out. And then it’s painful to change. Meanwhile you’ve spent a lot of money on someone who didn’t pay off.”

Both clocks run at the same speed whether the hire works out or not, which is why Chris keeps returning to flexibility as the underrated advantage of outside help. Moving on from a contract stings. Moving on from a bad hire costs far more.

AI Raised the Bar on Hiring Instead of Lowering It

Everyone gets the same tools. A strong hire uses them to speed up the people around them. A weak one just produces more of what they were already producing.

“AI has made hiring the right person even more important,” Chris said. “You still want the senior background. But you want them plugged into the AI world, because that combination will accelerate what you already have going.”

Every role that existed a few years ago now touches AI somewhere, and the people worth hiring know it. “We’re highly unlikely to hire anyone in almost any role who doesn’t at least want to lean on artificial intelligence,” Chris added. “Marketing, sales, software development, design. It’s across the board.”

He’s also watching entry-level and mid-level roles thin out, including junior developer roles. Those first jobs get harder to land every year. A new graduate who’s gone deep on AI stays interesting in almost any function. One who hasn’t touched it faces a genuinely difficult market.

Doug flagged a second shift, and it reorders the decision itself. “AI has made everybody more efficient,” he said. “So now we look first at whether we actually need a new person, or whether we can make the people we already have efficient enough to absorb it.”

Same gap. Same company. Different answer than 2023 would have given.

Automation Gets Cheap Where the Work Repeats and the Data Is Ready

Two things mark a gap as automatable. The work repeats, and the data behind it is already reachable. Chris starts with repeatability and admits a bias, since he automates whatever he dislikes first. Doug backs that instinct, because clearing the tasks people resent lifts morale and frees experienced people to spend their day on what they actually know.

Access is the harder test. “Does the AI have access to everything the person doing that job has access to?” Doug asked. “And is it safe to give it that access?” Sometimes the honest answer is no.

Chris offered an example from inside Slingshot. “We would badly like to turn on the Google Drive connector in Claude,” he said. “It would help a lot of people. But we haven’t done the homework yet to be confident we can do it safely, so it stays off.” The distance between wanting a connector and being ready for one is real work, and it almost never lands on anyone’s roadmap.

The vendors won’t flag it for you. “A lot of AI tools default to giving the model access to everything,” Doug said. “They overreach right out of the box, and they give you no good way to rein it in.”

Which brings up “free,” a word that follows automation around and rarely earns it. A few automations really are close to free, like an inbox monitor that pings someone when a message needs attention. Others hide the bill in custom tools that have to get written and then hosted. Chris adds the line items no vendor will quote you: mapping how the work happens today, retraining everyone around the new workflow, and the real chance somebody leaves over it.

Augmentation Buys Expertise Faster Than You Can Hire It

Augmentation usually gets framed as a stopgap you run until you can hire properly. The more useful version aims for the opposite outcome: the engagement ends, and the capability stays.

“If you have a couple of champions inside your organization who just need training or direction, that’s exactly when it makes sense to pull in an outside company,” Doug said. “You’re accelerating their learning, and you’re building that expertise into your own employees.”

Two conditions make the math work, and AI meets both right now. The skill costs too much to buy permanently, and it moves too fast to grow on your own. “It might be cost-prohibitive to hire somebody who’s an expert in that field,” Doug said. “So you augment, bring in the expertise, and you only have them temporarily.”

Speed of change is the harder condition to solve by hiring. Whoever you bring on has to track a field that rewrites itself every few months, and they’re doing it between the rest of their job. “An outside company might be living and breathing that technology,” Doug said. “They’re constantly up to date with the latest. You tap into that expertise as needed.”

Chris framed the payoff differently. “Augmenting with people who know AI can be a catalyst,” he said. “They show your team the way.” A catalyst speeds up a reaction without being consumed by it. That’s the test worth applying before you sign anything, because an engagement that leaves nothing behind was staffing, not augmentation

Some Gaps Still Deserve a Full-Time Hire

None of this argues for a hiring freeze. Chris hires when the work isn’t going away and doing it well takes real expertise. Both have to be true.

Doug adds a harder case. “In a very niche area, there isn’t much information for the AI to train on,” he said. “Your expert may simply know more than the model does.” Leading-edge work behaves the same way, because the knowledge is too new for any model to have absorbed it. Hire the person who can reason it out.

What’s changing is the shape of the role you’re filling. Titles are merging, descriptions cover wider ground, and AI fluency is becoming a requirement across functions. So Chris evaluates candidates against a longer horizon.

“I think about what this job looks like two years from now,” he said. “You can’t predict the future, but you can feel where things are heading. You want someone who’s going to evolve with it.”

Doug’s last check happens before you post anything, and it points inward rather than at the market. “Have you done everything you can to train up and support the people you already have?” he asked. “Hiring is a long-term commitment. Do that due diligence first.” Answer that one honestly, and you’ll know whether you’re closing a gap or just adding a person to it.

Run the Options in the Right Order

Most people never ranked the three options by cost, and that is the whole problem. Hiring takes the longest, commits the most, and corrects the slowest, yet it goes first because a gap instinctively looks like a missing person.

Flip the sequence. Describe the work instead of the title. Check whether the task repeats and whether your data is ready, since that is the cheapest close when the answer is yes. Borrow expertise when the skill moves faster than you can hire or grow it. Then hire deliberately for the durable, specialized gaps that remain, with a clear picture of what that role becomes two years out.

The job description sitting in your drafts folder is not the wrong document. It is just answering a question nobody asked yet.

Slingshot