How-to guide

How to build a CRM-driven renewal process

Renewals do not fail at the renewal date; they fail quietly in the ninety days before it. A durable renewal process starts four months out, scores health on evidence rather than hope, and uses CRM automation to make sure no account slips through unopened. This guide walks you through the full build: the 120/90/60 touch cadence, the health signals that actually predict churn, the auto-renew logic that balances revenue capture with customer trust, and the expansion motion that turns renewal conversations into growth. Follow it end to end and gross retention above ninety percent becomes a system, not a quarter-end scramble.

Before you start

What you need.

Time: 120 minutes

  • Admin access to your CRM (Strkr or equivalent) so you can edit stages, fields, playbooks, and automations
  • A complete book of business with contract start date, end date, ARR, and term length populated on every account
  • At least one year of historical renewal outcomes, including churned, downsold, flat, and expanded accounts
  • Executive alignment between Customer Success, Sales, Finance, and RevOps on who owns the renewal number
  • A defined product usage signal, or product telemetry pipeline, that can feed health scores back into the CRM
  • An agreed definition of gross retention, net retention, and the segment thresholds you will measure against
Build a CRM-driven renewal process

Step by step.

  1. 1

    Model the renewal opportunity as a first-class record

    Before you touch cadences or health scores, make sure the renewal exists in the CRM as a real opportunity record, not a date field on the account. Create the renewal opportunity automatically the moment the original contract is countersigned, with a close date set to the contract end date, a stage of "Renewal: Not Started," an amount equal to current ARR, and the account owner and customer success manager both populated. Treat the renewal exactly like a new-business opportunity for pipeline, forecasting, and review purposes. Teams that store renewals as a date on the account inevitably lose them. The record has no owner, no stage, no next step, and no forecast weight, so it drifts until someone notices it is thirty days out and panic sets in. A renewal is a sales motion. Give it the same system support you give new business and the whole process gets cleaner.

    • Auto-create a renewal opportunity on contract signature, dated to the contract end date, amount set to current ARR
    • Assign both the account executive and the customer success manager so dual ownership is visible from day one
    • Set the initial stage to a dedicated renewal pipeline, not the new-business pipeline, so forecasts stay clean
    • Backfill renewal opportunities for every active contract before you launch the new process
    Tip: If your CRM shows renewals as dates on the account rather than opportunity records, you do not have a renewal process, you have a prayer.
  2. 2

    Build the dedicated renewal pipeline and stages

    Renewals need their own pipeline because the stages are different from new business. A reasonable default is six stages: Not Started, Discovery, Value Review, Commercial, Negotiation, and Closed. Not Started is the parking lot where every renewal lives until T-minus 120. Discovery is where the CSM runs the health conversation and surfaces usage gaps. Value Review is where the business case is quantified and shared. Commercial is where pricing, term, and uplift are proposed. Negotiation covers legal, procurement, and signature logistics. Closed splits three ways on the close reason field: Renewed, Downsold, or Churned. Keep the stage definitions short and the exit criteria tight. Reps and CSMs will not read anything longer than four bullets. Store the stage definitions where the forecast lives so nobody has to hunt. The goal is a renewal that can be forecast with the same discipline as any other deal.

    • Create a dedicated renewal pipeline with six stages and distinct exit criteria for each
    • Make close reason a required picklist on Closed, with values for Renewed, Downsold, and Churned
    • Add a secondary field for renewal type: like-for-like, downsell, flat with term change, or expansion
    • Train CSMs and AEs on the stage definitions before enabling the pipeline for forecasting
  3. 3

    Install the 120/90/60 touch cadence as an automation

    The 120/90/60 cadence is the backbone of every renewal process that holds up at scale. At T-minus 120 days the renewal moves from Not Started to Discovery, the CSM is prompted to open a health review, and a task is created to confirm the economic buyer and procurement contact are still in seat. At T-minus 90 the Value Review stage opens: the CSM is prompted to deliver a quantified value recap, and the account executive is looped in to flag any expansion signals. At T-minus 60 the Commercial stage opens: pricing is proposed, uplift is justified, and legal review is initiated for any non-standard terms. At T-minus 30 the Negotiation stage opens and finance is pulled in for revenue recognition timing. The automation does not do the work. It makes sure the work gets started. Reps who have run this cadence for a year will tell you the single most important moment is the T-minus 120 ping, because it is the only one that catches silent churn before it hardens.

    • Create a time-based automation that advances renewal stage based on days-to-close-date
    • Fire a task to the CSM at T-minus 120, 90, 60, and 30 with a stage-specific checklist
    • Flag any renewal that has not advanced within seven days of its scheduled trigger as at-risk
    • Escalate any renewal that is still in Not Started at T-minus 90 to the segment leader
    Tip: The T-minus 120 touch is the one that saves the renewal. Every other touch is damage control.
  4. 4

    Define the health signals that actually predict churn

    Health scores fail when they are built from vibes. Build yours from four categories of hard signal. Product usage: active users, weekly active days, feature adoption against the baseline the account signed up to use, and the trend over the trailing ninety days. Commercial: time since last expansion, days until renewal, open credits, outstanding balance, and payment on time rate. Relationship: executive sponsor last engaged, number of named stakeholders in the account, open support tickets by severity, and NPS or CSAT trend. Lifecycle: has the account completed onboarding milestones, hit the usage threshold their plan was sized for, and attended at least one business review this term. Weight the categories by what historically predicted churn in your own data. Do not borrow a competitor's formula. Your product, your contract shape, and your buyer behavior are different, and borrowed health scores produce false confidence until the first bad quarter rips the illusion open.

    • Pull last year of churned accounts and run a backward regression against candidate signals
    • Weight the top four to six signals by predictive power, not by what feels important
    • Score every account weekly and store the score history so trend becomes visible, not just the point value
    • Publish the formula to CSMs and AEs so health is a shared language, not a black box
    Tip: Point-in-time health lies. Trend over ninety days tells the truth. Always show both.
  5. 5

    Wire the auto-renew logic without burning customer trust

    Auto-renew is a two-edged tool. Done well it protects revenue on long-tail accounts and reduces renewal friction for happy customers. Done badly it generates refund requests, chargebacks, and churn-with-a-vengeance when a customer finds the surprise charge. The honest version of auto-renew has five rules. First, auto-renew clauses are disclosed at signature in plain language, not buried on page nineteen. Second, the system sends a renewal notice at T-minus 60, T-minus 30, and T-minus 7, no matter what the contract says about notice. Third, any uplift above a published threshold (we use five percent) requires explicit opt-in, not silent application. Fourth, downgrades and cancellations are available self-serve in the admin console with no retention gates designed to trap. Fifth, finance reconciles the auto-renew list seven days before invoice to catch any account flagged as at-risk or in active negotiation. Teams that follow these rules see their auto-renew revenue hold up because the customers who get auto-renewed are the ones who actually meant to stay.

    • Document auto-renew terms in plain language on the order form and the customer portal
    • Send notice emails at T-minus 60, 30, and 7, with the invoice preview attached to the T-minus 7 note
    • Require explicit opt-in for any uplift above the published threshold; default to flat if the customer does not respond
    • Build a seven-day pre-invoice reconciliation hold so finance can suppress any at-risk or disputed renewals
    Tip: A customer who is surprised by an auto-renew charge is a customer you lose for two years, not one.
  6. 6

    Make expansion a required conversation at T-minus 90

    The renewal window is the single highest-leverage expansion conversation of the year. The customer is already engaged, the business case is on the table, and procurement is briefed. Build the expansion motion into the Value Review stage so it happens on every renewal, not just the ones a rep remembers to pitch. At T-minus 90 the system should prompt the CSM to pull the usage report, flag any account that has crossed its license tier threshold, surface any adjacent product the account has not adopted, and route a lightweight expansion brief to the account executive. The brief includes current ARR, usage against limits, three expansion plays scored by fit, and a suggested uplift range anchored to published list pricing. The AE then owns the expansion conversation, the CSM owns the renewal conversation, and the two merge into a single commercial offer at T-minus 60. Teams that run this consistently see net retention gains of ten to fifteen points without changing their pricing, because expansion is finally happening on purpose instead of by accident.

    • Auto-generate an expansion brief at T-minus 90, pulled from usage, product adoption, and account-fit signals
    • Route the brief to the AE while the CSM owns the health conversation; the two reconcile before T-minus 60
    • Score every expansion play against three criteria: fit, usage signal strength, and economic buyer appetite
    • Track expansion win rate separately from renewal win rate so you can tune the motion over time
  7. 7

    Install a weekly renewal and at-risk review

    Health scores and automation only matter if the humans who own the number actually look at the data. Run a weekly renewal review with the segment leader, every CSM, and the account executive counterpart. Walk every renewal that is inside the T-minus 120 window and every at-risk account outside the window. For each one, ask three questions: what is the current health trend, what is the specific commitment the customer has made or needs to make this week, and what is the probability we land it at or above current ARR. Record the probability. Track delta from actuals. If you discover the team is systematically under-forecasting at ninety days and over-forecasting at thirty, you have a calibration problem, and calibration problems are fixable with coaching. The review is not a status meeting. It is a working session where next steps get assigned, saves get planned, and expansion asks get finalized. Hold it every week, same time, same agenda.

    Tip: If a CSM leaves the renewal review without a specific next step for every at-risk account, the review did not happen.
  8. 8

    Build the save motion before you need it

    When a customer gives notice, the first forty-eight hours decide the outcome. Build the save motion ahead of time so nobody is improvising at the moment of maximum stress. The save kit contains four assets. First, a diagnostic script that walks a CSM through five questions in under fifteen minutes to understand whether the issue is product, price, people, or priority. Second, a tiered concession ladder with pre-approved pricing, term, and feature-unlock options the CSM can offer without escalation. Third, an executive sponsor outreach template so the account executive and a VP can co-sign a save plan within twenty-four hours. Fourth, a post-save commitment plan with a sixty-day check-in built in so a save does not just defer the churn by one cycle. Track save rate as a separate metric from gross retention. A save rate under thirty percent means the diagnostic is wrong or the concession ladder is too stiff. Above sixty percent and you are probably giving away margin that was not required.

    • Write the diagnostic script with five questions covering product fit, pricing, stakeholder change, and strategic priority
    • Pre-approve a concession ladder with CFO sign-off so CSMs can act without a two-day escalation delay
    • Build an executive sponsor template library so VP outreach is twenty minutes, not two days
    • Attach a sixty-day commitment plan to every save so you track whether the save held
  9. 9

    Instrument retention metrics and recalibrate quarterly

    Once the renewal process is live, four metrics belong in front of leadership every quarter. Gross revenue retention: how much of starting ARR you kept, before any expansion. Net revenue retention: how much starting ARR you kept, after expansion. Logo retention: what percentage of customer logos renewed, which exposes mix shifts the dollar metrics can hide. And renewal win rate by segment, so you see whether your mid-market retention is masking enterprise erosion or the reverse. Compare each metric to the prior four quarters and against your published target. Then dig into the drivers. If gross retention slipped, is the leak in a specific segment, a specific product line, or a specific cohort tenure band? If expansion dropped, did a product gap emerge, or did an AE change absorb attention away from the motion? Treat the renewal process like a product. Measure it, iterate on it, retire the parts that stopped working. The system that worked a year ago will not keep working forever, and renewal processes decay quietly, so the quarterly review is the circuit breaker that catches drift before it becomes damage.

    • Report gross retention, net retention, logo retention, and renewal win rate every quarter at the leadership table
    • Segment every metric by product, cohort, and ARR band so trends are visible, not hidden in the average
    • Compare actual outcomes to the probabilities the team committed to; the gap is your true calibration score
    • Retire health signals and stage criteria that stopped predicting outcomes; the system is a living artifact
    Tip: Net retention is a vanity number if you do not also publish gross. One of them is honest about churn and the other is not.
