A software company’s future is not determined only by what it sells next. It is determined, in large part, by what is already happening inside the customer base it already has. 

Are customers renewing because they are deeply dependent on the product — or because leaving still feels harder than staying? 
Are they adopting the platform broadly — or using one narrow corner of it while the rest of the account sits flat? 
Are they growing with the company — or simply remaining on the books? 
Are they becoming more valuable over time — or quietly becoming more fragile? 

That is what this pillar is built to examine. 

Customer Health & Expansion Potential measures the strength, resilience, and upside of the installed base. It looks at retention quality, adoption depth, support burden, sentiment, concentration, and the company’s ability to grow revenue inside existing accounts without creating disproportionate strain. 

Because the real question is not just whether customers are still there. 

The real question is this: 

Are customers staying, thriving, and expanding in a way that makes future revenue more durable — or are they slowly weakening beneath the surface? 

That distinction matters more than many leadership teams realize. 

A healthy customer base creates: 

• stronger renewal confidence
• Better revenue quality
• Lower cost of growth
• more predictable forecasting  
• higher expansion efficiency  
• greater valuation resilience  

An unhealthy one creates: 

• hidden churn risk  
• flatter net retention 
• higher GTM pressure   
• weaker pricing power  
• more support strain  
• more fragile revenue than topline numbers suggest  

That is why Customer Health & Expansion Potential is one of the most important pillars in the BDE model. 

It is not a customer success topic alone. 

It is a business quality topic. 

Why this pillar matters 

Many software companies spend too much time evaluating future growth through net-new demand and not enough time evaluating the quality of the base already under management. 

That is a mistake. 

In most recurring-revenue software businesses, the installed base is not just a source of retained revenue. It is also the most important proving ground for: 

• product value  
• customer trust  
• pricing resilience 
• expansion opportunity
• supportability   
• long-term business durability    

If the customer base is healthy, the company usually feels stronger across multiple dimensions: 

• renewals become more stable  
• upsell becomes easier  
• NRR improves  
• customer references get better  
• sales efficiency increases  
• roadmap confidence rises  
• roadmap confidence rises  
• financial quality improves  

If the customer base is unhealthy, the opposite happens: 

• more pressure shifts to new-logo sales  
• support starts carrying more emotional strain  
• revenue predictability weakens  
• more accounts renew flat or reluctantly  
• price sensitivity increases  
• expansion becomes harder  
• churn risk builds quietly before leadership is ready to name it  

That is why this pillar matters so much. 

Because a software company can look commercially active while its customer base is quietly becoming less valuable. 

And that is one of the fastest ways for future revenue quality to weaken without the company fully understanding why. 

What this pillar really measures 

Customer Health & Expansion Potential is built around a simple but important idea: 

The installed base should behave like a compounding asset, not a slowly decaying obligation. 

This pillar evaluates six core dimensions. 

1. Retention quality 

Not just whether customers renew, but how strong, broad, and durable that renewal behavior really is. 

We look at: 

• gross revenue retention
• renewal stability    
• logo churn patterns 
• account contraction   
• concentration inside renewal exposure  
• whether retained customers actually feel strong or merely intact  

Retention is not just a number. It is evidence of product dependence, account fit, and long-term customer trust. 

2. Adoption depth 

Whether the product is deeply embedded enough to create resilience. 

We look at: 

• user penetration  
• breadth of usage  
• workflow dependency  
• module usage  
• stickiness by role and function  
• whether the platform is becoming more central or remaining too narrow  

Low adoption is one of the most dangerous hidden risks in a recurring-revenue business because it makes churn easier before churn becomes visible. 

3. Customer sentiment 

How customers actually feel about the product, the support model, the implementation experience, and the long-term value of the relationship. 

We look at: 

• support tone
• escalation patterns
• review signals
• reference willingness
• account energy
• renewal posture
• relationship confidence
• evidence of trust versus quiet fatigue

Sentiment matters because accounts often weaken emotionally before they weaken financially. 

4. Support burden and account strain 

Whether customers are healthy to serve, not just retained to invoice. 

We look at: 

• ticket volume and mix
• recurring issue classes
• escalation frequency
• support cost intensity
• engineering involvement
• operational friction inside the customer lifecycle

A support-heavy account may still be retained, but that does not mean it is a high-quality account. 

5. Expansion potential 

Whether the customer base contains credible room to grow. 

We look at: 

• module attachment opportunities
• seat expansion
• adjacent workflow adoption
• account whitespace
• product depth by customer segment
• openness to broader use-case penetration
• installed-base expansion patterns

A healthy customer base should not only stay. It should contain pathways to become more valuable over time. 

6. Customer concentration and structural fragility 

Whether too much of the installed base is dependent on: 

• a few large accounts
• one vertical
• one workflow type
• one ERP dependency
• one sponsor pattern
• one expansion thesis

