The SaaS Renewal Process: A 120-Day Operating Plan

What does a working renewal process look like?

A dated sequence with exit criteria at each step, run as a forecastable deal rather than an administrative task. Most renewal processes are a calendar reminder and a paperwork chase. That works while customers are happy and fails the moment one is not, which is precisely when the process needs to earn its keep.

The timeline below assumes an annual enterprise contract. Compress it for mid-market and shorten again for monthly plans, but keep the sequence intact.

Each row has a date and an owner. A step that slips past its date is the earliest reliable warning that the renewal is in trouble.

When should the renewal process start?

120 days out, because the time between first contact and the renewal date is your only leverage. Every week you wait removes an option. At 120 days you can fix an adoption gap, build a business case, and involve an executive. At 30 days the only lever left is price.

Start the clock from an internal review rather than a customer conversation. Pull the account's usage trend, support history, seat deployment, and open escalations before anyone reaches out. Walking into a value review without knowing that half the purchased seats were never provisioned costs you the room.

Who owns the renewal?

One person, with the renewal ARR carried on their number. Shared accountability between customer success and the account team sounds collaborative and produces a renewal nobody chased. Name the owner at the 120-day review and make them the person who reports on the account in the weekly forecast call.

The owner does not do all the work. A solutions engineer may run the adoption fix and an executive sponsor may take the sponsor-to-sponsor meeting. But the forecast entry has one name against it, and that person answers for the close date.

What stages should a renewal opportunity use?

Four stages tied to buyer evidence, not to internal activity. Stage names like "outreach sent" describe what your team did. Stages need to describe what the customer did, because that is what predicts the outcome.

Use committed value confirmed, stakeholders confirmed, proposal delivered, and terms agreed. An account moves to stage two when the buyer has named the economic decision maker for this cycle, not when your team has guessed at one. Renewals modeled this way behave like any other deal and belong in the same sales forecast as new business, with the same standard of evidence for stage progression.

Hold renewal opportunities to a coverage view as well. Renewal ARR up for decision in a quarter needs the same visibility as new pipeline coverage, because a quarter with heavy renewal exposure and thin new pipeline is a different quarter from one with the reverse.

How do you handle a renewal that goes quiet?

Escalate on silence rather than waiting for a stated objection. The strongest signal that a renewal is at risk is the absence of a signal. No responses, no scheduled meeting, no data changing on the account. In deal work the earliest warning is the same, and a close date that keeps moving is the clearest single indicator of trouble, which is why deal slippage is worth watching on renewals as closely as on new business.

Set a rule and enforce it. Two unanswered touches inside a 10-day window triggers a different channel and a different sender. Executive to executive, or a written note that names the risk plainly: the contract expires on a specific date and you need a decision path. Politeness here costs money. Buyers who have decided to leave rarely announce it, and the team that keeps sending gentle check-ins finds out at the deadline.

How do you keep renewals off the discount table?

Separate the value conversation from the commercial conversation by 60 days. Discounts get granted when a buyer questions worth at the moment a signature is due, because at that point the seller has no time and no argument prepared.

Run the value review at 90 days with numbers the customer supplied. Usage they can verify, outcomes their team reported, hours or dollars they can attribute. Get agreement on that in writing before pricing appears. When the proposal lands 30 days later, the debate is about terms and structure instead of about whether the product earned its budget line.

How does the process change for multi-year or monthly contracts?

The review cadence stays and the commercial step moves. A three-year agreement still needs an annual value review, because the sponsor who signed it may be gone by year two and the account has to be re-sold internally long before any signature is due. Run the 90-day value review on each anniversary and use it to accumulate the evidence for the renewal that eventually arrives. Multi-year deals fail at renewal for the same reason annual deals do, except the neglect had three years to compound.

Monthly contracts invert the problem. There is no renewal date to organize around, so the process attaches to behavior instead. Set a threshold review for any account whose deployment or activity dropped month over month and treat that drop as the renewal event, because a monthly customer makes the repurchase decision whenever they next look at the invoice. The 120-day timeline collapses into a 30-day one, and the value review becomes a usage conversation, but the sequence and the ownership rule hold.

How do you know the process is working?

Three measures: on-time renewal rate, days from process start to signature, and the share of renewals closing at or above prior ARR. On-time renewal rate catches administrative failure, where a contract lapses into month-to-month because nobody moved. Cycle time catches process drift. The ARR measure catches the discounting habit, which hides inside a perfect logo retention number.

Add one diagnostic. For every renewal that closed below prior ARR, record whether the process started on time. The correlation between late starts and lost dollars is usually the most persuasive argument you will have for enforcing the 120-day rule.