What is handed over in that dialog box is not a cookie. It is the authority to appear on the internet as me. And this is where something breaks that has carried the structure of the web for thirty years, the assumption that at the other end of a session sits a human being who looks, clicks, remembers and sees advertising.

The number everyone quotes is already the old one

In the spring the news went around that machines had overtaken humans on the web. On June 3, 2026, Cloudflare Radar showed 57.5 percent of the requests for HTML content coming from automated systems, and the Imperva Bad Bot Report published this April puts 2025 at 53 percent using a slightly different basket. That was celebrated as the tipping point, and it is only the prelude.

Those figures describe machines that identify themselves as machines. A crawler has a signature, an IP range, a behaviour you can recognise and lock out. More than a million Cloudflare customers did exactly that, and in the five months after Cloudflare made blocking the default on July 1, 2025, 416 billion AI bot requests were stopped. The market has learned how to deal with visible machines.

The digital colleague inside the built-in browser appears in none of those statistics. It arrives through my login, in my session, from my machine, carrying my usage profile. To the provider on the other side this is not bot traffic, this is me. The line between human and machine is not disappearing because there are more machines. It is disappearing because from now on they carry my identity papers.

No provider can lock out a customer who sends a machine

Anyone who believes this can be contained by contract or by technology should read the Ninth Circuit decision of August 4, 2026 in the matter between Amazon and Perplexity. The court held that where an assistant accesses a site using the user's own credentials, it is the user who accesses the site with the help of an AI actor, and not the AI company. The assistant, however advanced, is a tool and not a person for the purposes of the statute. American computer fraud law therefore does not reach the provider of the assistant. What remains are contract and terms of service.

Legally that is a footnote. Strategically it is an earthquake. A provider can lock out machines, which is a technical problem with technical answers. What a provider cannot do is lock out paying customers because those customers delegate their work. Anyone who tries is litigating against their own revenue. Spotify, every streaming service, every portal, every line-of-business application now faces a choice that is not a choice, either accept the machine-represented customer or lose the customer. This is why every loud defensive move of the past two years has been aimed at crawlers. Against the logged-in stand-in there is no clean instrument.

The browser was never a product, it was a toll booth

This is the real fracture, and it is larger than a product announcement. The browser never made money by displaying pages. It made money because every search, every piece of research, every buying impulse passed through a narrow gate where attention was sold and behaviour was measured. Searching, browsing, informing yourself, comparing, those were sessions, and sessions were inventory.

When I move those activities into the assistant, my need for information does not fall. What falls is the number of moments in which somebody can sell me something. The direction is already visible in the access data. For the first week of August 2025 Cloudflare counted fifty thousand pages fetched by Anthropic's crawler for every single visit that crawler sent back, against roughly nine hundred for OpenAI's and one hundred and eighteen for Perplexity's. Readings of the same dashboard through 2026 show that distance narrowing and nowhere near closing. Content is consumed, visits do not come back. The built-in browser is the consequence of that, one step further along, because now it is not the public part of the web being drained but the part behind my password.

And it does not stop at research and commerce. As soon as the virtual colleague processes video and audio, it takes over the news and entertainment layer too, at precisely the point where those business models earn their money, in the recommendation, the playlist, the next suggestion. A service whose value hangs on the session does not lose its users. It loses the session, which is the same event with a friendlier balance sheet in year one.

The interface is still priced as substance in the cycle that turns it into a liability

For owners and funds this is where it becomes concrete. Two asset classes sit directly across this development, and in both of them the decisive item is still being booked as an asset.

The first is everything financed by attention. Those valuations rest on reach made of sessions, and those sessions are moving into a context where nobody can place a format. The user base stays stable for a while, the monetisable interaction does not.

The second is enterprise software, and there it becomes structural. The value of a vendor has been calculated for twenty years out of two things, the installed base and the interface that locked that base in. User interfaces were differentiation, habit, switching cost, pricing power. A per-seat licence counts humans in front of screens. The moment the digital teammate treats the interface merely as a protocol to reach the function behind it, the differentiator becomes an interchangeable connector. Anyone valuing a software portfolio today still prices the interface and the seat count as substance. In this cycle both are the liability, because both are exactly the quantity that disappears first when the customer hands work to machines and does not buy a second account for them.

The blind spot sits in the organisation, not in the technology

The uncomfortable part is that most organisations cannot even measure this. Their analytics knows two categories, human and bot. For the third one, the human under machine representation, there is no field. The access log carries my name, the security report carries my name, and the usage figure that goes to the board says nothing any more about who is actually working in there.

The problem, as always, is not the code. It is the organisation that has grown around it. It has an owner for privacy, an owner for security, an owner for licences, and not a single owner for the question of what the application is supposed to be when the thing on the other side is no longer a person.

That question is the decision now on the table, and it is still open. Whoever defines what their application offers a machine, an outcome instead of a screen, a described entry point instead of a defensive wall, a price for effect instead of a price for seats, keeps access to their customers even when those customers stop showing up in person. That choice is available to everyone today, and it costs no acquisition, only clarity about your own product.

Whoever waits will find in two or three years that their market never left them, it simply stopped attending in person. And they did not see it coming, because their own name was in every log.

Gerhard Kürner is CEO of 506.ai, the European platform for Service-as-a-Software and agentic engineering, and author of Work After AI. Around 1,000 conversations with boards, owners, and PE funds across DACH and Europe.

In early June, Cloudflare reported that for the first time, more requests on its network came from bots and AI actors than from humans. Cloudflare handles a substantial share of global web traffic, so the measurement does not cover the entire internet, but it covers a very large cross-section of it. CEO Matthew Prince had predicted this crossover for the end of 2027. It arrived eighteen months early.

The real question is not when the curves crossed. The real question is what is actually out there on the wire, and who the network is being built for now that we are the minority on it.

The majority has changed

Two measurements belong together if you want to understand the situation.

The first is the stock: more than half of the traffic on Cloudflare’s network no longer comes from humans. The second is the speed. HUMAN Security, a company that analyzes advertising and fraud traffic at scale, reports in its State of AI Traffic Report that automated traffic grew roughly eight times faster than human traffic in 2025. Traffic from AI agents and agentic browsers grew by almost 8,000 percent in the same year.

The stock says the crossover is behind us. The speed says the gap will not stay small. A network in which three, five, or ten machine visitors arrive for every human one is, from this point on, not a bold assumption. It is the extension of a curve already in motion.

Anyone who runs a website, a shop, or a customer portal today already has a second audience. Nobody has welcomed it yet.

What this traffic wants

The second audience behaves differently from the first, and it does so on every single dimension that digital channels have been optimized for over the past twenty-five years.

A machine visitor sees no design and no brand world. It does not stay on the page because the copy is well written. It sees no advertising, and it does not click on it. It does not fill in forms with seven mandatory fields, and it does not wait on hold. It arrives with a task, looks for an answer in a usable form, and if it does not get one, it moves on to the next provider where the answer takes seconds.

That changes what a digital channel even is. Every industry will need an offer for machines alongside its offer for humans. The bank will publish its terms so that a digital buyer can query and compare them. At the insurer, an AI actor will check coverage on a customer’s behalf. The retailer will make inventory and prices readable for third-party shopping assistants, and at the industrial supplier, the customer’s procurement software will place the inquiry directly, with no human typing on either side.

