Why renewal and expansion pipeline needs its own stage-weighted coverage check

Renewal and expansion pipeline needs its own stage weighted coverage check because the two numbers that check runs on, the weight assigned to each open deal and the cycle length used to set the target, are both wrong when borrowed from new business pipeline. A win rate earned on qualification criteria does not describe a renewal motion scored on churn risk and usage trend, and Gartner's own research into expansion timing shows the cycle itself runs longer too.

The stage weighted coverage check published here last week deliberately scoped its worked example to new business pipeline, and the bowtie already argues expansion deserves the same signal discipline as acquisition. This is that check rebuilt for the other side of the close.

Why doesn't the new business stage weighted check transfer to renewal and expansion pipeline?

Because the input that sets each deal's weight, a stage conversion rate earned from qualification criteria, assumes a buying process renewal and expansion pipeline never goes through.

A new business deal moves through stages because a buyer is being qualified: budget confirmed, a champion identified, a proposal issued. An existing customer skips most of that. They already bought, already pay, and a renewal or expansion conversation starts from a different question entirely, whether the account's usage and sentiment is trending toward more spend or toward churn. Stage labels built around a qualification sequence do not describe that question, so a conversion rate earned from new business stages has nothing to weight a renewal deal against.

Gartner's own research into expansion timing, published 17 June 2024, found something closer to a coin flip than a predictable sequence: 27% of surveyed customers expanded their contract to at least 1.5 times its original value, and another 27% expanded by less than 1.1 times. Customers in the larger group also took 1.5 to 2.5 additional months to move from first considering the expansion to a finalised contract. A single flat weight cannot describe a population that splits that evenly between a near miss and a major expansion, the same problem a flat 3x multiplier has on the new business side, doubled.

What replaces stage conversion rate as the input for renewal and expansion weight?

A health band weight built from your own churn-risk and usage data, scored against actual renewal and expansion outcomes over the same two quarter window used for the new business check.

Score each open renewal or expansion opportunity into a small number of health bands, healthy, watch, at risk, using whatever combination of usage trend, support ticket volume and engagement your own product and customer success data support. Then, exactly as the new business check does for a pipeline stage, go back over the last two closed renewal cycles and measure what each band actually produced: the real rate at which a healthy account renewed or expanded, not the rate a product dashboard's default thresholds assume it should.

A third party signal can corroborate that band the same way it corroborates a new business score. The Revenue Signal Field Manual uses Bombora's Company Surge product for acquisition: it scores an account's topic level research activity from 0 to 100 each week, comparing the last three weeks of activity against a rolling twelve week baseline, and Bombora's own documentation treats a score of 60 or above as a statistically significant surge. The same mechanism works for a renewal risk read if the topic list points at a competitor's category instead of your own. A surge there, landing inside a renewal window, is corroborating evidence for a downgraded health band, never proof on its own, the same rule how to score a revenue signal sets for any third party signal.

What does a worked renewal and expansion coverage check look like?

Multiply each open deal's value by its health band weight, then discount it further the longer the account's usage data has gone unchanged.

Say a renewal and expansion pipeline looks like this part way through a quarter:

The face value of that pipeline is £690k. The weighted value is a little over £361k. The gap matters most in the stale row: a £120k account sitting in Watch with no usage data movement for six weeks was contributing its full face value to a flat coverage number and a fraction of that to the real one, exactly the pattern the new business staleness discount already catches on the acquisition side.

Why does the cycle length in the coverage formula need its own number for expansion deals?

Because required coverage is one divided by win rate, adjusted for sales cycle length, and Gartner's own data shows the renewal and expansion cycle is not the new business cycle.

The stage weighted coverage check for new business pipeline already makes the point that a flat 3x multiplier only holds at a 33% win rate and a one year cycle, and moves as soon as either term does. Gartner's finding that larger expansions take 1.5 to 2.5 months longer between first consideration and a finalised contract means the cycle length term for expansion pipeline has to be calculated on its own, from your own closed expansion deals, rather than inherited from a new business number that was never measuring the same motion.

Should renewal and expansion coverage sit in the same number as new business coverage?

No. Keep them as two separate targets reported side by side, because combining them hides which side of the revenue engine is actually short.

The bowtie model treats acquisition and the retention and expansion side as different disciplines with different inputs, and the coverage number should follow the same split. A board that sees one blended coverage ratio cannot tell whether a healthy looking number is hiding thin new business pipeline behind strong renewals, or thin renewals behind a strong new business quarter. The Revenue Forecast Accuracy Handbook's weekly update rate diagnostic runs the same way on both sides once they are split: the share of open opportunities with a genuine change in the last seven days, measured separately for new business and for renewal and expansion.

The mechanics are the same shape on both sides of the close, weight each deal by what it has actually produced, discount what has gone stale, then set coverage from your own cycle length rather than a borrowed one. What changes is the data that earns the weight. New business earns it through qualification. Renewal and expansion earn it through usage and churn risk, which is why the two checks were never going to share one number.