Your developers changed jobs. Has your messaging caught up?

I know a developer who hasn't written a line of code by hand in six months.

She's not been made redundant. Far from it. She's busier than ever. Her days are spent reviewing what the AI's written, deciding what's safe to ship, and working out how it all fits into everything else the business runs on.

Same job title. Completely different job.

And she's not unusual. This was the thread running through many conversations I had at the 2026 European Power Platform Conference in Copenhagen — with developers, with business leaders, over coffee between sessions. Everyone's watching the same shift happen in real time.

Chris O'Brien, CTO of Advania UK, put it best in his keynote, which you can watch in full here.

The numbers behind the shift

In February this year, the markets had what's now being called the "SaaS-pocalypse." In 48 hours, roughly $285 billion was wiped off software company valuations. Thomson Reuters had its largest single-day drop on record. LegalZoom fell 20% in a day.

Why? Because AI agents had just proven they could do the work the software was built to support — without needing a seat licence to do it.

Satya Nadella said as much on Microsoft's last earnings call: any per-user business they run is becoming a per-user and usage business. Even Microsoft is rebuilding its own economics around this.

Salesforce went further. They've just relaunched their entire platform — "Headless 360" — so every function can be run by an AI agent directly, no human clicking through a screen required. Their own framing was blunt: does a company still need a CRM with a graphical interface? Their answer was no. That's a big bet to make on your own product. But it tells you where the smart money thinks this is heading.

So what does this mean for the people who build things?

O'Brien's framing was the clearest I've heard: creation isn't the hard part any more. Governance is.

I think that's what most businesses are still missing. Everyone's excited about what AI can build, but who is excited about checking that it's secure, compliant, and actually adding value to the business?

Anthropic's own research backs this up — their GDPval study found AI models are now performing at industry-expert level on 83% of the tasks tested, across roles from software development to accounting. Creation itself has become easy.

What hasn't been easy is making sure it doesn't fall over, doesn't leak data, and fits into everything else the business already runs on without landing anyone in front of a regulator.

That's not a coding problem any more. That's a judgment problem.

O'Brien laid out the shift like this: the old model asked developers to learn languages, master frameworks, and write everything from scratch. The new model asks for architecture and system design, the ability to direct AI tools rather than compete with them, and the judgement to review and challenge rather than just build.

Same brilliant people. Completely different brief.

It's the same pattern I see through my work — the people who end up most valuable in a team aren't always the fastest coders. They're the ones who can see the whole picture and ask "but should we?" before anyone else thinks to.

Here's where I think this gets interesting for you specifically

If your website still leads with "we have excellent developers," you're answering a question nobody's asking any more. Everyone assumes AI can write the code now.

What clients actually want to know is: who's making sure this doesn't go wrong? Who understands the technology and the business well enough to be trusted with the decision?

That's the pitch worth making. Not "we can build it." "We know how to build it so it holds up."

Where this leaves you

None of this means panic. It means paying attention to where the value's actually moved.

The businesses getting ahead won't be the ones with the most developers. They'll be the ones who worked out early that their technical people were never just there to type. They were there to think.

---

If you're looking at your own team and wondering how to make this shift — from "great coders" to "trusted advisors on how AI fits your business" — that's exactly the kind of conversation I love having. Always happy to chat it through, whether you're mid-transformation or just starting to ask the question.

---