The Three Little Pigs Problem: How Many of Your Customers Actually Need You?

Most CS leaders know the story. Three little pigs, three houses made out of straw, sticks, and bricks. The wolf has no trouble with the first two. Only the house built from the right material survives when the pressure comes.

I've used this story for years when working with CS organisations because it maps so cleanly onto one of the most revealing questions you can ask about any subscription business:

What proportion of your customers would say that your solution is: no longer needed, nice to have, or essential?

In 2026, this question has moved from a CS programme health check to a board-level commercial metric. The economic environment of the past several years - sustained budget scrutiny, aggressive SaaS rationalisation, procurement teams instructed to cut anything that isn't demonstrably business-critical - means the wolf is at the door for a significant proportion of most SaaS customer bases. The houses made of straw and sticks are not holding.

When I ask CS leaders to honestly estimate how their base would answer this question, the answers are still startling. Most believe the majority of their customers sit in the "nice to have" category. Some put that figure as high as 85%. At current renewal rates and the current appetite for cost reduction, that is not a sustainable position.

This article is about what to do about it and how to build the systems, processes, and customer intelligence infrastructure that move the distribution in your favour.

Why the Question Matters More Now
The three categories map directly onto the commercial risk profile of your customer base.

Customers who evaluate your solution as no longer needed are churning at the first contractual opportunity. The decision has already been made; you are in the final countdown. Customers who see you as nice to have are at material risk the moment budgets tighten, a new CFO arrives, or a competitor offers a consolidation play. They will renew when conditions are comfortable and cut when they aren't. Only customers who evaluate your solution as essential and embedded in their workflows, tied to outcomes they cannot easily achieve another way, understood by their leadership as business-critical can be considered genuinely churn-resistant.

The commercial implications run deeper than retention. A high-essential customer base supports expansion. Customers who need you don't just renew - they bring in adjacent teams, upgrade tiers, and buy new products as you release them. Gross Revenue Retention and Net Revenue Retention both move materially when you shift even a modest percentage of your base from "nice to have" to "essential." This is not a soft CS metric. It is a direct driver of the numbers your CFO and CRO present to the board.

Building Your Essentialness Model
Before you can shift the distribution, you need to understand it and to understand it reliably, you need to move beyond subjective CSM assessments and single-metric proxies.

Customer satisfaction scores - whether NPS or any single-question variant - tell you something about sentiment, but sentiment and essentialness are not the same thing. A customer can feel positive about your product while using a small fraction of its capability and remaining entirely replaceable by a cheaper alternative. What you need is a multi-signal model that captures the real indicators of embeddedness.

The most reliable signals of essentialness cluster around three dimensions.

Depth of adoption. Not just login frequency, but breadth of feature usage across the customer's workflows. A customer using a wide cross-section of your platform's functionality - including features that solve problems adjacent to the original use case - is substantively harder to replace than one who has mastered a single workflow. Your product analytics should be able to surface this. If they can't, that is a CS Ops gap worth addressing.

Organisational penetration. How many people, teams, and decision-making layers is your solution touching? A single-threaded relationship with one champion is structurally fragile, regardless of how positive that relationship is. Solutions that are embedded across multiple stakeholders, integrated into management reporting, or woven into cross-functional processes are categorically more essential than those that live in one person's daily workflow.

Outcome attribution. Can your customer articulate (unprompted and in their own language), what they would not be able to do, or would have to do significantly worse or more expensively, without your solution? This is the acid test. If neither your CSM nor the customer's main contact can answer it clearly, you are in the "nice to have" tier regardless of what the health score says.

Most CS platforms now support the construction of a composite health model using these dimensions. The CS Ops investment required to build and calibrate it is meaningful, but the return - a reliable, real-time view of your essentialness distribution across the full base - is one of the highest-value pieces of infrastructure a CS organisation can own.

Modern AI capabilities add another layer. Sentiment analysis running across support interactions, call transcripts, and email correspondence can surface early warning signals that precede visible health score deterioration: the shift in language from "we use this for X" to "we're evaluating whether we still need this," the increasing involvement of procurement contacts who weren't previously in the picture, the gradual withdrawal of executive engagement. These signals are detectable before churn risk is obvious; the CS organisations catching them earliest are the ones with the infrastructure to do so.

Finding Your "Essential" Signal in Product DataOne of the most valuable exercises any CS leader can run is identifying the product usage patterns that correlate most strongly with customers in the "essential" tier and what some teams call finding your North Star metric.

The method is straightforward: look back at your customer base over the past 18 to 24 months and identify the accounts with the strongest retention, expansion, and advocacy profiles. What did their early product usage look like? Were there specific features, adoption milestones, or usage thresholds that reliably appeared in their first 90 days and were absent in accounts that later churned or stagnated?

This analysis tends to surface a small number of leading indicators (typically two or three) that predict long-term essentialness with surprising accuracy. Once identified, these become the targets your onboarding motion should be designed around, the triggers your CS Ops team monitors at scale, and the milestones your CSMs are focused on accelerating in every new account.

