Your champion has to sell you again every year
Somebody inside each of your customer accounts went out on a limb for you. They ran the evaluation, wrote the business case, sat through procurement and told their boss this tool would pay for itself. That person is your champion, and the sale they made on your behalf does not stay made.
Every budget cycle, every renewal and every time finance looks for savings, your champion has to make the case again. Their boss asks what the team got for the money. Finance asks why this line item grew. A new VP asks why they shouldn't consolidate onto a platform they already pay for. Each of those conversations is a sales call where you are absent and your champion is the rep.
Most vendors leave them to run that call with nothing in hand.
What the research says about renewal decisions
Gartner surveyed 1,503 people involved in decisions to renew or expand technology subscriptions and found that 60 percent of them regret nearly every purchase they make. The analysts attributed that regret mostly to distributed buying teams, poor communication and conflicting objectives inside the customer, rather than to the products themselves.
That is the environment your champion walks into at renewal. Several people with different goals, a default mood of doubt, and little shared memory of why the purchase made sense. Gartner's own recommendations include giving buyers material that builds confidence and helping teams build business cases together. In plain terms: arm the person who has to argue for you.
Why the QBR is not enough
The quarterly business review is where most vendors try to deliver proof. It has three problems as a tool for your champion.
It happens four times a year at best, and budget questions don't wait for it. The deck is built for a meeting, so it doesn't survive being forwarded without someone to narrate it. And it usually describes your product, with feature slides and roadmap teasers, when your champion needs something about their team.
Between QBRs, what does the champion get? Release notes written for everyone, a monthly newsletter, maybe an in-app banner. None of it answers the question their boss actually asked, which is some version of "what did we get out of this?"
What forwardable proof looks like
A useful test: could your champion forward this message to their manager with one line on top, such as "FYI, worth a look", and have it make sense with no other context? If the answer is yes, it is forwardable proof. If they would need to rewrite it, explain it or attach a screenshot, it isn't.
Messages that pass that test tend to share a few traits.
- Short. A few sentences. Nobody forwards a long email, and nobody reads one that was forwarded to them.
- About their team. The subject is what changed for the customer's people, not what your engineers built.
- In their terms. Use the names their team uses for their own workflows, reports and roles, not your internal feature names.
- Anchored in their numbers where you have them. "Your team ran 340 reconciliations last month" is proof. "Customers love our reconciliation engine" is marketing.
- From a person they know. A note from their own CSM or account rep carries more weight than a message from a no-reply address.
Here is a hypothetical example. A CSM writes to the operations lead at an account:
Subject: Month-end close for your AP team just got shorter
Hi Dana, we shipped a change last week that lets your AP team approve matched invoices in bulk instead of one at a time. Based on last month's volume, that would have saved your team roughly a day at close. It's already on for your account. Happy to walk Marcus through it if useful.
Dana can forward that to her CFO without touching it. The subject line says what happened in her terms. The first sentence explains the change. The second sentence attaches it to her team's own volume. Nothing in it requires knowing your product.
Writing for the forward
When you write to a champion, assume the real reader is one step further away. A few habits help.
Put the outcome in the subject line. In a forwarded email, the subject is often the only thing the second reader sees before deciding whether to open it. "Product update: October" gets ignored. "Your support queue now routes refunds automatically" gets opened.
Make the first sentence carry the whole message. If the boss reads only one sentence, it should still tell them what changed and why it matters to their team.
Drop the jargon. Internal feature names, acronyms and version numbers mean nothing to someone who has never logged in. Describe what people can now do.
Leave out the pitch. A forwarded message that ends with an upsell makes your champion look like they are passing along an ad. Keep it useful and stop.
Don't let the champion be the only one who knows
The weakest position in any account is a single relationship. If your champion is the only person who understands what your product does for the company, their job change, reorg or bad quarter becomes your churn event.
The fix is to reach the other roles directly, each with what matters to them.
- The admin who configures the product wants to know about settings, permissions and anything that changes how their users work.
- Finance wants to know about cost, consolidation and anything that affects the invoice or the value per seat.
- End users want to know what got easier in their day, ideally right when it matters to them.
Each of these people will be in the room, or in the email thread, when renewal comes up. If they each already know one or two concrete things your product did for them this year, your champion is no longer defending you alone. They are summarizing what everyone already saw.
This also helps your champion personally. When the admin and the finance contact have heard good news directly from your team, the champion's original decision looks better to everyone around them. That's worth more to them than any QBR slide.
Making this work at scale
The hard part is volume. A CSM with sixty accounts can't read every release note, figure out which change matters to which account and which role, and write a personal note for each one. So it doesn't happen, and the champion goes another quarter without ammunition.
This is the problem we call value distribution: getting each change you ship to the specific people it helps, in words they can use. Cheerblast reads what your product team changed, works out which accounts and roles each change matters to, and drafts a short note from the right rep or CSM. A person reviews and approves every message before it goes out, so the relationship stays with your team.
Your champion will make your case again next year whether you help or not. It's better if they walk in with a folder of short, specific messages about their own team.
If you want to see what that looks like for your accounts, take a look at Cheerblast.