A Series B CRO told me last quarter that his team had hit 118% net retention the year before. Six months later it was 94%. Same product, same team, same playbook. What changed was the renewal motion. Or rather, what changed was that one CSM left in November and nobody noticed her 14 renewals were uncovered until February.
That is how most B2B SaaS teams lose 20% of ARR at renewal. Not through bad product. Not through churn that nobody saw coming. Through an operational gap that lives in the 90 days before a contract ends, where the work either gets done or it does not, and where the difference between 92% gross retention and 78% gross retention is whether someone built a process or whether they hoped it would sort itself out.
I have run RevOps inside B2B SaaS companies for over a decade. The renewal motion is the single most undervalued lever in the revenue engine. It costs less to fix than the SDR motion. It pays back faster than a new product line. And almost nobody actually builds it. They build dashboards that track renewal date. They do not build the operating model that actually closes the renewal.
This is the playbook I run when I am hired to fix this.
Average gross retention difference between B2B SaaS teams with a structured 120-day renewal motion and teams that handle renewals 30 days out as a fire drill.
Why the 30-day renewal is already lost
The dominant pattern I see in HubSpot portals and Salesforce orgs is this. A renewal task gets generated 30 days before the contract anniversary. A CSM or an AE picks it up. They email the buyer. The buyer is busy. By day 15 the conversation has not started. By day 5 the buyer says they want to negotiate. By day 0 the contract auto-renews on legacy terms, or it lapses, or someone scrambles to sign a one-year extension at a discount.
The problem is not the CSM. The problem is that 30 days is not a renewal motion. It is a panic.
Real B2B buyers in 2026 are not the same people who signed the original contract. Average tenure of a SaaS champion is now 18 months according to LinkedIn data and our own client analysis. If your contract is two years old, the person who bought your tool has a 65% chance of having moved roles or companies. The person sitting in their seat does not know why the tool was bought. They are getting pressure to cut software spend. They are reading every renewal email with a question: do we actually still need this?
You cannot answer that question in 30 days. The answer needs to be built across the year. The renewal motion is the operational system that builds that answer.
The 120-day renewal motion
A working renewal motion has four phases. Each phase has a different owner, a different output, and a different failure mode. If any one phase is missing, the renewal is at risk.
The discipline is the dates. Most teams know they should do this. They do not actually do it because the renewal date field in their CRM never triggers an action at day 120. It triggers a calendar reminder at day 30. The whole operating model has to shift backwards.
Day 120: risk review
At 120 days out, the CSM owns one job. Score the account on three dimensions and submit the list.
The first dimension is product usage. Pull a 90-day usage trend. Is the account using the product more, the same, or less than it did six months ago? A flat or declining usage trend is the strongest churn predictor we have in our data. We see roughly 3x higher non-renewal rates on flat-or-declining accounts versus accounts with 20% or more usage growth year over year.
The second dimension is champion strength. The person who bought the tool, are they still in seat? Are they still using it personally? Do they have at least one other advocate inside the account? If the answer to any of those is no, the account is at risk even if usage looks fine.
The third dimension is economic signal. Did the company do layoffs in the last quarter? Did the buyer's department budget get cut? Is the company in cost-cutting mode? These signals are public for most B2B SaaS customers. You can pull them from job postings, earnings calls if they are public, LinkedIn headcount data, and BuiltWith for stack consolidation signals.
The CSM produces a 1-to-5 risk score on every account and submits it to RevOps. RevOps reviews the bottom 20% with the CRO. That meeting takes 30 minutes a week. It is the single highest impact meeting in the revenue org.
Day 90: value review
Every account renewing in the next quarter gets a structured business review. Not a generic check-in. A specific review against the value case that was made at the original sale.
What did the buyer say they wanted? What metrics moved? What is the dollar value of the change? If you cannot answer those questions, your CSM does not have a renewal conversation, they have a "please re-sign" conversation. Buyers do not re-sign on hope.
I have seen this go wrong in two ways. The first is that the CSM never knew the original value case because Sales never wrote it down. Fix this at the handoff stage with a one-page document the AE has to write before the deal closes. The second is that the value case was written but never measured. Fix this with quarterly automated value reports that pull data from product analytics and surface dollar-impact numbers.
If the value case is real and the data backs it up, the buyer renews. If the value case was never delivered, you do not have a renewal problem, you have a product problem. Better to know at day 90 than at day 5.
Day 60: commercial conversation
By day 60, the renewal owner opens the commercial discussion. This is where most teams confuse two different conversations and lose money.
The renewal conversation is about extension. Same terms, same product, longer commit. The expansion conversation is about more. More seats, more modules, more usage. The negotiation conversation is about price. Discount, restructure, multi-year terms.
These are three different conversations with three different motions. Trying to run them all in one meeting at day 30 is how you end up giving 25% off and a one-year extension when you could have gotten a flat renewal with an expansion if you had run them as separate motions across 30 days.
Renew first, expand second, discount last.
If you do those in any other order, you will leave money on the table or give away the renewal as part of an expansion negotiation. Buyers who feel the renewal is at risk will use it as a bargaining chip on expansion pricing. Lock the renewal first.
Day 30: close
The last 30 days are paperwork, legal review, and signature. If a deal is still being negotiated at day 30, escalate. The CRO should be on the call. No deal should arrive at day 0 with a surprise.
The metric that matters at this phase is the percentage of renewals signed before the contract end date. World-class B2B SaaS teams run this at 85% or higher. Most teams I audit run at 40% to 55%. That gap is operational, not commercial.
Risk scoring before the renewal
A renewal motion without risk scoring is hope. A risk score does three things. It tells you who to spend time on. It tells you when to escalate. And it tells you what intervention to run.
We use a simple 1-to-5 grid built on three dimensions. Usage trend, champion health, and economic signal. Each dimension scores 1 to 5. The lowest score wins. So an account that has great usage but lost its champion gets a 1 on champion and a 1 overall, even if usage looks fine.
The score gets reviewed weekly in a 30-minute meeting with CS, Sales, and RevOps. Any account that drops a level gets a save plan. The save plan is a one-page doc with three things. The reason for the drop, the specific intervention, and the owner. No save plan, no escalation, no fix.
You can read more about how we build customer health scores in HubSpot and the operating model that sits behind them.
Who actually owns the renewal
The most common mistake I see at Series A and B is unclear renewal ownership. The CSM thinks the AE owns it. The AE thinks the CSM owns it. The CRO thinks somebody owns it. Nobody owns it.
There are three valid models. Pick one. Document it. Train both teams. Do not let the model drift across deal sizes.
CS-owned renewal
The CSM runs the renewal from day 120 to close. The AE is looped in only for expansion or if the deal lands in commercial negotiation. This model works best for SMB and mid-market accounts under $50K ACV where the CSM is the primary relationship.
The advantage is one owner, one relationship. The disadvantage is that CSMs are often uncomfortable with commercial conversations. You need to train them on commercial negotiation, or hire CSMs who can handle it.
AE-owned renewal
The AE owns the renewal and the CSM owns the relationship through the year. This works for enterprise accounts over $100K ACV where the renewal is a structured commercial event with a procurement team on the other side.
The advantage is that AEs are built for commercial work. The disadvantage is that the AE is incentivized to chase new logos and renewal work falls to the bottom of the priority list. The comp plan has to fix this.
Renewal manager
A dedicated renewals function. Not CS, not Sales. Their entire job is to close renewals and process expansions. This is the model HubSpot itself uses on enterprise accounts, and what we see at most Series C and D companies above $50M ARR.
The advantage is focus and discipline. The disadvantage is that you need scale to justify the headcount. Below $15M ARR, you do not have enough renewals to keep a dedicated renewal manager busy. Use CS-owned or AE-owned until you cross that threshold.
The bigger point is that the model is a decision. Make it. Write it down. Train against it. Do not run a hybrid that nobody understands.
Multi-year contracts and the incentive problem
Multi-year contracts are the single highest impact lever on net retention. A two-year contract removes one renewal cycle. A three-year contract removes two. Every renewal cycle removed reduces churn risk by 8 to 12 percentage points based on our internal client data across 40 plus B2B SaaS engagements.
Most teams price multi-year wrong. They offer a flat 10% discount for year two and call it a deal. The buyer takes the discount and you give up 10% on the renewal you were going to get anyway. The deal economics are negative.
The right multi-year offer has three components. A small discount on the headline price, around 5% to 8%. A price lock that protects the buyer from list-price increases. And a one-time co-investment, like onboarding credits or implementation services that you can deliver at low marginal cost. The price lock is the most valuable component to the buyer and the cheapest component to you.
The internal incentive is the other half. Most comp plans pay the renewal owner on the first year of a multi-year deal. So the rep has zero incentive to push for years two and three. Fix the comp plan to pay a multi-year accelerator, even if it is small. A 5% extra commission on the years two and three TCV will change rep behavior overnight.
If you are designing a sales compensation plan from scratch, build the multi-year accelerator in from day one.
The tools you actually need
A renewal motion does not need a new tool category. It needs the existing CRM to do four things.
I have built this exact stack with HubSpot custom objects and n8n workflows for under $300 a month in tooling at three different Series B clients. You do not need Gainsight to run a renewal motion at this stage. You need discipline and the right CRM data model.
If you want help on the HubSpot side specifically, we map the contract object, the risk score property, and the workflow stack as a single 30-day project.
Common failures and how to spot them
Three patterns I see in almost every broken renewal motion.
The first is the renewal date that nobody owns. The contract end date exists in three places. The CRM, the billing system, and somebody's spreadsheet. They do not match. Fix this by making the CRM the source of truth and reconciling against billing weekly.
The second is the silent at-risk account. The CSM knows the account is in trouble but does not flag it because the CSM is comp-ed on retention and a downgrade is on their record. Fix the comp plan to reward early flagging and a structured save attempt, not just gross retention number. Reward telling the truth.
The third is the renewal that auto-renews on legacy pricing. The contract has an auto-renewal clause. The buyer never opens a conversation. The renewal happens but you missed every upsell opportunity and locked in old pricing for another year. Fix this by treating auto-renewals as a process failure, not a success. Every auto-renewal should trigger a post-renewal commercial review.
The math at Series B
Let me put numbers on this. A Series B B2B SaaS company at $15M ARR with 85% gross retention is losing $2.25M a year to churn. Push gross retention to 92% with a real renewal motion and you save $1.05M annually. That alone funds two full-time CSMs and the entire RevOps function with money left over.
The same math at $30M ARR with the same retention improvement is a $2.1M annual saving. At $50M ARR, $3.5M. The renewal motion has higher ROI than any new logo investment at this stage and most teams refuse to staff it.
The board asks why net retention is dropping. The CRO blames product. The CPO blames CS. The CS leader blames the comp plan. Everyone is half right. The real answer is that the renewal motion was never built as a real operating system. It was assembled from CSM goodwill, CRM reminders, and luck.
Want a renewal motion that actually closes?
We build the operating model, the CRM data layer, and the workflow stack in 30 days. Book a free audit and we will show you the three fixes we would make first.
Book an audit →FAQ
What is a renewal motion in B2B SaaS?
A renewal motion is the operating model that runs in the 120 days before a customer contract ends. It includes risk scoring, value review, commercial conversation, and close. It is the difference between renewals happening by accident and renewals happening by design.
When should the renewal motion start?
120 days before contract end for any account over $25K ACV. 90 days for smaller accounts. 30 days is too late for any account size because the buyer does not have time to do a proper value review, run procurement, or negotiate.
Who owns the renewal, CS or Sales?
It depends on contract size. CS owns SMB renewals under $50K ACV. Sales or a renewals manager owns enterprise renewals over $100K ACV. Mid-market is the messy middle. Pick one model, train both teams, and do not run a hybrid.
How much can a renewal motion lift gross retention?
In our client data across 40 plus B2B SaaS engagements, structured renewal motions lift gross retention by 5 to 9 percentage points within two quarters. The lift is highest on accounts in the $25K to $100K ACV range where the previous motion was the least structured.
What CRM setup do I need for renewals?
A custom contract object that holds contract start, end, ACV, multi-year flag, and renewal owner. A risk score property with three dimensions, usage, champion, and economic signal. Workflows that fire at day 120, 90, 60, and 30. Quarterly automated value reports. You can build all of this in HubSpot or Salesforce without a dedicated customer success platform until you cross $25M ARR.