How to Ask for a Renewal Before It's Due

Why ninety days

A renewal conversation at thirty days is a negotiation. At ninety days it is a conversation, and that difference is most of the outcome.

At ninety days there is still time to fix a problem, add the second team, run the training that never happened, or repair a relationship after a champion left. At thirty days none of that is possible, so the only available moves are price and pressure.

There is a second reason for the early start. Many customers have their own internal process: budget approvals, procurement cycles, a finance calendar. A supplier who raises renewal at thirty days can force a customer into an awkward internal scramble, which is not how you want to be remembered when the alternatives are being considered.

The conversation

1. Day 90: ask whether it still earns its place

   Not "are you renewing?" but "is this still doing what you needed when you signed?". Then be quiet and take the answer seriously.

   This question feels risky and is the whole point. You are trying to surface the objection now, while there is time to do something about it.

   Day 90Ask the risky question

2. Day 90: check the shape of the account, not just the mood

   How many people use it, whether the original champion is still there, whether it spread beyond the first team.

   Warm words from a single remaining user is the most common profile of an account that does not renew. The signals in [spotting a customer about to churn](/blog/spot-a-customer-about-to-churn) apply directly here.

   Day 90Shape beats sentiment

3. Days 60 to 75: fix whatever surfaced

   One thing, visibly, before the renewal date. Training for a new team, a workflow that never worked, an introduction to whoever replaced the champion.

   The fix matters less than the fact that raising something with you led somewhere. That is what a renewal decision is actually made on.

   Days 60-75Act on what they said

4. Day 45: put the commercial terms in writing

   Price, term, anything changing, and the date. Plainly, in an email they can forward to whoever approves it.

   Give them a document that survives their internal process, for the same reason a [proposal](/blog/proposal-that-gets-signed) is written for the person who was not on the call.

   Day 45Forwardable

5. Day 30: confirm, and name what happens next year

   Get the confirmation, then agree what would make next year better. That conversation sets up the following renewal twelve months early.

   It also gives you something specific to have worked on when you open the next cycle.

   Day 30Set up the next one

Raising a price increase

Increases are accepted much more often than people fear. Surprises are not.

Give more notice than the contract requires. If it says sixty days, tell them at ninety. Notice is the variable that most affects how an increase is received.

Give a reason and a number in the same message. "Our prices are increasing by 8% from January, which is the first change in two years and reflects the support and product work in that period." Vague increases invite a challenge; specific ones are usually processed as a fact.

Send it from a person, not from billing. An increase arriving as a system notification reads as something being done to them.

Offer something in exchange where you can. Locking the current price for a two year term, or adding seats at the old rate. It converts an imposition into a choice.

Expect the good customers to ask. A customer questioning an increase is engaged. The ones who say nothing and quietly start looking are the harder problem.

When they want to reduce or leave

Find out what changed before defending anything. A customer reducing seats because their team shrank has a different problem from one reducing because only one person ever used it. The first is a fact about their business, the second is a value problem you might be able to solve.

Take a reduction over a cancellation, without drama. A smaller renewal keeps the relationship and the option of growth later. Making a customer feel judged for reducing is how you convert a reduction into a departure.

Ask the honest question when they are leaving. "What would have had to be different?" and then listen without arguing. This is the single most valuable input you will get all quarter, and it belongs in the same fixed-list record as your other loss reasons, as covered in win/loss analysis.

Leave well. Help with the export, do not make cancellation difficult, and say the door is open. Customers who leave cleanly recommend you, and some of them come back. Customers made to fight their way out tell people about it.

Only discount for something in return. A longer term, an upfront payment, a case study. A discount given purely to stop a cancellation resets your price permanently with that customer and usually leaves the original reason untouched, which means you have the same conversation next year from a lower base. The same trade logic applies as in handling price objections without discounting.

One structural point. Nearly everything above depends on knowing what happened in the account over the year: who used it, what they raised, what you fixed. If that history lives in one person's inbox, the renewal conversation starts with archaeology. Keeping it on the customer record, as CRM data hygiene sets out, is what lets anyone on your side open a renewal conversation with specifics rather than pleasantries.