The SaaSpocalypse: A $2 Trillion Design Failure Being Exposed

· Petar Ceklic

They're calling it the SaaSpocalypse. $2 trillion in software value wiped out.

Salesforce. Workday. Atlassian. Figma. DocuSign. All down hard. And Wall Street isn't slowing down.

But this isn't just a market correction. It's a design story that's been twenty years in the making.

What actually happened

Wall Street didn't suddenly turn on SaaS. It watched Klarna rip out Salesforce and replace it with AI. It watched Anthropic launch a tool that does what some platforms charge $150 per seat for. Atlassian cut 1,600 people to fund an AI pivot, and the stock went up. And it panicked.

The panic is rational. If one company can replace a major enterprise platform with an AI integration built in weeks, every SaaS company with a similar architecture is vulnerable. The market is pricing in that risk across the entire sector.

But the vulnerability isn't new. AI just made it visible.

The design failure that built $2 trillion in fragile value

Most SaaS products never solved the problem. They digitised the workflow around it.

Support tickets don't solve customer service. They give customer service a place to happen. Kanban boards don't solve project delivery. They give project managers a surface to organise tasks. Approval chains don't solve procurement. They add structure to a manual process.

Every one of these tools took an analogue workflow, put it on a screen, and charged monthly for access. The work itself, the thinking, the deciding, the doing, still happened in human heads and human hands.

That was fine when there was no alternative. Digitised workflows were faster than paper ones. Cheaper than custom software. Easier to scale. The value proposition was real, even if the underlying problem was untouched. The Yellow Pages is the extreme version of this: a product that lost its purpose but kept shipping because the business model still worked.

AI changes the equation because it doesn't optimise the workflow. It skips it entirely.

Why skipping the workflow matters

When an AI handles customer service, it doesn't file a ticket, assign it to an agent, wait for a response, escalate if needed, and close the loop. It reads the question and answers it. The entire ticketing infrastructure becomes unnecessary.

When an AI manages procurement, it doesn't create an approval chain. It evaluates the request against policy, checks budget, and executes. The workflow that justified the software disappears.

This is why the market correction is so severe. Investors aren't worried about AI making SaaS products slightly less competitive. They're worried that AI eliminates the need for the category entirely.

What comes after the workflow

The next generation of products won't have dashboards to manage. They won't have ticket queues to triage. They won't have Kanban boards to drag cards across.

Someone has to design what comes after.

That's the opportunity hidden inside the SaaSpocalypse. The tools that survive will be the ones that encode genuine domain expertise, the ones that understand the actual problem deeply enough that AI can't replicate the value by skipping the workflow.

If your product needs a tutorial to explain the workflow, the workflow is the problem. And AI just made that problem impossible to ignore.

---

Get in touch

👋 Hello - I live in sunny Leederville, Western Australia.

If you've got a project in mind, let's talk! We can grab a coffee in person or if it's easier, simply book in a Google Meet and we can jump on a call.

Petar Ceklic