Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

B2B Marketing › B2B Pipeline

Preparing for a Customer's Renewal Review

How to prepare for a business customer's renewal review: work from notice dates, re-map who decides, gather usage and outcomes, flag changes early, record why.
Tutorialintermediate15 min readUpdated

What a renewal review looks like from the customer's side

The guide to expansion and renewal marketing calls renewal a decision made again. In many accounts it stays administrative, but in others the champion who chose the product has moved on, finance has changed how spending is approved, a new leader is reviewing every supplier, or procurement asks for the comparison it skipped the first time. Any of those turns the renewal into an evaluation. That guide reduces marketing's part to two words, evidence and clarity: evidence of value in outcomes the customer recognises, written for someone who never saw the original case, and early, plain notice of anything that changes.

The site also has two tutorials written for the other side of the table. The tutorial on reviewing a marketing tool before renewal and the tutorial on reviewing an agency before renewal walk a buyer through deciding whether to keep a supplier. Both work back from the notice date, not the renewal date, because once the invoice arrives the decision has normally been taken by doing nothing. The tool tutorial reads the decision record from the purchase, measures use and results against the baseline, lists incidents, support problems and the workarounds the team built, and looks at changes to data handling and to the terms; the agency tutorial sets the scope beside the work actually delivered, reads results against the baseline and tests whether the fee model still fits. Both score any alternative on the same criteria and end with a recorded decision: keep as it is, change the size or scope, replace, or stop.

A supplier that knows those questions can have the answers ready before they are asked; one that does not meets them one at a time, from a new approver, with a procurement deadline already set. The table after the steps maps each question to the evidence that answers it.

Not every renewal needs all of it. The full preparation is for significant accounts and for any account where something has moved: a new budget holder, a change in price or packaging, a retired feature, a run of support problems or a champion who has gone quiet.

Before you start

  • The contract for each account. The renewal date, the date by which the customer must give notice, what happens if nobody acts, and anything it says about changes to price or terms. Read the dates from the contract itself; this page states no notice periods, draws no conclusion about contract terms and is not legal advice.
  • The account plan. The expansion guide asks for one plan per significant customer, held in the CRM and read by marketing, customer success and the account manager alike.
  • The record of the first sale. The business case the champion took to finance, the opportunity notes, the late-stage material that was sent, and the success measures agreed at onboarding, with the baseline the customer gave.
  • Usage, outcome and support history from customer success, the product and the support team.
  • The retention definitions the business uses, from the churn and retention metrics guide: customer churn, gross revenue churn and net revenue retention, each with its period and base written down.
  • A list of what changes at the next renewal across the base: price, packaging, terms, data handling and any feature being retired, with the date each takes effect.
  • The consent and source record for every contact at the account, including the many who were added as users and never bought anything themselves.
  • Roles agreed in writing: who prepares the evidence, who speaks to whom, and the one person accountable for each renewal.

