Who should write the renewal brief?

The person who owns the renewal — usually customer success — with sales contributing the original promise and the shape of the ask. One author, several contributors: a brief written by committee tends toward flattery, because each contributor edits out their own exposure.

How far ahead of the renewal should the brief be written?

Early enough that a gap it reveals can still be closed before the conversation — typically weeks rather than days. A brief that discovers under-delivery with no time left to respond documents a problem instead of preventing one.

How is the renewal brief different from the QBR deck?

The deck is shown to the customer; the brief never is. The brief holds the honest deltas, the dated risks, and the walk-away position, while the deck holds what both sides agreed to review together. Preparing the second without the first is a common way to end up presenting to a customer you have not actually thought about.

Should the brief include a renewal probability?

No. A number without a method invites false confidence, and the brief's value is that every line in it can be checked. Dated risk observations let the team apply judgment; an invented percentage replaces judgment with false confidence.

How to write a renewal brief

Guide · Customer Success · 4 min read · last verified 2026-07-27

Reviewed before publication Editorial board Independent commercial review

In shortThe internal one-pager before any renewal: what the customer bought versus what they got, how their market moved since signature, dated risk signals, and the written ask — argued from evidence, never shown to the customer.

A renewal brief is a short internal document — one page is the discipline — prepared before a renewal conversation, stating what the customer bought, what they actually received, how their market has moved since they signed, what risk signals are visible, and what you intend to ask for. It never leaves the building. Its audience is your own team, and its job is to make the renewal case from evidence before anyone is in a room improvising it.

The name borrows from law on purpose. A brief argues a position from evidence, anticipates the other side's strongest objection, and is written expecting to be challenged. A renewal document that only celebrates the relationship is not a brief; it is a greeting card.

What the brief is not

It is not the QBR deck. A QBR is a meeting held with the customer, and running one on market evidence rather than usage charts is its own craft, covered in How to run a QBR with market evidence. The renewal brief is the preparation artifact your side writes before that meeting — or before any renewal touchpoint — so the conversation starts from an agreed internal position instead of three colleagues' differing recollections.

It is also not a forecast. The brief records what has been observed and what will be asked. It makes no promises about the outcome, and it resists the temptation to attach a confidence number to a decision that belongs to another company.

Bought versus got: the honest delta

The first section puts the original promise next to the delivered reality. Pull the promise from the proposal, the contract, and the sales notes — the words used at the time, not the current product narrative. Then record what the customer actually received and adopted.

Deltas run in both directions, and both belong in the brief. Under-delivery goes in because the customer's team is likely to remember it whether or not you write it down, and a renewal conversation that pretends otherwise tends to lose credibility at the exact moment it needs it. Over-delivery goes in because value delivered but never promised is often invisible to the buyer until someone names it — and named, dated, sourced value is the spine of the renewal case. The standard from What is a proof point applies to renewal evidence exactly as it applies to marketing claims: what you can show outranks what you can assert.

A brief showing zero deltas was written to reassure. Reassurance is not preparation.

Their market since signature

The second section answers a question the account team rarely writes down: what has changed in the customer's market since they signed? New entrants in their category, shifts in the questions their own buyers ask, changes in how their competitors describe themselves. The renewal case often rests here rather than in the product, because the argument is not only that the customer got what they paid for but that the conditions that made it worth buying have held — or sharpened.

Honesty pays forward in this section too. If the customer's market moved in a direction that makes your product less central to them, the brief should say so, because the customer has probably noticed, and the ask should be shaped with that in mind. Teams that already track their market on locked questions — the reading loop a platform like Magrios runs — can lift this section from dated readings instead of assembling it from memory.

Risk, written from observation

The third section lists risk signals actually observed, each with a date and a source: a champion who changed roles, support conversations that shifted in tone, procurement appearing earlier than usual, and research behaviour of the kind described in How to spot churn risk in what buyers research. What this section must not contain is padding — invented probabilities, gut-feel scores, or a renewal likelihood produced by no method anyone can name. Write what was seen and when it was seen. A short, dated, factual risk section is worth more than a long speculative one.

The ask

The final section states, in writing, what you want: the term, the scope, any change to the commercial structure, and what you are prepared to trade. It also states the fallback and the walk-away. An ask that exists only in someone's head tends to shrink in the room; writing it down costs a paragraph and tends to hold the position steadier when the conversation gets uncomfortable.

Sourcing without a scramble

A brief assembled the night before is usually thin. The bought-versus-got section pulls from wherever delivered value is already evidenced — a maintained proof library turns this from an archaeology project into a retrieval task. The market section pulls from whatever standing market reading the team runs. The risk section pulls from success notes, support history, and observed research behaviour. If each source exists, the brief takes an afternoon. If the brief is hard to write, that difficulty is itself a finding about the account, and it arrived in time to act on.

The flattering brief fails at its only job

The recurring failure mode is the brief written to make the account team look good: deltas softened, risks omitted, the ask left vague to avoid internal argument. Every softened line moves a surprise from the page — where it is cheap — into the renewal conversation, where it is expensive. A useful test: a good brief should make at least one person on your side slightly uncomfortable. If it reads smoothly to everyone, it is describing the account you wish you had, and the renewal will be negotiated against the account that exists.