Run the renewal motion

The situation

You have customers on annual contracts. The renewal conversation happens six weeks out, and by then the answer is usually already decided by things that happened in months four through nine, when nobody was looking at the account because nothing was wrong.

A traditional CRM handles this with a renewal date field and a task reminder, which tells you about the renewal exactly when it is too late to change the outcome.

What must be true when you are done

• Every renewal in the next quarter is a deal with a date and a number.
• You know which accounts have gone quiet, separately from which are due.
• Each at-risk account has a next action and somebody's name on it.
• Why a renewal was at risk is written down before the outcome is known.

Renewals are deals, not dates

Model a renewal as an opportunity in its own pipeline. A date field on the company cannot be forecast, cannot be weighted, and cannot be lost, so it tells you nothing until it fires.

Two pipelines rather than stages bolted onto the new-business one, because a renewal at fifty percent means something completely different from a new deal at fifty percent, and mixing them makes both forecasts useless.

The two signals

Run these monthly. They are different questions and the second one is the one nobody asks.

What is due. Obvious, and everybody does it.

What has gone quiet. The one that predicts the outcome. An account nobody has spoken to in two months is not a renewal risk yet, and it is exactly the account that becomes one.

Cross the two lists. An account that is both due and quiet is where the month's attention goes. An account that is quiet but not due is where the month's attention actually pays off, because there is still time.

Write the risk down before you know the answer

This is the step that turns the pass into something cumulative rather than a monthly panic.

Recording the reason while the outcome is still open is what makes the history worth anything. A year of renewals with reasons written down afterwards tells you what you decided to believe. A year with reasons written down in advance tells you which risks were real.

Then look back and check yourself

After a couple of quarters, ask the question the data can now answer.

Those two numbers are not the same and the gap is the interesting part. The first tells you whether At risk means anything. The second tells you what you are not seeing: churned renewals you never flagged are the signals you have not learned to read yet, and they usually have something in common.

What this deliberately does not do

There is no health score. Nothing computes a number from product usage, ticket volume and email sentiment and puts a red dot next to an account.

Partly because the inputs are not here: no product telemetry, no support desk. But mostly because a health score is judgement laundered into a number, and the number is what people argue with instead of the judgement. "Quiet for sixty days and their champion left" is a sentence somebody can disagree with usefully. A 62 is not.

If you want a score, you have the data to compute one outside and write it back as a custom field. That is a deliberate act rather than a default.

Verify the pass

• Total the renewal pipeline against billing. They should agree. If they do not, some customer has no renewal deal, which is how renewals get missed entirely.
• Check every At risk deal has a task. A risk with no next action is a note, and notes do not change outcomes.
• Read one account you marked at risk last quarter. Does the history tell you what happened next? If it stops at the flag, the pass is producing worry rather than work.

Run it again

Monthly, and the quiet list is the half to protect. When the pass gets compressed it is always the due list that survives, which means the motion degrades into exactly the six-weeks-out scramble it was meant to replace.