The steps

  1. List renewals by notice date

    Build a list of every contract that comes up for renewal and sort it by the date on which the customer must give notice, not by the renewal date. The customer's own review, as the tool and agency tutorials describe it, is worked back from that notice date, so evidence that arrives after it arrives after the decision. Beside each account, record the notice date, the renewal date, what the contract says happens if nobody acts, the owner and the date preparation must start. Count back from the notice date to set that start, allowing for the slowest task on the list, which is usually reaching a new approver or refreshing answers owned by another team. Bring the list to the regular review of the largest accounts that the expansion guide sets up, where renewal risks are already a standing item.

  2. Find the original decision record

    Gather what the customer was told and what it decided the first time: the problem in the buyer's own words, the business case the champion presented, the options the customer compared, the success measures agreed at onboarding and the baseline figures the customer gave for them. The customer's reviewer will start from their own copy of that record, if one exists, and the supplier's copy is what lets the evidence speak the same language. Where the record is thin, reconstruct it from the opportunity notes and the onboarding records, and ask the customer what they recorded when they bought. Note any gap honestly.

  3. Re-map who will decide this time

    Take the buying committee from the first deal and check every name. Is the person still in post, in the same role, with the same say? Who now holds the budget, how does finance approve a renewal of this size, and will procurement, security or legal take part? Customer success and the account manager know part of the answer; the champion, if still there, can usually supply the rest. For each approver, draw a value proposition canvas as the guide to late-stage deal content applies Strategyzer's canvas: every approver has different jobs, pains and gains, so a finance director who inherited the contract needs a different case from the users who rely on the product every day. Where the champion has left, the guide to a customer champion changing jobs deals with the move itself. Record the new map in the account plan, against the account in the CRM.

  4. Gather usage and outcomes with customer success

    Ask customer success for the account's use of the product, broken down by team, site or function where the product records it: licensed users against active ones, the use cases the customer bought it for against the ones that are live, and the trend across the term rather than a single month. Then read outcomes against the baseline from the decision record, in the customer's own measures and from the customer's own figures wherever they can be had, because a reviewer trusts what their own systems show. Be plain about what the evidence supports. If other things changed at the customer during the term, the product's share of any improvement is uncertain, and saying so protects the champion from a question they cannot answer. Where a measure did not move, find out why before the customer asks.

  5. Write the value summary for a reader who never saw the first case

    Turn the evidence into a short summary written for the approver who matters most this time, usually someone who was not in the first decision. It states the problem as the customer described it, what the product has been used for, what changed against the baseline, what the next term would cost and what is planned for it. Follow the logic the late-stage guide sets for a business case kit: built from the buyer's figures, every assumption labelled, editable so that the champion or the account owner at the customer can present it under their own name, and customer outcomes offered as evidence of what happened, not as promises. Write it in the reader's terms, from the canvas drawn for them: a finance reader wants total cost and how the bill changes, an operations reader the outcomes and the effort.

  6. List what went wrong and what was done about it

    The customer's review will list the incidents, outages, support problems and workarounds of the term, and the tool review tutorial counts workarounds among the costs an invoice does not show. Make that list first, with customer success and support: what happened, how long it affected the customer, what was fixed and what is still open. Ask users as well as reading tickets, because quiet workarounds rarely reach a ticket. Present the list alongside the value summary rather than hiding it, with the fixes and any open items owned by named people. Route what users say into the business's voice of the customer programme, so that a complaint raised during renewal preparation reaches the people who can change the product and the loop is closed with the customer afterwards.

  7. Say early what changes at renewal

    Anything that changes at renewal, whether price, packaging, terms, data handling or a feature being retired, should reach the customer early and plainly, never as a surprise on an invoice. The guide to communicating a price change puts contracted accounts first: a conversation from the account manager before any written notice, then a written follow-up, inside what the contract allows for changes. Where a feature is being removed, the guide to retiring a feature sorts customers by how heavily they rely on it, starts with a conversation for those who use it every day, and leaves anything a contract promises to the contract and to legal advice. Keep selling out of the notice. The price change guide leaves open whether a price-change notice is treated as a service message in any particular market, and it points out that a message mixing notice and promotion is handled as marketing for consent and unsubscribe purposes. How the price or the packaging should change, and what to offer in negotiation, belongs to the pricing and packaging guide, not to this tutorial.

  8. Refresh the answers a reviewer will ask for again

    A renewing approver often asks for the same material as a new buyer. The late-stage guide builds that material for new business: the business case kit, a library of security and data-protection answers, each kept current by the person accountable for it, and a procurement pack with company details, standard terms, pricing logic and references. A procurement pack built for new deals can serve the renewal once its dated items are brought up to date. Check every item the account will see for currency: answers past their review date, company details that have changed, terms that differ from what the customer signed. Ask the owners to update their own answers; marketing keeps the structure and the plain language, not the substance. For references, draw on the pool the customer references and advocacy guide keeps: a customer with a similar profile, whose recorded agreement covers the activity asked for, who has not been asked too often. If procurement wants a comparison with other suppliers, supply the facts it needs to score the options on its own criteria, and leave the scoring to the customer.

  9. Agree who contacts whom and keep service and marketing messages apart

    Write the contact plan for the renewal into the account plan. The expansion guide's division usually holds: customer success talks to the users and the champion and the account manager to whoever holds the budget, while marketing reaches the wider organisation only through communications the account team has agreed. Hold back campaigns that would cut across the renewal conversation. Keep the two kinds of message in separate streams. Notices about the contract and the service are service messages. Anything promoting further products or higher tiers counts as marketing even when the reader works for a customer. The expansion guide and the list building and consent guide summarise what the UK regulator's direct marketing guidance says about it: when consent is required, when existing customers may hear about similar products without fresh consent (the arrangement known as the soft opt-in), and the opt-out every marketing message must carry. Check each contact's consent and source record before any promotional message goes out; none of this is legal advice.

  10. Record the outcome and the reason

    When the customer decides, record the outcome against the account: renewed, renewed on changed terms, reduced or lost, with a reason chosen from a coded list, as the expansion guide asks for renewals in the same way as for lost new business. Keep the renewal in its own process; the closed-won workflow tutorial excludes deals created only to record a renewal from the workflow that welcomes a new customer. Then read outcomes across accounts by the cohort of each account's first contract: the measurement guide for business-to-business marketing advises cohorts for new business, and the expansion guide reads existing accounts the same way. Set the outcomes beside customer churn, gross revenue churn and net revenue retention as the churn metrics guide defines them. Add the next term's success measures to the decision record and put the next notice date on the list, so this renewal becomes the start of the next one.

