Blog

Renewing with proof: the brief that should open every renewal call

Most renewal problems are decided before anyone schedules the renewal call. The customer has already formed a view of whether your product got better for them this year. If that view is vague, the conversation drifts to the one number everyone can see: the price.

This post is about the other way to open that call, with a short, specific record of what improved for that account. It covers why customers leave without warning, what a renewal brief should contain, how to build one by hand, and why the brief works best when it is the last of many updates instead of the first.

Silent churn

Jason Lemkin described the pattern from the buyer's side in a SaaStr post titled "We just left a vendor we've used for 5 years. They don't even know it yet." His company had paid the vendor for more than five years and upgraded along the way. There was no major product failure. Support quality slipped, a competitor offered to run the whole migration, and the team switched in a few weeks. He did not tell the old vendor. His conclusion about complaints is worth keeping in mind:

"The ones that complain probably don't want to leave."

The customers who complain are still talking to you. The ones to worry about have stopped. From the vendor's dashboard, a quiet account and a satisfied account look the same: invoices get paid, usage holds steady, nobody files a ticket. Then the renewal comes up and the answer is no, or the account arrives with a competing quote and a request for a discount.

Silent churn is rarely about one event. It is about a customer whose picture of your product stopped updating. They remember the version they bought, the gaps they hit in the first months, and the support ticket that took too long. They do not know about the fifteen things your team shipped since, because nobody told them in terms that applied to them.

Two ways to open a renewal call

Consider a hypothetical account renewing at $60,000 a year. The account owner can open the call in one of two ways.

The first opening starts with the commercial terms: here is the renewal quote, here is the uplift, is there anything we need to discuss. The customer's only reference point is the number, so the conversation becomes a negotiation about the number. Anything good that happened during the year has to be argued from memory, usually by the vendor, usually defensively.

The second opening starts with the account's year: in March you asked for bulk export and we shipped it, your team now runs the weekly report instead of building it in spreadsheets, and the approval step that slowed your finance group is gone. Then the quote. The price is the same in both calls. The difference is what the customer is weighing it against.

The second call is only possible if someone has the facts ready. That is the job of the renewal brief.

What goes in a renewal brief

A renewal brief is one page, written for a single account, prepared before the renewal conversation starts. It is a working document for the account owner, and a version of it can be shared with the customer. Keep it to the facts that apply to that account:

  • Requests delivered. Things this customer asked for, with the date they asked and the date it shipped. This is the strongest section because the customer can verify it from their own memory.
  • Improvements that touch their workflow. Changes to the features they actually use, described in terms of their process. Skip the release notes for modules they have never opened.
  • Adoption since the last renewal. Features, teams or integrations they started using this term. Name them.
  • Open items. Requests still in progress or declined, with the honest status. Leaving these out does not make them disappear from the customer's mind.
  • What comes next. One or two items on the roadmap that matter to this account, if you can commit to them.

What to leave out: generic product marketing, platform-wide metrics the customer cannot connect to their own work, and anything you cannot back up if they ask.

Building it by hand

A careful CSM can assemble this today. The steps usually look like this:

  • Pull the account's tickets, feature requests and call notes from the CRM and support tool for the past year.
  • Read the changelog or release notes for the same period and mark which items relate to those requests.
  • Ask product analytics, or whoever owns usage data, which features the account adopted and when.
  • Check with the product team on the status of the open requests.
  • Write it up in plain language and cut it to a page.

For one strategic account, this is a few hours of work and usually worth it. The problem is scale. A CSM carrying dozens of accounts, with renewals spread across the year, cannot do this for every account every time. The data lives in four or five systems, the changelog is written for a general audience, and the person who knows which change mattered to which customer is often the engineer who built it. So the brief gets made for the largest renewals and skipped for the rest, and the mid-sized accounts, the ones most likely to leave quietly, renew on price.

Why one QBR deck is not enough

Even a good brief has a limit if it is the first time the customer hears the news. A list of twenty improvements delivered at the renewal call reads as a sales argument, because it arrives at the moment you want something from them. The customer has no way to tell whether any of it mattered, since they never got to try it while it was new.

The same applies to the quarterly business review. A QBR deck compresses three months of changes into one meeting, often with the people who attend QBRs instead of the people who use the product. Much of it is forgotten by the next quarter.

What works better is telling each account about the changes that apply to them as they ship, in a short note from the person they already deal with. "You asked about faster exports in June. That shipped this week, here is how to turn it on." That message does three things a deck cannot. It reaches the person who asked. It gives them time to use the change and form their own opinion. And it creates a record, so by the time the renewal brief arrives, every line in it is something the customer has already seen and, ideally, used.

At that point the brief is a reminder of a year the customer lived through, and the renewal call starts from a shared set of facts. Customers renew on what they know and remember. The job is to make sure they know, all year, and remember when it counts.

Cheerblast drafts those per-account updates as your product team ships, and prepares the renewal brief for each account owner thirty days before the date.

Make your next update pay.

For B2B software sales and customer success teams. Your first pilot is free.