The SaaSpocalypse Is Real — But Not for the Reasons Wall Street Thinks

February 6, 20269 min read

A colleague of mine runs a blog. It gets decent traffic — or at least it used to. When I checked his analytics recently, I noticed something strange: most of his visitors aren't human anymore. AI chatbots doing web searches are now his primary traffic source. Zero organic human traffic. The bots love his content. They cite it, they reference it, they send their users to it. But actual people typing queries into Google and clicking through? Gone.

That happened quietly. What happened this week was not quiet at all.

The Week Wall Street Panicked

On January 30th, Anthropic dropped 11 starter plugins for Claude Cowork on GitHub. Legal review, NDA triage, vendor checks, sales workflows, data analysis. Nothing new if you've been paying attention. But for the broader market? It was a bomb.

Thomson Reuters — a company pulling in roughly six billion a year from lawyers paying expensive subscriptions for databases and research tools — lost 22% of its stock value in five days. LegalZoom cratered nearly 20%. RELX, the parent of LexisNexis, dropped 14%. Even ServiceNow and Salesforce took 7% hits as investors questioned whether per-seat licensing has a future at all.

Analysts at Jefferies called it the "SaaSpocalypse." JPMorgan's Toby Ogg put it more bluntly: the software sector is "being sentenced before trial."

And the thing is — they're not entirely wrong to panic. They're just late.

LinkedIn Discovered Claude Code

Here's what actually happened. People on LinkedIn finally figured out what Claude Code and Cowork can do. I know that sounds reductive, but it's the truth. For months, the AI enthusiast crowd — the people building agents, replacing their own SaaS subscriptions, running agentic workflows — we've been living in this reality. The LinkedIn crowd was still posting about n8n "agents" and calling themselves AI consultants for knowing how to write a ChatGPT prompt.

The Cowork plugins didn't create new capabilities. They made existing capabilities visible to a non-technical audience. That's the difference. When you can type /review-contract and get clause-by-clause analysis against your firm's playbook — green, yellow, red flags — suddenly the abstract idea of "AI replacing knowledge work" becomes concrete. People could see it. And Wall Street, as usual, was the last to notice.

The enthusiasts have been here for a while. I've been using Claude Code for months, building agent systems, replacing tools I used to pay for. WhisperFlow is a perfect example — a speech-to-text app you can vibe code in under an hour that does what MacWhisper does, running entirely on local models, zero subscription cost. The software exists because I told an AI to build it. That's the new reality.

The Consulting Reckoning

This isn't limited to SaaS companies. Nathaniel Whittemore — host of The AI Daily Brief and someone whose analysis I follow closely — has been laying out how AI will gut the consulting industry. His argument is specific and worth paying attention to: small teams of consultants managing swarms of agents will become the default model. Billable hours will give way to results-based pricing because charging for time makes no sense when AI collapses the cost of inputs. Partners at big firms will realize they don't need the firm's resources anymore and leave to start their own practices with one or two anchor clients.

McKinsey is already there. They've deployed over 12,000 AI agents internally. Teams of 2-3 people are replacing teams of 14. This isn't hypothetical — it's happening inside the firm that literally wrote the book on corporate consulting.

The implication is stark: if you're a consulting firm charging $200K for work that an agentic system can deliver for a few dollars in API costs, your moat just evaporated. Not completely — Whittemore rightly points out that judgment, taste, and emotional intelligence become the new differentiators. But the commodity layer of consulting? The research, the analysis, the slide decks? That's getting automated whether the industry likes it or not.

Vibe Coding Is No Longer a Joke

We just passed the one-year anniversary of Andrej Karpathy coining "vibe coding." In that year, it went from funny insider term to existential threat for billion-dollar companies. The cost of building a minimum viable product dropped from hundreds of thousands of dollars to almost nothing.

That doesn't mean the technical debt problem disappears. It doesn't. Vibe-coded software is often a ticking time bomb — poor documentation, security vulnerabilities, unscalable architecture. I take this seriously in my own work. When I'm building agent systems, I write proper tests, I think about architecture, I document what I'm doing. That's not typical vibe coding behavior.