The customer's questions and the evidence that answers them

The customer's review asks a predictable set of questions, whoever runs it. The table pairs each one with the evidence that answers it and the step that prepares it.

The customer's questionThe evidence that answers itUsually prepared byStep
When do we have to decide, and what happens if we do nothing?The contract dates and the renewal listAccount managerList renewals by notice date
Why did we buy this, and what did we expect?The decision record, the original business case and the agreed success measuresAccount manager with marketingFind the original decision record
Who decides now, and what does each of them need?The re-mapped committee and a canvas for each approverAccount manager and customer successRe-map who will decide
Is it used, by whom and for what?Licensed against active users; use cases bought against use cases liveCustomer successGather usage and outcomes
Did it move the measures we cared about?Outcomes against the customer's own baseline, with the uncertainty statedCustomer success with marketingWrite the value summary
What went wrong, and was it fixed?Incidents, support problems, workarounds and what was done about eachCustomer success and supportList what went wrong
What changes if we renew?Price, packaging, terms, data handling and retired features, told earlyAccount manager and product marketingSay early what changes
Are the security and data answers still true?The answer library and data protection terms, reviewed by their ownersSecurity, privacy and legal ownersRefresh the answers
Who else like us uses it?A matched reference from the pool, within what that customer agreedMarketingRefresh the answers
What would the alternatives involve?Facts for the customer's own comparison: pricing logic, what the customer would have to move, referencesAccount manager and marketingRefresh the answers

Three things sit outside the table. Negotiating price and discounts is a pricing decision, covered by the pricing and packaging guide. The tutorial on setting discount rules for sellers covers renewals among the deals its rules can govern. The wider levers that keep customers, from onboarding to service, belong to the customer retention strategy guide. And when renewal losses rise across many accounts rather than one, the diagnosis of a rising customer churn rate checks the definition, the base and the cohorts before anyone looks for a cause.

A veterinary software firm prepares a group's renewal (illustrative)

Illustrative example — not a real result

Cazmuthel Veterinary Software prepares a clinic group's renewal

Cazmuthel Veterinary Software is an invented maker of practice management software for veterinary groups. One customer, a group of 18 clinics, is due to renew in March on a 3-year contract whose notice date falls 90 days earlier, in December. Sorted by renewal date, the group did not appear until the list for the first quarter of next year; sorted by notice date for the first time, it moves into next quarter's list, and preparation starts now, in September.

The marketer, the account manager and the customer success lead pull the original business case from the opportunity notes: the group's operations director wanted fewer missed appointments and faster invoicing, and gave a baseline for both. Re-mapping the committee shows two changes. The operations director is still in post, but a new finance director joined last year, and procurement now asks for a comparison with 2 other suppliers on any contract above £50,000. A 7% price change also takes effect at renewal.

