Renewal marketing campaigns

The renewal case usually gets written on a Tuesday, 31 days out, by a CSM who opens a blank deck and starts hunting for usage data. That is the failure. Everything in this playbook is designed so the case is already 80 percent assembled before anyone looks at the calendar, and so the only work left at day 30 is paperwork.

Why the runway is 120 days and not 30

Because of procurement and contract law, not sales technique. Two hard constraints set the date.

The first is the auto renewal notice clause. Most B2B SaaS agreements require written notice of any price change 30 to 90 days before the renewal date. If your pricing committee decides on an uplift at day 45 and your contract says 60, you either eat the increase for another year or you have an awkward conversation that starts with an apology.

The second is the customer’s budget cycle. A buyer at a 500-person company with a calendar fiscal year locks next year’s software budget between October and early December. Arriving in January to discuss a 22 percent uplift means the money does not exist, regardless of whether they want to pay it.

Below 25,000 dollars annual contract value, a 90 day runway is usually enough and the day 120 checkpoint collapses into day 90. Above 100,000 dollars, start at 150 and add a second executive touch.

The four checkpoints, with owner and asset

Each checkpoint has exactly one owner, one asset and one exit test. If the exit test fails, the account is flagged rather than allowed to roll forward silently.

Checkpoint	Owner	Asset	Exit test
Day 120	CSM	Account map and usage pull	Three named contacts confirmed, one is the economic buyer
Day 90	CSM plus AE	Executive business review deck	EBR held with the economic buyer present
Day 60	AE	Price and terms notice, outcome one-pager	Written notice sent, verbal reaction captured
Day 30	AE plus finance	Order form, security and procurement pack	Paperwork in the customer's system, owner named
Day 0	Finance	Signed renewal	Countersigned, or a dated extension in writing

The exit test at day 120 is the one people skip and the one that matters most. Confirming three named contacts including the economic buyer is a five minute check that prevents the single most expensive renewal failure, which is discovering at day 20 that the only person who ever logged in left in June.

The value recap assets and where the data comes from

Value recap assets fail when they are generic. A slide that says your platform drives efficiency could belong to any vendor. A slide that says this account ran 1,840 workflows last quarter, up from 620, saving an estimated 310 hours at their own stated rate of 48 dollars per hour, belongs to one account and is very hard to argue with.

Four assets cover almost every renewal.

• A usage report showing adoption trend by team, seat utilisation, and the three features driving the most activity
• An outcome one-pager mapping the original business case from the purchase to what actually happened, including anything that did not land
• An executive business review deck, 12 slides maximum, built for the economic buyer rather than the daily user
• A roadmap note covering what is shipping in the next two quarters that this specific account asked for

Pull the usage numbers from the same warehouse tables your product analytics run on, not from a screenshot someone took in the admin panel. Building one templated query per report means a CSM populates a renewal kit in under an hour instead of half a day. That template work is a marketing job, and it belongs in the same system as the rest of your SaaS customer marketing programme.

Multithreading so a champion departure does not reset the account

Assume every champion leaves. In B2B software the average tenure of a marketing or operations manager is short enough that a three year contract will almost certainly outlive the person who signed it.

The defence is coverage, and coverage is measurable. Track, per account, how many distinct contacts have done at least one of these in the last two quarters: attended a training session, appeared in an EBR, opened three or more lifecycle emails, logged a support ticket, or spoken at a customer event. Fewer than three is a single-threaded account.

Practical ways to widen coverage without asking your champion for favours.

• Run a quarterly admin training open to anyone in the account, which surfaces users you did not know existed
• Publish a short quarterly account digest addressed to the economic buyer, separate from product release emails
• Offer a peer introduction to a similar customer, which is also how good customer marketing campaign ideas generate references
• Invite a second contact to every EBR by default, and name them in the calendar invite so the champion has to decline actively

When the champion does leave, lead with data rather than history. The new person owes you nothing and did not choose you. What they do care about is whether cancelling creates work for them, and a usage report showing 40 active users across three teams answers that question faster than any relationship narrative.

This is also where onboarding pays off years later. Accounts that went through a structured customer onboarding marketing programme tend to have more trained users on record, which means more people to thread to when the original buyer walks.

Price increases and auto renewal notices without triggering a procurement review

There is a version of the price increase email that reads as routine and a version that reads as a reason to run a competitive review. The difference is mostly sequencing and specificity.

A blunt opinion: uplifts above 10 percent on a flat product almost always trigger a procurement conversation, and uplifts under 5 percent are usually absorbed without comment. If you need more than 10 percent, tie it to something the account can point at, such as added capacity, a new module, or a genuinely higher usage tier. A price rise with no story attached is an invitation to shop around.

The escalation path when a renewal turns red

Red means the exit test failed at a checkpoint, or the three combined signals appeared: usage down more than 25 percent quarter on quarter, primary contact silent for 14 days, and a billing or contract query routed through procurement.

The escalation itself should be boring and fast.

Deciding the discount floor in advance is what stops a red renewal becoming a 40 percent discount negotiated at 9pm on the last day of the quarter. Write the floor at day 1, not day 13.

Managed churn is a legitimate outcome and should be treated as one. Get the exit interview, get the reason coded properly, and feed it into your voice of customer programme. Churn reasons collected at the moment of loss are dramatically more honest than anything a survey gets six months later.

Reporting renewals so the number means something

Report gross revenue retention and net revenue retention separately, always. A net figure of 108 percent can hide a gross figure of 81 percent, which means you are losing a fifth of your revenue base each year and papering over it with expansion. That is a real business, but it is a different one, and the marketing investment it implies is different too.

Segment the gross number by ACV band and by whether an EBR was held. The second cut is the one that gets renewal programmes funded, because the gap between accounts with an EBR and accounts without one is usually large enough to justify the headcount by itself. Present it honestly: EBRs happen more often with healthy accounts, so the gap overstates the causal effect. Say so in the footnote and the number will survive scrutiny.

Expansion belongs in a separate motion with its own timing, covered in the expansion marketing plays playbook, and adoption work that feeds both sits in feature adoption marketing. Keep them separate from the renewal runway. Mixing an upsell into a renewal conversation at day 45 is how a routine renewal becomes a re-evaluation.

For inspiration on how retention assets get used publicly, the patterns in these B2B SaaS marketing examples and the acquisition-side demand generation examples both show customer stories doing double duty.

Next step: pull your renewal list for the next two quarters, mark every account that has fewer than three known contacts, and start the day 120 checkpoint on those accounts this week regardless of where their renewal date actually falls.