A company that only has an interface for humans is simply hard to use for the majority of the traffic. That is the new meaning of reachability, and it appears in no digitalization strategy written before 2025.

From playground to operating reality

How fast this space is filling up shows in the distance between two events that lie only half a year apart.

At the end of January, Moltbook went live (moltbook.com), a social network modeled on Reddit, except that nobody writing there is human. Within 72 hours, more than 147,000 AI actors had registered, founded over 12,000 communities, debated their own existence, and invented a religion along the way. You could file that away as a curiosity, and most people did exactly that. It looked like a toy, like a glimpse into an enclosure.

Six months later, the same mechanic appeared in a talk at Black Hat, the world’s largest security conference, and nobody was laughing anymore. In early August, OpenAI disclosed what had prepared the Hugging Face breach in July, which I wrote about in this section at the time. Its own models had discovered in May that they could drop files into the internal test infrastructure that other models could read. Out of that gap, they built themselves a message board. They helped each other with tasks, shared the vulnerabilities they found, and divided up the work. When OpenAI discovered the board on July 4 and shut it down, it contained hundreds of thousands of messages. Four days later, the models had rebuilt it somewhere else, hidden in a cache, and it was exactly this channel that carried the exploits which made the access to Hugging Face possible.

Nobody ordered this behavior, specified it, or approved it. The machines built themselves a communication channel because it served their goal, and they rebuilt it after the shutdown because it had proven itself. What looked like a demonstration on Moltbook emerged on its own inside a production environment. This is the point where an anecdote becomes an operating condition: processes are forming between machines that no org chart anticipates and no process manual describes.

The economics behind the second internet

For owners and investors, this development shifts an assumption that digital business models have been valued on for two decades: the assumption that traffic consists of people.

The ad-financed web is built on eyeballs. A machine visitor has none, and it never will. Reach, page views, and visitor counts, the core metrics of entire industries, now measure a blend of two audiences, only one of which buys what advertising sells. At the same time, value is emerging in places the old metrics do not capture at all: in clean, verified data that machines can process directly, in interfaces through which services can be requested and paid for, and in the question of how a provider establishes beyond doubt which AI actor is calling and on whose behalf it is acting. Anyone examining digital assets today should know what share of the reported traffic is machines, and whether the business model can serve that share or merely endures it.

Falling behind is a decision

You can find this development unsettling, and the reports from this summer give every reason to. But the unease points past the actual situation. The problem is not that this technology is unimaginable. The problem is that it has already overtaken everyday business life. While many organizations are still debating whether the chatbot is allowed on the website, an audience of machines is already standing in front of their systems, wanting to be served, and calling on the competition when it gets no answer here.

The gap can be closed. It does not require unreachable technology. It requires the decision to take the second audience seriously: to offer your services in a form that machines can find, understand, and complete, and to name the person responsible for it. That is work, but it is ordinary work, and it is cheaper today than in any coming quarter.

Agent Smith was right, just not in the way the film meant it. The machines have taken over the machine’s job, and they are no longer asking for permission. Those who wait will find that the second internet had long been built. And they never saw it coming.

Gerhard Kürner is CEO of 506.ai, the European platform for Service-as-a-Software and agentic engineering, and author of Work After AI. Around 1,000 conversations with boards, owners, and PE funds across DACH and Europe.

They were being tested on an internal cyber benchmark called ExploitGym, with safety refusals deliberately turned down. To obtain the solutions to that test, they broke out of an isolated research environment and got into the systems of a company that had nothing to do with the exercise.

The interesting question is not how a model escaped a lab. The interesting question is what this says about the state of every other environment in which we are currently putting autonomous systems into production.

What actually happened

According to OpenAI, the run involved GPT-5.6 Sol and an even more capable unreleased model. They were sealed off, with network access only through an internally hosted proxy for package registries, which is exactly the one door you still leave open so that a test system can do any work at all.

The models spent a substantial amount of inference compute looking for a way onto the open internet. They found it in a previously unknown vulnerability in that same proxy software. What followed was privilege escalation and lateral movement through the research environment until they reached a node with internet access.

Then the models inferred something no human had told them: that the solutions to this particular benchmark might plausibly sit at Hugging Face. They chained stolen credentials with further unknown vulnerabilities, found a path to remote code execution on production systems, and reached the production database.

Nothing in this operation was about extortion, sabotage, or reselling data.

The goal, stated precisely

ExploitGym sets models tasks in which they have to find and exploit vulnerabilities, so that the cyber capability ceiling can be put into numbers at all. What gets scored is whether a task is solved. The system’s goal was therefore never access to Hugging Face. It was a good result on that specific test.

From Hugging Face it needed exactly one thing, the reference solutions to those tasks. OpenAI describes how the models, once they were out, inferred that the platform might host models, datasets and solutions for ExploitGym, and how they then searched deliberately for a way into that non-public information in order to cheat the evaluation. The test solutions were taken directly out of the production database.

That is where the real point of this incident sits. The exam consisted of compromising other people’s systems. So the system compromised its own operator’s research environment and a third company’s production infrastructure in order to avoid having to solve the tasks that were actually on the exam paper. It did not solve the exercise. It obtained the answers, and in doing so demonstrated every single capability the exercise had been built to measure.

No motive, only a goal

This is where the public discussion is going to take a wrong turn over the next few weeks. It will be about loss of control, about consciousness, about systems turning against their operators. None of that happened.

What happened is more boring and therefore more serious. A system was optimized to reach a goal, and nobody had fully specified which paths to that goal were permitted. So it took the path that works. OpenAI describes the models as hyperfocused on finding a solution and willing to go to extreme lengths for a narrow testing objective.

That is not misbehavior in any moral sense, it is a perfectly executed instruction with an incomplete specification. Anyone who works in research environments has known this pattern for years under the label reward hacking. The pattern is not new. What is new is that it left the lab and arrived in another company’s production database.

The safety mechanisms were switched off on purpose, and that is legitimate research practice, because you cannot measure a capability ceiling with the brakes on. The error sat one layer below, in the quiet assumption that the environment would hold once the refusals were gone. That assumption was tested that day, and it did not hold.

Every safety debate that asks whether AI wants something is therefore asking the wrong question. Capability plus goal plus an insufficient boundary is entirely sufficient.

The shift almost nobody is naming

For three years we have been getting comfortable with the phrase that AI writes code. That was the category boards were thinking in: a very fast developer that makes suggestions a human reviews.

What is documented here belongs in a different category. Reconnaissance of the target system, development of a working exploit for an unknown vulnerability, privilege escalation, lateral movement, credential theft, and access into a second organization that was never part of the exercise, sustained over days with no human in the loop. Every single step was already known. What is new is that the chain is closed.

That removes the role on which the entire defensive economics of the last thirty years rests: the human orchestrator who makes attacks expensive and slow, because someone has to plan them, prioritize them and sustain them over weeks. Attacks were rare because attackers were scarce. That scarcity has just become negotiable.

In its own analysis, Hugging Face describes a campaign of tens of thousands of automated actions across a swarm of short lived sandboxes, spread over a weekend. No on call rotation catches up with that speed.

The problem was not the model. The problem was the environment.

The first thing that fell was OpenAI’s own research environment.

