What Is a Good Renewal Rate for B2B SaaS?

What Is a Good Renewal Rate for B2B SaaS?

A good renewal rate is one where the dollar version sits close to the logo version, because the gap between them is where quiet revenue loss lives. Renewal rate measures a specific event: a contract reaching its decision date and either continuing or ending. That framing makes the headline percentage easy to game and easy to misread. A team can renew 95% of its contracts while renewing only 80% of the value attached to them, and the first number will be the one in the deck.

Chase the gap first. Closing a spread between logo and dollar renewal usually recovers more revenue than moving the logo rate up by a point, and it points at a specific failure: scope reductions, seat cuts, or discounts granted to secure the signature.

How Is Renewal Rate Different From Churn Rate and NRR?

Renewal rate is event-based, churn rate is population-based, and NRR is dollar-based with expansion included. They answer three different questions and will disagree with each other in any period where the renewal calendar is lumpy. The denominator column is the whole distinction. A quarter with few renewals due can produce a spectacular renewal rate and a terrible churn rate at the same time, because the losses came from accounts that were not up for renewal. Report the renewal rate alongside the value of contracts that were actually due, or the percentage means nothing.

Which Renewal Rate Version Should You Track?

Track logo and dollar renewal separately, and keep upsell out of both. Logo renewal answers whether the renewal team is holding accounts. Dollar renewal answers whether it is holding value. Blending upsell into a renewal rate produces figures above 100%, which feels good and destroys the diagnostic value of the metric. Expansion has its own home in net revenue retention, where it is netted against every form of contraction.

Two mechanics decide whether the numbers are usable. First, fix the denominator at the start of the period based on scheduled renewal dates, and do not let renegotiated early renewals move contracts between periods without a restatement. Second, decide how auto-renewals count. A contract that renewed because nobody canceled is a different signal from one a customer actively re-committed to, and tracking those separately gives you an early read on which segments are coasting.

What Does Renewal Timing Do to Your Forecast?

It concentrates risk into specific weeks, which makes a blended monthly retention assumption wrong in both directions. Renewal dates cluster around the anniversaries of past selling seasons, so a company with a strong Q4 history carries a heavy Q4 renewal book years later. Applying an even monthly churn assumption across that calendar understates risk in the heavy months and overstates it everywhere else.

Renewals also deserve a separate forecasting method. New and expansion revenue moves through stages with progression probabilities. Renewals have known decision dates and known values, so the method looks more like a scheduled event with a risk score than a pipeline. This distinction matters when accuracy claims get quoted: forecast accuracy figures for new and expansion revenue describe that scope only. Renewal forecasting is measured on its own terms, and mixing the two produces an accuracy number that means nothing to either.

What Are the Earliest Signs a Renewal Is at Risk?

Engagement extremes, visible months before anyone opens a renewal conversation. In ORM's data, a customer with zero support cases in a year is at real risk of churning, and so is a customer with seven or more. The healthy middle is three to five moderate tickets, usually tier 2 or tier 3 rather than severe. Those customers are engaged, getting help, and generally happy.

Silence is the signal most teams misread. No tickets gets logged as a satisfied account when it usually means the product has fallen out of the daily workflow, and a product nobody uses is trivial to cut in a budget review. High-volume severe tickets carry the opposite problem and are at least easy to see. Build the renewal risk review around usage and support patterns 120 days out rather than around a relationship check-in 30 days out, when the budget decision has already been made somewhere you were not invited.

How Do You Set a Renewal Rate Target That Means Something?

Set it per segment, on dollars, against the specific book due in the period. One company-wide renewal target applied to a quarter with a heavy enterprise renewal book and a quarter with a heavy SMB book asks two different things of the same team. Segment the target, weight it by the value at risk, and name the accounts that carry the outcome.

Then close the loop with a retrospective. For every renewal that came in below full value, record whether the loss came from a downgrade, a discount, a product removal, or an outright non-renewal. Those four causes have four different owners and four different fixes, and a rate reported without them tells you only that something went wrong. Feeding that history back into the renewal model is what turns the target into a plan rather than a hope. For how renewal risk enters the broader revenue number, see how to forecast revenue.