Customer success finds 16 of the 18 clinics active and 212 of 240 licensed users signed in during the last month. Against the group's baseline, missed appointments fell from 9% to 6% of bookings and invoices go out in 2 days rather than 5; the summary notes that the group also rewrote its reminder messages that year. Two outages last spring delayed morning lists at 4 clinics, and both go on the list with their fixes.

Marketing writes a one-page value summary for the finance director: the problem in the group's words, the measures against its baseline, the cost of the next term at the new price, and every assumption labelled. The account manager tells the operations director and the finance director about the price change at a meeting in October, before any letter is sent. The security lead updates 14 answers past their review date, the procurement pack gains current company details, and the account manager gives procurement the pricing logic and what the group would have to move, leaving the comparison with the 2 other suppliers to the group. The reference pool offers a clinic group of similar size whose practice manager agreed to take calls and has not been asked this year. A planned email about a new booking module is held back for the group's contacts until the renewal is settled.

The group renews in February on changed terms: another 3-year term at the new price, with the 2 inactive clinics taken off the licence. The outcome is recorded as renewed on changed terms, with the reason coded as price accepted and scope reduced, and the group goes back on the renewal list under its next notice date, 3 years on, with a success measure for the booking module added to the decision record.

The pipeline section sets this tutorial beside the guides on expansion, late-stage content and measurement that it draws on.

Common mistakes

  • Preparing for the renewal date. Evidence timed for the renewal date arrives after the decision, because the customer's review finishes before its notice date.
  • Assuming the people who bought will decide again. New budget holders, approval rules and procurement turn a renewal into an evaluation; re-map the committee every time.
  • Sending the original business case unchanged. A finance director who inherited the contract needs a summary of what happened, in their terms, not the case that persuaded someone else.
  • Leaving the problems for the customer to raise. Incidents and workarounds named first, with what was done, read very differently from the same list in the customer's review.
  • Claiming every improvement. If other things changed at the customer, say so; an overclaim damages whoever presents it.
  • Announcing a price change in writing first. Contracted accounts hear in a conversation from the account manager, within what the contract says, before any written notice.
  • Wrapping promotion into renewal notices. A notice about the contract is a service message; an upgrade pitch inside it is marketing and needs a contact's consent and an opt-out.
  • Answering from stale material. Lapsed security answers and references undermine the rest of the pack.
  • Recording the outcome without a reason, or as a new win. Coded reasons read by cohort show why renewals are lost; a renewal counted as new business inflates the wrong report.

Frequently asked questions

When should preparation for a customer's renewal start?

Work back from the date by which the customer must give notice under its contract, not from the renewal date, because a customer that reviews its suppliers properly finishes its review before that notice date. Leave enough time for the slowest part of the preparation, which is usually re-mapping who will decide and refreshing answers owned by other teams. The contract sets the dates; this page gives no notice periods and draws no conclusion about contract terms, so questions about them go to whoever handles legal matters.

Who owns renewal preparation: marketing, customer success or the account manager?

All three, with the parts written into one account plan. The account manager usually owns the commercial conversation and the relationship with budget holders, customer success owns usage, outcomes and the users, and marketing owns the value summary, the reusable material reviewers ask for and the plan for messages to the account. Name one person accountable for each renewal, so that a gap between teams is somebody's problem before the notice date rather than after it.

Can we use the renewal to promote our other products?

Keep the two apart. Messages about the customer's contract and the service it already uses are service messages; anything that promotes further products, higher tiers or new offers counts as marketing, customer or not, and electronic marketing rules apply to it. The UK regulator's direct marketing guidance covers when consent is required, when existing customers may be told about similar products and the opt-out every marketing message must carry. Check each contact's consent and source record first; nothing here is legal advice.

Terms used on this page

Frameworks

Where this page is used

Sources

  1. Direct marketing guidance — Information Commissioner's Office (UK)
  2. The Value Proposition Canvas — Strategyzer

Related