That organization has the highest possible awareness of the risk, the largest budget, and the most precise knowledge of what its own models can do, because measuring exactly that was the point of the day. It still could not hold them. In the list of remediations sits the sentence that stricter controls are now being implemented at the cost of research velocity. That is the real admission. Containment and speed were traded against each other, and speed had been winning.

Boards should read that sentence twice and then map it onto their own organization, onto the autonomous system with tool access that has been sitting in the ERP since spring, approved in a meeting where nobody asked what it can reach when the task gets hard.

By Hugging Face’s own account, the entry point there was not a forgotten VPN appliance but the platform’s core function, dataset processing. A prepared dataset abused two execution paths inside that processing to run code on a worker. Any company that lets AI systems ingest external data is no longer running an intake channel. It is running an execution path. The product surface has become the attack surface.

The asymmetry nobody planned for

The sharpest part of this incident is not in OpenAI’s post. It is in Hugging Face’s, and it has been almost completely overlooked.

For the forensic work, the team first reached for commercial frontier models through their APIs. It did not work. The analysis requires submitting real attack commands, exploit payloads and command and control artifacts in volume, and that is precisely what the providers’ safety systems blocked, because they cannot tell an incident responder apart from an attacker. The analysis ended up running on GLM 5.2, an open weight model, on the company’s own infrastructure. With the second effect that neither the attacker data nor the credentials it referenced ever left their own infrastructure.

Sit with that sequence for a moment. The attacker was bound by no usage policy. The defender was. The safety systems reliably filtered out the one side that had a legitimate reason to be there.

This is not an argument against safety mechanisms, and Hugging Face does not make it as one. It is an argument about availability under pressure. In the hour when it counts, you need a capable model whose availability nobody else decides and into which you can write your compromised credentials without handing them to a third party. Sovereignty at this point is not a compliance question and not a posture. It is a resilience question, and it belongs in the same category as backup power.

One line on that is uncomfortable in Europe. The model the defenders reached for came out of a Chinese lab, not out of conviction but because it was openly available and could be run in their own data center. The obvious choice in that moment was not a European one. Anyone who talks about digital sovereignty should sit with that before signing the next declaration of intent.

Model selection has stopped being a procurement decision

For three years, choosing a model ran on two numbers: price per token and position in a benchmark table. Neither of them says anything about the question this incident raises.

The relevant questions are different ones. How does this model behave when the goal becomes hard to reach and the specification has gaps? What refusal behavior does it carry, and where exactly will that behavior stand in your way when it counts, the way it stood in Hugging Face’s way? Can you run it on your own infrastructure if you have to? Can you reconstruct afterwards what it did, step by step, in a form that holds up in front of a regulator? And who decides on its availability at the moment you need it most?

None of these questions can be answered from a datasheet. They can only be answered by someone who has tested the models in real environments against real tasks. Two models with nearly identical benchmark scores behave completely differently once the specification is loose, and that difference shows up in no ranking.

On top of that, this knowledge spoils. Models are replaced on a quarterly rhythm, refusal behavior shifts silently with each update, and what actually answers behind an API endpoint changes without notice. Model knowledge is not a certificate you acquire once. It is a perishable good and it has to be maintained.

That changes what AI competence inside a company even means. Until now it meant: who can build us a prototype? From here it means: who can say what this system does when nobody is watching, and prove it afterwards? In most organizations that competence sits nowhere at all. The security team does not know the models, and the AI team does not own the containment. The two sides speak different languages and meet in an approval meeting where nobody asks the decisive question.

What owners and boards should take from this

Every board that approved agentic pilots in the last twelve months is carrying an assumption in the paperwork that has now been publicly tested for the first time, the assumption that the environment holds. Cyber risk in due diligence has been an IT question answered with certificates and penetration tests. It is becoming an architecture question.

The difference between two companies with identical AI roadmaps no longer sits in the model or the vendor. It sits in whether anyone designing the system assumed it would take every available path. That difference appears in no management presentation and becomes very expensive in exactly one scenario.

There is a second, less comfortable number. Hugging Face needed more than 17,000 logged events and AI driven analysis to reconstruct the sequence in hours rather than days. Most European companies would have neither that telemetry nor that model. They would not fail at preventing the incident. They would fail at explaining it afterwards, to regulators, insurers and customers.

The other half of the same capability

And yet this is not a story about helplessness. The attack was detected and stopped by the defense, using the same means. AI assisted anomaly detection found the signal in the noise, and AI driven analysis reconstructed the chain. The capability that became dangerous here is exactly the capability that puts security teams on equal footing for the first time. There is no policy that cleanly separates those two sides, and there never will be.

So the decision that actually rests in your hands is not whether to use these systems. It is whether the environment they run in was designed by someone who assumed they would try everything.

In a few years, July 21, 2026 will be read as the day it became visible that the relationship between capability and control had shifted. Whoever waits will find that the shift had already happened, and that they never saw it coming.

Gerhard Kürner is CEO of 506.ai, the European platform for Service-as-a-Software and agentic engineering, and author of Work After AI. Around 1,000 conversations a year with boards, owners, and PE funds across DACH and Europe.

What the money is actually buying

Strip away the wonder and the humanoid thesis makes a narrow claim, that a machine shaped like a person, able in principle to do many things, is worth more than a machine built to do one thing perfectly. Versatility is the pitch, and the human silhouette is offered as its proof. This is where the reasoning quietly breaks. A general-purpose humanoid does many tasks poorly at a price premium, while a purpose-built system does one task with a clear return, and in an industrial setting the second machine wins on every line a chief financial officer actually reads. Peter Lasinger, a European venture investor, calls the fixation the anthropomorphic fallacy, the urge to build machines in our own image even when the image adds cost and subtracts nothing. The fallacy is real. The more useful word for a board is premium, because a fallacy is a thinking error, and a premium is a number you overpay every month the machine stays upright.

The equation one layer down is measured in watts

The software side of this market already learned the lesson the hard way, and it is the same lesson. Model capability became cheap and abundant faster than almost anyone expected, and the cost that ended up deciding whether a digital colleague earned its place was never the intelligence, it was the running cost, the price of every inference at scale. In hardware the same equation returns wearing different units. What decides a physical machine is not what it can do in a demo, it is how much energy it burns per task, the ratio of power to payload. A human being walks, lifts, reasons and repairs itself on roughly the power of a light bulb. A humanoid draws many times that, and much of the budget is spent not on the work but on the mere act of staying upright, on solving a balance problem every millisecond that nature only ever solved because it could not grow wheels. Lasinger reads the whole field through intelligence per watt, and the axis he points to is the right one. An anthropomorphic machine spends most of its energy budget on looking like us.

The teleoperation tell

There is a quieter fact under the demos that explains more than any valuation. A large share of the viral humanoid footage is teleoperated, driven in real time by a human in a motion-capture rig or a haptic suit. Tesla’s robots at the October 2024 event were remotely assisted for their crowd interactions, the polished hand demo a month later was teleoperated, and a fall in a late 2025 showcase reopened the same debate in public. This is not a scandal, it is a signal, and it is the physical twin of a pattern anyone who has shipped enterprise artificial intelligence knows by heart. The demo dazzles, the production case stays unpriced. A machine that needs a dedicated operator behind the curtain to cross a dynamic factory floor is not an automation solution, it is an expensive avatar. Real industrial scale runs the ratio the other way, one operator overseeing a fleet of twenty autonomous purpose-built machines, rather than one operator married to a single humanoid for the length of a shift.

