Why a Wait-and-See Hiring Freeze on AI Costs More Than It Saves

Turn this article into takeaways for your work.

Each assistant summarizes the article only for you and suggests best practices for your work.

Should you stop hiring until it's clear what AI will do to your headcount? It's a reasonable instinct, and it's the one a lot of cautious leaders are acting on. But the freeze is not a neutral pause. Work doesn't wait while you wait, so it lands on the people already in the building, and the capability you were going to add stays unbuilt. The better move is narrower: keep hiring for roles that AI makes more valuable, and redesign only the roles it clearly absorbs.

Key Facts

The Freeze Rests on a Bet About Speed

A freeze says: AI will change our needs soon, so let's not commit to people we may not need. That's a bet about timing. And the evidence says the timing is slower and bumpier than the bet assumes.

Take the economics first. Erik Brynjolfsson, Daniel Rock and Chad Syverson argued in The Productivity J-Curve that a general-purpose technology like AI only pays off after firms make complementary investments in new processes, business models and human capital. In the early years, productivity looks flat or worse because that investment is real but poorly measured. The gains arrive later. Their finding on AI specifically was that effects on measured productivity were small but growing.

Then look at adoption inside companies. In 2024, Census Bureau researchers tracking firm AI use in the Business Trends and Outlook Survey found adoption at 5.4% of firms by February 2024, up from 3.7% five months earlier. They also noted that few AI-using firms reported employment reductions. That's a dated snapshot, and adoption has certainly climbed since. But the shape is the point: broad use came slowly, and the headcount effect was much smaller than the headlines suggested.

And inside the firms that did try, results were uneven. A 2025 MIT NANDA report, as covered by Fortune, found that about 5% of AI pilots achieved rapid revenue acceleration while the rest delivered little measurable P&L impact. It drew on 150 leader interviews, a survey of 350 employees and 300 public deployments, so treat it as a directional read on pilots, not a verdict on all AI work.

Put those together and the freeze logic weakens. If gains arrive late and unevenly, then holding headcount flat today doesn't buy you clarity next quarter. It buys you a longer stretch of the same workload on fewer shoulders.

Where the Cost Actually Lands

A freeze looks free on the P&L because nothing new appears there. The costs show up elsewhere.

On the people who stay. Open roles don't disappear; their work gets redistributed. Gallup's analysis of nearly 7,500 full-time U.S. employees named unmanageable workload among the five main causes of burnout. The same study found burned-out employees were 63% more likely to take a sick day and 2.6 times as likely to be actively looking for a different job. That's a 2018 study of U.S. full-time workers, not of hiring freezes specifically. But a freeze is one of the most reliable ways to create the workload it describes. If you're already working through how AI changes retention, the retention side of this question matters just as much as the hiring side.

The research on downsizing points the same direction, with a caveat. Joel Brockner and colleagues studied survivors of layoffs and found an inverted-U relationship between job insecurity and survivors' work effort, stronger among people with greater financial need to work. A freeze is not a layoff. But it sends a cousin of the same signal: leadership doesn't know what it needs from this team. Insecurity of that kind can raise effort for a while and then stop working. And you won't see the turn until someone good resigns.

On capability. AI-fluent people are the ones who turn tools into process change, and the J-curve says process change is where the value sits. If you stop hiring, you also stop importing the skills that make your own pilots work. The skills gap leaders keep misreading is partly a hiring-pipeline problem, and a freeze widens it.

On the bench. Entry-level and junior roles are where AI skills often enter the company first. The same support-agent study found that an AI assistant raised productivity about 14% on average and about 34% for novice workers, with minimal impact on experienced ones. That's a single call-center population, not all workers. Still, it suggests juniors paired with good tools ramp faster than before, which is a reason to keep hiring them, not to stop. For the longer view, see the broken bottom rung.

A Better Test: Amplify, Absorb, Unclear

The alternative to a blanket freeze is a role-by-role decision. Sort every open or soon-to-open role into one of three buckets, then act differently on each.

Role type What AI does to it How to tell What to do
Amplify Makes each person more productive or more valuable; demand for the work grows Judgment, relationships, or customer context is the scarce part; AI tools speed up the rest Keep hiring. Prefer candidates who already work fluently with AI
Absorb Takes over most of the task volume; the role as written shrinks The work is repetitive, rule-based, high-volume, and already partly automated in pilots Pause the backfill, redesign the role, and move people into adjacent work
Unclear Could go either way; evidence from your own pilots is thin You can't answer "what will this person do in 18 months?" Hire on a short, structured contract or a redesigned scope, and set a date to decide

Two rules keep the test honest. First, "absorb" requires evidence from your own workflows, not from a vendor deck. If a pilot hasn't shown the task volume actually dropping, the role goes in "unclear," not "absorb." Second, "unclear" is a bucket with an expiry date. A role can sit there for one planning cycle, not indefinitely, or you've rebuilt the freeze under another name.

This is the same logic as the executive decision framework for AI workforce planning, applied to a single question: who do we add, and who do we redesign around.

An Illustrative Example

Here's a hypothetical, labelled as such. A 150-person services firm freezes all hiring for two quarters. Its support team of eight loses one person to attrition. Nobody is added back. The remaining seven absorb the tickets, and the two strongest start taking interviews elsewhere. Meanwhile the one role that would have mattered most, an operations lead to own the company's AI workflows, never gets posted. Six months later the firm has spent nothing on the hire and a good deal on the replacements, and its pilots are still run by whoever has spare time.

Now run the three-bucket test on the same firm. The ops lead role is "amplify": post it now. The backfill for support is "absorb" if the ticket-deflection pilot has shown volume dropping, and "unclear" if it hasn't. Either way, the decision is explicit and dated instead of a default.

What to Do Next

If you're a CEO, COO or CHRO sitting on a freeze right now, here's a practical sequence.

  1. List every role the freeze is currently holding open. Include backfills, not just net-new headcount. Most freezes have a long tail nobody has reviewed since they were announced.
  2. Sort each into amplify, absorb or unclear, using evidence from your own workflows. Ask the function head to show the task volume, not describe it.
  3. Release the amplify roles first. These are the ones where waiting costs you the most. Write the job description around AI-fluent working, using what AI-native new hires now expect.
  4. Set an expiry date on the freeze itself. A freeze with no end date turns into policy. Pick a review date tied to a measurable trigger, such as a pilot result.
  5. Measure strain on the team you kept. Track overtime, time-off patterns, and regretted attrition monthly. If workload is the cost of the freeze, you want to see it before a resignation shows it to you.
  6. Talk about it plainly. People read silence as threat. The job anxiety piece covers how to say what you know and don't know without false comfort.

The Principle Underneath

Uncertainty is a reason to be specific, not a reason to stop. A blanket freeze treats every role as equally unknowable, which is rarely true. Some roles are obviously more valuable with AI around. Some are obviously shrinking. A few are honestly unclear. Treating them differently is not a hedge. It's what a plan looks like when the future is slow, uneven and partly visible.

Learn More

About the author

Victor Hoang

Victor Hoang

Co-Founder, Rework.com

Victor Hoang is Co-Founder and CMO of Rework. He spent 12+ years scaling B2B SaaS growth, building a lead engine that generated over 1 million leads and $10M+ in annual recurring revenue. Today he builds AI agents and MCP servers into Rework's products to empower customers across growth and operations. He writes about what actually works.