The SaaS business model took a beating in February 2026. Adobe, Salesforce, ServiceNow and Shopify together lost more than a trillion dollars in market capitalisation in a matter of weeks, according to the Fireship channel. The problem isn't SaaS as such, it's the assumption it was built on: that every user would keep paying indefinitely to click buttons. That assumption is holding up less and less well, and I'm going to show you why, along with what it changes in practice if you're building a SaaS today, or having one built.
- 📉 Margins are cracking, Fireship documents a trillion dollars in SaaS market cap wiped out in a matter of weeks.
- 🤖 Agents are replacing entire roles, Codex and Claude Opus make buying ten seats for ten users a debatable proposition.
- 💸 Subscription fatigue is real, one small-business owner reports paying $4,100 a month for 23 SaaS tools.
- 🚀 SaaS isn't dying, it's changing engines, ListKit and Papermark prove you can still build fast, just differently.
I'm not here to sell you the idea that SaaS is finished. It isn't. But the machinery that has kept it running for fifteen years, seat-based pricing and growth funded by successive rounds, is showing its limits at exactly the moment AI is making every workstation replaceable in a few seconds.
The SaaS model is cracking, and this isn't theory
A SaaS, strictly speaking, is software hosted in the cloud and sold by subscription rather than by licence, as Stripe's guide to the business of SaaS puts it. The global market is worth $465 billion in 2026 according to youtrust.com, and it's still growing. So this isn't a sector on its way out.
What's cracking is the margin promise. Fireship points out that the model rests on an average profit margin of 80%, achieved by selling the same software to thousands of customers at no marginal cost. That promise assumes the customer keeps paying even as perceived value drops. Yet a post on r/Entrepreneur describes the annual software audit of a 12-person company: 23 active subscriptions, $4,100 a month, against $1,200 five years ago for roughly the same functionality. The author of the thread points to a specific mechanism: every software category keeps splitting into ever-narrower tools, which forces you to stack subscriptions where one used to do the job.
Why are 80% margins drawing so much attention right now?
Because they've become the main argument against traditional SaaS. When an executive realises they're funding an 80% margin on a product an AI can partly reproduce, the question of price changes in nature. It's no longer "how much does this cost", it's "why am I still paying for this".
Why AI agents change the SaaS equation
Where the reasoning really tips over is the cost of the work SaaS was already replacing. A CRM, a billing tool or a support platform exists to organise human work around a process. An AI agent capable of executing that process directly strips away a good part of the tool's reason to exist.
OpenAI launched the Codex app for macOS in early 2026, described as a command centre for agents, with more than a million downloads in a week according to Fireship. Codex 5.3, the model behind it, now includes skills for generating images, writing and researching, to the point of covering a good share of a product team's tasks. Anthropic answers with Claude Opus 4.6 and pushes the same model towards legal analysis and financial modelling. Alibaba isn't sitting it out either, with Qwen3 Coder Next, an open-weight model that gives companies an alternative to closed American models.
The executive's calculation has changed: they no longer need to buy ten seats for ten users, an agent can cover the work in milliseconds. That shift, more than the quality of the models themselves, is what explains the fall in valuations for traditional SaaS vendors.
How does an AI agent replace an entire SaaS role?
By automating the process the tool used to organise for a human. An email prospecting tool existed so a salesperson could find addresses and send messages. An agent that does both steps without an interface no longer needs the intermediary software, only the result.
What the founders who succeed do differently
Despite this backdrop, SaaS products are still being built, fast and well. André Heckle Jr launched ListKit (also known as Sauce), an email prospecting tool, and reached $1 million in annual recurring revenue in 87 days, according to his interview on the Starter Story channel. The entry price is simple, $97 a month, and the company had more than 1,500 paying customers a year after launch.
A different profile: Mark and Julia built Papermark, an open source alternative to Docsend, off the back of a single tweet that racked up 40,000 views in a few hours. Eighteen months later, the company was approaching $900,000 in recurring revenue, still bootstrapped, according to their account on Starter Story.
Dan Martell, who has founded and sold three software companies and invested in more than 60 businesses, sums up the method he'd reuse if he started from scratch: begin with consulting to identify a real problem, then package the solution as a product. That's exactly the path Shopify, FreshBooks and 37Signals took in their early days.
What these three stories have in common isn't luck, it's execution speed relative to team size. Neither ListKit nor Papermark needed an army of developers to ship something they could bill for.
Is it still worth launching a classic SaaS in 2026?
Yes, but not with the team size you'd have used in 2022. The product that wins today isn't the one with the most features, it's the one that solves a specific problem, fast, with an engineering team that absorbs AI tools rather than being slowed down by them.
The real variable is no longer headcount
This is where I take a position, and I'll be upfront: I run an offshore software company in Vietnam, so I have an obvious bias on this subject. That's also why I know its concrete limits, not just the sales pitch you read everywhere.
Across the SaaS projects my team delivered in 2025 and 2026, the variable that won or lost months was never the number of developers assigned to the project, it was their ability to use Claude Code or equivalent tools without wrecking the architecture behind it. Generating code with AI doesn't mean knowing how to build a product that lasts. A non-engineer can produce working chunks of code, but they don't handle architecture, security, or the edge cases that get expensive six months down the line.
Vibe coding is useful for prototyping an idea over a weekend, exactly as Mark and Julia did with Papermark. It becomes dangerous the moment you build something billable without technical supervision behind it, as I set out in vibe coding and offshore developers. I see it regularly with clients who arrive with a quickly generated MVP and discover the real bill when it comes time to stabilise it.
The advantage of a senior Vietnamese team augmented by AI doesn't come from a lower rate, it comes from faster delivery without giving up technical accountability for the result. It's the combination that counts: senior engineers, AI tools that are properly steered, and someone who answers the phone when things break in production.
"AI isn't killing the SaaS model, it's killing the teams that sold development time without ever taking responsibility for the outcome."
Vincent, September 2026
How does an AI-augmented offshore team change the cost calculation?
It shortens the gap between the idea and something billable without growing headcount. Where a SaaS would have needed a team of six developers two years ago, a senior team of three, properly equipped with AI, can cover the same scope, provided someone keeps a hand on the architecture and the structural technical decisions.
What this means in practice for your SaaS roadmap
The table below sums up what's shifting between the classic SaaS model and the one I see emerging on recent projects.
| Dimension | Classic SaaS (pre-2025) | AI-augmented SaaS (2026) | Trend |
|---|---|---|---|
| Target gross margin | 80% through user volume | 80% through process automation | → goal unchanged |
| Engineering team size for an MVP | 5 to 8 developers | 2 to 4 senior developers + AI | ↓ smaller headcount |
| Time to market | 6 to 12 months | 87 days to 6 months (ListKit, Papermark) | ↑ clear acceleration |
| Dominant sales argument | Features and integrations | Outcome delivered, process replaced | ↑ observed shift |
| Main risk | Churn and customer acquisition | Unstable architecture if AI generates unsupervised | ↑ new risk |
SOURCE: cited transcripts (Fireship, Dan Martell, Starter Story) · UPDATED 09/2026
This shift isn't confined to consumer SaaS. A founder on r/Entrepreneur building a vertical SaaS in healthcare describes another symptom of the same problem: the more configuration options he adds to fit each customer's workflows, the more his product looks like custom software dressed up as SaaS. That's exactly the trap I see on the French client side: wanting to hold on to a pure SaaS model when the actual need calls for a configurable product with technical support behind it. According to McKinsey, generative AI automation is advancing faster in technical functions than elsewhere in the business, which sharpens this tension between standardised product and bespoke need.
If you're driving a SaaS project today, the question to ask yourself is no longer "how many features before launch", it's "which process am I actually replacing, and with what team can I ship it fast enough for it to matter". I've spelled out how that logic plays out in practice, in particular on the choice between an AI agent and a developer depending on the nature of the task.
The SaaS business model isn't collapsing, it's tightening. The vendors who sold margin on user volume will keep hurting, because the founding assumption, every user clicking buttons indefinitely, no longer holds against agents that just do the work. But founders who build fast, with a senior engineering team able to absorb AI without losing control of the architecture, are still finding their million dollars in a matter of months, as ListKit and Papermark have shown. My verdict is simple: don't try to save yesterday's SaaS model, build the one that replaces a real process, with a team that knows how to use it. If you want to dig into how this approach translates on the AI tooling side inside companies, the AI First blog covers the operational use cases in more depth than I can here.
Frequently asked questions
Is the SaaS model really going to disappear because of AI?
No, the SaaS market is still growing and is worth $465 billion in 2026 according to youtrust.com. What's changing is vendors' ability to justify an 80% margin when an AI agent can replace part of the work the tool used to organise. SaaS products that replace a real process, rather than just an interface, keep their relevance.
Why are companies paying so much in SaaS subscriptions today?
Because every software category has split into increasingly specialised tools, which forces you to stack subscriptions. A post on r/Entrepreneur documents a 12-person company paying $4,100 a month for 23 different tools, against $1,200 five years ago for equivalent functions.
Can you still launch a profitable SaaS in 2026?
Yes, provided you target a specific problem and ship fast with a small senior team. ListKit reached $1 million in annual recurring revenue in 87 days, and Papermark passed $900,000 in 18 months while staying bootstrapped. Neither started with a large engineering team.
Do you need a big development team to build a SaaS today?
No, and that's the main change in the SaaS model in 2026. A small senior team properly equipped with AI can cover a scope that needed twice as many developers two years ago, provided a technical lead keeps control of the architecture and doesn't let generated code pile up unsupervised.
Is vibe coding enough to build a commercial SaaS?
No. Vibe coding is effective for prototyping an idea quickly, as Papermark's founders did over a weekend. But a billable product needs technical supervision on architecture, security and edge cases, skills that AI code generation doesn't automatically replace.
Vidéos YouTube
- How AI is breaking the SaaS business model... — Fireship
- How to Start a SaaS Business From Scratch — Dan Martell
- I Built A $1M SaaS In 87 Days — Starter Story
- How We Built It: $900K Open Source SaaS — Starter Story
Discussions Reddit
- the SaaS model is quietly falling apart for small businesses and nobody in tech wants to admit it — r/Entrepreneur
- at what point does vertical SaaS just become a services business? — r/Entrepreneur