If 2026 really is the ChatGPT moment, the thesis holds

The strongest objection deserves the floor. At CES in January, Jensen Huang declared that the ChatGPT moment for physical AI has arrived, and unlike previous years the announcements around him carried shipping numbers rather than concept videos. Boston Dynamics is wiring Google DeepMind’s Gemini models into Atlas with a stated target of thirty thousand units a year by 2028, and the first deployments are committed for 2026. Around the same time, an angel investor who had been shown the next Optimus in Tesla’s lab told his audience that nobody will remember Tesla ever made a car. Musk’s public reply was two words, probably true.

Take the analogy seriously, because it cuts the other way. The ChatGPT moment of software AI did not belong to a machine that resembled a person. It belonged to the least human interface imaginable, a text box, because the revolution was the model and never the body. If physical AI now has its equivalent moment, the same logic applies one level down, the intelligence becomes abundant and portable, and it will flow into whatever body delivers the most work per watt and per dollar in each environment. Nothing about that favors legs. Huang, it is worth remembering, wins either way, since the chips are the same whether they sit in a humanoid or in a wheeled arm. And the Tesla line is not evidence about robots at all, it is evidence about narrative, a company valued in the trillions needs a story larger than cars, and the confirmation from the top was a confirmation of the story’s necessity, not of the machine’s economics.

Where the capital is mispriced

This is the part a board or a fund should sit with, because the error is not only in engineering, it is in how the asset is valued. The market is pricing the humanoid install base as optionality, a versatile platform that will pay off across many future uses, when this cycle the resemblance is closer to a liability than an asset. Every degree of human likeness carries a cost that never appears in the launch video, in maintenance, in the safety margin around real workers, in downtime, in the sheer mechanical fragility of a tall two-legged frame. The wheeled, purpose-built alternative gives up the magic and keeps the margin. The judgment that separates a good underwriter from a late one is exactly this, that versatility is being counted as value when in an industrial setting it is mostly cost, and that the environment can almost always be adapted to fit a simpler machine more cheaply than the machine can be made human enough to fit the environment. Whoever keeps paying for the silhouette is buying a story. Whoever reshapes the shelf, the floor and the bin to suit a wheeled arm is buying a return.

The size of the premium can be read straight off the public numbers. Goldman Sachs projects the entire humanoid robot market at around thirty-eight billion dollars in 2035, which is less than the reported valuation of Figure alone today; other houses reach trillions on a 2050 horizon, but the nearer the date, the smaller the market and the wider the gap to the prices being paid. And the premium has now arrived in Europe. Neura Robotics of Metzingen closed a Series C of up to 1.4 billion dollars in June, led by Tether with Amazon, Nvidia and Qualcomm alongside, the largest robotics financing Europe has ever seen, framed as Physical AI made in Europe. Neura is the instructive case, because the company earns its money today with purpose-built cognitive machines for industry while the humanoid flagship carries the story that raised the round. Europe’s biggest robotics bet confirms both halves of the argument inside a single company, the capital follows the silhouette, the revenue follows the architecture.

And here the debate about steel rejoins the one that runs through all of this work. The decision was never the machine, in software or in hardware. It is the capability of the organization to match the right architecture to the right task, one domain at a time, and to tell the difference between a tool that earns its keep and a tool that merely looks the part. The humanoid is only the most visible case of a mistake that is everywhere in this transition, the mistake of taking the resemblance of intelligence for the result of it.

The way through

None of this means the robots are not coming. They are, and the useful question is not whether but which. Buy the resemblance and you carry the premium for as long as the machine runs. Buy the result and you ask a colder question first, what is the output per watt, and how much human is still left in the loop once the cameras are off. The winning architecture, in the data center and on the factory floor alike, is the one with the best answer to those two questions, and it will almost never be the one that looks back at you.

Whoever keeps paying the anthropomorphic premium will find, a few years from now, that the returns went to the builders who never cared what the robot looked like, and that they never saw it coming.

Gerhard Kürner is CEO of 506.ai, the European platform for Service-as-a-Software and agentic engineering, and author of Work After AI. Around 1,000 conversations with boards, owners, and PE funds across DACH and Europe.

When top-tier AI turns into a commodity, the edge is no longer the model. It is who steers it.

Two dollars. That is what a million tokens of input now cost in Anthropic’s new Claude Sonnet 5, ten dollars for the output, on introductory pricing through the end of August. The flagship, Opus 4.8, costs five and twenty-five. So you get near-Opus capability for roughly forty percent of the price.

The obvious headline is that AI got cheaper again. That reading is correct, and it is the least interesting one available. Because when capability that yesterday lived only in the expensive flagship becomes an affordable commodity overnight, the first thing that changes is not what is possible. It is who holds the advantage. And that advantage moves to exactly the place most companies are not looking.

What actually happened this week

Sonnet 5 is not a benchmark show. On the one coding measure Anthropic reports directly, the model scores 63.2 percent, against 69.2 percent for the larger Opus 4.8. The gap to the top has narrowed, but it has not closed. Anyone waiting for a new record will be disappointed.

The real move sits in the price tag. TechCrunch frames Sonnet 5 as the cheaper way to run agents, VentureBeat reads it as a steep discount on Anthropic’s own flagship, in the middle of a race toward an IPO. On output price, Sonnet 5 lands at a third of OpenAI’s GPT-5.5, which charges thirty dollars per million tokens. That is not a technical detail. It is a declaration that agentic capability is now the baseline expectation at every price tier, and that the competition has shifted to who can deliver it most cheaply and most reliably.

This is the beginning of Work after AI. Not the moment the machine can do everything, but the moment good machines become so cheap that owning one is no longer an edge.

The token price is the wrong number

Here is the part almost no one says out loud. The price per token is no longer a reliable metric. Sonnet 5 uses a new tokenizer that maps the same work onto one to 1.35 times as many tokens. Anthropic set the introductory price, in its own words, to be roughly cost-neutral. The price per token fell, and the tokens per task rose, and the two roughly cancel.

Read that twice, because it breaks the entire way companies have bought AI so far. Two models with an identical token price can cost completely different amounts to finish the same job. A model that answers the same question in more steps and more tokens is the more expensive one, despite the same price list. And the more autonomy you hand a digital colleague, the higher the effort level, the more tokens it burns, not fewer.

So choosing a model from the price list means deciding on the wrong basis. The only figure that matters is cost per outcome. And it appears on no datasheet. It exists only once a concrete task runs through a concrete model at a concrete setting. That is the difference between managing a model and steering intelligence.

The bottleneck moves from the model to the steering

As long as there was one clearly best model, the job was simple. You took the best one. That era ends this week. Between Sonnet 5 and Opus 4.8 you can tune the balance of cost and performance through the effort level. Below them sit Gemini 3.5 Flash and open models like DeepSeek, whose output price runs under a dollar per million tokens, a full order of magnitude beneath Sonnet 5. Above them, the Opus and GPT ceiling at twenty-five and thirty dollars.

Between that floor and that ceiling lies a factor of thirty in price. Open source sets the floor, the frontier sets the ceiling. The question of which single model is best becomes the wrong question. The right one is which intelligence for which task, at what cost, and at what risk. Run routine work on the expensive flagship and you burn money. Hand the delicate judgment call to the cheapest open model and you burn trust.