This matters because a base can look healthy in aggregate while still being dangerously exposed beneath the surface. 

The core question behind this pillar 

At the center of this pillar is a simple diagnostic tension: 

Is the customer base becoming stronger as time passes — or merely surviving? 

A strong base tends to: 

• deepen usage
• build more champions
• create broader workflow dependency
• support pricing confidence
• produce cleaner renewals
• create expansion paths
• reduce GTM pressure

A weak base tends to: 

• renew narrowly
• expand inconsistently
• remain shallow in usage
• generate more support drag
• feel more fragile than the dashboard admits
• require more rescue behavior around renewals
• become more economically defensive over time

What strong customer health looks like 

A healthy installed base usually has a recognizable feel. 

Customers are not only staying. They are engaged in ways that suggest the product matters. 

That often means: 

• multiple users rely on it
• multiple workflows depend on it
• support is active but not corrosive
• issues get resolved without destroying trust
• renewal discussions feel grounded, not panicked
• expansion conversations are plausible
• the product sits inside a meaningful operating reality
• customers are more likely to deepen than merely endure

At a business level, this usually shows up as: 

• stronger GRR  
• healthier NRR  
• lower hidden churn risk  
• better account economics  
• more strategic optionality inside the installed base  
• more believable forward revenue quality  

But it makes the company more resilient, more efficient to grow, and easier to trust. 

What weak customer health looks like 

A weaker installed base often hides inside superficially acceptable revenue. 

Contracts may still be renewing. 
Accounts may still be open. 
Customers may still say they are “using the product.” 

But underneath, the warning signs start clustering: 

• adoption is too shallow  
• one user or one team carries too much of the account  
• support tickets repeat around the same issues  
• expansion never really materializes  
• price sensitivity is rising  
• sentiment feels neutral rather than strong  
• account reviews become more transactional than strategic  
• the product is being tolerated more than embraced  
• the company is counting retained revenue that is weaker than it looks  

This is what makes customer health so important. 

The damage often starts before revenue drops. 

By the time churn becomes obvious, the conditions that created it may have been visible for months. 

The hidden danger of low adoption 

One of the most important ideas inside this pillar is that low adoption is often more dangerous than loud dissatisfaction. 

A loud customer may still be deeply dependent on the product. 
A quiet customer may already be drifting away from it. 

Low adoption matters because it reduces: 

• switching cost
• internal advocacy
• workflow dependency
• pricing resilience
• expansion likelihood
• tolerance for friction

That means the account may still renew once or twice while its underlying quality is declining. 

This is why a serious customer-health model should always ask: 

• Who is using the platform?
• How broadly?
• In how many workflows?
• Across how many roles?
• With what level of dependency?

Adoption depth is one of the strongest predictors of whether recurring revenue is truly durable or just temporarily recurring. 

Support is a strategic signal, not just a service function 

Support patterns tell the truth about the customer base faster than many leadership teams realize. 

Support reveals: 

• where the product is hard to use  
• where implementation did not land cleanly  
• where technical debt is surfacing in the customer experience  
• which accounts are expensive to maintain  
• which segments are weak fit  
• where churn risk may already be forming  

This is why BDE treats support behavior as a major input to customer health. 

We do not just ask: 

• how many tickets exist
• how fast the queue is moving

We ask: 

• what kinds of issues keep recurring  
• which accounts generate disproportionate burden  
• how tone is changing  
• whether customers still believe the product is worth improving  
• whether support interactions show confidence, frustration, or resignation  

Support tickets are not just operational noise. 

They are often one of the sharpest windows into both product risk and customer risk. 

Expansion is one of the clearest signs of health 

A truly healthy customer base does not just stay in place. 

It creates room to grow. 

That growth may come through: 

• more users  

• more users
• more modules
• adjacent workflows
• stronger integration usage
• premium capability adoption
• broader departmental penetration
• analytics or data-layer opportunity
• service-to-product migration
• deeper strategic reliance

Expansion matters because it tells you the product is not just being retained. It is becoming more relevant. 

This is one of the clearest signals of installed-base strength. 

When expansion is weak across the base, leadership should ask why: 

• Is adoption too shallow?
• Is product breadth too narrow?
• Is customer success too reactive?
• Are accounts under-threaded?
• Is the company missing obvious whitespace?
• Is the base stable but not truly strengthening?

A stagnant base is not always unhealthy. 

But a base that never seems to deepen should not be assumed strong by default. 

Concentration makes customer health more fragile 

A company can have a decent-looking customer base and still be more exposed than it appears if too much health is concentrated in: 

• a few large accounts
• one vertical
• one ERP environment
• one sponsor type
• one expansion pattern
• one group of high-value customers carrying the whole thesis

That is why customer health cannot be evaluated only in aggregate. 