If you do not know what these signals are for your product, finding them is worth prioritising over almost any other CS analytics investment.

Converting "Nice to Have" to "Essential" at ScaleIdentifying the distribution is diagnostic. The harder work is moving it. Here is where CS leaders need to think systematically rather than account by account because no team has the bandwidth to manually re-engage every customer sitting in the "nice to have" tier.

Reconfirm the use case, programmatically. The use case that justified the original purchase is often six to eighteen months out of date by the time a customer reaches their first or second renewal. Business priorities shift, teams restructure, original champions leave. A systematic use case review, conducted at regular intervals through structured outreach, should be part of every CS programme's operating cadence. For scaled segments, this does not require CSM time: a well-designed digital survey, triggered at the right moment and followed by a branched outreach sequence, can surface use case drift before it becomes churn risk.

Close the Consumption Gap. The Consumption Gap is the distance between what your product is capable of and what the customer is actually using. It is one of the clearest measures of risk.  The wider the gap between what the customer is using and what would satisfy/surpass their use case (note - the goal should not be to try and have every customer use every possible product feature), the more of your solution is invisible to the customer, and the more replaceable you are by something simpler and cheaper. Closing it requires diagnosing why it exists. Is it an onboarding failure - did the customer never fully learn the product? A product fit issue - is the functionality that would make them more essential not yet built or not yet discoverable? A communication failure - are your customers unaware of capabilities that would directly serve their evolving needs? The answers drive different interventions, but in every case, the Consumption Gap should be a monitored metric, not an anecdotal observation.

Re-onboard continuously, not once. Onboarding is not a phase; it is a recurring motion. Every significant product release is a re-onboarding opportunity. Every new stakeholder who joins the customer's account is a re-onboarding opportunity. Every new contract period, particularly where you know the original use case has shifted, is a re-onboarding opportunity. Teams running digital-led CS motions are embedding this logic into their engagement programmes: milestone-triggered in-app guidance, automated feature spotlight sequences based on usage gaps, proactive outreach when product analytics detect that a user has not yet discovered a capability that is statistically associated with higher retention.

Make value visible, repeatedly. Never assume a customer is carrying an accurate mental model of the ROI they are getting from your solution. In a world where the person who originally championed the purchase may have left, where the original business case document is two years old, and where your solution competes for attention against dozens of other tools, the default state is that customers underestimate the value you are delivering. Your CS motion should be systematically surfacing usage data, outcome metrics, and business impact in a format that is accessible to both the day-to-day user and the executive who signs the renewal. This is not just an EBR activity. It should be part of the ongoing digital engagement cadence for every segment of your base.

Educating Sales: The ICP Implication
One of the most commercially significant things CS can do with the essentialness distribution is feed it back into the front of the funnel.

If you have a clear picture of which customer profiles tend to land in the "essential" tier  and equally, which firmographic patterns, use case types, or onboarding trajectories predict "nice to have" outcome - that intelligence belongs in your ICP definition and your pipeline review process, not just in CS programme notes.

CS leaders who present this analysis to their CRO are offering something concrete: a way to identify, before a deal closes, which prospects are likely to become retained, expanding, advocating customers and which are likely to churn within 18 months. The short-term bookings uplift from closing a poor-fit account is almost always offset by the downstream costs such as the CSM time, the reputational damage, the NRR drag, the organisational demoralisation of working accounts with no path to success.

Building this into a formal CS-to-Sales feedback loop - regular ICP reviews informed by churn analysis and essentialness scoring, shared in a format Sales can act on at the pipeline stage - is one of the highest-leverage things CS Ops can build. It makes CS a revenue protection function, not just a retention function, and positions CS leadership as a commercial partner rather than a post-sale service organisation.

Making the Distribution a Boardroom Metric
The final shift is cultural and structural. The essentialness distribution, the proportion of your base in each of the three tiers, should be a reported metric, visible to leadership, with a clear owner and a clear improvement trajectory.

When CS leaders present this number alongside GRR and NRR, they are telling a more complete story about the health of the customer base than any satisfaction score can convey. A business with 70% of its customers in the "essential" tier has a fundamentally different risk profile and growth trajectory than one carrying 70% in "nice to have" and that difference deserves to be legible to the people making decisions about where to invest.

The CS organisations that are building durable commercial impact in 2026 are the ones that have moved from managing customer relationships to managing customer value at scale. Tracking and improving the essentialness distribution is one of the clearest ways to demonstrate that the shift has happened.

The wolf has not gone anywhere. Budgets are still under scrutiny, alternatives are still being evaluated, and the question of whether your solution is genuinely business-critical is being asked in procurement reviews across your entire customer base, right now, whether you know it or not.

The houses made of straw and sticks will not hold. The work of Customer Success leadership,  in 2026 as much as ever, is making sure as many of your customers as possible are living in brick.