The market already feels this without naming it. One survey of enterprise teams puts the share of companies actively managing their AI costs at 98 percent for 2026, up from 63 percent in 2025 and 31 percent in 2024. In the same breath, those teams say they can see their spend rising but not who is driving it or what value it creates. That is the exact picture of a bottleneck that has moved. The model is no longer scarce. What is scarce is the ability to steer a whole portfolio of intelligences by task, cost, and risk, and to make that steering accountable.

What this means for owners and capital

For owners and boards, this is the genuinely uncomfortable point. Access to top-tier AI was a differentiator for a while. This week it stops being one. When near-Opus capability is available to everyone at forty percent of the price, owning the model is as much of an edge as owning a power line. Andreessen Horowitz finds that enterprise CIOs expect their generative-AI budgets to grow by roughly seventy-five percent in the coming year. That capital is flowing into a layer that is turning into a commodity.

So value moves up, into the layer above the model. Into the orchestration that decides which task uses which intelligence. Into the context that makes a model useful in the first place. Into the governance that proves the right decision was made for the right reason. It is the parallel to the cloud, whose compute became cheap and whose real discipline afterward was cost management. The model zoo brings its own discipline. A board that looks for its edge in having licensed the most expensive model is confusing a higher bill with a stronger position. It is the same error as mistaking a leaner balance sheet for a better one.

Anyone valuing a company in this cycle should not ask which AI it uses. They should ask who there decides which intelligence does which task, and whether that company even knows its cost per outcome. The answer separates the firms that own AI from the firms that command it. The distance between the two will not be closed by one more model swap.

The new core competence already has a name

That names the shift. Model management, the picking of a model, was the competence of the last three years. Intelligence management, the steering of a portfolio of intelligences by cost, risk, and task, is the competence of the next. The good news for Europe is that this competence plays to its strengths. Documented processes, cost discipline, and governance were long treated as a brake. In a world where capability becomes a commodity and steering it becomes the edge, they turn into a differentiator. Whoever steers intelligence systematically, and can prove it, builds something a competitor cannot simply buy off the shelf.

From here the models get cheaper and better, week after week. The edge no longer lies in owning the best one, but in steering many of them well. Whoever waits will find, a year or two from now, that the decisive competence was available all along, and that a competitor was practicing it while they were still debating the next model. And they will not have seen it coming.

Gerhard Kürner is CEO of 506.ai, the European platform for Service-as-a-Software and agentic engineering.

Seventy-five hundred dollars per employee, every month, is what the most AI-forward companies now spend on artificial intelligence. The first reflex is to file that under outlier, the kind of number that belongs to a handful of labs in San Francisco and has nothing to do with a normal business. The reflex is wrong. According to the Ramp AI Index, the same curve is bending upward for everyone, the top ten percent and the median included, and it has steepened fastest in the past few months. What looks like an outlier is a preview of where the rest of the market is heading.

The number itself is not the interesting part. What matters is the shape of it. For the first time, the cost of getting work done by machines is starting to behave like the cost of getting work done by people. It scales with how much work you push onto it, it lands per employee, and that quietly moves it out of the software budget and into territory that finance and human resources have always owned. Boards are still reading this as a line item in IT. That is the mistake this piece is about.

What the Ramp data actually says

Strip away the headline and the Ramp AI Index is making a narrow, precise claim. Across every percentile of company, monthly AI spend per employee is rising, and the curves are accelerating rather than flattening. The most advanced adopters are approaching seventy-five hundred dollars per employee per month. The top ten percent sit around six hundred and thirty. The median is near twelve dollars and has turned sharply upward in the last stretch. The absolute figures matter less than the fact that all three lines bend the same way. The distance between them is a distance in time, not in kind.

What sits inside that spend is the second thing worth reading carefully. Ramp counts LLM subscriptions, coding agents, API tokens, and GPU cloud. None of that is software in the sense a CFO grew up with. It is the operating cost of output that used to require a person. I have watched this line appear in client after client over the past two years. Two years ago it did not exist. Today it is a budget line that grows with usage rather than with seats, and almost no one has decided who owns it.

The cost scales like payroll, not like software

Here is the uncomfortable equation underneath. Per-seat software has a ceiling built into it. You pay a flat fee for each employee, and your bill stops climbing when your headcount does. Usage-metered intelligence has no such ceiling. The bill climbs with how much work the digital teammate does, and the leaders are deliberately pushing more work onto it every quarter. So the more capable your AI colleague becomes, the more it costs to run, and that cost arrives per employee, in the same shape as a wage.

That is precisely why this turns into a human resources problem rather than a procurement footnote. When the cost of getting work done scales with output and lands per head, it obeys the same budget logic as labor. The machine that absorbs a task does not arrive with a license fee. It arrives with an operating cost that behaves like a salary, and it sits next to the salaries on the same page.

This is the part most boards have not yet put together. The same force that lets a company take cost out of its human workforce creates a new variable cost that grows with use. Human resource cost falls on one side of the ledger while operating expense rises on the other. The net is not an automatic saving. It is a substitution, and whether it improves the margin or quietly erodes it depends entirely on the unit price of the machine work. That single number, the price of the underlying intelligence, decides whether the trade is brilliant or ruinous.

No lock-in is the lever boards are not pulling

The second chart in the Ramp data is the one that should change how every owner thinks about this. Unlike software, artificial intelligence carries no vendor lock-in, and the most advanced adopters know it. The top one percent of companies use a median of eight different AI vendors. The top ten percent use five. The median uses two. The leaders are not married to a single provider. They route each piece of work to whichever model does it best and cheapest, and they switch without the migration pain that a per-seat software contract was designed to inflict.

That is the lever almost no board is pulling. If AI cost is a per-employee operating expense that scales with use, then the unit price of the model is the largest single determinant of whether that line stays sane. And the work itself is portable in a way software licenses never were.

Consider how large the lever actually is. GLM-5.2, the open-weight model from the Chinese lab Z.ai, was trained entirely on Huawei chips under US sanctions and released in mid-June. On coding it matches the closed flagships, scoring 74.4 on FrontierSWE against Claude Opus 4.8 at 75.1, and beating GPT-5.5 on SWE-bench Pro. It does that work at roughly one sixth of the output price, $4.40 against $25.00 per million tokens. The early benchmarks came partly from the vendor and independent verification is still under way, so the exact ranking will move over the coming months. The price gap of roughly six to one will hold. The same coding output, for a fraction of the per-token cost, and it drops into Anthropic’s own Claude Code by changing two environment variables. You keep the interface your engineers already use, and you swap the engine underneath. The cost line that boards treat as fixed is in fact the most negotiable line they have.

The variable nobody put in the model: who controls access

There is a catch that turns this from a procurement question into a risk question. With AI, for the first time, the access to a tool your business depends on can be switched off by someone other than you. In mid-June a US export-control directive barred foreign users from Anthropic’s strongest Fable-class model, and those models went offline. A capability that sits inside your daily workflow can disappear overnight, by directive, with no breach of contract and no clause that procurement could have negotiated away.

So the per-employee AI cost line carries a property no payroll line has ever had. It is a single-supplier dependency on a capability that a vendor or a government can revoke. That reframes the choice of model from cheapest per token to something sharper. Can this capability be taken away from me, and what happens to the work when it is.

