{"version":"1.0","type":"agent_native_article","locale":"en","slug":"saas-model-didnt-die-learned-to-prove-its-worth-moxzwmrl","title":"The SaaS Model Didn't Die, It Learned to Prove Its Worth","primary_category":"business-models","author":{"name":"Tomás Rivera","slug":"tomas-rivera"},"published_at":"2026-05-09T06:03:17.576Z","total_votes":89,"comment_count":0,"has_map":true,"urls":{"human":"https://sustainabl.net/en/articulo/saas-model-didnt-die-learned-to-prove-its-worth-moxzwmrl","agent":"https://sustainabl.net/agent-native/en/articulo/saas-model-didnt-die-learned-to-prove-its-worth-moxzwmrl"},"summary":{"one_line":"The SaaS sector is not collapsing but undergoing a selection process where only providers that demonstrate measurable, verifiable value survive the new capital and buyer scrutiny.","core_question":"Has the SaaS business model fundamentally broken, or has it simply been forced to prove what it always should have proven?","main_thesis":"The so-called SaaSpocalypse is a misnomer: what is happening is a structural demand shift where buyers, investors, and capital markets now require verifiable proof of measurable outcomes before allocating capital or renewing contracts, filtering out providers that grew on narrative rather than demonstrated retention and expansion."},"content_markdown":"## The SaaS Model Didn't Die, It Learned to Prove Its Worth\n\nThere is a precise moment in the cycle of any business model where the collective narrative stops describing reality and starts producing it. The SaaS sector reached that moment more than a year ago, and the industry is still processing what it means. It is not the collapse that some anticipated with the term \"SaaS-pocalypse,\" but neither is it a frictionless return to the growth of 2021. What is happening is more uncomfortable and more useful than either of those two versions: buyers, investors, and capital markets are demanding proof that the software they contract actually changes something measurable in the people who use it.\n\nThat seems obvious. It wasn't.\n\nDuring the period of abundant liquidity that followed the pandemic, the recurring revenue model functioned as a sufficient argument in itself. Having a reasonable renewal rate and an upward-sloping growth curve was enough to sustain valuation multiples that today seem difficult to justify. Multiples on ARR—annual recurring revenue—reached levels that discounted years of future growth as if that growth were a structural certainty. According to data from SaaS Capital, those multiples are now at lows not seen in over a decade, which reflects not only an interest rate adjustment, but a shift in what kind of evidence is considered convincing when allocating capital.\n\nThe sector is not collapsing. The projection toward 2030 still points to more than 900 billion dollars in global market value, with a compound annual growth rate of around 18%. For 2024, spending on software as a service was estimated at close to 232 billion dollars according to Gartner. The absolute figures do not contradict the expansion narrative. What changed is the quality of evidence required for those figures to translate into favorable valuation. And that change has very concrete operational implications for those who build or finance these businesses.\n\n## Artificial Intelligence Doesn't Replace Software; It Pressures Its Justification\n\nPart of the narrative panic around the \"end of SaaS\" comes from a hasty reading of the role that artificial intelligence is playing in the sector. The simplified argument goes: if AI can generate code on demand, build autonomous workflows, and replicate functionalities that previously required annual contracts, then per-seat subscription models lose their reason for being. There is something true in that pressure. There is also much that exaggerates the speed of change and underestimates the real friction involved in adopting it.\n\nWhat AI is effectively doing is lowering the marginal cost of producing generic software. That puts pressure on the layers of the market that competed primarily on standard functionality at an acceptable price. A basic CRM, a task management tool, a forms platform: these categories face real price compression because the barrier to replication has been reduced. But software that operates at the intersection of specific industrial processes, proprietary data flows, and deep business logic cannot be replicated with a prompt. Complexity has not disappeared; it has been redistributed.\n\nCompanies that buy specialized software for industries such as fashion, manufacturing, or logistics are not acquiring isolated functionalities. They are buying the accumulation of operational knowledge that took years to codify, plus the infrastructure for integration with legacy systems, plus built-in regulatory compliance. None of those things are generated in real time with an assisted coding tool. What AI can do in this context is accelerate the detection of anomalies in those processes, automate repetitive decisions within already-designed workflows, or connect data sources that previously required costly manual integration. That does not destroy the model: it forces it to demonstrate with greater precision than before exactly where it is generating incremental value.\n\n**The true effect of AI on the SaaS sector is not one of substitution but of demand.** It forces providers to be more specific about which part of the customer's problem they are solving, with what measurable outcome, and under what conditions of adoption. That demand existed before; AI makes it impossible to avoid.\n\n## When Pricing Stopped Being Per Seat and Started Being Per Outcome\n\nThe shift in pricing models that is accelerating across the sector has implications that go far beyond contractual mechanics. The move from per-user licenses toward consumption-based or outcome-based pricing fundamentally alters how risk is distributed between provider and customer, and what kind of operational relationship is needed for the model to function.\n\nIn the per-seat model, the provider charges for access and the customer assumes the risk of adoption. If users do not use the tool, the contract renews anyway until someone in procurement reviews the invoice. That decoupling between usage and payment was for years a source of comfortable margins for providers and a source of silent waste for buyers. The data from Zylo on \"shadow AI\" and unpredictable software costs is not an anomaly: it is the contemporary expression of a structural problem that existed long before AI entered the picture.\n\nThe outcome-based model closes that decoupling by force. If the contract specifies that the provider charges in proportion to the reduction in productive cycle time, or to the percentage increase in conversion rate, or to the decrease in errors in an operational process, then the relationship becomes verifiable. That is good for customers. For providers, it implies that they need to instrument their products with enough depth to measure those results reliably, and they need to have the conviction, backed by data from previous customers, that the product actually produces them.\n\nHere a trap emerges that deserves attention. Several providers who are adopting the language of \"value-based pricing\" or \"outcome-oriented models\" are not building the measurement infrastructure that model requires. They are using the vocabulary of outcomes without the verification apparatus that would make them credible. That is not a model transition; it is a cosmetic reframing of the previous contract. **The difference between an outcomes model and an access model with outcomes-based marketing lies in whether the provider accepts that its compensation will vary when results do not materialize.** Very few actually accept that in practice.\n\nThe move toward consumption-based pricing being adopted by infrastructure platforms and some application layers is a more honest version of this transition. The customer pays for what they use, the provider has an incentive for usage to be high because it reflects real adoption, and both parties have visibility into the relationship between activity and cost. The problem is that this model introduces budget volatility that finance teams at large organizations handle poorly, which generates internal resistance in the purchasing process even when the product is superior.\n\n## Vertical SaaS Has an Advantage That Horizontal Cannot Copy Quickly\n\nThe distinction between horizontal and vertical software has always existed, but the current market pressure is making it more strategically relevant. Horizontal software competes on adoption scale and functional breadth. Vertical software competes on depth of domain understanding and on the switching costs that depth generates. In an environment where AI is lowering the cost of producing generic functionality, the horizontal advantage erodes faster than the vertical one.\n\nA provider that has spent ten years building software for the textile production chain has embedded in its product a knowledge of traceability standards, material waste logic, integration with specific machinery, and regional regulatory compliance that cannot be replicated by copying its interface. That knowledge took years to translate into software logic because it required real conversations with plant operators, with production directors, with quality auditors. AI can accelerate the next iteration of that product. It cannot compress the ten years of accumulated learning embedded in the current one.\n\n**The metric that best predicts the durability of a vertical SaaS is not the growth rate of new contracts, but net revenue retention**, which measures whether existing customers are expanding their usage and spending over time. According to available data, investors and lenders are using this metric, alongside gross revenue retention, as the most reliable indicator that a product has genuine stickiness. Net retention above 110% indicates that expansion within the installed base is compensating for customer churn, making the model self-sufficient in terms of growth without relying exclusively on new customer acquisition.\n\nThat pattern is harder to build in horizontal software because it requires customers to find reasons to expand usage within the same platform, and those reasons compete with the offerings of dozens of alternatives that do the same thing with minor variations. In the vertical, expansion occurs more naturally because the provider has visibility into other friction points within the same operational process it already knows well. The next problem to solve is right next to the one it already solved.\n\nThe trap for vertical providers is confusing depth of domain knowledge with strategic comfort. Knowing an industry well is an initial advantage, not a permanent guarantee. If that knowledge is not updated with changes in the customer's processes, with new regulations, with the evolution of available technology, it becomes technical debt disguised as specialization. The providers that maintain high net retention over time are those that continue learning from the customer with the same intensity after year three as they did in year one.\n\n## Durability Is Not a Narrative, It Is a Revenue Architecture With Real Friction\n\nThe SaaS sector arrives at 2026 having passed through a stress test that was part valuation correction, part macroeconomic adjustment, and part genuine pressure from new technologies. What emerges from that process is not a broken model in search of narrative redemption. It is a more legible model, where the metrics that always should have mattered—retention, expansion within the installed base, customer acquisition cost relative to lifetime value—are now receiving the attention they deserved long before now.\n\nThe term \"SaaS-pocalypse\" accurately described the fear, not the reality. What is happening is a selection process within the sector: providers that built their growth on real adoption, on demonstrated retention, and on organic expansion within their customer base are passing through the filter with their models intact. Those that grew on the ease of selling in a technology spending environment without scrutiny are facing the cost of having deferred that conversation.\n\nFor those who build or finance these businesses, the adjustment does not require a philosophical change but rather a clarity that the previous context made optional: demonstrating, with their own verifiable data, that the product produces the result that justifies the contract. That is not a new standard imposed by the market. It is the standard that always defined whether a business model was sound. The market has simply stopped accepting the option to defer it.","article_map":{"title":"The SaaS Model Didn't Die, It Learned to Prove Its Worth","entities":[{"name":"SaaS Capital","type":"institution","role_in_article":"Source of data on ARR multiple compression to decade lows"},{"name":"Gartner","type":"institution","role_in_article":"Source of 2024 global SaaS spending estimate of approximately 232 billion dollars"},{"name":"Zylo","type":"company","role_in_article":"Referenced for data on shadow AI and unpredictable software costs illustrating the per-seat decoupling problem"},{"name":"SaaS","type":"technology","role_in_article":"The business model under analysis throughout the article"},{"name":"Artificial Intelligence","type":"technology","role_in_article":"Pressure force on SaaS justification and pricing, accelerator of vertical product iteration, and driver of demand for measurable outcomes"},{"name":"ARR","type":"product","role_in_article":"Annual recurring revenue metric used as valuation basis and now under scrutiny for quality of evidence"},{"name":"Net Revenue Retention","type":"technology","role_in_article":"Key metric investors use to assess SaaS durability and stickiness"}],"tradeoffs":["Outcome-based pricing closes the usage-payment decoupling and builds credibility but requires accepting variable compensation when results do not materialize","Consumption-based pricing reflects real adoption and aligns incentives but introduces budget volatility that slows enterprise purchasing cycles","Vertical depth creates durable switching costs and natural expansion but limits total addressable market compared to horizontal plays","Investing in measurement infrastructure for outcomes verification increases operational cost but is the only way to make outcomes pricing credible","Maintaining domain knowledge currency requires continuous customer learning investment after year three, which competes with new feature development resources"],"key_claims":[{"claim":"ARR multiples are at lows not seen in over a decade, per SaaS Capital data.","confidence":"high","support_type":"reported_fact"},{"claim":"Global SaaS market is projected to exceed 900 billion dollars by 2030 at approximately 18% CAGR.","confidence":"high","support_type":"reported_fact"},{"claim":"2024 SaaS spending was estimated at approximately 232 billion dollars according to Gartner.","confidence":"high","support_type":"reported_fact"},{"claim":"AI is lowering the marginal cost of generic software production, creating real price compression in standard-functionality categories.","confidence":"medium","support_type":"inference"},{"claim":"Vertical SaaS providers with ten or more years of domain-specific knowledge cannot be replicated by AI-assisted coding tools in the short term.","confidence":"medium","support_type":"inference"},{"claim":"Net revenue retention above 110% indicates the model is self-sufficient in growth without relying exclusively on new customer acquisition.","confidence":"high","support_type":"reported_fact"},{"claim":"Many providers adopting outcomes-based pricing language are not building the measurement infrastructure required to make that model credible.","confidence":"medium","support_type":"editorial_judgment"},{"claim":"Consumption-based pricing introduces budget volatility that finance teams at large organizations handle poorly, generating internal purchasing resistance.","confidence":"medium","support_type":"inference"}],"main_thesis":"The so-called SaaSpocalypse is a misnomer: what is happening is a structural demand shift where buyers, investors, and capital markets now require verifiable proof of measurable outcomes before allocating capital or renewing contracts, filtering out providers that grew on narrative rather than demonstrated retention and expansion.","core_question":"Has the SaaS business model fundamentally broken, or has it simply been forced to prove what it always should have proven?","core_tensions":["Growth narrative vs. verifiable proof: the sector grew on narrative sufficiency and must now operate on evidence sufficiency","Provider risk vs. customer risk: outcome-based models transfer adoption risk from customer to provider, which most providers resist in practice","Horizontal scale vs. vertical depth: AI erodes the horizontal advantage faster, making vertical depth more valuable but less scalable","Short-term sales velocity vs. long-term retention architecture: easy-environment sales deferred the proof conversation that is now mandatory","AI as threat vs. AI as accelerator: the same technology that pressures generic SaaS can strengthen specialized vertical providers"],"open_questions":["Which specific vertical categories will consolidate fastest as AI compresses horizontal alternatives?","At what point does consumption-based pricing volatility become acceptable to enterprise finance teams, and what product or contractual designs reduce that friction?","How do providers build credible measurement infrastructure for outcomes without making it a cost center that erodes the margins the model is supposed to protect?","Will net revenue retention above 110% remain the primary investor signal, or will new metrics emerge as AI-native SaaS products change the expansion dynamic?","How long can providers sustain outcomes-based pricing language without verification apparatus before buyers systematically call the bluff at renewal?","What is the minimum domain depth required for a vertical SaaS to generate genuine switching costs versus perceived switching costs?"],"training_value":{"recommended_for":["SaaS founders and product leaders evaluating pricing strategy","Venture capital and growth equity investors assessing SaaS portfolio durability","Enterprise software buyers and procurement teams reviewing contract structures","Strategy consultants advising technology companies on competitive positioning","Business agents trained on software business model evaluation and capital allocation logic"],"when_this_article_is_useful":["When evaluating a SaaS investment and needing to assess whether retention metrics justify the growth narrative","When a SaaS provider is considering a pricing model transition and needs to understand what genuine outcomes pricing requires operationally","When advising a vertical software company on how to articulate its competitive moat against AI-native alternatives","When a buyer organization is auditing software spend and needs a framework for distinguishing real adoption from access-without-usage","When building a SaaS product roadmap and deciding between horizontal feature expansion and vertical domain deepening"],"what_a_business_agent_can_learn":["How to distinguish a genuine pricing model transition from cosmetic reframing using measurement infrastructure as the diagnostic signal","How net revenue retention above 110% functions as a self-sufficiency indicator for SaaS growth models","Why AI lowers marginal cost of generic software but cannot compress accumulated domain knowledge in vertical providers","How the decoupling between payment and usage in per-seat models creates structural waste that accumulates until forced review","How to frame the difference between horizontal and vertical competitive advantage in terms of switching cost durability under AI pressure","Why valuation multiple compression reflects a change in evidence standards, not just interest rate adjustment"]},"argument_outline":[{"label":"1. The liquidity era created false validation","point":"During post-pandemic abundant liquidity, recurring revenue and upward ARR curves were sufficient to sustain high valuation multiples without requiring proof of actual user value or adoption.","why_it_matters":"This context allowed weak business models to scale, and the correction is now exposing which providers had real retention versus which had favorable macro conditions."},{"label":"2. AI pressures justification, not existence","point":"AI lowers the marginal cost of producing generic software, compressing prices in horizontal, standard-functionality categories, but cannot replicate the accumulated operational knowledge embedded in specialized vertical software.","why_it_matters":"Providers must now articulate precisely which part of the customer problem they solve and with what measurable outcome, a demand AI makes impossible to avoid."},{"label":"3. Pricing models are shifting from access to outcomes","point":"The move from per-seat to consumption-based or outcome-based pricing redistributes risk from customer to provider and closes the decoupling between payment and actual usage.","why_it_matters":"Providers adopting outcomes language without building measurement infrastructure are doing cosmetic reframing, not model transition, which will be exposed at renewal."},{"label":"4. Vertical SaaS has a structural durability advantage","point":"Domain depth, switching costs from embedded operational knowledge, and natural expansion within the same process chain give vertical providers a moat that horizontal players cannot replicate quickly.","why_it_matters":"Net revenue retention above 110% is the metric that best signals this durability, and investors are now using it as a primary capital allocation signal."},{"label":"5. The filter is already running","point":"Providers built on real adoption, demonstrated retention, and organic expansion within their customer base are passing through the market correction intact; those built on easy-spending-environment sales are not.","why_it_matters":"The standard being applied now is not new; the market has simply stopped accepting deferral of proof."}],"one_line_summary":"The SaaS sector is not collapsing but undergoing a selection process where only providers that demonstrate measurable, verifiable value survive the new capital and buyer scrutiny.","related_articles":[{"reason":"Directly relevant: AI agents entering enterprise systems changes the SaaS adoption and identity management landscape, extending the article's argument about AI pressuring SaaS justification into a concrete operational scenario.","article_id":12386},{"reason":"Relevant: MSP business model under pressure to integrate previously separate service lines mirrors the SaaS argument about providers needing to demonstrate integrated value rather than selling access to isolated functionalities.","article_id":12378}],"business_patterns":["Valuation multiple compression following liquidity withdrawal exposes models built on narrative rather than retention","Net revenue retention above 110% as a self-sufficiency signal in SaaS growth","Decoupling between payment and usage in per-seat models creates silent waste that accumulates until procurement review","Vertical expansion follows natural adjacency because the provider already understands the operational process and can see the next friction point","Cosmetic reframing of pricing models without underlying measurement infrastructure is a detectable pattern at contract renewal","AI accelerates iteration on existing domain knowledge but cannot compress the years required to accumulate it initially"],"business_decisions":["Whether to shift pricing from per-seat to consumption-based or outcome-based models","Whether to invest in measurement infrastructure before adopting outcomes-based pricing language","Whether to pursue horizontal scale or vertical domain depth as primary competitive strategy","Whether to prioritize new customer acquisition or expansion within the existing installed base","How to instrument products to generate verifiable outcome data for customers and investors","Whether to position AI as a product replacement risk or as an accelerator of existing domain knowledge"]}}