How do you structure a renewal motion — and who should actually own it in 2027?

The $35M analytics company that thought it had a renewal process

Picture a Series C analytics vendor sitting at $35M in ARR, roughly 240 customers, average contract value around $145,000. On paper the company has a renewal process. There is a field in Salesforce called Renewal Date. There is a report that filters opportunities closing in the next quarter. There is a rule that account executives are supposed to log a renewal opportunity 60 days out. Leadership describes this in board decks as "our renewal motion."

What actually happens is this. The AE who closed the logo eighteen months ago is now carrying a $1.4M net-new quota and sitting at 61% attainment in week nine of the quarter. She has eleven renewals in her book expiring in the next 120 days, worth about $1.6M combined. Her comp plan pays her 10% on net-new ACV and 2% on renewal ACV. Do the arithmetic she is doing: a $200,000 new logo pays her $20,000, and a $200,000 renewal pays her $4,000 — and the renewal is, in her mental model, already money the company has. So the renewals sit untouched until roughly Day -35, when her manager's pipeline review flags them red.

At Day -35 she discovers three things. The VP of Analytics who championed the purchase left four months ago, and nobody at the vendor noticed because the CSM's QBR cadence had quietly slipped from quarterly to "when the customer asks." The replacement VP has an existing relationship with a competitor from a prior company. And procurement has instituted a new vendor review process that requires a completed security questionnaire and a legal redline cycle that historically takes 45 days. She has 35 days.

That single account is not the problem. The problem is that this pattern reproduces across the book. In the trailing four quarters this company logged gross revenue retention of 88%. That means it burned roughly $4.2M of ARR just to stand still — which, at their $9M of net-new bookings, meant net new ARR of about $4.8M instead of the $9M the board was modeling against. Their sales efficiency looked broken. Their pipeline coverage looked broken. Their marketing spend looked inefficient. None of those were the actual defect. The defect was that nobody owned the commercial close of the existing book, and the process that was supposed to catch it started 145 days too late.

When the company installed two dedicated Renewal Managers against that same $35M portfolio and moved the forecast trigger from Day -60 to Day -180, GRR moved from 88% to 94% over four quarters and expansion attached at renewal moved from 18% to 31% of renewing accounts. Nothing about the product changed. Nothing about the CSM team changed. What changed was that a specific human with a specific quota looked at every expiring contract six months out and was paid on the outcome.

That is the whole argument for treating the renewal as a designed motion rather than an administrative event. The renewal is a commercial transaction with a buyer, a budget cycle, a procurement gate, a legal review, a competitive alternative, and a signature. It has every characteristic of a new-logo deal except discovery. Treating it as a calendar reminder attached to whoever happens to be nearby is the organizational equivalent of not staffing your largest deal.

How the mechanism actually works: six stages and a confidence gate

The motion is not a linear checklist. It is a forecast gate at Day -180 that routes each account into one of three tracks, and each track has a different cadence, a different owner set, and a different definition of a good outcome.

