blog.JanWiersma.com

The State of SaaS Disruption – 2025 | Part 1

The AI Tsunami: How the SaaS World is Evolving

For the past fifteen years, the Software-as-a-Service model has been the engine of enterprise innovation. It created trillion-dollar companies and reshaped how every business on the planet operates. That era is now undergoing a profound evolution.

I’m hearing a growing chorus in boardrooms and PE/VC conversations declaring that “SaaS is dead.” While I find that statement to be a dramatic oversimplification, it points to an undeniable truth: the SaaS world we knew—built on per-seat licenses, feature wars, and apps as the primary interface—is facing a seismic shift. This isn’t a distant forecast; it is the central strategic challenge for every SaaS leader and investor in 2025.

The force driving this change is not another business model innovation. It is a technological tsunami called “Artificial Intelligence”.

This isn’t about adding a “smart” feature to your dashboard. It is a fundamental rewiring of how software is created, experienced, and valued. The goal of this series is to move beyond the hype, acknowledging the real threats while framing the situation as a profound evolution—one that presents immense opportunity. Over these six parts, I will provide a clear-eyed playbook for navigating this disruption, starting with a stark assessment of the landscape today.

Key Takeaways for the C-Suite & Investors

  • SaaS Isn’t “Dead,” But Its Foundation is Obsolete. The model of an application sitting on top of a database is no longer a defensible moat. AI has commoditized the very act of building software, forcing a change in where we find value.
  • The Feature War is Over. The Outcome War Has Begun. Competing on who has the longest feature list is a losing battle. The new competitive frontier is about providing autonomous outcomes, driven by AI that can execute complex tasks without direct human operation.
  • The User Interface is No Longer a Guaranteed Moat. The rise of AI Agents threatens to unbundle the front end from the back end. If an AI can interact with your service via an API, the value of your carefully crafted UI could plummet.
  • This is a Strategic Imperative, Not a Product Update. Responding to this shift requires more than a new line item on your product roadmap. It demands a holistic re-evaluation of your business model, go-to-market strategy, and a clear-eyed assessment of your company’s true defensibility.

The End of an Era, The Beginning of a Reckoning

The SaaS business model was beautifully simple. Build a compelling application on top of a database, deliver it via the cloud, and charge users a recurring fee. For years, the primary axes of competition were feature velocity, user experience (UI/UX), and go-to-market execution. Companies with the best-funded engineering teams could out-build competitors, and those with the most efficient sales and marketing engines could out-sell them.

That model is being redefined at breathtaking speed.

AI has become a massive force of supply-side commoditization. Tools like GitHub Copilot and other AI-assisted platforms have supercharged developer productivity, enabling smaller, leaner teams to replicate features that once took large engineering departments months or years to build. As I’ve seen with my portfolio companies, what used to be a technical moat is now, at best, a temporary speed bump. When a motivated developer can knock off your core functionality in a weekend, you are no longer competing on technology; you are competing on something else entirely.

This isn’t a gentle tide. It is an AI Tsunami, and it is washing away the foundations of value that the SaaS industry was built upon.

Beyond Clippy: Understanding the Two Waves of AI Disruption

To navigate this new reality, it’s critical to understand that the AI Tsunami is hitting the SaaS shoreline in two distinct, powerful waves. Many leaders are preparing for the first wave, but it’s the second one that heralds a true paradigm shift.

Wave 1: Generative AI – The Great Feature Accelerator

This is the wave we are all feeling right now. Generative AI (GenAI) models like GPT-4 and Claude are being integrated into existing SaaS products to enhance functionality. They can draft marketing copy, summarize sales calls, write SQL queries, and automate repetitive tasks.

This is the evolutionary force of AI. It makes existing products better, faster, and smarter. While powerful, this wave primarily accelerates the old game. It helps you win the feature war, but it doesn’t change the rules of the war itself. The danger here is complacency. Adding GenAI features is now table stakes, and the productivity gains it offers your team are also available to your competitors. It’s a race that requires you to run faster just to stay in the same place.

Wave 2: Agentic AI – The Great Interface Unbundler

This is the revolutionary wave, and it demands strategic preparation. The next paradigm is Agentic AI—autonomous systems that can understand a goal, create a plan, and execute complex, multi-step tasks across different applications on a user’s behalf.

Think beyond a chatbot. An AI Agent is an entity you could instruct: “Find the top five enterprise leads from our CRM who have a budget over $250k, draft personalized outreach emails based on their recent company news, and schedule introductory calls on my calendar for next week.” The agent would then perform those tasks without you ever opening your CRM or email client.

As Microsoft CEO Satya Nadella has argued, AI agents are poised to become a new “AI tier” in the software stack. This layer sits between the user and the applications. In this future, the primary interface to software is no longer a graphical user interface (GUI); it is a conversational command to an agent. Your SaaS product, in this scenario, becomes a “headless” collection of APIs that these agents call upon. Your beautiful, award-winning UI, a traditional moat, risks being bypassed entirely.

The New Strategic Imperative: From Application to Outcome

This brings us to the core strategic shift required to thrive. The value proposition of SaaS is moving from the application to the outcome. Customers will not pay for access to a tool; they will pay for a result that an AI delivers.

This shift challenges traditional SaaS business models. Per-seat pricing becomes illogical if an AI agent can perform the work of ten employees. If your value is no longer in the UI, then your brand, your user habits, and your ecosystem integrations become paramount.

As a SAAS business leader or investor, you must now ask a new set of honest questions:

  • What is our core, defensible asset? If it’s not the code or the UI, is it our proprietary data, our deep workflow integration, our trusted brand, or our unique access to a distribution channel?
  • How do we price for outcomes? What does a value-based model look like when AI is delivering that value?
  • How do we prepare for a “headless” future? Is our product architected to be “agent-friendly” with robust and well-documented APIs?

