Survival means going local

Here we are at the end. Nine chapters spent looking squarely at what’s playing out. The curve that won’t wait for you, your ERP’s wall turned into a door, the new value equation, the jobs that are mutating, the alliances aimed at your payroll, the value switching sides, and the social tab nobody wants to see. One question remains, the only one that really counts. Now what do we do?

Local, or responsibility regained

My answer fits in one word, and its technical modesty will surprise you: local.

Running AI locally — that is, on your own machines, with your own data that never leaves your premises — is not an engineer’s whim. It’s a position. When a model runs on your premises, your candidates’ and your employees’ data stays with you. So does the judgment. You’re not renting your intelligence from a vendor who, somewhere else, is recording its own employees’ every move the better to replace them. You stay in control.

And what makes this possible today is new

For a long time, local was wishful thinking — too slow, too weak. That changed in a matter of months, and I’ll spare you the technical details, but hold on to two movements. First, new methods are sharply accelerating models on ordinary machines — multi-token prediction, for instance, which delivers a speed gain of one and a half to two times through software optimization alone, without changing hardware, or the quantization techniques that slim models down. If you want to dig in, the sources are at the bottom of the chapter. Second, and this is the most important part, open models are no longer years behind proprietary ones. They’re months behind.

That’s not an impression, it’s measured. The Epoch AI institute calculated the capability gap between the best open models and the best closed models. Since January 2026, that gap has averaged just four months.

Take the measure of the opportunity. Models you can host yourself, with nothing leaving the building, are catching up with the most advanced proprietary systems. Mistral in France, or Chinese labs like Qwen and DeepSeek, are releasing lightweight versions that already deliver serious results on concrete tasks. Without compromising the sovereignty of your data, without sending anything outside, and above all without chaining yourself to a single vendor. Because the day the models evolve, and that’s a certainty, your systems can evolve too — at your pace, not theirs.

What I do with it, concretely

That is exactly the choice I made. Not for large corporations — I’m not an IT engineer and they have their own teams. But for my community: HR people in French-speaking Switzerland, and the recruiting world more broadly. Giving them autonomy without compromising themselves with a vendor, keeping the most sensitive data encapsulated in a local system, and freeing people from the tasks that bring no value to the trade. Or, better yet, letting them do what a well-trained human knows how to do, but faster and at scale. Doing better, in short. And that’s good for everyone.

Remember the formula from Mistral’s CEO, met earlier in this guide. AI is converting electricity into intelligence. The real question is where that conversion happens, and who profits from it. At the scale of a continent, that’s sovereignty. At the scale of your HR department, it’s exactly the same fight — smaller, and every bit as decisive.

Not to add a layer of admin — to remove one. Because it’s by freeing themselves from valueless tasks that HR people will finally be able to take up the strategic subjects that are rightfully theirs. I’m not telling you this in theory. I do it, and it works.

Above all, don’t panic

Now, a warning, and it matters as much as everything else. Becoming aware of this shift does not mean rushing. Quite the opposite.

Remember Klarna. That company, whose CEO is one of the most AI-enthusiastic people on the planet, charged in headfirst. Hiring freeze, headcount cut from five thousand five hundred to three thousand four hundred, a chatbot presented as the equivalent of seven hundred agents. Six months later, quality was collapsing, customers were fleeing, and the company was rehiring humans. The CEO’s admission became famous: we focused too much on efficiency and cost, the result was lower quality, and that’s not sustainable.

This is not an isolated case. More than half of the companies that rushed to replace humans with AI regret it, and one research firm predicts that by 2027, half of those that cut into customer service will have to rehire.

The lesson is crystal clear, and it’s the first rule of survival. Don’t fire anyone right away. The cut-costs-first reflex is the most expensive of all, because we always forget the price of undoing what we broke.

Now, here is what to do

No miracle solution. Four steps, in order.

First, become aware. Reread these articles, open the sources, verify everything. Take the facts, feed them into an AI if you feel like it, discuss them with it, ask your questions. Learn. It’s free, and it’s the only investment that will never turn against you.

Second, alert your leadership. This shift can’t be managed from a corner of the HR department. Someone at the top has to take it on. Not necessarily a board member, but clearly someone in senior management who grabs the subject with both hands and decides to understand. Look at Ivalua: the founder left his CEO seat to become Chief AI Officer, a role created just for this, explaining that you need a global view of the whole company and its processes to make the change happen. When a founder switches chairs for that, the signal is clear.

Third, get your hands dirty. Don’t be afraid. You don’t know how? Nobody knows how — it’s new for everyone. So start in a sandbox, run a hackathon as we saw, tinker with things, for yourself or for your company. Your asset is knowledge of the trade, and it’s the most precious one, because the technical barrier between a business problem and its solution has almost disappeared. You may need to surround yourself with people who aren’t afraid to get their hands into the technology, but it’s not as complicated as it used to be. What counts is going in.

And to go in, there is one condition — just one, but it’s absolute. You have to free up the time. As long as you’re bogged down in the time-consuming, valueless tasks of your job, you’ll never have an hour to think, analyze, step back. It’s the snake biting its own tail, and that’s the whole point: freeing yourself from those tasks is precisely what will give you the time to learn how to free yourself from them. That’s why the very first move, lifting the administrative weight, isn’t a comfort. It’s the key to everything else.

Fourth, once you’ve touched the tools with your own hands, dare an audit. With me or with someone else, it doesn’t matter. And it will be far more useful once you’ve experimented, because you’ll know what to look for. The goal isn’t even to find solutions right away. It’s to become aware of your weak points, to gauge how fast things are moving, and to understand where AI could bring something to your shop. You can perfectly well detach a few people to go explore. Because the real question isn’t do you want to go. It’s: if you don’t, your competitors will. And then what happens?

And all of this has a name

These four steps — become aware, give the subject an owner, get your hands dirty, dare the audit — are not a fad. They’re a discipline. In recruiting it has a name, RecOps, and it’s the trade I practice. But never mind the word. RecOps for recruiting, TalentOps, HROps, Ops of whatever you like, the moment you’re looking at systems and processes. Or Forward Deployed Engineer, if it’s purely AI applied to company processes. The title doesn’t matter at all. What matters is the movement: stop submitting to the tool, and get back to driving it.

And this is where I add a string to that bow. RecOps sets the course — the right processes, the right goals. But between the course and the daily life of a bogged-down team, a bridge is almost always missing. That bridge is small custom tools. Not bloated monsters: simple objects, cut for a specific trade and a specific problem, that remove the chore eating up the time. I build them as a craftsman, with a recruiter’s command of the trade, and with one rule that never moves: rigor on risks and on data first, power second. Even if it means offering something smaller than the giants do. The open models we run locally are improving so fast, as we saw above, that the gap closes month after month. It’s my way of reconciling the two — what we should do, and what we can actually do, starting Monday morning.

And the real skill, the rare one, isn’t technical. It’s knowing what you want to do. Understanding well enough what these tools make possible to walk into a company, spot what can be transformed, and turn that into a roadmap. That’s where the opportunity lies, and it’s immense, for whoever wants to seize it.

Let’s be clear: as of mid-2026, some things aren’t feasible yet. But at the speed everything is moving, what looks crazy today will be normal, and simple to set up, in 2027. The only mistake would be to wait until it’s easy before starting to understand.

That’s why this guide is called a survival guide. Not because the ending is written. On the contrary. Because nothing is settled — provided you look, understand, and take back control while there’s still time.

I could have joined the race and helped speed up the machine. I chose the opposite: helping people keep their footing. That’s all this guide will have tried to do. The rest is up to you.

I’m a sourcer. If you look for me, you’ll find me.