Your Company Hired an AI Consultant — What Happens Next

There's a particular flavour of dread that lands when you hear the words "we've engaged an external consultant to help us explore our AI strategy." It's different from the dread of a reorg announcement or a hiring freeze. It's more ambiguous, which somehow makes it worse. Consultants could mean anything. And "anything" is where your brain fills in the worst possible outcome.

I know this from both sides. I was on the employee side when my company brought in consultants before my redundancy. And i've since been on the consultant side, working with companies navigating AI transitions. The perspective from both seats is useful, so let me share what i've learned.

The first thing to understand

Not all AI consultants are the same. This sounds obvious but it's the thing most people miss. "AI consultant" covers a spectrum that runs from "genuinely helpful technical advisor" to "expensive justification for decisions already made." Knowing which type your company has hired tells you a lot about what's coming.

Type one: the technical implementer. These are people or firms brought in to actually build or deploy AI systems. They're there because your company doesn't have the internal expertise to implement a specific tool or workflow. This is generally the least threatening type for employees. They're there to make something work, not to make recommendations about headcount.

Type two: the strategy consultant. These are the big-name firms or boutique strategy shops hired to assess how AI could transform the business. They'll produce a lot of PowerPoint slides with quadrants and roadmaps. This type is more ambiguous. Sometimes it leads to genuine transformation that creates new roles. Sometimes it leads to a restructuring proposal dressed up as a strategy document.

Type three: the efficiency consultant. This is the type that should make you pay attention. If the consultant's brief is specifically about operational efficiency, process automation, or cost reduction through AI, then the subtext is fairly clear. Someone in leadership wants to reduce headcount and they want a third party to provide the rationale.

Type four: the change management consultant. These people are brought in to help the organisation manage the human side of AI adoption. If your company has hired one of these, it's actually a relatively good sign. It means someone is thinking about the transition, not just the destination.

How to figure out which type you're dealing with

You probably won't be told directly. Companies are cagey about the scope of consulting engagements, for good reason — if they announced "we've hired someone to figure out which of you can be replaced by AI" there'd be a mass exodus.

But there are signals you can read.

Who's sponsoring the engagement? If it's the CTO or Head of Engineering, it's more likely to be a technical implementation. If it's the CFO or COO, it's more likely to be about efficiency and cost. If it's the CEO, it could be anything, but it's being taken seriously at the highest level.

What access are they being given? Consultants who are interviewing employees, shadowing workflows, and mapping processes are gathering data about how work gets done. This is what happens before recommendations about how work could be done differently. The more access they have to your day-to-day, the more you should be paying attention.

What's the timeline? A three-month engagement suggests a strategic assessment. A six-to-twelve-month engagement suggests implementation. A four-week engagement suggests someone needs a slide deck for the board by end of quarter, and the recommendations may already be written.

Are they talking to you? If the consultants are interviewing people at your level, it could mean two things. They're either genuinely trying to understand the work (good sign), or they're building a case for which roles are "automatable" (less good sign). The questions they ask will tell you which. "What's the hardest part of your job?" suggests the former. "What percentage of your time is spent on repetitive tasks?" suggests the latter.

The consulting timeline, decoded

Here's roughly what happens in most AI consulting engagements, based on what i've seen from inside the process.

Weeks 1-4: Discovery. The consultants are learning. They're interviewing stakeholders, reviewing processes, understanding the tech stack. During this phase, nothing happens to your job. But everything is being documented.

Weeks 5-8: Analysis. They're taking what they learned and mapping it against AI capabilities. They're building the "opportunity matrix" — the grid that shows which tasks, roles, or processes could be enhanced, automated, or eliminated with AI tools. This is the phase where your job is being assessed on a spreadsheet.

Weeks 9-12: Recommendations. The consultants present their findings to leadership. This is usually a tiered roadmap: quick wins (things that can be automated easily), medium-term initiatives (things that require investment but have clear ROI), and long-term bets (things that might work in two to three years).

Weeks 13+: The silence. After the consultants present, there's usually a period where nothing visible happens. Leadership is debating internally. Finance is running numbers. HR is being consulted about implications. This silence is when anxiety peaks, because you know something was recommended but you don't know what.

Eventual: The announcement. If the recommendations include restructuring, it'll come as an announcement about "organisational changes" or "realignment" or "transformation." If the recommendations are about tool adoption without headcount changes, it'll come as a new project or initiative.

What the consultant is actually doing all day

I can tell you from personal experience that most AI consultants are doing a lot less scheming than employees imagine. A significant chunk of the work is trying to figure out what the company actually does and how it actually works, which is often much more chaotic and undocumented than anyone wants to admit.

Consultants also spend a remarkable amount of time managing the expectations of the leadership who hired them. Leaders often come into these engagements expecting to hear that AI can cut 40% of their workforce. What they usually hear is that AI can automate specific tasks within roles, which might eventually lead to some headcount reduction but will require significant investment, cultural change, and several years of implementation.

This isn't always welcome news. I've seen engagements where the consultant's honest assessment was essentially "you don't need to restructure, you need to invest in training" and the leadership was visibly disappointed.

The point is: consultants are not all-powerful architects of your doom. They're often just people with Excel models trying to give reasonable advice to unreasonable expectations.

What you should actually do

Don't panic, but don't ignore it. The presence of an AI consultant is a signal. File it alongside other signals of restructuring and see if a pattern is emerging. One signal on its own doesn't mean much. Multiple signals together mean something.

Engage, don't avoid. If the consultants are interviewing people at your level and you're invited to participate, do it. This is your chance to demonstrate the complexity, nuance, and human judgement that your role requires. The things that don't show up in a process map. Be honest about what you do, including the parts that require experience and intuition. Don't oversell how busy you are, but don't undersell how complex your work is.

Document your impact. While the consultants are assessing what can be automated, make sure there's evidence somewhere of the things you do that can't be. The client relationship you saved. The edge case you caught that the standard process wouldn't have flagged. The decision you made that required context no AI has access to. This isn't about performing value. It's about making the invisible visible.

Get curious about the AI tools. If the consulting engagement leads to tool adoption, the people who've already started experimenting will be ahead of the curve. Don't wait for the official rollout. Start now. The best defence against being replaced by AI is being the person who knows how to use AI and how to handle the things it can't.

Watch the pilot programme pipeline. If the consulting engagement leads to a pilot programme, pay close attention to how it's structured and which roles are included. Pilots have a way of turning into permanent changes faster than anyone expects.

The uncomfortable truth

Most companies that hire AI consultants are doing it because they believe, correctly, that AI will change how their business operates. The question isn't whether change is coming. It's what kind of change, on what timeline, and how it will be managed.

Some companies will use consulting engagements as genuine learning exercises and will invest in transitioning their workforce. Some will use them as cover for cuts they were already planning. Most will fall somewhere in between, making it up as they go, reacting to the consultant's recommendations one quarter at a time.

Your job in all of this is to be paying attention, to be building skills, and to have a plan that doesn't depend entirely on your company making good decisions. Because if there's one thing i've learned from being on both sides of the consulting table, it's that companies are just as uncertain about the future as you are. They've just hired someone expensive to be uncertain on their behalf.

The one thing to do today: Find out who the consultant's sponsor is. Is it the CTO, the CFO, or the CEO? That single piece of information will tell you more about what's coming than any amount of speculation.