A few large healthy customers can make the overall picture look stable while much of the rest of the base is flatter, weaker, or less expandable than it should be. 

Likewise, a handful of fragile but economically important accounts can create hidden risk even when the rest of the customer base looks acceptable. 

This is why BDE evaluates: 

• top-account exposure
• concentration by segment
• concentration by ERP dependence
• concentration by margin contribution
• concentration by expansion thesis

Because a healthy-looking base that is too narrowly concentrated is still a weaker asset than it first appears. 

Why this pillar matters so much in diligence and value creation 

This pillar is one of the strongest indicators of future revenue quality. 

It matters in diligence because it helps answer: 

• Is the customer base resilient or fragile?  
• Are renewals likely to stay strong?  
• Is NRR supported by real account health or just a few expansion stories?  
• Is the installed base a growth engine or just a retention challenge?  
• How much support burden sits inside recurring revenue?  
• Is customer value broad enough to survive change, pressure, or transition?  

It matters in value creation because improving customer health often improves multiple other pillars at once: 

• illars at once: 
• Financial Health improves through stronger GRR, NRR, and pricing power  
• GTM pressure decreases because more value comes from the installed base  
• Product & Technical Maturity becomes more visible through better adoption and fewer friction points  
• Operational Maturity improves when onboarding and support become stronger  
• Service-to-Software Ratio improves as cleaner adoption supports more scalable product value  

This is one reason Customer Health & Expansion Potential is such a powerful pillar. 

It is both a measurement pillar and a leverage pillar. 

How BDE evaluates this pillar 

BDE evaluates customer health by combining signals across: 

• renewal patterns  
• account concentration  
• adoption behavior  
• support burden  
• sentiment indicators  
• expansion motion  
• relationship depth  
• workflow dependency  
• ecosystem exposure at the customer level  

That means we are not only looking at: 

• churn rate  
• NRR  
• customer counts  

We are looking for the deeper patterns underneath those metrics: 

• why customers stay  
• where accounts are vulnerable  
• which customers are most expandable  
• which parts of the installed base are healthy versus merely intact  
• what is likely to get stronger or weaker over the next 12 to 24 months  

That is what makes this pillar strategically useful. 

It is not just retrospective. 

It is predictive. 

Key warning signs inside this pillar 

When Customer Health & Expansion Potential is weaker than leadership thinks, the signs often look like this: 

• renewals are happening, but expansion is flat  
• adoption is too narrow inside too many accounts  
• one champion carries too much of the relationship  
• support burden is high in ways that do not look scalable  
• customers are less enthusiastic than they are retained  
• price sensitivity is rising  
• account reviews feel more administrative than strategic  
• too much of NRR depends on a few expansion stories  
• churn risk exists behaviorally before it exists contractually  
• customer concentration is masking broader weakness  

These warning signs matter because they often indicate the company is carrying weaker future revenue quality than the headline ARR or retention number alone suggests. 

What “good” looks like 

A strong score on this pillar generally means: 

• GRR is healthy and believable  
• NRR is supported by real expansion patterns  
• adoption is broad and meaningful  
• support burden is manageable and informative, not corrosive  
• sentiment is strong enough to support trust  
• accounts are reasonably diversified  
• the installed base contains real whitespace  
• customers are becoming more valuable over time  
• the business is not overly dependent on a few fragile relationships or accounts  
• renewal behavior reflects durable product dependence, not just inertia  

That kind of customer base creates: 

• stronger valuation confidence  
• better expansion economics  
• lower GTM pressure  
• more believable recurring revenue quality  

What “weak” looks like 

A weaker score on this pillar often means: 

• GRR is weaker than the company wants to admit  
• NRR is flat or overly concentrated in a few accounts  
• adoption is shallow  
• expansion is inconsistent or absent  
• support reveals repeated customer strain  
• sentiment is mixed or quietly weakening  
• relationships are too narrow  
• concentration risk is meaningful  
• the product is retained more out of habit or inconvenience than strong strategic relevance  
• the company is carrying recurring revenue that is less durable than it appears  

That does not always mean the business is failing. 

But it does mean the customer base is a weaker asset than leadership may believe. 

Final perspective 

Customer Health & Expansion Potential is one of the clearest indicators of whether a software company is building durable value or simply preserving revenue. 

A healthy installed base is not just something to defend. 

It is something to grow through. 

It creates stronger renewal confidence, stronger expansion economics, and stronger evidence that the product matters in the real world — not just in the pitch. 

A weaker installed base may still look acceptable in topline metrics for a while. 

But if adoption is shallow, support burden is high, sentiment is flattening, and expansion is weak, then the company is carrying more hidden risk than it appears. 

That is why this pillar matters. 

Because in the end, a software company’s long-term strength is not just about how many customers it has. 

It is about what kind of customers those are becoming over time.