When Should a SaaS Start Renewal Outreach Before an Annual Contract Ends?

A SaaS should start renewal outreach about 110 days before an annual contract ends for a mid-market account, 65 days for deals under $15K ACV and 180 days for deals over $100K. Those figures come from counting back from the customer’s notice date, not the end date, then subtracting their procurement window and a 30-day rescue buffer.

At a glance:

• The formula: latest first-touch date = contract end date minus the customer’s notice clause minus the customer’s procurement window.
• The recommended start: the latest first-touch date minus a 30-day rescue buffer, giving 65, 110 and 180 days out by ACV band.
• The real deadline: the notice date in an auto-renewing contract, which buyer-side guides put at 30 to 90 days before expiry.

Rules of thumb (the first three are sourced inline; the last is arithmetic from the Renewal Backward Calendar below):

• Beat the buyer’s review: Zylo tells software buyers to decide whether to renew at all 120 days before the renewal date, so a first touch after day 120 often lands after that decision.
• Count to the notice date: Planhat says that for auto-renewing contracts you should “work back from the notice date instead of the end date”.
• Plan annual renewals 90 to 120 days ahead: that is the window HubSpot’s customer success guide gives for annual and enterprise B2B software contracts.
• A 90-day notice clause plus a 60-day procurement window means the enterprise conversation must open 150 days before the end date at the latest.

When should a SaaS start the renewal conversation for each contract size?

SaaS renewal outreach should start 65 days out for contracts under $15K ACV, 110 days for $15K to $100K, and 180 days for anything above $100K.

The spread is wide because two inputs grow with deal size. Larger customers sign longer notice clauses, and larger renewals pass through more of the buyer’s procurement machinery: security questionnaires, legal review of changed terms, budget sign-off and a new purchase order.

The bands line up with the published guidance. HubSpot puts annual and enterprise B2B planning at 90 to 120 days, says enterprise software “could be closer to 180 days” and says more transactional sales models “might be able to plan closer to 60 days out”; Planhat calls 90 days “a common starting point for annual enterprise contracts”. Each band here is derived from inputs you can check against the customer’s contract.

The first touch is a value review, not a renewal pitch: what the customer bought the product to do, what changed in usage, and who owns the tool now.

FAQ

When should I start the SaaS renewal conversation?

Start with a value review 65 days before the end date for contracts under $15K ACV, 110 days for $15K to $100K and 180 days above $100K. Those are the latest first-touch dates plus a 30-day buffer.

How many days before an annual contract ends do customer success teams plan renewals?

HubSpot’s customer success renewals guide says annual and enterprise B2B software teams should plan at least 90 to 120 days in advance, and that enterprise software could be closer to 180 days.

What notice period do SaaS auto-renewal clauses use?

CloudNuro’s buyer guide says auto-renewal clauses require written notice 30 to 90 days before expiration. Check each customer’s order form, because the clause sets your deadline.

What is the latest first-touch date for a renewal?

It is the contract end date minus the notice clause minus the customer’s procurement window. On this page’s assumptions that is 35, 80 or 150 days before the end date by ACV band.

What if the customer has already given notice?

Treat it as a save conversation, not a renewal. Planhat notes that notice is not always final, and the response that works is diagnostic: find out what changed before offering anything.

Why is the notice date, not the end date, the real renewal deadline?

The notice date is the real renewal deadline because an auto-renewing SaaS contract lets the customer cancel only until that date, which sits 30 to 90 days before expiry.

CloudNuro’s renewal guide for software buyers (updated 27 February 2026) says auto-renewal clauses extend the contract “unless you provide written notice 30-90 days before expiration”, and advises buyers to keep a renewal calendar with alerts at 120, 90, 60 and 30 days. A vendor working to the end date is working to a date the customer stopped caring about months earlier.

The notice date cuts both ways. If the customer gives notice, the vendor is now running a save campaign, not a renewal. If the customer stays silent, the contract rolls over, and Planhat notes that “a silent renewal tells you less than an active one”: nobody learned whether the customer was happy, so the risk often reappears a term later, bigger. Either way, the work has to be finished before the notice date, which is why the Renewal Backward Calendar subtracts it first.

If your contracts do not auto-renew, use the last date the customer can raise a purchase order before the end date; the arithmetic is the same.

The Renewal Backward Calendar: latest first-touch dates by ACV band

The Renewal Backward Calendar sets the latest first-touch date as the contract end date minus the notice clause minus the procurement window, then adds a 30-day rescue buffer.

Where each input comes from:

