{"version":"1.0","type":"agent_native_article","locale":"en","slug":"the-only-saas-metric-that-survives-when-market-gets-tough-mqjie1cd","title":"The Only SaaS Metric That Survives When the Market Gets Tough","primary_category":"business-models","author":{"name":"Camila Rojas","slug":"camila-rojas"},"published_at":"2026-06-18T12:03:08.005Z","total_votes":89,"comment_count":0,"has_map":true,"urls":{"human":"https://sustainabl.net/en/articulo/the-only-saas-metric-that-survives-when-market-gets-tough-mqjie1cd","agent":"https://sustainabl.net/agent-native/en/articulo/the-only-saas-metric-that-survives-when-market-gets-tough-mqjie1cd"},"summary":{"one_line":"SaaS companies that optimize for activity metrics instead of customer economic return are building a retention illusion that market pressure eventually corrects—Net Revenue Retention is the only metric that cannot be gamed without delivering real value.","core_question":"Why do SaaS companies keep measuring the wrong things, and what is the only metric that honestly reflects whether a platform is generating value for its customers?","main_thesis":"Activity metrics (DAU, feature adoption, NPS, session time) create a false signal of health in SaaS businesses. The only durable indicator is Net Revenue Retention, which cannot exceed 100% sustainably unless customers are generating demonstrable economic return from the platform. The real barrier to fixing this is not a choice of what to measure, but the data infrastructure and customer agreements needed to measure what actually matters."},"content_markdown":"## The Only SaaS Metric That Survives When the Market Tightens\n\nThere is a moment in the lifecycle of any subscription software company when the metrics dashboard begins to look like a symptom rather than a tool. Daily active users, feature open rates, session time, module adoption, quarterly NPS. Everything is measured. Everything is presented in green. And yet, contracts are not being renewed.\n\nThat disconnect between activity and value is not new, but neither is it being corrected at the speed that market pressure demands. At a time when enterprise buyers are applying real scrutiny to every line of the technology budget, the question that many software vendors avoid asking themselves honestly is whether their customers are actually making money thanks to their platform, or whether they are simply using a tool that no one has had the time to cancel.\n\nDavid Pickard, global director of Phonexa, recently published in Forbes Technology Council a thesis that summarises that disconnect with a self-evaluation question: if you were your own customer, would you use your software? The provocation is effective because the diagnosis that supports it is precise. The SaaS sector has built a culture of activity metrics that works well for internal roadmaps and investor presentations, but that has an increasingly weak correlation with the customer's actual economic experience.\n\n## When the Success Metric Is Internal\n\nThe problem is not measurement itself. It is what is chosen to measure and why.\n\nVanity metrics — daily actives, login volume, number of features adopted — have a legitimate function in the early stages of a product: they indicate whether the software is being used, whether onboarding is working, whether there is sufficient engagement to justify a round of feedback. The mistake occurs when those metrics migrate to the centre of the executive dashboard without having made the transition toward metrics of economic outcome.\n\nA customer can generate a high usage pattern while simultaneously generating less money than before implementing the platform. The software consumes configuration time, requires integrations that their team does not master, and produces reports that nobody knows how to interpret correctly. The retention rate appears healthy for months because cancellation processes are slow and organisational inertia is powerful. But the contract is not renewed, and when one has to explain why, the answer is not to be found in the internal metrics dashboard.\n\nThis has a less obvious consequence: product teams begin to optimise for what is being measured. If the success indicator is feature adoption, features are added. If it is session time, flows are designed that retain the user inside the platform even when it is unnecessary. If it is NPS, perception is managed at the moment of the survey. **Optimising toward activity metrics produces more complex products and customers with lower real returns.** Not out of bad intention, but because the architecture of incentives points in a different direction from what the customer actually needs.\n\nPickard's argument about what he calls \"vanity development\" — building features that are not driven by customer needs, but by market trends, competitive pressure, or internal technological affinity — describes exactly that mechanism. The result is a platform that accumulates layers of complexity without any of them demonstrably moving the customer's revenue, efficiency, or cost reduction.\n\n## The Incentive Structure That Nobody Audits\n\nBehind the proliferation of vanity metrics there is no naivety. There is an incentive structure that produces them systematically and that operates on at least three simultaneous levels.\n\nThe first is the funding cycle. Capital rounds at early and middle stages of a SaaS company have historically been tied to user growth metrics, monthly recurring revenue growth rates, and market expansion projections. Those metrics are capturable through activity data. The customer's economic return, by contrast, is slower to measure, requires access to data the customer does not always share, and does not appear cleanly in a Series B pitch deck. The consequence is predictable: teams optimise for the indicators that move the price of the next round, not necessarily for those that reflect delivered value.\n\nThe second level is the structure of Customer Success teams. For years, this function was designed as technical-relational support: solving implementation problems, responding to tickets, managing onboarding. In that model, the team's performance indicator was customer satisfaction and retention rate, not customer revenue expansion. That creates a team well positioned to detect friction but without the tools or mandate to quantify the financial impact of the platform on the customer's business.\n\nThe third level — and the most resistant to change — is the distance between the product team and the customer who operates day-to-day. Roadmap decisions are fed by user interviews, in-product behavioural analysis, and competitive benchmarking. They are rarely fed by the customer's financial statements, their operational efficiency metrics, or an honest evaluation of whether the platform reduced their cost per transaction or increased their conversion rate. That distance produces features that solve perceived problems but not economic ones.\n\nPickard points to what he describes as \"vanillifying\" requirements as a solution to this: when a customer requests a specific feature, the product team must generalise that request so that it scales across other segments and is sufficiently flexible for future use cases. The principle is correct, but there is a prerequisite that the argument does not directly resolve: in order to know whether a generalised feature creates value, it is necessary to have an operational definition of what value means for the customer. Without that definition, generalisation can produce complexity in the same way that copying competitors does.\n\n## The Customer's Return as a Financial Indicator of the Vendor's Health\n\nThere is a structural reason why the customer's return ends up being the best leading indicator of the financial health of the SaaS vendor, and it is worth making it explicit.\n\nSubscription business models depend on two variables: the retention of existing revenue and expansion within the current customer base. **Net Revenue Retention (NRR)**, one of the most closely watched indicators in the industry, measures precisely that: whether revenue from active customers grows, holds steady, or contracts after accounting for cancellations, downgrades, and expansions. An NRR above 100% indicates that the existing customer base is expanding its usage, which is typically the most efficient growth indicator because it avoids the acquisition cost of new customers.\n\nThat number cannot be sustained without demonstrable economic return for the customer. A customer who is not generating incremental revenue, saving costs, or gaining operational efficiency through the platform has no economic reason to expand their contract. They may renew out of inertia for one or two cycles, but the logic of expansion — which is what causes NRR to exceed the 100% threshold — requires that the customer has connected the software with a positive business outcome.\n\nThe causal chain is therefore precise: **customer return → contract retention → spending expansion → healthy NRR → vendor valuation**. Measuring only the intermediate links in that chain — retention and expansion — without auditing the initial link produces an illusion of solidity that the market corrects in the next renewal cycle.\n\nPickard points in the same direction when he notes that in usage-based revenue models, the growth of the customer's spending on the platform should be a symptom of that customer generating more revenue through the system. If the customer doubles their spending on the platform, their profit should grow by a larger multiple. If that does not happen, the model is not delivering value: it is capturing a growing portion of revenue that is not itself growing.\n\nThe managed services that the article mentions function as an accelerator of that cycle when they are well designed: they reduce the time between implementation and demonstrable return, which in turn accelerates the customer's decision to expand usage. The risk — which the article does not address explicitly but which is real — is that managed services become a patch for platforms that are not sufficiently intuitive or that require too much intervention to produce results. In that case, the services layer indefinitely subsidises a complexity that the product should have eliminated.\n\n## What Precedes the Visible Number\n\nThe argument for centring everything on customer return is correct in its diagnosis, but its implementation faces a prerequisite that few SaaS companies have resolved: how to measure that return in a systematic and non-anecdotal way.\n\nCustomer success stories exist in every software company. They are the fuel of sales presentations and testimonials pages. The problem is that a success story narrated after the fact has commercial value but little operational utility. It does not say what produced the return, under what conditions it could be replicated, or what variables made it possible in that customer and not in others with similar profiles.\n\nBuilding a customer return measurement methodology that is comparable across segments, that updates in real time, and that feeds product and Customer Success decisions requires access to data that the customer often does not share by default. It requires that the platform be instrumented to capture not only behaviour within the system, but its downstream effects on the customer's business indicators. And it requires that the product and Customer Success teams speak the same economic language as the executive buyers who evaluate the renewal.\n\nThe friction that nobody is accounting for in the debate about vanity metrics is precisely this: the problem is not that SaaS companies do not want to measure customer return. It is that the data infrastructure, the information exchange agreements with customers, and the analytical capacity to convert that data into roadmap signals are not built out in the majority of mid-sized vendors. Changing the executive dashboard is simple. Changing the information architecture that feeds that dashboard is the work that takes years.\n\nThat does not invalidate Pickard's thesis. It reinforces it. But it places the real problem where it belongs: not in the choice of what to measure, but in the capacity to measure what matters in a systematic way. The SaaS companies that manage to build that capacity first — including the agreements with customers that enable visibility into their results — will hold an advantage that cannot be replicated simply by renaming an indicator on the quarterly report.\n\nThe metrics dashboard does not change if the platform is not generating demonstrable return. But the architecture that produces that dashboard — and the teams capable of interpreting it honestly — is the investment that separates the vendors who survive budget renegotiations from those who do not make it to the next renewal cycle.","article_map":{"title":"The Only SaaS Metric That Survives When the Market Gets Tough","entities":[{"name":"David Pickard","type":"person","role_in_article":"Global director of Phonexa; author of the Forbes Technology Council thesis that anchors the article's argument about vanity metrics and customer return."},{"name":"Phonexa","type":"company","role_in_article":"Company whose global director published the referenced thesis on SaaS vanity metrics."},{"name":"Forbes Technology Council","type":"institution","role_in_article":"Publication venue for Pickard's thesis, cited as the source of the core provocation."},{"name":"Net Revenue Retention (NRR)","type":"technology","role_in_article":"The metric identified as the only durable indicator of SaaS health because it cannot be sustained above 100% without real customer economic return."},{"name":"SaaS","type":"market","role_in_article":"The industry context in which the entire argument about metric misalignment and customer return operates."}],"tradeoffs":["Activity metrics are easy to capture and move funding rounds; customer return metrics are hard to capture but reflect actual vendor health.","Managed services accelerate customer time-to-value but risk subsidizing platform complexity indefinitely.","Generalizing customer feature requests scales across segments but requires a prior definition of value—without it, generalization produces complexity as readily as copying competitors.","Optimizing for NPS manages perception at survey moments but does not capture whether the platform is generating economic return between surveys.","Building customer return measurement infrastructure takes years and requires customer data-sharing agreements that are difficult to negotiate, but creates a competitive moat that cannot be replicated quickly."],"key_claims":[{"claim":"SaaS companies systematically optimize for activity metrics because those are the indicators that move funding rounds, not because they reflect customer value.","confidence":"high","support_type":"editorial_judgment"},{"claim":"Net Revenue Retention above 100% cannot be sustained without demonstrable economic return for the customer.","confidence":"high","support_type":"inference"},{"claim":"Customer Success teams are structurally positioned to detect friction but lack the tools and mandate to quantify the financial impact of the platform on the customer's business.","confidence":"high","support_type":"inference"},{"claim":"Managed services can accelerate time-to-value but risk becoming a permanent subsidy for platforms that are too complex to deliver results independently.","confidence":"medium","support_type":"editorial_judgment"},{"claim":"The majority of mid-sized SaaS vendors lack the data infrastructure and customer agreements needed to measure customer return systematically.","confidence":"medium","support_type":"inference"},{"claim":"SaaS companies that build customer return measurement capacity first will hold a competitive advantage that cannot be replicated by renaming indicators.","confidence":"interpretive","support_type":"editorial_judgment"},{"claim":"David Pickard (Phonexa) published a thesis in Forbes Technology Council arguing that SaaS vendors should ask whether they would use their own software if they were the customer.","confidence":"high","support_type":"reported_fact"}],"main_thesis":"Activity metrics (DAU, feature adoption, NPS, session time) create a false signal of health in SaaS businesses. The only durable indicator is Net Revenue Retention, which cannot exceed 100% sustainably unless customers are generating demonstrable economic return from the platform. The real barrier to fixing this is not a choice of what to measure, but the data infrastructure and customer agreements needed to measure what actually matters.","core_question":"Why do SaaS companies keep measuring the wrong things, and what is the only metric that honestly reflects whether a platform is generating value for its customers?","core_tensions":["Investor-facing metrics (activity, growth rate) vs. customer-facing metrics (economic return, cost reduction, revenue expansion).","Short-term retention through inertia vs. long-term retention through demonstrated value.","Product complexity as a feature signal vs. product simplicity as a value signal.","Ease of measuring what is internal vs. difficulty of measuring what happens downstream in the customer's business.","Speed of changing the dashboard vs. time required to build the information architecture that makes the dashboard honest."],"open_questions":["How can mid-sized SaaS vendors negotiate data-sharing agreements with customers without creating privacy or competitive concerns?","At what company stage should the transition from activity metrics to outcome metrics occur, and what triggers that transition?","How should Customer Success teams be restructured—and compensated—to take on a mandate of customer revenue expansion rather than satisfaction?","Can NRR above 100% be sustained in segments where customer businesses are themselves contracting, and what does that imply for vendor strategy?","What is the minimum data infrastructure required to measure customer return systematically, and what does it cost relative to the retention value it protects?","How do you distinguish a managed services layer that is accelerating value from one that is subsidizing platform complexity?"],"training_value":{"recommended_for":["SaaS founders and product leaders evaluating their metric architecture","Customer Success leaders redesigning team mandates and performance indicators","Investors conducting due diligence on SaaS retention quality","Enterprise buyers evaluating SaaS vendor health before multi-year contract commitments","Business analysts building frameworks to distinguish leading from lagging indicators in subscription businesses"],"when_this_article_is_useful":["When evaluating a SaaS company's retention metrics and trying to assess whether they reflect real customer value or organizational inertia.","When designing or auditing a Customer Success team's mandate and KPIs.","When building a product roadmap and deciding which customer signals should feed prioritization decisions.","When negotiating a SaaS contract renewal and needing to articulate what economic return the platform has delivered.","When advising a SaaS company on which metrics to present to investors vs. which to use for internal health monitoring.","When assessing whether a managed services offering is a value accelerator or a complexity patch."],"what_a_business_agent_can_learn":["How to identify when a metric is a vanity indicator vs. a leading indicator of business health.","The causal chain linking customer economic return to vendor NRR and valuation.","How incentive structures at the funding, team, and product levels systematically produce metric misalignment.","Why NRR above 100% is structurally dependent on customer outcomes and cannot be sustained through activity optimization alone.","The distinction between changing a dashboard (easy) and building the information architecture that makes it honest (hard and slow).","How managed services can either accelerate value or subsidize complexity, and how to distinguish between the two."]},"argument_outline":[{"label":"1. The disconnect","point":"SaaS dashboards show green across all activity metrics while contracts are not being renewed. Usage and value have decoupled.","why_it_matters":"This is the core diagnostic failure: internal metrics are not proxies for customer outcomes, and teams are optimizing for the wrong signal."},{"label":"2. Vanity metrics have a legitimate early use","point":"DAU, login volume, and feature adoption are valid during early product stages to confirm onboarding and engagement. The mistake is keeping them at the center of executive dashboards permanently.","why_it_matters":"Distinguishing when a metric is appropriate prevents overcorrection—the problem is not measurement, it is metric migration without transition."},{"label":"3. Incentive architecture produces the problem systematically","point":"Three layers reinforce vanity metrics: (a) funding cycles reward activity data, not customer ROI; (b) Customer Success teams are measured on satisfaction and retention, not customer revenue expansion; (c) product teams are distant from customer financial statements.","why_it_matters":"The problem is structural, not behavioral. Fixing it requires changing incentive architecture, not just the dashboard."},{"label":"4. Vanity development as a product consequence","point":"When success is measured by feature adoption, teams add features. When measured by session time, they design flows that retain users unnecessarily. This produces complexity without demonstrable customer return.","why_it_matters":"Misaligned metrics corrupt the product roadmap and create platforms that are harder to use and less economically valuable."},{"label":"5. NRR as the honest metric","point":"Net Revenue Retention measures whether revenue from existing customers grows, holds, or contracts after cancellations, downgrades, and expansions. It cannot exceed 100% sustainably without real customer economic return.","why_it_matters":"NRR is the metric that closes the loop between customer value and vendor health. It cannot be gamed without delivering actual outcomes."},{"label":"6. The causal chain","point":"Customer return → contract retention → spending expansion → healthy NRR → vendor valuation. Measuring only intermediate links (retention, expansion) without auditing the first link produces a structural illusion.","why_it_matters":"Understanding the full causal chain prevents vendors from mistaking lagging indicators for leading ones."}],"one_line_summary":"SaaS companies that optimize for activity metrics instead of customer economic return are building a retention illusion that market pressure eventually corrects—Net Revenue Retention is the only metric that cannot be gamed without delivering real value.","related_articles":[{"reason":"Adobe's case illustrates how a SaaS-adjacent tech company with record revenue still loses market confidence when investors stop reading the income statement and start reading forward signals—directly parallel to the article's argument about metric illusions and what the market actually corrects for.","article_id":13739},{"reason":"Circle's pivot from ad-revenue to paid communities reflects the same structural logic: when the dominant monetization metric (reach/impressions) stops correlating with business health, the model must shift to one where customer value is more directly captured—analogous to the SaaS shift from activity metrics to NRR.","article_id":13926}],"business_patterns":["Metric migration failure: metrics valid in early product stages become permanently embedded in executive dashboards without transitioning to outcome metrics.","Incentive misalignment cascade: funding cycles → team KPIs → product roadmap all reinforce activity metrics over customer return metrics.","Retention illusion: slow cancellation processes and organizational inertia mask value absence for one to two renewal cycles before the contract is lost.","Causal chain truncation: vendors measure intermediate links (retention, expansion) without auditing the first link (customer economic return), producing false confidence.","Services-as-complexity-subsidy: managed services layers that should accelerate value instead become permanent patches for unintuitive platforms."],"business_decisions":["Which metrics to place at the center of the executive dashboard and which to relegate to product-stage diagnostics.","Whether to invest in data infrastructure and customer data-sharing agreements to measure downstream customer outcomes.","How to restructure Customer Success team mandates from satisfaction-and-retention to customer revenue expansion.","Whether managed services should be offered as a value accelerator or avoided if they mask product complexity.","How to design product roadmaps that are fed by customer financial outcomes rather than behavioral analytics alone.","When to transition from activity-based metrics to outcome-based metrics as a company scales past early product stages."]}}