Avoid

Common mistakes.

  • Treating the renewal as a date on the account rather than an opportunity record. Renewals without owners, stages, and next steps drift until the last thirty days, which is when it is too late to save them.
  • Starting the renewal motion at T-minus 60 instead of T-minus 120. By sixty days out, procurement has already moved on, the budget has shifted, and the real conversation is damage control, not value reinforcement.
  • Building a health score from vibes rather than from a regression against your own churned accounts. Borrowed health formulas feel sophisticated and produce false confidence until the first bad quarter.
  • Auto-renewing without three disclosed notices and an explicit opt-in on uplifts. The short-term revenue capture is real; so is the long-term reputational cost and the trail of refund disputes.
  • Separating renewal and expansion into two conversations run by different people on different timelines. Buyers see one commercial relationship, so the account team should bring one commercial offer.
  • Running the save motion as improvisation. By the time a customer gives notice, forty-eight hours is all you have, and nobody writes a good diagnostic script under that pressure.
  • Reporting net retention without gross retention. Expansion can mask severe churn in a cohort, segment, or product line, and the leadership team deserves to see both numbers side by side.
FAQ

Frequently asked questions.

When should the renewal process start?

A full twelve months before the renewal date for enterprise contracts above six-figure ARR, and T-minus 120 days for everything else. The twelve-month window on enterprise reflects the reality that procurement cycles, business-case approvals, and executive-sponsor turnover all unfold on a long clock. The 120-day window on everyone else is the earliest point at which usage trends from the current term are stable enough to feed a credible value review, and the last point at which you can still intervene on an at-risk account before the customer has mentally moved on.