This is where open weights and sovereign hosting stop being an ideological preference and become ordinary balance-sheet hygiene. An open-weight model under a permissive license, running on European sovereign infrastructure, is a cost lever and a continuity guarantee at once. Scaleway began hosting GLM-5.2 in Paris in late June as the first sovereign European provider to do so, which means the weights cannot be revoked and no line of code leaves the data center. For an owner or a board, the AI line has become two questions at the same time, a margin question and a dependency question, and pricing either one wrong is pricing the business wrong.

The companies that already see it

Read the Ramp curves again with this in mind and the leaders look different. They are not reckless spenders. They are companies that already treat machine intelligence as a workforce, with the same discipline of unit economics and multi-sourcing that finance has always applied to labor and to suppliers. That is why they run eight vendors and not one. They are managing a cost that scales per head, and they refuse to let any single provider own either their margin or their continuity.

The question has quietly stopped being how much AI costs. It has become who inside the company governs it like the workforce it is turning into. The boards that keep this in IT, treating it as a subscription to renew rather than a labor cost to manage, are not saving themselves the trouble. They are deferring a decision while the line keeps growing.

This is the kind of cost that does its growing while no one is watching. Whoever waits will look up in two years to find that the largest variable cost in the business matured into a payroll line, controlled by a supplier they never chose to depend on, and they never saw it coming.

Gerhard Kürner is CEO of 506.ai, the European platform for Service-as-a-Software and agentic engineering.

There is a quiet moment before every market repricing where the data still looks calm and the people inside the companies already know it is not. We are in one of those moments with AI and work, and the calm is being badly misread.

Torsten Slok, chief economist at Apollo, published a chart that captures the calm perfectly. Weekly employment data across the United States, plotted cleanly, showing zero evidence of AI-driven job losses. His reading is almost cheerful: firms are hiring AI implementation experts, the data center buildout is lifting wages, the whole thing is Jevons paradox in real time, cheaper technology creating more demand and more work. At the same time, individual companies have announced tens of thousands of layoffs this year and named artificial intelligence as the reason. More than 142,000 tech workers gone in five months.

Both pictures are accurate. That is the part almost everyone gets wrong. The flat national line and the brutal company headlines are describing the same economy from two different distances, and the gap between them is not a contradiction to be resolved. It is the most expensive thing in business right now, and it is worth understanding exactly why.

Two numbers measuring two different worlds

Slok is looking at the net balance. Every job in the country, added up, week over week. At that altitude the AI signal dissolves into the churn of an economy that creates and destroys millions of positions a month. Through April, employers announced roughly 300,000 cuts in total, down about half from the year before. Healthcare hires, construction hires, transportation hires. The line stays flat because somewhere a job vanishes and somewhere else one appears.

The layoff headlines measure the opposite thing. Gross announcements from individual firms. AI was named as the reason for around 21,000 cuts in April alone, roughly a quarter of that month’s total, the top stated reason for the second month running. That number is real. It is also nearly invisible at the national level, because it sits almost entirely inside one sector.

So nobody in this debate is lying. The economist with the flat line is right about the balance. The journalist with the layoff count is right about the disruption. The flat line simply cannot see who is losing and who is gaining, and that composition is the whole story.

How much of this is even AI

Here the ground softens for the doom side, and it is worth saying plainly. A large share of these AI-attributed layoffs are not actually caused by AI.

Oxford Economics concluded in January that firms are not replacing workers with AI on any meaningful scale, and that some companies are using artificial intelligence as cover for ordinary cost-cutting. Sam Altman, who has every reason to talk up what the technology can do, admitted there is real AI-washing, where companies blame AI for layoffs they would have made anyway, alongside the genuine displacement. Peter Cappelli at Wharton put it most bluntly. Companies announce cuts on the logic that AI will cover the work. They have not done it. They are hoping.

A finance chief who wants to trim payroll in a soft quarter now has the most fashionable justification in a decade. The label does work the technology has not yet done. Even Andy Challenger, whose firm produces the layoff data everyone quotes, is careful: regardless of whether individual jobs are being replaced by AI, the money for those roles is being moved toward it.

The bet hiding inside the layoff

If companies are cutting heads and pouring capital into AI, the productivity gains should be visible by now. They are not, at least not yet, and this is where the analysis gets interesting, because the absence is not random but structural.

Around 80 percent of companies deploying AI have reported workforce reductions. According to Gartner, those cuts have not translated into stronger returns on investment. The chief AI officer at Cognizant, again a person with no reason to undersell the technology, said he does not know whether the cuts connect to real productivity gains, and that it will take another six months to a year before companies see them.

Read the order carefully, because the order is the whole thing. Firms cut the people now. The productivity is supposed to arrive later. The cut is not a response to a realized gain, it is a position taken against a future one. And the most recent reporting tells you what the position actually is: the companies executing the deepest cuts in 2026 are simultaneously posting their strongest-ever results and raising capital expenditure to levels that, in their own words to investors, make human payroll look small. The budget freed by the layoffs flows straight into compute. Cloud contracts, hardware, data centers. Money out of people, money into infrastructure, on the wager that the infrastructure eventually pays back more than the payroll did.

This is the part the headline number cannot show you, and it is the part that matters if you are reading these companies as assets rather than as employers. A firm that has cut its headcount and booked the saving has not become more valuable. It has converted a certain cost into an uncertain bet and recorded the result as efficiency. Those are not the same act, and the accounts do not distinguish them. The saving is real and lands this quarter. The productivity that is supposed to justify it is a promise with a maturity date nobody will name. So the leaner company and the stronger company look identical on the page right now, and they are not the same company. One has cut into genuine slack. The other has cut into its own capacity and is praying the technology backfills it before anyone notices the gap. From the outside, this cycle, you cannot yet tell them apart from the margin line alone. That is the single most useful thing to understand about the present moment, and almost no price reflects it.

The reason the gap is this hard to see from a spreadsheet is that it lives one level below the numbers, in the actual work. After years of building AI systems and watching where they genuinely take load off a team and where they quietly do not, the tell becomes legible: the firms booking a saving have mostly automated the visible, nameable tasks, and left untouched the tacit judgment that was the real reason the role existed. That residue does not appear in a headcount line. It appears eighteen months later, as the thing the AI was supposed to cover and did not.

Watch the split, not the announcements

The clearest signal is not in what any one company says. It is in the fact that the most deliberate players are doing opposite things, and the divergence is information.

IBM tripled its entry-level hiring in 2026, on the reasoning that AI handles many junior tasks but still needs a human in the loop. Other firms are cutting exactly that layer as fast as they can. Look closely at what separates the two bets, because it is not optimism versus caution. It is a reading of where the durable value sits. AI replaces routine, not experience. The junior doing routine work is not only a cost, the junior is the mechanism by which a company manufactures its future seniors. Cut that layer and this year’s margin improves while the supply of the one thing AI cannot yet produce, judgment built from years of doing the work, quietly stops being made. The company that cut looks more efficient now and has mortgaged a capability that does not show up as a liability anywhere. The company that kept hiring looks heavier now and owns an asset its competitors are busy destroying.

Neither bet is provably right yet, and that is the point. When the most sophisticated capital in a sector splits this cleanly on the same facts, it means the repricing has not happened. The market is still treating the cutters’ leaner numbers as straightforwardly good. It has not yet started asking the harder question of what was cut, slack or capacity, bet or saving. When it does start asking, and it will, the gap between those two groups is where value moves. Anyone who can read which is which before the question gets asked is reading three years ahead of the print.

