Gross vs Net Renewal Rates: What Each One Actually Tells You

Gross renewal rate is simple: of the accounts up for renewal in a period, what share renewed in any form, even at a reduced contract value. It answers a binary question (stayed or left) and ignores expansion or contraction within the accounts that did renew. This is the number that most directly reflects whether your product and support are keeping customers, independent of upsell success.

Because it ignores dollar movement entirely, gross renewal rate is the cleaner number to trend over time when you specifically want to know whether churn itself is getting better or worse, without expansion revenue masking the trend.

Net renewal rate takes the same renewing cohort and asks what happened to total contract value, including downgrades and upgrades among those who stayed. A tier can have a strong gross renewal rate (few customers left entirely) but a weak net rate if the ones who stayed downgraded significantly, and that combination is exactly the kind of signal a blended, single number would hide completely.

This is the number that matters most to a board conversation about revenue growth, since it captures both the churn story and the expansion story in one figure, but it's also the number most likely to be misread if presented without its gross counterpart alongside it.

Your smallest-tier accounts and your largest-tier accounts often churn for completely different reasons: smaller accounts more often churn on price sensitivity or low usage, larger accounts more often churn on a champion leaving or a competitive displacement. Blending tiers together in one renewal number means the fix you'd apply based on the data is wrong for at least one of the segments driving it.

Build tier as a filter on your renewal report from the start, not something you split out later once a problem is already visible in the aggregate number. Retrofitting tier onto historical data is possible but tedious, and it's far easier to get right if the field exists before the data accumulates.

A renewal pipeline separate from your new-business pipeline, with the account's tier and prior contract value as required fields, lets you calculate both gross and net renewal rate directly from CRM data rather than reconstructing it from finance records after the fact. Foxit eSign fits into this pipeline at the actual signing step once a renewal term is agreed, keeping the whole renewal motion, not just the paperwork, inside one system.

To calculate both rates directly from CRM data, set up:

• A renewal pipeline that is separate from the new-business pipeline.
• The account's customer tier and prior contract value as required fields on every renewal record.
• Gross renewal rate, counting the share of accounts up for renewal that renewed in any form.
• Net renewal rate, tracking total contract value among renewing accounts, including downgrades and upgrades.
• Both rates reported side by side for each tier, never as one blended figure.

Once gross and net renewal rate are split by tier, review the weakest combination (usually the tier with both low gross and low net rate) with whoever owns that segment's relationships and ask a specific question: is this a product gap, a support gap, or a pricing mismatch. A general "renewals are down" conversation rarely produces a fix; a specific tier-and-metric combination usually points toward one fairly directly.

Bring the actual accounts behind the weak number into the conversation, not just the aggregate rate. Reading the notes from three or four real lost or downgraded renewals in that tier usually surfaces a pattern faster than staring at the percentage alone.

For example, imagine a small-business tier where nearly every customer renews but many move to a cheaper plan, while the largest tier loses a few accounts entirely but expands the rest. A blended renewal number would show a healthy total and hide both problems. Split by tier and by gross versus net, the first tier shows a net rate problem tied to pricing or low usage, and the second shows a gross rate problem tied to a champion leaving or a competitor. Each calls for a different fix, so the review conversation can start with the right question for each segment.