What is a leading product adoption signal and how should it be weighted in health scoring?

Product Adoption Signals & Weighting

Feature breadth (multi-module usage) is the single strongest adoption signal, outweighing login frequency or session duration. OpenView analyzed 850+ renewal outcomes and found: customers using ≥3 core modules churn at 8% annual rate; those using 1 module churn at 31% annual rate—a 3.9x difference.

Why Module Breadth Matters

When a customer uses multiple features, they've embedded the tool into 2+ departments, raising switching costs. A sales team using the prospecting module can jump to a competitor; a sales *and* customer success *and* finance team using prospecting, forecasting, and analytics modules has integrated dependencies across org. Cost of switching = migration for 3 teams, not 1.

Core vs. Premium Signals

Core module adoption (standard features included in all plans): Weight at 35–40% of health score. Indicators:

• Percentage of available modules used in past 30 days
• Number of user accounts actively logging in (seat utilization)
• Days since first login in key modules

Example: Customer bought 50 seats. If 22 seats have logged into search + analytics *and* forecast modules in past 30 days, adoption breadth = 44%. That's Green territory.

Premium module adoption (add-ons, advanced features): Weight at 15–20%. These indicate expansion appetite: API usage, custom reporting, workflow automation. If a customer enables these, they're deepening investment and likely to expand ARR.

Decay Weighting

Don't measure adoption as *ever used*; measure as *recently used*. Apply time decay:

• Active in module this month: Full weight (100%)
• Last active 30–60 days ago: 70% weight
• Last active 61–90 days ago: 40% weight
• Last active >90 days ago: 0% weight (suspect disengagement)

A customer who used 4 modules 120 days ago and 1 module today registers as declining adoption, signaling risk.

Breadth Scoring Formula

``` Adoption Score = (Active Modules in Past 30 Days ÷ Available Modules) × 100

Green: 60–100% (≥3 modules for typical product) Yellow: 30–59% (1–2 modules) Red: 0–29% (<1 module active) ```

Expansion Correlation

Pavilion's research: customers with 4+ active modules close expansion deals at 2.3x the rate of single-module users. CSMs should watch for module-adoption momentum (customer added a new module last month) as expansion trigger, not churn signal.

Avoiding False Positives

**Automation success may *lower* login frequency but *increase* module reliance**. A customer who built workflow automation needs to log in less but depends entirely on your platform for that automation. Track this via: API calls, automation rule count, or task completions—not login volume alone.

TAGS: product-adoption,feature-usage,module-breadth,health-scoring,expansion-signals,saas-analytics