32% of Companies Just Skipped a Software Purchase to Build It With AI. What It Means If You Sell SaaS.
McKinsey says 32% of firms skipped buying software to build it with agentic coding tools. Why this kills generic SaaS but widens the moat for deep vertical tools.
Key Takeaways
- McKinsey’s State of AI 2026 report (published August 25) found that 32% of organizations decided against buying at least one software product or feature because they could build it in-house with agentic coding tools. In the tech sector it’s 41%.
- This is not a survey blip. Retool’s 2026 Build vs. Buy report puts the share of enterprises that have already replaced a SaaS product with custom software at 35%. The direction is the same everywhere.
- The buyers most likely to build are the ones you most want as customers: “high performers” who attribute real profit to AI skip software purchases at nearly double the rate of everyone else.
- The doomers are half right. AI coding tools do gut the market for generic, thin, easily-cloned tools — but they widen the moat for deep, workflow-specific SaaS that costs more to maintain in-house than to license. The winning move is to be un-buildable, not undifferentiated.
This week the SaaS industry got the number it had been quietly dreading. In McKinsey's State of AI 2026 report, released August 25, 32% of organizations said they decided against buying at least one software product or feature — because they could just build it in-house with agentic coding tools. If you sell software, that sentence is either an obituary or an opportunity, depending on what you sell. Let's figure out which.
What The Data Actually Says
McKinsey surveyed 1,719 people across 97 countries between May and June 2026. The headline finding: nearly a third of organizations have already passed on a software purchase they would have made a year ago, because a coding agent can now stand up a workable version internally. Break it down by industry and it gets sharper — in technology, the figure is 41%.
Source: McKinsey, The State of AI in 2026 (survey of 1,719 participants across 97 nations, fielded May–June 2026).
And this isn't one survey with a spicy stat. Retool's 2026 Build vs. Buy report found that 35% of enterprises have already replaced a SaaS product with custom software. Two different methodologies, same trajectory. The build-vs-buy line that has sat in roughly the same place for two decades is moving, and it's moving toward build.
The most uncomfortable detail is who is doing the building. McKinsey's “high performers” — the ~6% of companies that attribute real EBIT to AI — skip software purchases at nearly half, versus 31% of everyone else. The customers most fluent in AI, the ones with budget and the ones you most want on your logo wall, are the fastest to build instead of buy.
Why This Matters For Builders
The reflex read is “SaaS is dead,” and half the internet has already written that post. It's wrong — but it's wrong in an instructive way, so it's worth taking seriously.
Here's what the doomers get right: if your product is a thin layer over one API, a basic CRUD app, a form builder, or a dashboard over data the customer already owns, an agent can now clone it in an afternoon. The floor just fell out of that market. When building costs almost nothing, “we built the same thing” stops being a moat and becomes table stakes.
Here's what they get wrong: building the thing was never the expensive part. Keeping it alive is. A team that builds a feature in-house with a coding agent inherits the maintenance, the security review, the migrations, and the on-call — every line the vendor was quietly pricing into the licence.
Published estimates put maintenance at 60–90% of a software’s total lifecycle cost. The agent writes the 10–40% everyone can see.
The catch nobody demos: McKinsey notes AI operating costs are already starting to constrain AI use for about one in five organizations. The agent that wrote your internal tool doesn't maintain it, doesn't get paged when it breaks, and doesn't carry the liability when it leaks data. That bill lands six months after the celebratory Slack message.
The Real Shift: The Moat Moved
So the market isn't collapsing. It's splitting. The question a buyer now asks isn't “does a tool exist for this?” — it's “is this cheaper to own than to license?” And the answer flips on one axis: not how hard it is to build, but how expensive it is to keep alive.
| Type of product | Verdict | Why |
|---|---|---|
| A form builder / simple CRUD tool | Replaced | An agent ships this in a day |
| A dashboard over your own data | Replaced | Internal tools are the #1 build target |
| A thin wrapper on one API | Replaced | No moat once the API is public |
| Deep workflow in a regulated domain | Survives | Compliance + liability nobody wants to own |
| A network / marketplace | Survives | You can’t build the other side in-house |
| System of record with years of edge cases | Survives | The moat is the accumulated mess |
| Anything with an integration web | Survives | Maintaining 40 integrations is a full-time job |
The line isn’t “hard to build.” It’s “expensive to keep alive.”
Everything in the “survives” column shares a trait: the cost of ownership stays high forever. Regulated workflows carry compliance and liability no internal team wants to sign up for. Marketplaces need a second side you can't conjure in-house. Systems of record are valuable precisely because of years of accumulated edge cases — the mess is the moat. And any product sitting on a web of 40 integrations is really selling “we maintain 40 integrations so you don't,” which no coding agent erases.
This is the same lesson we drew from Norm AI hitting a $1.2B valuation and from the broader collapse in the value of pure generation. When the act of making software approaches free, value migrates to everything around the code: distribution, trust, accumulated data, and the boring operational burden customers will happily pay to never touch.
Stay Ahead of the Trends
Get insights like this before they're everywhere. Weekly, no fluff.
What To Actually Do About It
You don't need to panic-pivot. You need to run one honest test on your own product and act on the answer.
1. Run the “weekend clone” test
Could a competent developer rebuild the core of your product in a weekend with Claude Code and a couple of APIs? If yes, your moat isn't the software — and you need to find where it actually is (data, distribution, brand) fast. If it would take them a year of edge cases to match, you're in a good position.
2. Sell the run cost, not the feature
Your pricing page probably lists features an agent can now replicate. Rewrite it to sell what it costs the buyer to not use you: the maintenance, the compliance, the uptime, the integrations you keep current. That's the number they can't build away. We wrote about why pricing is really an infrastructure decision — this is the demand-side version.
3. Go deeper, not wider
The safest ground is a specific, painful workflow inside a “boring” industry — deep enough that owning it in-house means owning a liability, not a feature. Our guide to defensible AI SaaS niches is a good place to hunt.
4. If they build, be what they build on
The build wave is a tailwind for infrastructure. If customers are shipping their own tools, sell the auth, the billing, the vector store, the deployment, the monitoring they need to run them. When everyone's a builder, sell shovels.
Where This Goes Next
Expect the build wave to crest and then partially reverse. Right now the industry is in the honeymoon — the agent ships v1, the demo dazzles, the purchase gets cancelled. The bill for maintenance, security and migration arrives on a lag. In 18 months, watch for the “build-buy-back” stories: companies quietly re-licensing the SaaS they replaced once they price the true cost of owning it.
Second, the middle hollows out. Generic horizontal tools with shallow moats get squeezed from both sides — buyers build the simple stuff, and the deep vertical players take the rest. If your product lives in that middle, the next two years are the window to pick a side and go deep.
Third, “buildable” becomes a due-diligence question. Investors and acquirers will start asking every SaaS founder the weekend-clone question directly. The startups that come out of this era strong aren't the ones that shipped fastest. They're the ones building something that's genuinely expensive to own any other way.
Don't Miss the Next Big Shift
Every week, we break down the trends that matter for indie hackers and SaaS founders. Stay informed, stay ahead.
Join 3,000+ founders who stay ahead of the curve
Sources
- McKinsey — The State of AI in 2026 (Global Survey)
- Yahoo Finance — The Build-vs-Buy Shift: 32% of Enterprises Bet on Agentic Coding Tools
- Retool — 2026 Build vs. Buy Report (35% have replaced SaaS with custom software)
- Startup Fortune — McKinsey Survey Finds 32% of Firms Now Building Software Instead of Buying It
- The D*AI*LY BRIEF — A Third Skipped a SaaS Buy. Now Price the Run Cost.
Keep Reading
Google Indexed Hundreds of Claude Share Links. Every AI Tool You Use Has the Same Button.
Google indexed hundreds of Claude share links, exposing resumes, business docs and legal questions. Here’s the 10-minute AI privacy audit every founder should run.
Anthropic Is Now the Only Frontier Lab Not Backing Open Weights. Here’s What the Standoff Means for Your Model Strategy.
Anthropic became the lone frontier lab not signing the industry open-weights letter. Here is what the open-weights standoff really means for your model strategy.
Curl Took July Off to Escape AI Slop. The Open-Source Supply Chain Is the Founder Risk No One Prices In.
curl paused all security reports for July 2026 to escape open-source AI slop. Here is why maintainer burnout is the supply-chain risk founders are not pricing in.