Who owns the renewal number: Customer Success or Sales?

Dual ownership works best. Customer Success owns health, adoption, and the value conversation. Sales owns the commercial negotiation, pricing, and legal path to signature. Both names appear on the renewal opportunity, both attend the weekly renewal review, and compensation is split so neither side can win while the other loses. The one organization-level requirement is that one leader (usually a VP of Customer Success or a Chief Revenue Officer) owns the aggregate retention number so there is no finger-pointing at the quarter close.

Should renewals live in the same pipeline as new business?

No. The stages, probabilities, and sales motions are different enough that mixing them pollutes the forecast and dilutes the reporting. Build a dedicated renewal pipeline with its own stages, its own forecast categories, and its own weekly review. Reporting tools should be able to roll both pipelines into a single total-company forecast at the leadership level while keeping the operational views distinct for the teams running the motions.

How do I set the uplift threshold for auto-renew without burning trust?

Publish the number. Five percent is a defensible benchmark for inflation-plus-usage-growth adjustments on standard contracts, and most buyers accept it as a reasonable annual escalator. Any uplift above the published threshold should require explicit customer opt-in, not silent application. If the customer does not respond, default to flat renewal rather than auto-applying the uplift. The short-term revenue hit on the small cohort that would have accepted it silently is dramatically outweighed by the long-term trust and renewal predictability of the broader base.