Day -180: forecast and rating. The owner rates every expiring contract Green, Yellow, or Red. The rating is not vibes. Build it from four observable inputs: product usage trend over the trailing 90 days versus the prior 90 (a drop greater than 20% in weekly active users or consumption volume is a downgrade signal), champion status (is the original economic buyer still employed and still in the same role), support signal (ticket volume more than roughly 3x the account's own baseline, or any unresolved severity-1 in the last 60 days), and commercial posture (has the account been through a budget review, has procurement been reorganized, is there a known competitor evaluation). Green means high adoption plus an engaged champion. Yellow means the account is fine on paper but something structural moved — usually the champion. Red means low adoption, active complaints, or a competitor in flight.

Rate the whole book at -180 even though most of the work happens later. The point of rating early is triage capacity: a Red at -180 has six months of runway for a save motion, and a Red discovered at -45 has almost none.

Day -120: triage and expansion opening. Greens do nothing yet except get an expansion hypothesis attached — which additional SKU, how many seats, what consumption tier. Yellows get executive outreach: a VP-to-VP sync whose only job is to re-establish the value narrative with the new sponsor and find out who now controls the budget line. Reds get save-team activation, meaning the renewal owner, the CSM, and an executive sponsor build a specific plan with a specific lever (scope reduction, pricing concession, extended pilot of a new module, services credit).

Day -90: proposal. Send the commercial proposal. Never one option — always two or three: a flat renewal with a modest uplift, a multi-year commitment at a discount, and an expansion path. One page, not twenty slides. The proposal carries the refreshed business case built on actual outcomes from the current term, not the original pre-sales projection.

Day -60: procurement and legal kickoff. This is the stage most teams underweight. Redlines, security review, vendor questionnaires, insurance certificates, and SOC 2 refreshes routinely consume 30 to 60 days at enterprise accounts and are almost entirely outside the seller's control. Starting legal at -30 is how a customer who fully intends to renew still lapses.

Day -30: signature window. Final negotiation, approval routing, and internal signoff on any nonstandard terms.

Day -7 to 0: close. Signed contract, or the auto-renewal clause fires as a backstop.

Two mechanical details make or break this. First, the "renew by" date on the final contract should be five business days before the actual contract end date, not on it — the gap absorbs signature slippage without triggering a lapse. Second, every stage transition must be a system state, not an email. If the stage lives only in a rep's head, the forecast is fiction and the manager cannot see a stalled deal until it is a lost one.

The numbers that decide the org design

The ownership question resolves against ARR scale, and the breakpoints are reasonably consistent across the benchmark literature from firms like Bessemer, Gainsight, and Pavilion. Treat the figures below as planning ranges, not laws — your contract sizes, sales cycle, and product complexity move them.

Under roughly $30M ARR: the AE owns it, and that is fine. At 100 to 200 customers with an average contract value under $100K, a dedicated Renewal Manager is not ROI-positive. A fully loaded RM costs $130K to $180K in base plus variable; that headcount needs to defend enough ARR to justify itself, and at $25M in ARR with 90% baseline retention, the addressable improvement is a few hundred thousand dollars of saved revenue. What you should do at this stage is fix the process, not the org chart: move the forecast to -180, install the Green/Yellow/Red gate, and put 20% to 30% of AE variable comp on gross retention so the incentive is not actively working against the book.

$30M to $100M ARR: split the role. This is the transition zone and it is where most companies wait too long. The tell is time allocation — by roughly $50M ARR, AEs in an AE-owned model are spending 30% to 40% of their selling time on renewal administration: chasing procurement, routing redlines, rebuilding value decks. That is the most expensive administrative labor in the company. A Renewal Manager running structured playbooks can carry 50 to 80 renewals per quarter in a sub-$100K ACV book. Target 92%+ GRR and an average close cycle under 30 days from proposal to signature. The commonly cited benchmark for the split-team model is a 4 to 7 percentage point GRR advantage over AE-owned renewals; at $60M of ARR that spread is $2.4M to $4.2M of retained revenue against maybe $600K of incremental fully loaded cost for three or four RMs. The math is not close.

Above $100M ARR: a renewal function. At this volume you get a VP of Renewals, a save-team motion with its own playbooks and approval authority, procurement specialists who know the twenty largest customers' contracting processes by name, and expansion-at-renewal as its own quota line rather than a bonus. The common structure is a pod: one Renewal Manager, one CSM, and one solutions architect covering 200 to 300 accounts, anchored on a QBR cadence that doubles as the renewal touchpoint. Pods in this model typically run 95%+ GRR with 15% to 20% expansion attach.

Compensation is the mechanism, not the org chart. A Renewal Manager whose comp is 100% activity-based will produce activity. Put 30% to 50% of variable on a gross retention number with a floor and an accelerator, and put the remainder on expansion ACV closed inside the renewal window. The reason to split it this way is that a pure-GRR plan makes discounting the path of least resistance — an RM protects the logo by giving away 15% and hits quota. Pairing GRR with expansion ACV forces the RM to hold price or trade price for scope, which is the behavior you actually want.

Discount bands should be pre-approved and published. Typical structure: up to 10% to 15% for a standard annual renewal without escalation, up to 20% for a multi-year commitment, anything beyond that requires VP approval and a documented save rationale. Publishing the bands is what removes the 7-day internal approval delay that kills momentum at Day -20.

Price uplift. A 5% to 10% annual uplift on flat renewals is standard in the market and is generally accepted when the value narrative is refreshed with real outcome data. Companies that never take an uplift because "we don't want to rock the boat" leave compounding revenue on the table and, more subtly, train customers to treat pricing as permanently negotiable.

Trade-offs: what you give up with each ownership model

There is no free choice here. Each model trades a real cost for a real benefit, and the failure is usually picking one for the wrong reason — cost avoidance masquerading as org design philosophy.

AE-owned. You get continuity of relationship: the person negotiating the renewal is the person who negotiated the original contract and knows the buying committee's politics. You give up focus and incentive alignment. The AE's comp plan and quota structure will always privilege net-new, and no amount of manager exhortation overrides a comp plan. You also get zero specialization — the AE is learning each customer's procurement process from scratch, every time.

CSM-owned. You get the deepest product and outcome knowledge in the company sitting across from the customer. You give up commercial muscle, and this is a more serious trade than it looks. CSMs are trained and hired to drive adoption and outcomes. Most have never negotiated a redline, never held price under pressure, never navigated a procurement gate with a deadline. Handing them the commercial close creates a specific failure pattern: the customer wants to renew, the CSM has a warm relationship, and the deal dies in legal at Day -20 because nobody had the standing to escalate. There is also a role conflict — a CSM who has to ask for money in Q4 is a different advisor in Q1 than one who does not.

Dedicated Renewal Manager. You get focus, specialization, and a clean quota. You give up relationship continuity and you add headcount cost. You also introduce a handoff, and handoffs leak. The mitigation is that the CSM stays in the account throughout and joins the commercial conversations — the RM owns the close, not the relationship.

Renewal pod. You get all three competencies in the room, which is what genuinely complex enterprise renewals require: technical validation from the SA, relationship and outcome credibility from the CSM, commercial authority from the RM. You give up cost efficiency and add coordination overhead. Below roughly 200 accounts per pod the model is over-resourced.

Where RevOps sits in all of this. RevOps does not own the renewal conversation and should not. What RevOps owns is the machinery: the stage definitions in the CRM, the data model that makes a renewal opportunity a real object with a forecast category rather than a date field, the health score inputs piped in from product analytics and support, the alerting that fires at -180, the discount approval workflow, and the reporting that shows GRR and expansion attach by cohort, by segment, and by owner. If RevOps does not own that layer, the motion degrades into whatever each manager remembers to enforce, and the forecast becomes uninspectable within two quarters.

Expansion mechanics compound inside the window. Three mechanics deserve explicit design. Consumption-based true-up: when the contract has a usage component, the renewal captures the higher run rate without a separate negotiation, which is why consumption-heavy vendors show such strong net retention. Seat bundling: instead of selling ten additional seats in a standalone mid-term motion that requires its own procurement cycle, package renewal plus seats into one signature event and eliminate the friction that kills small expansions. Multi-year with cross-product attach: offer a 10% to 15% discount for a 24- or 36-month commitment, but condition it on attaching a second SKU. That last one is the highest-leverage play available because it extends tenure, raises ARR per account, and improves CAC payback in a single transaction — the discount is bought with commitment, not given away.

Pitfalls that hide churn until it is too late to fix

The late forecast. Setting the renewal forecast at Day -30 instead of Day -180 is the single most common structural defect. By -30 the champion has rotated, the budget has been reallocated, or the competitor's proof of concept is already running. There is no time to triage Yellow into Green and no time at all to mount a save on Red. This failure clusters at $20M to $50M ARR companies still on AE-owned renewals, because the AE only looks when the quarter forces her to.

Auto-renewal treated as a win. A contract that auto-renews because nobody at the customer remembered to cancel is not a retained customer — it is deferred churn with a dashboard that says otherwise. The pattern is well documented in customer success research: accounts that roll over with no human commercial touchpoint churn at materially higher rates at the following cycle, because the next annual finance review catches the line item and cuts it. Track auto-renewals as a separate category in your retention reporting and treat any auto-renewal without a logged commercial conversation as a Yellow for the next cycle regardless of usage.

Discounting as the default save lever. When an RM's only tool is price, every Red becomes a 20% concession. The account is "saved," GRR looks fine, and the company has permanently repriced the customer downward while learning nothing about why the account went Red. Require that every save above the standard band include a documented root cause and a non-price component — scope adjustment, module swap, services engagement, executive sponsorship commitment.

No hard signature deadline. A renewal without a firm date slips 30 to 60 days on average, and every week past Day -60 measurably reduces close probability. Put a "renew by" date on the contract that is five business days before the term end, and put a genuine expiration on any multi-year discount — 7 to 14 days — so the concession has a shape.

Health score with no threshold action. Many teams compute a 0-to-100 health score and then do nothing structural with it. Define thresholds and attach behavior: below 60 requires executive intervention before any proposal goes out; above 80 proceeds on standard terms with an expansion hypothesis attached. A score that does not route work is a decoration.

Ambiguous ownership at the handoff seam. The most expensive ambiguity in post-sales is "the CSM and the AE both sort of own it." Both parties assume the other is on it, and neither escalates. Write down, per segment, who sets the forecast, who sends the proposal, who negotiates price, who routes legal, and who is on the hook for the GRR number. One name per box.

No win-loss discipline on churn. Every lost renewal should generate a structured interview within 30 days, and the findings should be tagged against a fixed taxonomy — product gap, price, champion loss, budget cut, competitor displacement, service failure. Without the taxonomy you accumulate anecdotes instead of a pattern, and the same defect churns the same kind of account four more times before anyone sees it.

Related questions

When should the CSM and the renewal owner split responsibilities?

The moment renewals require procurement navigation and price negotiation — typically once ACV crosses roughly $50K or contracts move to annual legal review. The CSM keeps adoption, outcomes, and expansion discovery; the renewal owner takes the proposal, pricing, redlines, and signature.

What is a healthy gross retention benchmark by segment?

Rough planning ranges: SMB 75% to 85%, mid-market 85% to 92%, enterprise 90% to 95%+ on a gross logo-and-dollar basis. Below the bottom of your segment's band, the problem is usually product fit or onboarding, not renewal execution.

How far in advance should legal and procurement start?

Day -60 for standard renewals, Day -90 for enterprise accounts with security review requirements. Redline cycles, vendor questionnaires, and SOC 2 refreshes routinely take 30 to 60 days and sit outside the seller's control.

Should renewal quota include expansion?

Yes — split it. Roughly 30% to 50% of variable on gross retention and the remainder on expansion ACV closed inside the renewal window. A pure-retention plan makes discounting the cheapest path to quota.

What does RevOps need to instrument first?

A real renewal opportunity object with stages and forecast categories, a -180 alert, health score inputs from product and support, published discount bands with an approval workflow, and GRR plus expansion-attach reporting by cohort and owner.

FAQ

How early should a renewal motion start?

Between 90 and 180 days before contract expiration. Use 180 for enterprise accounts with procurement gates, security reviews, or annual budget cycles that must be caught before the customer's planning window closes. Use 90 as the floor for straightforward, low-complexity renewals. Starting inside 60 days consistently produces rushed decisions, avoidable discounting, and lapses on contracts the customer fully intended to renew.

Who should own renewals at a company under $30M ARR?

The account executive, supported by the CSM for health data and expansion discovery. A dedicated Renewal Manager rarely clears the ROI bar at this scale. The critical fix is not org design but incentive and process: put 20% to 30% of AE variable comp on gross retention and move the forecast trigger to Day -180 so renewals are not discovered in the last month of a quarter.

When does hiring a dedicated Renewal Manager pay for itself?

Generally in the $30M to $100M ARR band, and the practical trigger is time allocation — when AEs are burning 30% or more of their selling time on renewal administration. At that point the RM headcount cost is small relative to both the retained revenue and the recovered net-new capacity. An RM in a sub-$100K ACV book can carry 50 to 80 renewals per quarter with structured playbooks.

Can a customer success manager own the commercial close?

They can, but it is usually the wrong assignment. CSMs are trained for adoption and outcomes, not for holding price under pressure or navigating a redlined contract through procurement on a deadline. The common failure is a renewal the customer wants that stalls in legal because nobody had commercial standing to escalate. It also compromises the advisor relationship the CSM depends on the rest of the year.

Is an auto-renewal a good outcome?

It is a backstop, not a strategy. Contracts that roll over with no human commercial touchpoint churn at meaningfully higher rates at the next cycle, because the customer's next annual software audit catches a line item nobody has defended. Report auto-renewals as a distinct category, and flag any that renewed without a logged commercial conversation as at-risk going into the following term.

What single change improves renewal outcomes fastest?

Moving the forecast gate from Day -30 to Day -180 and forcing a Green/Yellow/Red rating on every expiring contract. It costs no headcount, requires only CRM and alerting work from RevOps, and converts renewals from a reactive scramble into a triaged pipeline where the at-risk accounts get five months of runway instead of four weeks.

Sources

• https://www.bvp.com/atlas/state-of-the-cloud-2024
• https://www.gainsight.com/customer-success/
• https://churnzero.com/blog/
• https://www.saastr.com/
• https://openviewpartners.com/expansion-saas-benchmarks/
• https://www.forentrepreneurs.com/saas-metrics-2/
• https://a16z.com/16-startup-metrics/
• https://www.klipfolio.com/resources/kpi-examples/saas

Related on PULSE

• When should AE vs CSM own the renewal conversation?
• How do you build a renewal motion that scales in 2027?
• What's the core tension between founder pricing authority and CFO/FP&A governance in a growing B2B org?
• How should sales enablement evolve when buying committee members are trained by their own AI coaches?
• What email deliverability guardrails should RevOps own in 2027?