The Measurement Problem Nobody Talks About
Customer Success has a data problem that is hiding in plain sight.
Every CS team has health scores. Every CS team has QBR decks and renewal forecasts and executive sponsor maps. What most CS teams do not have is reliable, comprehensive data on the accounts they are managing.
PulseIntel's analysis of 938 companies found that the average customer success team operates with a 64% data gap on their account portfolio. This means that for the typical account, 64% of the data fields that should inform health scoring, expansion identification, and risk assessment are either empty, stale (more than 90 days old), or inconsistent across systems.
The consequence is not just imprecise health scores. It is systematic mis-categorisation of accounts — healthy accounts flagged as at-risk, churning accounts appearing green until the renewal conversation reveals the problem.
Why the Data Gap Is So Large
The 64% gap does not come from a lack of effort. CS teams spend significant time trying to maintain account data. The gap comes from structural problems in how account data flows between systems.
The CRM is not designed for CS. Sales CRM systems are optimised for deal tracking, not account health management. Contact records reflect the buying journey, not the post-sale relationship. The people who championed the purchase are faithfully recorded; the people who actually use the product every day are often not.
Product usage data does not connect. Usage analytics live in a separate system — the product analytics platform, the data warehouse, or a customer-specific BI report. CS teams access it through a separate tab, on a separate day, and mentally try to integrate it with what they know from their last call. That mental integration is unreliable and unsustainable at scale.
Enrichment is not continuous. Contact records reflect the world as it was when the account was onboarded. The champion has since been promoted. The economic buyer has left the company. The company has acquired a competitor that uses a rival product. None of this is visible in the CRM unless a CS team member manually discovers and records it — which happens inconsistently, if at all.
Meeting data is not structured. What the customer said in the last QBR, what concerns were raised in the renewal call six months ago, what the CSM promised in the onboarding session — all of this lives in note fields, or in the CSM's memory, or nowhere at all. It is not structured, not searchable, and not usable for portfolio-level pattern analysis.
What the 64% Gap Costs
The financial impact of the data gap is clearest in renewal outcomes.
Accounts that are accurately health-scored 90 days before renewal have a 76% renewal rate in our benchmark data. Accounts that are inaccurately scored — appearing healthier than they are because of data gaps — have a 41% renewal rate. The delta is not primarily explained by product satisfaction; it is explained by the CS team's ability to identify and address risk in time to act.
Early identification of at-risk accounts is the primary value driver of a CS function. Everything else — QBRs, business reviews, adoption coaching — is secondary. And early identification is impossible without accurate, current data.
The expansion side of the gap is equally significant. Accounts with full data coverage are 2.3x more likely to be identified as expansion candidates than accounts with high data gaps, even when the underlying expansion opportunity is comparable. The difference is visibility: you cannot propose a relevant expansion if you do not know what the account looks like today.
Closing the Gap: What Works
The companies in our dataset that have reduced their account data gaps below 20% share three structural practices:
Continuous enrichment on account and contact records. Not a quarterly data refresh — a continuous feed of updated contact information, firmographic data, and technographic signals that keeps records current without manual intervention. When a champion changes roles, the CS team should know within days, not at the next QBR when the new contact does not show up.
Structured meeting intelligence feeding CRM. QBR notes, renewal call summaries, and success plan updates that are structured and searchable rather than free-form text fields. This makes portfolio pattern analysis possible: identifying the specific language that predicts churn, the questions that surface expansion interest, the objections that appear six months before a difficult renewal.
Unified health scoring from multiple data sources. Health scores that incorporate product usage, contact engagement, meeting sentiment, and enrichment currency — not just one or two of these signals. Single-signal health scores (product usage only, or login frequency only) produce false confidence in accounts that are functionally healthy by one metric but at serious risk on others.
The Compounding Effect of Unified Data
The reason unified account data matters disproportionately is that the signals compound.
An account where the champion has changed roles (enrichment signal) AND meeting frequency has declined (meeting intelligence signal) AND product usage has dropped (product data signal) is a materially higher churn risk than an account showing only one of these signals. The compound risk is not additive — it is multiplicative.
CS teams with unified data can detect these multi-signal patterns at the portfolio level, triage them by severity, and allocate their attention where it will have the most impact. Teams without unified data are relying on individual CSM judgment for a problem that benefits from systematic pattern detection.
The 64% data gap is not an insurmountable problem. It is a structural one — the result of data living in disconnected systems that were never designed to work together. The solution is equally structural: data architecture that connects the signals and surfaces them in the workflow where CS teams make decisions.
When that architecture is in place, the data gap closes. And so does the churn gap it was hiding.