For thirty years a software renewal has had two answers, and procurement processes are still built around them. Renew at whatever the vendor now charges, or go shop for a cheaper seat elsewhere — and both answers end with somebody else's product deciding how your process runs. Building the thing yourself never made it onto the paper, because building meant a hiring plan, a roadmap, and a year of attention nobody had to spare.
That constraint moved, and analysts have started pricing the consequence. Enterprise application spend exposed to agentic arbitrage (Gartner, 2026) is put at up to $234 billion by 2030 — at that ceiling, roughly a fifth of enterprise application SaaS spending. Read the forecast as a forecast: it prices the risk of displacement, not the cost of building. The second half is our argument — the cost of producing working software against a specific, known process has fallen enough that pricing the build before you sign is now reasonable.
Renewal Now Has Three Answers
The third answer is not "write it from scratch", and anyone who sells it that way is selling a rewrite. It is instead an assembled system — managed infrastructure that you rent, models that you call, identity and payments that you never touch — with original engineering work reserved for the part of the workflow that exists nowhere but inside your company.
The renewal question was never really build or buy. It was whether building was reachable at all — and on a bounded workflow, for the first time in thirty years, it is.
Commodity Software, Commodity Outcomes
Every company in your category can buy the tool you are about to renew, at roughly the price you are about to pay. That is what makes it cheap, and it is the same thing that makes it useless as a difference. Buying commodity capability with minimal customization (HBR, 2020) is the disciplined move wherever there is no advantage in the workflow to lose.
The damage from getting this wrong is not the license fee. It is that a bought system imposes its own model of the work, and the company reshapes itself to fit it: the sales process becomes what the CRM has fields for, the clinical workflow becomes what the vendor's screens allow, and the thing that made the operation distinctive gets filed under "exceptions". Three signals that the tool runs the company rather than the other way round:
- The workaround is documented. A spreadsheet, a shared inbox, or a weekly meeting exists only to carry what the system cannot, and nobody notices it anymore.
- Onboarding teaches the tool, not the work. New employees learn which screens to click on before they learn why the process is shaped the way that it is.
- The differentiator is the manual part. The step your customers actually notice is the one nobody automated, because the vendor's product had no field for it.
Price The Build Before Renewing
A renewal with three answers needs a comparison finance can read, and it is not license cost against build cost. It is what each path leaves you holding at term end.
| Renew | Switch vendors | Build the workflow | |
|---|---|---|---|
| At term end | The same fit gap | Usually a different gap | A system closer to the process |
| Cost profile | Predictable, often rising | Migration, then steady | Front-loaded, then running cost |
| You own | A contract | A contract | Logic and data path; you run them |
Run that comparison only on workflows that pass a single test — the ownership sentence from the build, buy, or compose decision: "only we can build this, because ___". If the blank fills with data, a constraint, or a sequence of steps nobody outside your company would recognize, the build column is worth pricing. If the blank does not fill, renew without guilt.
ML LABS has built two systems for HeartSciences that had no off-the-shelf equivalent, because the processes were theirs. A claims and billing automation system whose automated path does not become the primary processor for a facility until it agrees with expert-adjudicated determinations on 98%+ of records, and a multi-site clinical operations platform built around how that group runs across locations. Neither is a thing anyone sells, and neither would have survived a fit-gap review against a vendor's product roadmap.
Cheap To Build, Costly To Own
Falling build cost does not touch the rest of the system. The fraction of a production machine learning system that is not model code (NeurIPS, 2015) is most of it — configuration, data plumbing, monitoring, glue — and holds the ongoing cost. A vendor's price already includes their operations team. Your build's price has to include your own team, or the board sees a dishonest comparison. When the honest answer to "who runs this in eighteen months" is a name nobody has hired yet, the build is not cheaper. It is deferred.
First Steps
- Pull the renewal calendar and mark the misfits. For every contract renewing in the next two quarters, write the workaround it forces on your team in one line. Contracts with no workaround are renewals; contracts with one are candidates for a build.
- Write the ownership sentence for the top candidate. "Only we can build this, because ___." Fill the blank, or drop the candidate and renew it without a meeting.
- Price the build and the run separately. Two numbers, never one: what it costs to get the workflow live, and what it costs to keep it live a year. The second number decides.
Price It Before You Sign
Treat the next renewal as a decision with three columns instead of two. The point of pricing the build is not to build everything; it is to stop paying differentiated prices for undifferentiated fit, and to find the one or two workflows where an approximation has been costing you the thing your customers notice. One way to get those numbers is to have the workflow taken apart by someone who has shipped similar ones, before the contract is signed. A fifteen-minute call ends in a recommendation, which can be that the system you were about to fund need not exist — that call has been made before, and it saved the client the build. Either way you reach the renewal with a number, not a default, and signing a three-year contract is a poor moment to learn you never priced the alternative.
References
- Gartner. Gartner Says $234 Billion in Enterprise Application Software Spend Is at Risk from Agentic AI. Gartner, 2026.
- Iansiti, M., & Lakhani, K. R. Competing in the Age of AI. Harvard Business Review, 2020.
- Sculley, D., et al. Hidden Technical Debt in Machine Learning Systems. NeurIPS, 2015.