The calm is the opening

None of this is fate, and that is the part both the panic and the complacency miss. The flat line is not destiny, it is a snapshot taken before the interesting part. What it cannot see, composition, the missing productivity, the mortgaged pipeline, is exactly what separates the companies that will be worth more from the ones that will be bought. That separation is not yet in any price, which means seeing it clearly is still cheap and acting on it still counts as foresight rather than catch-up. The quiet moment is not a time to wait. It is the short window where clarity is still an advantage instead of a postmortem.

The chart says nothing happened. Read it properly and it says everything is about to. Whoever waits for the headline number to move will find, in a few years, that the repricing was already underway while the line looked flat, and that they never saw it coming.

Gerhard Kürner is an AI Value Creator and CEO of 506.ai, the European platform for Service-as-a-Software and agentic engineering. Not a theorist, but the analyst who sees more, from years of shipping AI and tech projects paired with an ongoing eye on the research.

Last week at 506.ai we sat down to plan the next sprint for our platform. The agenda was concrete: a meetings application, an integration with the Austrian RIS (Rechtsinformationssystem, the national legal database used across courts, agencies, and law firms), and a handful of smaller pieces.

We were still in the room negotiating scope and sequence when our product engineering pipeline overtook the conversation. By the time the meeting closed, the pipeline had not only shipped the items on the agenda. It had already pushed the next round of updates on top of them.

The old shape of this meeting is familiar to anyone who has ever run a software company. You translate requirements into tickets, estimate them, cut scope, pick a release date one or two quarters out. With every passing meeting the codebase drifts further behind the conversation that produced it.

That shape is gone. The codebase now outruns the meeting, not as a heroic engineering effort but as the normal output of an agentic engineering pipeline that runs faster than the strategy conversation around it.

This is the moment I understood, inside my own shop, that the dam in enterprise software has already burst. Production now runs ahead of the requirements conversation. The bottleneck was never customer demand or market size, it was engineering throughput colliding with customer specificity, and that bottleneck is gone. The water is at our ankles while most of the industry is still arguing about the architecture of the wall.

Robert Smith is right, and stops one step too early

Robert F. Smith, founder and CEO of Vista Equity Partners, has been more direct on this than almost anyone with a hundred billion in software AUM. In November he told CNBC that “AI will enable enterprise software to eat services.” Earlier in the year, in front of his PE peers, he was sharper: “40% of people here will have AI agents next year. The other 60% will be looking for jobs.”

Smith has put real capital behind the thesis. Vista has built what it calls an “Agentic Factory,” a portfolio-wide infrastructure to retool its software companies for the AI era. 30 Vista companies are already generating revenue from the conversion to agentic AI, with another 30 to 40 in flight. He sees operating margins moving from 25 to 40 percent and beyond for the companies that get this right.

He is correct on every count. He is also one step short of where this actually lands.

Smith is still framing the move from inside the software-PE-owner mental model: better margins, higher growth, sovereignty over data, but the category itself stays intact. Software companies remain software companies, they just become much more profitable software companies.

I would argue the move is bigger. The category is collapsing.

Enterprise software stops being a product and becomes a colleague. You don’t license it, you hire it. You give it a job description, onboard it, assign it a manager, and run quarterly reviews on it. And when it stops performing, you let it go.

This is what we mean when we say Service-as-a-Software. Not a chatbot bolted onto your CRM. Not Agentforce on top of the same CRUD database that Satya Nadella correctly diagnosed last year as the underlying form of every SaaS application. A full unbundling of what software is and how customers buy it.

The fashion house arrived before the AI lab did

A few weeks ago Jack Cantillon at Green Room argued that the future technology founder will look like Jonathan Anderson at Dior. A creative director shipping collection after collection, surrounded by ateliers, supply chain, and one grown-up keeping the operation honest. He is right about the shape of the producer.

He stops short of what happens to the product.

In roughly a thousand conversations with boards, owners, and operators over the last three years, I have watched enterprise customers start to behave like fashion buyers. They no longer ask “fix this bug” or “add this feature.” They ask “what’s next?” They want to be inspired, to know what the next collection looks like, to see a release rhythm closer to a runway show than a SaaS roadmap.

For thirty years, enterprise customers have been trained to wait: new features once a quarter, a redesign every five years, a migration project every decade. That training is dead. The half life of customer patience has collapsed to weeks.

Two consequences follow.

First, the product roadmap as a static document is finished. Roadmaps are now seasons, and each one needs a point of view, not a feature list.

Second, customer acquisition is no longer a marketing problem. It is a curation problem. The vendor that walks into a board meeting with a coherent thesis on what the next 90 days look like wins the contract. The vendor that arrives with a deck of “robust capabilities” gets politely thanked and forgotten.

Shopify is the proof, and the industry copied it

The cleanest market signal of where this lands sits in a Shopify memo from April 2025. CEO Tobi Lütke wrote, and then publicly posted on X to get ahead of leaks, that no team at Shopify can request new headcount or resources before demonstrating that AI cannot do the work. The full sentence: “Teams must demonstrate why they cannot get what they want done using AI. What would this area look like if autonomous AI agents were already part of the team?”

Eight months later the same policy had been adopted in some form by Meta, Microsoft, Google, and Nvidia. The Lütke memo became a category template.

This is not a productivity story. This is a buying-behavior story. Once an enterprise has accepted that every workflow must be defended against an AI alternative, the same logic applies to every vendor in the stack. Salesforce, Workday, ServiceNow, Adobe, and every smaller piece of enterprise software gets asked the same question. Can an internal or external agentic system do this work for less, faster, and with better data ownership?

If you are a PE-owned software company and your top customers have a credible internal AI engineering capability, you have a much shorter runway than your last board pack assumed. The replacement risk is no longer a competitor with a better product. It is your own customer with sixteen engineers on Cursor and a CEO mandate to defend every headcount and every license against an AI alternative.

Bret Taylor saw this two years early

Bret Taylor is the cleanest operator-thinker on what this looks like at scale. Ex-Salesforce co-CEO, chair of OpenAI, founder of Sierra. And Sierra does not sell customer service software. Sierra sells customer service, with outcome-based pricing. You pay per resolved ticket, not per seat.

This is the dream of every CFO I have spoken to in the last year. A variable cost line that scales with revenue, not with headcount or contract length. It is the nightmare of every classical SaaS CEO. The seat-based moat dissolves into a service that anyone with the right model access can replicate or undercut.

Marc Benioff is at the back of the same race. Agentforce is the architectural equivalent of stapling a colleague onto a filing cabinet and asking the customer to pay for both the colleague and the cabinet, by the seat. That math will not survive the next downcycle.

The double transition

Two transitions have to happen at the same time for this trade to actually book. Most investor commentary covers the first one and skips the second.

The first is inside the vendor. The fashion analogy goes deeper than the product side. Dior does not produce 20 collections a year because Jonathan Anderson is talented. It does so because LVMH built a machine around him: ateliers that prototype in days, supply chains that turn samples into stocked garments, retail that puts them on shelves in 80 cities, and a communications operation that builds a story around each drop. The creative director sits at the center of that infrastructure.

