Most revenue leaders debate how to weight the five categories in an account health score. Fewer ask how often each category needs to be re-read. That second question is quietly more important. A signal that predicts renewal beautifully at 14 days often predicts nothing at all at 60. If the five categories in your score share one monthly refresh cadence, four of them are wrong most of the time.
This piece is a cadence framework for CROs, CCOs, and heads of key account management in non-SaaS service portfolios — logistics, IT managed services, professional services, manufacturing and distribution, financial services and insurance. It treats signal freshness as an operating decision, not a data hygiene task.
Why refresh cadence became a revenue problem
The B2B market has compressed. McKinsey’s 2026 B2B Pulse found that 60 percent of market leaders — the companies growing share by more than ten percent year over year — are posting double-digit revenue growth, versus 21 percent of laggards. The same research shows companies that move from lagging qualification signals to real-time intent signals see pipeline velocity improve by 20 to 40 percent. The same physics apply to retention. Stale signals don’t just slow the play; they misdirect it.
Independent benchmarks put a number on the decay. Salesmotion’s 2026 signal freshness benchmark found that teams working signals under 14 days old convert at 2.7 times the rate of teams working month-old signals, and the half-life of complex B2B intent signals sits at 30 to 45 days. On the identity side, Apollo’s data-freshness guidance recommends re-verifying contact records every one to three months, with company firmographics every six. That is the ceiling — not the floor — for a retention model that has to see risk before it moves.
The five categories, five different half-lives
A defensible multi-source account health score is built on five signal categories: Satisfaction, Engagement, Commercial, Delivery, and Expansion. Each category has a different velocity and a different half-life. Treating them uniformly is what produces the scenario every CRO recognises — the account looked green in the QBR deck and grey in the CFO’s forecast.
Delivery — refresh weekly, sometimes daily
Delivery signals decay fastest because operational performance changes fastest. An on-time-in-full rate that was 94 percent last month can be 71 percent this week, and by the time a monthly refresh catches it, the client’s operations lead has already had two conversations you were not in. In logistics, IT managed services, and manufacturing, delivery signals need a rolling 7- to 14-day window. Anything longer and the score reports history, not exposure.
Engagement — refresh weekly
Engagement covers meeting cadence, response latency, portal activity, ticket volumes and their trajectory. The half-life is short because silence is itself a signal, and silence needs a tight measurement window to be visible. A 30-day engagement refresh will miss the two consecutive weeks a champion stopped replying — which is usually the moment a competitor was invited in.
Satisfaction — refresh at a natural event, not on a calendar
Satisfaction is the category most teams over-refresh with surveys and under-refresh with structured listening. NPS pinged monthly to the same procurement contact produces response fatigue and a flat number. A better cadence is event-triggered: post-delivery, post-incident, post-QBR, and post-stakeholder change. The half-life of a satisfaction score is longer than delivery — roughly 60 to 90 days for a specific respondent — but that only holds if the respondent set stays current. When the champion moves roles, the score becomes historical the day they leave.
Commercial — refresh monthly, faster at renewal windows
Commercial signals — invoice trends, payment behaviour, discount pressure, contract clock — have a longer half-life than delivery because they change on billing cycles. A monthly refresh is usually enough, except in the 120 days before a renewal decision, when the cadence should shift to weekly. This is also the category most likely to sit in an ERP or finance system that the account team does not open, which is why the effective refresh cadence for many CROs is “whenever finance flags something,” and by then the DSO has already told the story.
Expansion — refresh continuously, act quarterly
Expansion signals are the odd one out. They are cheap to observe continuously — a new site opening, a new business unit spinning up, a stakeholder posting a job req for a role adjacent to your service — but expensive to act on more than once a quarter. So the read cadence is high, the action cadence is measured. The mistake is the reverse: reading whitespace only at QBR prep, when a competitor’s account team has been reading it every week.
What a cadence framework looks like in practice
Translated into an operating rhythm, the five categories produce four refresh tiers, not one:
- Daily to weekly: Delivery and Engagement. Pulled from ticketing, transport management, ERP delivery data, meeting systems, and the customer portal.
- Event-triggered: Satisfaction. Fired by delivery milestones, incidents, QBRs, and stakeholder changes — not the calendar.
- Monthly, weekly near renewal: Commercial. Pulled from finance and CRM opportunity data.
- Continuous read, quarterly act: Expansion. Combining CRM whitespace fields, stakeholder mapping, and public signal sources.
A composite health score that respects these tiers looks stable when signals are stable and moves early when they are not. A composite score that refreshes everything at the first of the month looks smooth and misses the two weeks that mattered.
The operational cost of stale signals
McKinsey’s earlier B2B Pulse work found that in B2B, inconsistent information across teams is now the leading reason buyers switch suppliers — ahead of coverage and product issues. Stale signals produce exactly this: the account team quotes last month’s delivery score to a client operations lead who is looking at yesterday’s dashboard. The client hears a different story from every seat at the table and quietly starts a shortlist.
The retention math sharpens the point. Bain’s long-running research on customer retention has consistently shown that a five-point improvement in retention drives outsized profit gains across service portfolios. Getting there is not a scoring problem; it is a cadence problem. Weekly-latent Delivery data, event-latent Satisfaction data, and near-real-time Engagement data are what let a CAPA playbook fire when there is still time to change the outcome.
How to instrument refresh without another data project
The instinct at this point is to launch a data warehouse initiative. For most non-SaaS service companies, that is the wrong first step. The faster path is to wire the systems that already hold the signals directly into the score and let each category run on its own clock:
- Map each of the five categories to its source systems — ticketing, ERP, TMS, delivery platforms, finance, CRM, customer portal, feedback tools.
- Set a refresh interval per category that matches its half-life, not the reporting calendar.
- Push the composite score back into Salesforce as custom objects on the Account record, so the sellers who own the relationship see the same score the CRO sees.
- Use a customer portal to expose the parts of the score that are safe to share, so stakeholders can react to a signal before the account team has to.
- Backtest quarterly. If the score didn’t move before a renewal was lost, the refresh cadence is almost always where the miss started.
The takeaway for revenue leaders
Signal weighting decides which category matters most. Signal cadence decides whether any of them matter in time. In non-SaaS service portfolios — where the churn signal rarely arrives as a product-usage drop and the expansion signal rarely arrives as a feature-flag toggle — the refresh interval is the difference between a health score that leads the number and one that reports it after the fact.
See how a five-signal score with category-specific refresh cadences looks against your Salesforce accounts. Book a demo to walk through your portfolio with our team, or start with a free account in the sandbox — no card required — and connect a source or two to see the cadence framework live.