Renewals — Complete Guide
Written by Alex Raymond, founder of AMplify and author of The Growth Department.
A renewal is a re-purchase. The customer decides again whether your product earns its place, and the auto-renewal clause in the contract does not make that decision for them. Josh Abdulla runs renewal risk reviews nine to twelve months ahead at Asana and holds his team to ±3% forecast accuracy. This page covers what a renewal is, when it starts, how to forecast and price it, what to do when it goes at-risk or the customer goes silent, and how renewal risk rolls up into the Risk Register.
Why renewals are the highest-return conversation in Post-Sale
Most renewal systems were built for a world that no longer exists. The model is twenty-five years old: open the renewal opportunity thirty days before the contract expires, send the paperwork, book the number. That model assumes revenue recurs. There is no such thing as recurring revenue. There is only re-earned revenue, and the renewal is the moment the company finds out whether it earned the period it just finished.
The economics are why the renewal deserves to be treated as the most important commercial conversation you have with a customer. A renewed dollar costs about thirteen cents to earn. A new-logo dollar costs more than a dollar, at negative gross margin, with a payback period that runs twenty to thirty months. The profit in a B2B company comes from the customers already in the door, and the renewal is where that profit gets protected or lost. Renewals are also the floor under Net Revenue Retention (NRR): you cannot expand a book you are losing, so the renewal is where the NRR number is first decided.
The team that opens the opportunity thirty days out is reacting to a decision the customer started making months earlier. By then the champion may have left, the value may have faded into the customer's baseline, and a competitor may already be in the room. The tooling taught a generation of teams to treat the renewal as administrative, and the habit is expensive precisely because it feels efficient. A renewal that looks easy thirty days out was won or lost in the eleven months before it. The operating system this work sits inside lives on The Growth Department Method page; the renewal is one of its instruments, governed by the operating standard of Keep, Grow, No Surprises.
What is a renewal?
A renewal is a re-purchase: the moment a customer decides again whether to keep paying for your product, independent of any auto-renewal clause in the contract. The clause is a convenience for billing. The decision still happens in the customer's head, and the customer makes it on the strength of what the relationship has produced and what it looks like it will produce next.
That makes the renewal a forward-looking conversation. The weak version is a recap of the period that just ended: tickets closed, features shipped, hours logged. The customer lived that period and gets no value from hearing it read back. The strong version is a planning conversation about the period ahead, about where the customer is trying to go and what role your product plays in getting them there. A renewal run as a recap is a defense. A renewal run as a plan is a partnership, and partnerships expand while defenses shrink.
The deeper reason to see it this way is that retention comes in two postures. Passive retention waits for the auto-renewal date and hopes. Active retention treats every period as something to be re-earned: chasing down bad news early, hunting for risks, looking for the next problem worth solving. The contract language can be identical in both cases; the energy behind the relationship is completely different, and customers feel that difference long before the renewal date arrives.
The renewal is also the highest-information moment in the relationship. The customer is paying attention, the internal politics are visible, and the competitive landscape is in play. This is the window each year when the customer will tell you what is actually true about the account, which is why an Account Manager who runs the renewal as paperwork throws away the most valuable intelligence they will get all year.
When does the renewal start?
The renewal starts on the first day of the contract. Not ninety days out, not sixty, not thirty. Everything that happens in the relationship between signature and renewal is renewal preparation, whether the team treats it that way or not, and the teams that win renewals are the ones that treat it that way on purpose.
In practice this means the questions you ask all year are the renewal-conversation infrastructure. The voice-of-customer questions in a Quarterly Business Review and the goals captured in account planning are what you draw on when the formal renewal arrives. By that point you should already know the answer to every question the customer might raise. A renewal conversation that contains surprises is a renewal conversation that started too late. The questions also have to match the altitude of the person you ask: strategic questions about three-year direction belong with the executive sponsor, operational questions about the workflow belong with the day-to-day champion, and reversing the two gets you classified as out of touch. The strategic conversation that does most of this work has its own home on the Quarterly Business Review page.
Joanna Hagelberger is the proof of what the long horizon produces. At Vertafore she grew a single account from $50,000 to $10 million in annual revenue. The growth started with one forward-looking question about where the customer wanted to be in five years, and the durability came from the system she ran in the years between renewals rather than any push in the final quarter. The renewal was never the cliff, because the work that earns a renewal had been running the entire time.
How to forecast a renewal
Forecasting a renewal means calling, months ahead, whether it closes, at what number, and with what risk attached, and then being right. The standard worth holding is the one Josh Abdulla set at Asana: ±3% forecast accuracy, quarter after quarter. To see how demanding that is, only about one in five Customer Success organizations forecasts within ±5%. Most teams are guessing and calling it a forecast.
Accuracy comes from reading the leading signals instead of waiting for the lagging ones. Three signals predict an at-risk renewal long before the number turns: engagement dropping, with meetings missed and replies slowing; turnover in the stakeholders on either side; and hesitancy in how the customer talks about the future. Abdulla is blunt about the signal most teams over-rely on. Low usage is a downstream symptom of an upstream failure that is already months old by the time the usage number drops, so a team watching the dashboard is watching the wrong thing.
Each of these signals has a response. Engagement that is dropping calls for a reason to meet that the customer actually values, and stakeholder turnover calls for immediate re-multithreading. When you hear hesitancy, ask the direct question early rather than late: if the decision were today, would it be yes?
No Surprises is the operating discipline underneath the forecast, and it has a part most teams refuse to accept: a positive surprise counts as a miss. A customer who adds an unexpected expansion you did not see coming is proof you were not asking the right questions or tracking the right signals. The executive team wants a number it can plan against, and a surprise in either direction means the system did not see the period coming. John Huber gave an entire episode to the questions that sharpen renewal forecast accuracy, and the through-line is simple: a forecast is only as good as the questions asked early enough to answer it.
How to price the renewal
Pricing a renewal well starts with a fact about psychology: customers forget. They have status quo bias like everyone else. The value you delivered last year gets absorbed into their baseline, and within months they experience it as the way things have always been. The difference between working with you and going without you, which is the exact difference that justifies the price, becomes invisible to the customer precisely because you delivered it well.
So the pricing conversation is won before it opens, by re-showing the value the customer has stopped seeing and by making the cost of leaving concrete. Name what a switch would actually take: the implementation effort, the data migration, the retraining, the integrations that would have to be rebuilt. Status quo bias is your asset at renewal, but only when the customer has internalized what walking away would cost them.
When a customer says there is no budget, treat it as a translation problem. It usually means one of two things: they are not yet convinced of the value, or you are talking to someone without the authority to fund it. Both are addressable, and neither is solved by discounting.
On discounting, hold the line, and never give a discount without something in return. A discount handed over for nothing tells the customer the value was not there at the original price, and it teaches them to ask again next year. Lead with risk reduction instead, which is worth more to most customers than a few points off and costs you less to provide: a smoother renewal, a guaranteed response time, a roadmap commitment. If price has to give, trade it for a multi-year term, expanded scope, a reference, or a case study. A renewal negotiated on interests, on what each side is actually trying to accomplish, produces expansion; a renewal negotiated on positions alone produces a smaller deal and a customer who renews resentfully.
What to do when the renewal is at risk
The first step is to find the risk early enough to act on it. The reason to forecast nine to twelve months out is that a risk surfaced that far ahead is workable, while the same risk surfaced thirty days out is a fire drill. The closest person to the customer should never be the last to know. When a green account churns, the early-warning system failed; the signal was there to be read, and the system did not read it.
When a risk is real, name it in the room. If you hear concern in a meeting, say so on the spot: "you sounded concerned about that a moment ago, can we talk about it?" The instinct to note the concern silently and press on protects the meeting and loses the account. Stakeholder turnover is the most common trigger to act on. Every time someone in your map leaves, the renewal risk goes up, and the right response is to re-multithread before the relationship thins to a single point of failure. Watch the foe column too: most renewal failures trace back to a stakeholder working against you that the team never knew was there.
Procurement deserves its own attention here. The Account Manager who meets procurement for the first time during the renewal gets treated as a line item to be competed down. Build that relationship months ahead, understand how procurement is measured, and you change the renewal from an ambush into a process you helped design.
One rule sits above all the tactics: resolve the renewal before you pitch anything new. An upsell floated while the renewal is wobbling kills both. Get the customer back to solid ground, confirm the renewal is real, and let expansion follow from restored confidence rather than compete with it.
What to do when the customer goes silent before renewal
Silence before a renewal is a signal, and reduced engagement is the most reliable at-risk signal there is. A customer who stops replying, or who sends a junior stand-in to the meeting that used to get the executive, is telling you something. The team that reads silence as a scheduling quirk and waits for the customer to resurface is handing the renewal to whatever is pulling the customer's attention elsewhere.
The response is to widen the relationship before it narrows to nothing. If you only know one or two people at an account, the renewal rests on whether those one or two stay and stay happy, and roughly 60% of contacts are passively open to a job change at any given time. Re-multithread until you are three contacts deep again rather than one. Your champion can raise a concern inside the rooms you are not in, and an executive sponsor paired with the customer's executive gives the relationship a floor that does not depend on one person answering email. A useful question to surface a successor before you need one: if you won the lottery tomorrow and left, who would take this over?
Above all, name the silence directly. A short, candid note to the champion, something as plain as "we have had a hard time connecting ahead of the renewal and I want to make sure nothing has changed on your side," does more than three cheerful follow-ups that pretend everything is fine. A customer who has gone quiet because something is wrong will usually tell you, once you give them the opening to say it.
How renewals feed the Risk Register
The Risk Register is the artifact that turns renewal risk from something an Account Manager holds in their head into something the company can see and work. Per account, it records the risk named plainly, its severity, the observable indicators, and a resolution plan with one named owner and a date. A risk that lives only in someone's memory is not being managed. Once it is on the Register, it becomes a task the organization can act on and a pattern the organization can learn from.
The per-account Registers roll up into a portfolio view sorted by severity, reviewed on a recurring cadence that some teams call a get-to-green meeting. That review should include the Chief Financial Officer or a designate, since the CFO owns the revenue forecast and can free the resources a red account needs. This is the discipline Josh Abdulla installed at Asana as Red Renewals: a non-negotiable biweekly meeting working the renewals nine to twelve months out, each risk categorized, each with a proposed resolution and an owner, with senior leadership in the room as the forcing function. He inherited a churn problem at a company doing $700 million in annual recurring revenue across 170,000 customers, and the Register plus the meeting is what produced the ±3% standard. The mechanics of the Register sit inside the Commitment phase of the Growth Department Method.
The renewal is won in the months before it
Josh Abdulla inherited a churn problem at Asana, a $700 million business with 170,000 customers, and the system he built around it was a calendar. Renewals worked nine to twelve months out, every two weeks, each risk categorized and owned, until the forecast came in within ±3% quarter after quarter. Joanna Hagelberger grew one account two hundredfold to $10 million by running the same kind of long-horizon discipline, so the renewal was never a cliff because the work that earns it had been happening for years. The pattern under both is the same. A renewal is the visible result of a system you either ran or did not run in the eleven months nobody was watching, and the final quarter only reveals which.
Where to start
Pick the one renewal you are most worried about right now. Pull it forward and treat it as live work for this week. Write the real risk down in a single sentence. Count how many people you actually know inside that account, and if the answer is one or two, fix that before anything else. Put the risk on the Register with an owner and a date. Then do the same for the next account, and the one after that, until the system is running and the renewals stop surprising you.
The Growth Department is the post-sale revenue operating standard for B2B companies. Take the ten-minute Post-Sale Stress Test to see where your function stands across Clarity, Commitment, and Cadence. Or download the free audiobook of The Growth Department and read the manifesto.
About the author Alex Raymond is the founder of AMplify and the author of The Growth Department, the operating standard for the function that delivers most of a company's revenue. He spent a decade building Account Management and Customer Success systems with B2B companies before founding AMplify, where he works with Post-Sale leaders on installing the Growth Department Method. He hosts the Account Management Secrets podcast.
