Most renewals don't die in the negotiation. They die in the calendar. The contract lapsed because nobody scheduled the business review in month nine, the stakeholder map went stale, the champion changed roles and nobody noticed until the invoice hit an empty desk. Renewal work is scheduling work โ a chain of touchpoints with hard dates, and if any link slips, the whole thing quietly detaches.
So stop treating renewals as an event and start treating them as a flow. A countdown: fixed checkpoints at 90, 60, 30, 14, and 7 days before the renewal date, each with a defined purpose, a defined attendee list, and a defined exit criteria. Get the scheduling right and the renewal conversation gets easy. Get it wrong and you're discovering procurement requirements two weeks before the contract expires.
Below is the checklist. It assumes annual contracts; I'll note the adjustments for shorter terms at the end.
The operating principle: schedule backward, confirm forward
The entire flow rests on one habit: schedule every touchpoint the moment the previous one ends. Never leave a renewal meeting without the next one on the calendar. The 90-day call ends by booking the 60-day. The 60-day ends by booking the 30-day. Customers who would never return a cold "can we find 30 minutes?" email will always accept a scheduling ask made live, while the previous meeting's momentum is still warm.
This is why the countdown starts with discovery rather than paperwork. Each checkpoint exists to produce one artifact and one booked meeting. If a checkpoint can't produce its artifact, that's your early warning โ not a scheduling problem, a risk flag.
T-minus 90: The renewal discovery call
Purpose: Learn everything the renewal will hinge on โ before it hinges.
Who: CSM, account executive if one owns the commercial motion, the day-to-day champion.
The agenda, in order: First, what changed since signing? Team changes, reorgs, mergers, new leadership โ half of all renewal surprises are org changes nobody told you about. Ask directly: "Who should I know about who wasn't in the room last year?" Second, how are they measuring the value of your product right now? Not your health score โ their answer, in their words. Write it down verbatim; you'll build the ROI narrative from exactly those words at T-30. Third, what's the procurement process this year? Vendor reviews, security reassessments, budget cycles, who signs. If procurement needs 45 days, your T-90 is actually T-135, and you need to know that now.
Artifact produced: a renewal brief โ one page covering the stakeholder map (updated), the customer's value language, procurement timeline, known risks, and expansion signals worth exploring.
Meeting booked on the way out: the T-60 business review, with the customer's executive sponsor invited. Yes, invite the sponsor now โ you're giving them two months' notice, which is respectful rather than presumptuous.
T-minus 60: The business review
Purpose: Remind them, with evidence, why this renewal is a good decision.
Who: CSM presenting, champion co-presenting (this matters โ more below), executive sponsor in attendance, any new stakeholders from the T-90 org-change sweep.
The agenda: This is a QBR with a thesis: the value story, told in the customer's own language from T-90, backed by their usage data. Three sections, no more. What they set out to do (their goals from onboarding or last year's review). What happened (outcomes in their numbers โ adoption, time saved, revenue touched, whatever they said they cared about at T-90). What's next (the expansion or optimization conversation, framed as their idea, because it should be โ the T-90 discovery told you what to propose).
The co-presenting trick: ask the champion to present one slide: "what this changed for my team." A vendor telling a sponsor the product is great is sales. A champion telling their own sponsor is proof. If the champion won't co-present, that's a risk signal โ note it in the brief and adjust the T-30 plan.
Artifact produced: the value recap โ a one-pager or three-slide deck the champion can forward internally. Assume the person who signs the renewal never attends this meeting. The artifact is what attends for you.
Meeting booked on the way out: the T-30 commercial check-in, this time with procurement or the economic buyer looped in.
T-minus 30: The commercial check-in
Purpose: Surface every contractual, legal, and procurement obstacle while there's still time to clear them.
Who: CSM plus whoever owns the commercial motion on your side, economic buyer and procurement contact on theirs.
The agenda: Start with the renewal terms on the table โ same scope, adjusted scope, multi-year option. Then run the obstacle audit, out loud: "What needs to happen on your side for this to sign by [date]?" Get each step named with an owner and a date: security review, legal redlines, budget approval, signatory availability. Write them down live and read them back. The awkwardness of this exercise is the point โ vague processes produce vague timelines, and vague timelines produce lapsed contracts.
The multi-year move: T-30 is when you float the multi-year option if you haven't already. Frame it around their incentives (price protection, budget certainty), not yours. A three-year deal signed now is worth more than a one-year deal renegotiated twice.
Artifact produced: a mutual close plan โ the dated checklist of everything between now and signature. Share it as a living document both sides can see.
Meeting booked on the way out: a 15-minute T-14 confirmation call with the champion.
T-minus 14: The confirmation call
Purpose: Verify the close plan is on track. That's it.
Who: CSM and champion. Fifteen minutes, async-first if the close plan is green.
This meeting is a tripwire, not a review. Two questions: is every item on the close plan still on schedule, and has anything changed since T-30? If the answers are yes and no, end the call early and celebrate briefly โ protect the pattern of these being easy. If something slipped, you have two weeks, which is enough for almost any single obstacle. This is the call that T-30 earns you the right to have.
T-minus 7: The signature push
Purpose: Get the signature before the week of the deadline, because the week of the deadline is when everyone else's emergencies become yours.
By T-7, there should be no new information in play โ only execution. Confirm the signatory has the document, confirm the signing method (Docusign link? wet signature? portal?), and confirm the date. If finance needs to process the PO before the renewal registers, that clock is ticking on their side, not yours.
Adapting the countdown to shorter terms
For six-month contracts, compress: 45/30/14/7. For quarterly terms, the flow becomes 30/14/7 โ and honestly, if you're running quarterly renewals manually, the real fix is longer contract terms or a self-serve renewal path, because the countdown economics break down. Monthly terms get no countdown; they get the proactive health system from Day 17's playbook instead.
Enterprise accounts get the full countdown even at longer terms, plus a T-180 executive alignment touch โ because at seven figures, the org chart has usually changed completely since signing, and you need a full half-year to map it.
Running this across a whole book
The flow is per-account, but the operations are portfolio-level. Once a week, every CSM should see a single view: every account in their book sorted by days-to-renewal, with the current countdown stage flagged. Anything within 90 days with no T-90 completed is red. Anything past a checkpoint with the artifact missing is red. This is a ten-minute weekly review that catches every slipped renewal before it becomes a save play.
Automate the stage detection โ renewal dates live in the CRM, the countdown math is trivial โ but keep the meetings human. The flow's job is to make sure the conversations happen at the right time with the right people. The conversations themselves are still the whole game.
Most renewal risk isn't a bad product or a strong competitor. It's an empty calendar where a T-60 should have been. Schedule backward, confirm forward, and the renewals take care of themselves.
Tomorrow: the Eisenhower matrix for inbox zero โ a CSM's daily prioritization ritual, and the ten-minute morning triage that tames the chaos.
