Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

Alex Lieberman says rebuilding gets harder as you move upmarket because a wrong rip-and-replace can put hundreds of millions or billions at stake. CJ Hess says mid-tier SaaS replacement depends on whether the prize justifies ongoing maintenance and cognitive load. Tenex built its own CRM and OS, but treats that as exception.

Related Insights

Contrary to conventional wisdom, MongoDB's CEO reveals enterprise leaders have a surprising appetite for full system replacement. An AI-native company that can replace an entire legacy system of record—making it cheaper, faster, and better—will get a leader's attention far more effectively than one offering an incremental feature layer on top of an existing platform.

Frontier AI companies still pay for legacy SaaS not because they can't build alternatives, but because it's a poor allocation of scarce, expensive engineering resources to replace established, functional tools.

For Constellation Software's customers, like court systems, switching software isn't just a complex IT project. It involves maintaining a legal chain of custody for records. The high risk of data alteration during migration makes switching practically impossible unless a new solution is 10x better.

The predicted death of SaaS will be slower than expected because enterprises are hesitant to build and maintain their own software. They prioritize having a vendor for liability ("someone to blame"), need external maintenance, and want the competitive advantage of early access to new AI models that major SaaS providers receive.

The fantasy of replacing a major SaaS platform like Salesforce with a custom-built tool ignores the total cost of ownership. Beyond initial development, the internal team becomes responsible for documentation, feature upgrades, security, support tickets, and user enablement—functions that are bundled with a commercial product.

The "SaaSpocalypse" threat is real, but primarily for smaller software platforms that offer a single point solution. Large, established systems of record (like ERPs and CRMs) are not at risk of being replaced by an LLM. Enterprises value the stability and compliance of these platforms, making integration, not replacement, the likely path forward.

To transition to AI, leaders must ruthlessly dismantle parts of their existing, money-making codebase that are not competitively differentiating or slow down AI development. This requires overcoming the team's justifiable pride and emotional attachment to legacy systems they built.

The idea that AI will eliminate SaaS is overblown because it incorrectly projects small startup behavior onto large enterprises. Fortune 100s face immense change management, security, and maintenance challenges, making replacing established vendors with internal AI-coded tools impractical.

Point solutions that integrate with existing CRMs rarely become massive, generational companies. To achieve a monumental outcome, especially during a platform shift like AI, a startup must take the harder path of building the new system of record from the ground up, not just layering on top of the old one.

The ability to rapidly build custom software with AI is tempting. However, the ongoing maintenance and data quality assurance are the core business of SaaS companies. Buying a dedicated tool like a CRM often provides more value and less overhead than a custom-built solution, even with AI assistance.