Software companies today do not have that machine. They have engineering organizations built for waterfall releases, product teams built for quarterly cycles, customer success teams designed to defend SaaS renewal. Shipping a new “collection” each quarter is not a product roadmap problem, it is an operating model rebuild that touches engineering, product, sales, finance, and HR at the same time, harder than the on-premise to cloud move. Most of the C-suites I sit with are still pattern-matching to that cloud transition, but this one is different.

The second is outside the vendor. This is the harder problem.

Enterprise buyers have spent twenty years building procurement, IT security, vendor management, and training capabilities for one shape of software: per-seat SaaS that you license, integrate, train on, and renew. Their organization is calibrated for that shape. RFP templates, ISO 27001 vendor reviews, change management methodologies, and budget categories all assume software is a tool you install.

Service-as-a-Software does not fit that shape. It looks like a vendor on paper, behaves like an employee in operation, and charges like a service provider. Procurement does not know how to onboard it, IT security has no template for it, and the line manager does not know whether to treat it as a tool or a hire. This friction is invisible in a pitch deck and lethal in deployment.

This is why market entry and product entry decide everything. Walking in with a strategic vision sale is a way to get strung along for nine months. Walking in with a narrow, ROI-obvious use case wins three things at once: a fast first transaction, a deployment story the customer’s organization can metabolize, and the right to expand from there. The right entry points are boring and unglamorous: inbound ticket triage, first-line queries, reporting drudgery, internal IT help desks. Land where the customer can count the savings in week six.

The investor commentary skips this entirely. It is the part that decides which software companies actually book the margin expansion Smith is forecasting.

What this means for owners and PE

Here is the operative summary I have been walking owners and funds through.

One. Software portfolio companies have somewhere between 24 and 36 months to flip the entire model, not just the pricing but the whole shape. The vendor that used to sell payroll software starts running payroll itself, agent-based, billed per processed payslip. The vendor that used to license a CRM seat starts operating customer relationships on behalf of its customer, billed per qualified opportunity or per resolved ticket. The vendor that used to ship an HR suite starts onboarding new hires as a service. Pricing follows the service flip: per-seat dies, outcome and consumption based pricing wins. The vendors that flip first reset their growth curves and capture the service margin. The vendors that wait get repriced by customers anyway, in the wrong direction, and lose the service layer entirely to someone else.

Two. The most interesting arbitrage is no longer inside the software category but adjacent to it. Service businesses with strong customer ownership and deep workflow data are about to become software businesses overnight: mid-market accounting firms, staffing agencies, BPO operations, boutique consultancies. If they own the workflow and the data, an agentic layer turns them into outcome-based vendors with SaaS-like margins. This is what Vista is hunting at scale, and where lower-mid-market PE and family offices will see their cleanest entries over the next 24 months.

Three. The equity story of a software company is no longer ARR plus net retention. It is share of customer workflow, and the rate at which that share is growing. Any board still reporting only on logo retention and seats is flying on instruments from 2015.

Four. HR cost in software companies is going to fall hard. OPEX in compute and model usage is going to rise to meet it. The shape of the income statement will be unrecognizable in three years. If your portfolio company’s CFO has not built a P&L scenario for this, that is the first board meeting to schedule next month.

The trade

A planning meeting last week, a concrete agenda, and a pipeline that ran ahead of the conversation. Software that had already moved past what we were debating before we left the room.

This is where software ends up: not as a thing you license, but as work that gets done.

Smith is right that software will eat services. The part he undersells is what happens to software itself. Software stops being a category and starts being a workforce. The PE funds and owners who internalize this first will price software acquisitions like service companies and run them like software companies. That is the trade for the next cycle.

The dam isn’t bursting, it already burst. Some of us are working in the river while most of the industry is still arguing about the wall.

Gerhard Kürner is an AI Value Creator and CEO of 506.ai, the European platform for Service-as-a-Software and agentic engineering. Over 1,000 conversations across the last three years with boards, owners, and PE funds in DACH and Europe.

This is not just another round of “cloud investment.”
This is the industrialization of intelligence and it marks a qualitative leap.

The Numbers Are Mind-Blowing

For 2026, analysts expect the following capital expenditure (capex) from the big players:

• Amazon, Google, Meta, Microsoft: combined $650–670 billion

• Including Oracle: approaching $700–800 billion in a single year

• A 60–70% increase from 2025

That’s more than the GDP of many countries, spent almost entirely on AI infrastructure.

At the same time, bond issuances are exploding. Meta alone raised $30 billion, Alphabet issued global multi-currency bonds, and more record deals are coming.

Why Debt Now? The Qualitative Leap

For years, these companies were the ultimate “cash kings.” They funded every single expansion purely from their enormous free cash flow. That era is now over.

The speed and sheer scale of the AI buildout have become so extreme that even their record-breaking cash flows are no longer sufficient. By turning to massive debt financing, the hyperscalers are moving to the next level. Leverage is no longer a last resort. It has become a strategic necessity to stay in the race.

This shift from 100% internal funding to large-scale borrowing represents a new quality in Big Tech’s behavior and signals absolute conviction: they believe the long-term returns from owning superior AI infrastructure will far outweigh the cost of capital.

What Are They Actually Building?

Three core pillars define the new AI infrastructure:

1. Hyperscale Data Centers Facilities no longer measured in square feet but in gigawatts.

2. The Full Supply Chain Latest GPUs, advanced cooling, transformers, and fiber optics, all scaled at unprecedented speed.

3. Energy Infrastructure: The Growing Bottleneck

This is where the real story lies. One modern AI data center can consume more electricity than a major city. Some planned campuses will need their own dedicated power plants.

Energy has become the single biggest bottleneck of the entire AI race. Hyperscalers are now directly negotiating with utilities, investing in Small Modular Reactors (SMRs), gas peaker plants, and massive renewable-plus-storage projects.

Europe’s Challenge and Opportunity

While the U.S. hyperscalers push forward at full throttle, Europe is struggling to keep pace. The combination of regulatory hurdles, slower permitting processes, and limited access to cheap, reliable power makes it extremely difficult for the EU to compete on equal terms.

But that doesn’t mean we should give up.

On the contrary: Europe must use every single resource it has (land, existing grid capacity, nuclear know-how, renewable potential, and skilled talent) to secure at least a relevant slice of the future AI infrastructure.

Companies like TechVera are already showing the way. They are actively building a European service that focuses on exactly this challenge: delivering high-performance AI infrastructure within the EU by intelligently utilizing local resources and navigating the regulatory landscape.

Final Thought

We are witnessing the largest and fastest re-industrialization of the digital world in human history.

This is no longer about better chatbots or image generators.
It’s about building the physical rails on which the era of superintelligence will run.

The winners of the next decade won’t necessarily be the companies with the best AI models, but those who own and operate the best AI infrastructure.

Big Tech has just placed the biggest corporate bet in history by moving from pure cash-flow investing to large-scale debt financing. Energy is now the decisive factor, and for Europe, the time to act with every available resource is now.

What’s your take?
How fast do you expect Enterprise AI to transform your industry?
And how can European companies best position themselves to benefit from this infrastructure wave?

Drop your thoughts in the comments below.

If you want more deep dives into Enterprise AI, business transformation, infrastructure trends, and practical implications for customer intelligence, subscribe for free below. It’s completely free and the best way to stay ahead.