Your next software vendor won’t ship code. It will clock in.

Robert Smith says enterprise software will eat services. He stops one step short of where this actually lands. Notes for owners and PE funds rewriting their software thesis.

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.