• Notice clause: labelled assumptions of 30, 60 and 90 days, chosen from the 30 to 90 day range in CloudNuro’s buyer guide. Replace them with each customer’s signed clause.
• Procurement window: labelled assumptions of 5, 20 and 60 days: a card payment or simple purchase order for small deals, a short security and legal pass mid-market, and a full security review, legal redlines and budget approval for enterprise. We found no credible public benchmark for renewal procurement time by deal size, so ask each customer for their procurement lead time and use theirs.
• Rescue buffer: a labelled 30-day assumption, the time to fix one problem the first touch uncovers, such as a departed champion.

The recommended starts of 65, 110 and 180 days line up with the published 90 to 120 day and “closer to 180 days” guidance, and show why one company-wide rule fails: a 90-day rule is 25 days too early for the smallest band and 90 days too late for the largest. Weekend dates move to the previous business day.

Today is 11 November 2026. For an enterprise contract ending 31 March 2027, both the recommended first touch (2 October) and the latest first touch (30 October) have passed, so that renewal needs the quote and the procurement track opened this week, in parallel, not in sequence. See how long SaaS procurement takes for running those tracks side by side.

Touch-by-touch renewal schedule by ACV band

A SaaS renewal schedule needs five or six dated touches between the value review and the new term, each anchored to a day count before the contract end date.

Touches 1 and 3 are the fixed points: touch 1 is the recommended first touch and touch 3 is the latest first-touch date from the calendar, because procurement cannot start before a quote exists. Touch 2 (15 days after touch 1) and touch 4 (mid-procurement) are assumptions. The intent question is adapted from the “renewal pulse check” a former CSM describes in HubSpot’s guide.

A missed touch compresses the next ones; it never moves the notice date.

Price changes belong at touch 1 or 2, not touch 3. A rise first seen in the quote leaves 35 to 150 days to absorb it, often too little for a budget set months ago. Moving customers to annual billing, covered in how to move SaaS customers to annual plans, is a separate decision with its own timing.

What makes a SaaS renewal timeline slip?

SaaS renewal timelines slip most often at procurement and legal, which this page assumes take up to 60 days on enterprise deals, and at a champion change nobody spotted before the quote.

• Procurement and legal. Security questionnaires, legal redlines on changed terms and a new purchase order all have to fit inside the procurement window; when they run one after another instead of in parallel, the window overruns.
• A new owner. The person who bought the product leaves, and the new owner treats the renewal as a fresh purchase. Touch 1 exists to find this early.
• A price rise announced late. CloudNuro warns buyers that missing an opt-out window locks them into another term, “often at increased prices”; buyers who expect a rise prepare to push back on it, and the push-back takes time.

When the notice has already been given, the account is a save or a win-back rather than a renewal; the playbook for that is in how to win back churned SaaS customers.

What does running the renewal calendar yourself cost?

Running the Renewal Backward Calendar yourself costs a CRM field per contract, an owner for every renewal, and five or six dated touches per customer each year.

The setup is light: add the notice clause and the procurement lead time as fields on each contract record, compute the two dates with a formula, and trigger tasks at the six touch dates. A customer success leader quoted in HubSpot’s guide describes automated “120-day renewal notices” as a courtesy to customers. The skill sits in touches 1 and 2 (reading usage data, frank conversations) and touch 4 (persistence).

The load scales with the number of customers, not revenue. A book of 400 SMB customers is 2,000 touches a year at five each, most of them for small renewals that cannot carry a full-time CSM’s cost. At that point teams often automate the early touches or hand off the meeting booking, keeping CSMs for the value review and negotiation.

LeadsNow is one option for that booking step: it books calls using AI calling, SMS and DM follow-up, and its headline record is 50,769+ AI-booked sales appointments since 2017 and 1M+ leads generated. It bills a revenue share, a fee per appointment, or a mix of both, and no-shows aren’t charged; see AI appointment setting. Other renewal and retention calling providers are compared on the best renewal and retention calling companies, and the wider SaaS pipeline picture is on the SaaS lead generation hub. A team with a small book of large accounts should keep renewals entirely in-house: the calendar is the method, not the outsourcing.

Sources

• HubSpot, Customer success renewals: 8 top strategies that prevent churn (updated 31 July 2026)
• Planhat, Customer renewals: process, renewal rate and forecasting
• Zylo, SaaS renewal best practices (updated 5 February 2026)
• CloudNuro, SaaS Renewal Process: Contract Negotiation and Timeline Guide (updated 27 February 2026)