This is no longer a technical discussion to be delegated to the CTO. It is a fundamental business model conversation that belongs in the boardroom. The companies that thrive will be those that confront these questions head-on.

The established SaaS world is changing, but this disruption is also creating a once-in-a-generation opportunity to build the next wave of market-defining companies.

Coming up in Part 2: I will dive deep into the most transformative force on the horizon: The Agentic Shift and the coming “No UI” future. We’ll explore what it means to build “agent-native” products and how to survive when your interface is no longer your own.

Share

The tale of Services v.s. Cloud product organizations

<This blog is background material as part of my 2017/2018 VU lecture series >

 

As companies transition their product delivery methodology from on-premise software to a As A Service (PAAS/SAAS) model, they are confronted with very different motions across their Sales, Marketing, Development, Services and Support organizations.

One of the examples that show the difference how ‘execution’ is done in these models, is how Services and Product is managed across the organization. For larger on-premise software companies it is not uncommon to see Professional Services (PS) bookings v.s. software bookings rates of >3, meaning that customers pay more for the implementation and assistance in software management, then the actual purchase price of the software.

The Cloud delivery model has very different PS dynamic, as Waterstone reports in their 2015 report – changing Professional Services Economics ;

“There is growing preference for Cloud- and SaaS-based solutions that, on average, have a PS attach rate around 0.5x to 1.0X (versus the 2.9x PS attach rate commonly seen with traditional licensed products).”

The analysis is not strange, as Cloud is all about providing low friction of onboarding by self-service and automation. This means getting the human out of the equation, as it’s a limiting factor in scalability and raises cost.

Cloud is all about minimizing the time from idea -to- revenue, while being able to scale rapidly and keeping cost low.

The definition of ‘the product’ in a Cloud world therefore isn’t only about the bits & bytes, but includes successful onboarding of the customer and maximizing their usage.

Continue with reading

Share

Lecture: Operate unreliable IS in a reliable way

I recently started a lecture series at the Vrije University of Amsterdam (VU). As part of this I did a lecture on how to operate unreliable Information Systems in a reliable way – or: Everything breaks, All the time.

Synopsis:

Behind the clouds of cloud computing! How can we reliably operate systems that are inherently unreliable?

What if for some hours, we do not have access to the services such as navigators, routers, and other communication technologies? It seems our life will be at stake if major digital services fail! Many promises of digital technologies, from big-data to the Internet of the things and many others are based on reliable infrastructures such as cloud computing. What if these critical infrastructures fail? Do they by the way fail? How the responsible companies and organizations manage these infrastructures in a reliable way? And what are the implications of all this for companies who want to base their business on such services?

As part of the lecture we explored modern complex systems and how we got there, using examples from Google and Amazon’s journey and how it relates to modern enterprise IT. We used the material of Mark Burgess to explore how to prevent systems from spiralling out of control. We closed off looking at knowledge management based on the ‘blameless retrospective’ principles and how feedback cycles from other domains are helping to create more reliable IT.

Relevant links supporting the lecture :

The used presentation can be found here:  VU lecture
Recording of the session is available within the VU.

VU Assistant Professor Mohammad Mehrizi posted a nice lecture review on LinkedIn, including a picture with some of the attending students.

 

Share

DCD EMEA Awards 2016 Finalist !

Less then 24 hours after I published my ‘thank you team’ post, Datacenter Dynamics announced their nominees for this year’s DCD EMEA 2016 Awards.

I’m very proud one of the mentioned projects in my original post got nominated in the Category Cloud Journey of the Year

finalists_logos

The selected project is our move of SDL Machine Translation from our co-lo datacenter to a IAAS cloud solution;

Availability of content in multiple languages is key to driving useful international business. SDL’s Statistical machine translation delivers high quality translation services to more thousands of customers. While SDL’s research organisation already explored a new approach to machine translation, the future development and deployment needed more flexibility in technology choice and dynamic scalability to be commercially successful. Over 10 months, SDL migrated their current workload deployment consisting of hundreds of servers, without customer downtime, to a private Cloud deployment. The migration included a project team of more than 35 staff in 5 time zones. Besides flexibility and scalability gains, the migration saves SDL more than 450k GBP over 4 years.

The teams worked long hours, overcoming many obstacles a long the way. Congrats to all involved!

Share

The new normal – Cloud & developer enablement.

48_imgAccording to AWS CTO Werner Vogels “Cloud is now the new normal.”

Where the first day keynote at AWS’s ReInvent 2015 conference was all about enabling companies to migrate their current services to the cloud, the second day keynote by Vogels was all about the ‘new normal’ – developer enablement.

With new services like AWS Snowball , AWS Database Migration Service and AWS Schema Conversion Tool , AWS tries to smoothen the migration path from old on-premise infrastructure & application deployments, to using AWS’s Infrastructure As A Service offering (EC2, RDS, VPC, S3, ..).

While these new services help companies to move to a consumption model for compute, storage and networking, it is still very infrastructure focused. Design decisions around (virtual)network layout, load balancers and the build & management of the operating systems (Windows/Linux) are still the customer’s responsibility.

Needing to still deal with all these elements, holds developers back from moving fast as they go from idea to the launch of a new service. It slows the creation of real value to the company down.

In the real ‘new normal’ world, the developer is enabled to deploy a new service by building & releasing something fast, without needing to worry about the infrastructure behind it. By stitching external managed capabilities/services together in a smart way the developer can move even faster.

Where in the past a developer would try to speed releases up by code-reuse with, for example, software libraries, the availability of developer ready services like a fully managed message queuing service (AWS SQS) or a push messaging service (AWS SNS) have enabled developers to move even faster without worrying about the manageability of the solution.

Continue with reading

Share