But here's the thing the skeptics miss: the technical debt problem is a stage two problem. Stage one is proving the idea works. Stage one is getting your first users, testing product-market fit, iterating fast. For that? Vibe coding is perfect. You build it in an afternoon, you ship it, you see if anyone cares. If they do, you invest in proper architecture. If they don't, you've lost a few hours instead of a few hundred thousand dollars.

The startups get way more shots on goal now. That's the real disruption — not that existing software companies die overnight, but that the barrier to competing with them just collapsed.

The Salesforce Cautionary Tale

Before anyone gets too excited about replacing humans wholesale, remember what happened at Salesforce. Benioff cut 4,000 customer support roles in 2025, proudly announcing that Agentforce could handle it. Months later, executives admitted they were "too confident." Automated systems choked on complex issues. Complaint volumes spiked. Service quality cratered. They ended up reassigning remaining employees and increasing human oversight — exactly the opposite of what the layoffs were supposed to achieve.

The lesson isn't that AI can't do the work. It's that ripping out humans without understanding what they actually do is a recipe for disaster. The companies that will thrive are the ones running human-in-the-loop patterns — AI handling the volume, humans handling the judgment calls. At least for the next few years, until these systems mature.

Where This Actually Goes

I work at a digital marketing agency. I see this disruption from the inside. Website creation is becoming a commodity. SEO services will follow. At some point — probably a 10-year horizon for full commoditization — business owners will register with a platform and get their entire digital presence handled automatically. Websites, lead generation, content, analytics. One-shot builds that are 90-99% production-ready. OpenAI and Anthropic are both moving in this direction. The endgame is a business operating system — agentic infrastructure that handles everything a company needs to exist online.

The big players will build the generic version of this. But here's the gap they can't fill: every business is different, and a one-size-fits-all platform can't account for the specific workflows, data, compliance requirements, and competitive advantages that make each company unique. You can't have an AI automation expert embedded in every business at scale — but you can have specialists who build custom agentic systems tailored to what a specific company actually needs.

That's the market I'm moving into. My own trajectory mirrors what's happening to a lot of people in this space — I started as a working student — web design, concept development, copywriting, Webflow builds. 5.5+ years of full-stack agency work. Now I'm evolving into something that didn't have a job title two years ago: an AI automation specialist, an agentic systems architect. Someone who understands both the business side and the technical infrastructure well enough to build these systems for others.

We're not there yet. But the trajectory is clear, and it's already changing how I work. I can build a complete client prototype faster with my agentic workflow than our traditional process allows. At some point the logical move is to just build the whole project and hand it to the team, because the AI gets me further, faster.

The deeper trend is a shift toward personal software and owned infrastructure. The Unix philosophy, applied to the AI era: small, purpose-built tools created on demand for specific needs. Personal computers running personal software. I'm already living a version of this with my homelab — Nextcloud replacing Google for my personal data, local models for transcription, self-hosted infrastructure I actually control.

For businesses, the same principle applies. Invest in your own agentic infrastructure rather than depending on big platforms. Proprietary datasets, high standards for security and privacy, owning your own data and services. The companies that build their own moats through custom AI systems will thrive. Not because Thomson Reuters or Salesforce disappear — but because the tools are now good enough that you don't need to depend on them anymore. The question is whether you build that independence yourself, rely on a generic platform to do it, or work with someone who can architect it specifically for you.

The Bottom Line

The SaaSpocalypse is real, but it's a slow burn, not a sudden death. Thomson Reuters isn't going to zero. The difficult things these companies do aren't going away. But a lot of them make a lot of money on very simple software, and now any motivated person with Claude Code can build their own version of that simple software in an afternoon.

The stock market is overreacting in the short term and probably underreacting in the long term. These companies' valuations were projecting growth and profitability that assumed their customers had no alternative. That assumption just broke.

We — the enthusiasts, the early adopters, the people who've been building with these tools for a year or more — we're the leading edge. But the wave is catching up fast. When LinkedIn figures something out, mass adoption is right around the corner.

The best position to be in right now is already building with the tools that are causing this.

Sources

Related Posts

X
LinkedIn