When Should You Start a Renewal Conversation? 90 to 120 Days Is the Baseline

For annual B2B contracts, start renewal planning before the deadline becomes the conversation.

For most annual B2B contracts, a useful baseline is to start renewal planning 90 to 120 days before the contract expires. HubSpot currently recommends that range for annual, multi-year, and enterprise B2B software renewals. Simpler subscription motions may work at 60 to 90 days, while complex enterprise renewals can require closer to 180 days. The point is not to send a commercial renewal email four months early. It is to create enough time to identify risk, confirm stakeholders, prove value, and establish a clear next step.

Quick answers

When should you start a renewal conversation?: For most annual B2B contracts, start renewal planning 90 to 120 days before expiry. HubSpot recommends this range for annual, multi-year, and enterprise software customers; shorter buying cycles may work at 60 to 90 days, while complex enterprise motions can require more time.
What should happen 90 days before renewal?: Confirm the renewal date, review account health and recent customer activity, verify stakeholders and ownership, and make sure there is a dated next step. The 90-day checkpoint is for readiness and risk discovery, not just a reminder email.
Should every customer get the same 90-day cadence?: No. Segment by contract complexity, procurement effort, customer value, and buying cycle. Use 90 to 120 days as a baseline, then extend the window for enterprise or multi-stakeholder renewals and shorten it for simpler transactional subscriptions.
Can HubSpot automate a 120/90/60/30 renewal timeline?: Yes. Date-based workflows can create tasks, notifications, or other actions at defined intervals when a trustworthy renewal date is available. HubSpot Contracts can also show renewal alerts and support renewal workflows.

Why 90 to 120 days is a useful baseline

A renewal is usually decided before the contract end date. Procurement may need time. A budget owner may need approval. A champion may have changed roles. An unresolved support issue may still need to be fixed. If those facts surface with ten days left, the team has very little room to change the outcome.

HubSpot's July 2026 customer-success renewal guidance says annual, multi-year, and enterprise B2B software teams should plan at least 90 to 120 days ahead. It also notes that enterprise processes can move toward 180 days and that less complex models may work closer to 60 days.

Source: HubSpot: Customer success renewals.

A 120/90/60/30-day renewal timeline

120 days: validate the contract end date, customer value, decision-makers, and commercial ownership. For complex accounts, this is where the renewal forecast starts.

90 days: identify risk, confirm who needs to be involved, review recent customer motion, and establish an owned next step.

60 days: move from readiness into a concrete commercial path: scope, proposal, quote, procurement, or remediation plan.

30 days: resolve open blockers and escalate uncertainty. This should not be the first time the renewal is visible.

Earlier does not mean more aggressive

Starting early should make the customer experience less transactional. At 120 or 90 days, a conversation can still focus on outcomes, adoption, unresolved issues, and the customer's next-year priorities. At 10 days, even a good relationship is forced into signatures, deadlines, and procurement.

This is also why a renewal reminder alone is a weak operating model. The useful event is not “the date is getting closer.” It is “the date is getting closer and there is no sufficient next step.” See what renewal-reminder evidence actually supports.

Make the cadence conditional on real follow-up

A healthy account renewing in 75 days with a meeting next week does not need the same treatment as an account renewing in 75 days with no recent customer motion and no owner action. A useful renewal system therefore checks both timing and follow-up.

In HubSpot, that means combining a trustworthy date with the operational evidence that the renewal is actually being worked. If your dates are scattered, start with the renewal tracking setup that fits your portal rather than layering more workflows onto uncertain data.

The rule to use

Use 90 to 120 days as the default planning window for annual B2B renewals, then adjust by complexity. The exact number matters less than having a repeatable checkpoint early enough that a newly discovered problem can still be fixed.