In plain English
Auto-renewal (evergreen) clauses extend a contract for another term unless a party gives notice inside a defined window, often 30–90 days before the end date. Startups should match notice length to budget and board cycles, calendar the deadline on day one, and treat "auto-renew + 30-day notice" as a process risk, not a paperwork detail.
Not legal advice. Confirm termination rights with counsel when spend or lock-in is material.
By version90 staff Published Updated How this was made
The clause that renews while you're in a board meeting
Auto-renew is how a "we'll revisit next year" vendor becomes a surprise invoice during fundraising week.
It is also how your own customer contracts keep ARR alive, so this guide cuts both ways. The goal is not "kill every evergreen." The goal is notice windows your calendar can hit.
If the deal history is still SOW_renewal_FINAL(3).docx buried in email, you will miss the window. Guaranteed.
See also: Startup MSA redline checklist · Contract version control: end final v7.
How do auto-renewal clauses work?
Typical pattern:
- Initial term (e.g., 12 months from effective date or go-live).
- Renewal term (same length, or successive 12-month periods).
- Notice window (e.g., at least 30 / 60 / 90 days before the then-current term ends).
- Method of notice (email to a legal@ address, certified mail, in-app, whatever the contract says).
- Sometimes: price uplift on renewal (capped % or "then-current list").
| Term element | Question to answer | Ops trap |
|---|---|---|
| Start date | Signature, Effective Date, or first invoice? | Wrong anniversary math |
| End date | Calendar day vs end of month | Off-by-one notice fails |
| Notice lead time | 30 / 60 / 90 days? | 30 days vs quarterly planning |
| Notice method | Exact address / form? | "We emailed the AE" ≠ notice |
| Auto vs opt-in | Evergreen or explicit renewal order? | Silence renews you |
| Uplift | Cap? Prior written notice? | Silent 15% bump |
Why 30-day notice is tight for startups
Thirty days sounds generous until you map it to reality:
- Finance closes books.
- You need a founder or budget owner.
- Switching vendors requires a migration plan.
- Board or investor update might be required above a spend threshold.
60–90 days is a common ask when renewals hit quarterly planning. If the other side insists on 30, compensate elsewhere: termination for convenience, month-to-month after initial term, or a clear non-renewal reminder obligation.
How to negotiate notice windows (buyer and seller)
When you buy (vendor contracts)
- Prefer no auto-renew + explicit order form for year two, or
- Auto-renew with 60–90 day notice and written reminder.
- Cap renewal uplifts; require advance notice of price changes with an out.
- Align termination for convenience with wind-down / data export needs.
When you sell (customer MSAs)
- Auto-renew can stabilize revenue, just don't hide the window in a footnote.
- Make notice instructions boringly clear (email + portal).
- If customers are startups too, 30-day windows create churn fights and goodwill debt.
- Document renewals in the same system as the MSA, see Word tracked changes negotiation.
Calendar the deadline on signature day
A usable internal process:
- On signature, log initial term end and notice-by date (end date minus notice period, with a buffer).
- Put the notice-by date on finance and ops calendars, not only the AE's phone.
- Attach the notice method checklist (addresses, required form, CC list).
- Thirty days before notice-by, run a keep / replace / renegotiate decision.
- Send notice early enough that delivery disputes don't eat the window.
Missed windows are rarely "legal mysteries." They are version-control and calendar failures.
Price increases at renewal
Watch for:
- "Then-current list price" with no cap
- Uplifts that apply unless you non-renew, creating a hostage dynamic
- Mid-term unilateral increases (different issue; often worse)
Redline cue: Cap increases (e.g., mid-single digits or CPI-like) and require prior written notice with a non-renew path that is operationally hittable.
Redline cues in the .docx
Search: renew, renewal, evergreen, notice, terminate, term.
Confirm:
- Notice period length and whether business or calendar days
- Whether notice must be received or merely sent by the deadline
- Conflict between MSA auto-renew and order form term (order of precedence)
- That the version you're signing is the one that contains the notice language you negotiated
About this page
Who. Written by version90 staff at Latent Ape LLC, the company that builds version90, working with AI tools. We build contract software and run our own contracts through it; we are not a law firm, and nothing here is legal advice.
How. Each piece starts from the review workflow version90 is built around. AI drafts and structures the text; staff edit, fact-check, and rewrite it before it is published, and we update the date shown above whenever the substance changes.
Why. The library exists to give founders and ops teams a shared standard for reviewing contracts without a legal department. If you spot an error, email [email protected] and we will fix the page.