How to Answer "Are You Here to Replace My Staff?"

The objection that rarely gets said out loud, and why arguing the economics loses the room.

August 30, 2026

Read Time: 7 minutes

Artificial intelligence has now been the leading stated reason for US job cuts for five straight months running.

In July, employers attributed just under eleven thousand redundancies to it. Across the year so far it accounts for more than a fifth of every announced layoff, already well past the total for all of 2025.

Your prospect has read those headlines. Or his operations manager has. Or his wife has.

Now here's the number nobody puts next to it. The NBER surveyed nearly six thousand executives across four countries and found that more than nine in ten reported no effect on employment at their own firm over the past three years.

Both things are true at once. The headlines say one thing and the actual data from inside businesses says something else entirely.

You are walking into that gap every time you take a first meeting.

It Usually Doesn't Get Said Out Loud

Here's the first thing to understand. You will rarely get asked this question directly.

Owners are not going to sit across from you and say "are you here to cut my staff." It's too blunt, it makes them look either callous or frightened, and most of them haven't fully worked out their own position on it yet.

So it arrives disguised.

"Let me talk to the team first."

"I think we're a bit early for this."

"Can you send the proposal over and I'll come back to you."

Or it doesn't arrive as words at all. The operations manager who was engaged for twenty minutes goes quiet. The meeting that was moving forward suddenly needs another meeting. A deal that should have closed sits at ninety percent for three weeks.

If you can't name what's happening, you'll assume it's a pricing problem and start discounting a deal that was never about price.

Why Arguing the Economics Loses

The instinct, when you finally do hear it, is to defend.

You reach for the case, because you have one. Payroll versus software cost. Hours recovered. The efficiency gain. All of it is accurate and all of it makes things worse.

Because the moment you argue the economics of headcount, you have confirmed exactly what he was afraid of. You are the person who has turned his team into a line item, and you did it inside ten minutes of meeting him.

I've written before that you never argue with a prospect. Agree, validate, then expand the frame with a genuinely curious question. That applies to the "we're already using ChatGPT" objection I covered a few weeks ago, and it applies twice as hard here, because this one isn't a commercial objection at all. It's a personal one.

The owner asking it employs thirty people he knows by name. Some of them have been with him a decade. He has probably told them, out loud, that nothing is going to change.

What to Say

Something close to this. Adjust it to sound like you.

Agree first, and mean it.

"That's a fair thing to be thinking about. It's the first place most owners go, and honestly it's the right instinct."

Then validate the thing underneath it.

"You've built a team here. I'm not walking in on day one to tell you which of them you don't need."

Then expand the frame with a question you actually want the answer to.

"Can I ask you something. If your team got a day and a half back every week, what would you want them doing with it?"

That question does the work, and it does it without you having made a single claim.

Because he has to answer it, and the answer is almost never "I'd let them go." It's the backlog. It's the accounts nobody has time to call. It's the quotes going out four days late. It's the thing he's been meaning to do for two years.

He has just told you, unprompted, what the capacity is for. Now you're both on the same side of the table looking at the same problem.

The Two Ways to Look at the Same Business

There's a decision underneath all of this that most owners have never consciously made, and it's worth putting to them plainly.

Any capacity gain can be taken one of two ways.

As a cut. Same output, fewer people, lower cost. That's a real option and some businesses genuinely need it.

As expansion. Same people, more output, higher revenue and higher profit. Growth rather than contraction.

The technology is completely indifferent to which one he picks. It's a business decision, not a technical one, and it belongs to him.

Saying that out loud is one of the most useful things you can do in a first meeting, because it hands him back the authority he thought you were taking. You're not there to make the call. You're there to make the call possible.

Most owners, when they actually stop and choose, choose growth. Cutting is what you do when you're out of ideas. Expansion is what most of them got into business for.

The Bottleneck They Haven't Named

Here's the argument that lands hardest with an owner, and almost nobody makes it.

Recruiting is expensive, slow and unreliable, and it's a cost they feel every single month.

Ask any owner of a fifty person business what's actually holding them back and hiring will be in the top three. The advertising spend. The agency fee. The three months of someone at sixty percent output while they learn the systems. The one in four who doesn't work out and puts you back at the start.

If the existing team can absorb more work, that entire process gets postponed. Not one role. The next several.

That's not a headcount reduction. It's a headcount deferral, and it shows up in profit without anybody losing anything. It is also the version of the argument that his operations manager can repeat to the team without it sounding like a threat.

Sometimes the Honest Answer Is Yes

Worth being straight about this, because the rest of it collapses if you're not.

Occasionally you will go into a business and find a role that genuinely does not survive contact with what you're proposing. Somebody spending four days a week rekeying data between two systems that could talk to each other. It happens.

When it does, you don't hide it and you don't lead with it. You put the finding in the report as what it is, a process that shouldn't exist, and you let the owner decide what happens to the person doing it. Redeployment is usually on the table and usually better for him. But it's his decision, and pretending the finding isn't there is how you lose the relationship in month six.

The other honest thing worth saying is that the layoff headlines deserve some scepticism. Challenger's own data measures the reason employers state, not what actually happened, and Glassdoor's chief economist has pointed out publicly that a company saying AI caused the cuts doesn't mean AI caused the cuts. It's a convenient thing to attribute a restructure to.

Meanwhile, in the same July report that had AI leading the reasons for the fifth month, total announced cuts were the lowest in two years and hiring was up a quarter on the previous year. As Challenger put it themselves, AI is shifting the labour market rather than dismantling it.

Say that to a worried owner. It's true, it's sourced, and it's a great deal more reassuring than anything you could make up.

This Is Change Management, Not Sales

The last piece, and the one that separates people who close these deals from people who close these deals and keep the client.

The objection doesn't disappear when the contract is signed. It moves into the building.

If thirty staff think you're the consultant who was brought in to work out who's expendable, you will get nothing useful out of a single process interview. They will show you the tidy version of their job. They will not tell you about the workaround, the spreadsheet, the thing they do manually every Friday because the system has never worked properly.

Which means your audit is worth less, because your audit is only as good as what people are willing to tell you.

So get the communication sorted before you start. Ask the owner what the team has been told and what he wants them to be told. Agree the reason out loud, and make sure it's the real one. Then let him say it, not you. It has to come from him.

Alignment first, access second, findings third. In that order.

The Real Point

Nobody says this objection out loud, so you have to hear it in the delay.

Arguing the economics confirms the fear. Agreeing, then asking what he'd do with the time, dissolves it.

The technology doesn't decide whether it's a cut or an expansion. He does, and telling him so is the fastest way to get on his side of the table.

Then handle it inside the business before you start, or your audit will be built on what people were willing to admit.

See you next week,

– Andrew

💡 How I Can Help

AI Audit Workshop ($9): Last week I announced that for a short time I’m reopening this workshop. Get the complete step-by-step system for conducting professional AI audits. Includes all templates, interview scripts, opportunity matrix frameworks, ROI calculators, and presentation slides I use to charge $10K+ per audit.