SaaS Isn’t Dead. The UI Monopoly Is.

The "SaaS is dead" narrative is running hot right now. Reid Hoffman rightfully pushed back on it this week. The inference most people are drawing is imprecise, and imprecision here is expensive.

Quoting Yogi Berra, "It's déjà vu all over again."

The rise of SaaS wasn't the end of licensed software companies. It forced a reckoning... business models had to evolve, technology bases had to modernize, and the transition was deeply uncomfortable. Microsoft became one of the most successful SaaS businesses in history, built on top of decades of entrenched installed base. SAP, the subject of the a16z piece I referenced earlier this week, is still a backbone for the world's largest enterprises over twenty years later. The platform value held. The interface and delivery model evolved around it.

Adobe might be the most interesting case right now, not as a clean success story, but as a live illustration of the pattern. The company successfully navigated a rough transition from boxed software to Creative Cloud, emerging dramatically stronger. Today, it's growing revenue at double digits with industry leading margins... and its stock is down 57% from its peak as the market prices AI transition risk.

Speaking of that risk, the $400B SaaS market won't evaporate. Many will survive, though some won't. But systems of record will endure. What's being reinvented is the interface and workflow layer on top. Those are very different things, and confusing them leads to bad strategic decisions.

For media SaaS specifically, this distinction matters. The platforms powering content operations, asset management metadata, QC, distribution... They encode decades of institutional knowledge, workflow logic, compliance rules, and integration architecture. That doesn't become worthless because agents can now orchestrate across it. It can become more valuable, provided it's exposed correctly.

The SaaS leaders who win in this moment aren't the ones declaring funerals. They're asking a different question: how do I make my platform the essential substrate for an agentic ecosystem to run atop? How do I become a reliable building block in the orchestration layer rather than a UI people navigate manually?

That's not a defensive posture. It's an offensive one. The platforms that get agent ready first, that expose clean, well documented capabilities that orchestration layers can compose reliably, will be integrated into far more workflows than their original SaaS footprint ever enabled.

The funeral is for the seat-based UI paradigm. The underlying value, the data, the domain logic, the integrations, that's not in the casket. It's the foundation everything else gets built on.