What is a good health-score weighting?

There is no universal answer, and that is the point. Run a backward regression against your own last year of churned accounts and let the data tell you which signals predicted outcomes. For most SaaS businesses the top predictors are weekly active users against the baseline, executive sponsor engagement in the last ninety days, outstanding support tickets at severity one or two, and completion of onboarding milestones. The specific weights will drift over time as your product matures, your buyer changes, and your contract shape evolves, which is why the quarterly recalibration is non-negotiable.

How do I handle renewals where the economic buyer has changed?

Treat it like a new-business cycle inside a renewal shell. The usage history, product fit, and existing commercial terms are advantages you did not have in net-new, but the buyer discovery, business-case construction, and executive alignment all need to be rerun from scratch. Account executives who try to shortcut this because "we are already in the account" lose these renewals more often than they realize. The buyer change is a signal to add thirty days of lead time to the standard cadence and to escalate the opportunity to a senior reviewer early.

What save rate should I target?

Between thirty-five and fifty-five percent is the realistic healthy band for a save motion that is well instrumented but not giving away margin. Below thirty percent and the diagnostic script is probably missing the real reason customers are leaving, or the concession ladder is too narrow to be useful. Above sixty percent and you are likely offering concessions that were not required to close the save, which erodes margin and trains customers to threaten churn as a negotiation tactic. Track save rate separately from gross retention so you can tune the motion without hiding behind aggregate numbers.

How do I forecast renewals accurately?

Weight each renewal by stage probability derived from your own historical conversion data, then overlay a manager judgment call that moves deals between Commit, Best Case, and Pipeline. Probability math alone will produce a smooth-looking forecast that misses the specific accounts your team already knows are at risk. Manager judgment alone will produce an optimistic forecast that papers over systemic weakness. The combination of calibrated probabilities and recorded manager overrides, measured against actuals every quarter, is the only method that produces forecast error inside ten percent at scale.

See it in Strkr

Related product surfaces.

Strkr CRM All features

Run a renewal process that protects revenue and surfaces growth

Strkr gives you the renewal pipeline, health scores, 120/90/60 cadence, and save-motion views you need to run this playbook end to end. Build once, review weekly, retain with confidence.

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.