Skip to content
Back to blog
contracts

Auto-renewal traps: how to spot evergreen clauses in your MSP contracts

Dylan Conkle6 min read

An evergreen clause is the line in a contract that renews it automatically unless you give notice to cancel, usually 30, 60, or 90 days before the current term ends. Miss that window and you're locked in for another full term, often at a higher price. If you run an MSP, you're on both sides of this: your vendors use evergreen terms to keep billing you, and your own client MSAs probably use them to protect your recurring revenue. Both matter, and they fail in different ways.

This is general information, not legal advice. Use it to know what to look for and what to ask your own attorney about your specific contracts.

What an evergreen clause actually looks like

You're hunting for language in the term or renewal section. It usually reads something like this:

"This Agreement shall automatically renew for successive twelve (12) month terms unless either party provides written notice of non-renewal at least ninety (90) days prior to the end of the then-current term."

Three things in that sentence decide how much trouble it can cause:

  • The renewal length. A one-month auto-renew is easy to exit. A twelve-month one means a missed deadline costs you a full year.
  • The notice window. Ninety days before term end is common and easy to blow past. Some vendors go to 120.
  • The notice method. "Written notice" sometimes means certified mail to a specific address, not an email to your account rep. If the clause names a method, that's the only method that counts.

Search your PDFs for the words "automatically renew," "successive," "evergreen," "non-renewal," and "then-current term." Those five terms will surface almost every one of these clauses.

The vendor side: where evergreen clauses cost you money

Your tool stack is full of these. RMM, PSA, backup, EDR, email security, licensing agreements. Most run on annual terms with auto-renewal and a notice window measured in months, not days.

Here's the pattern that burns MSPs. You sign a three-year deal at a promotional rate. Year one is $2,400 a month. The contract says it renews for another year unless you cancel 90 days out, and the renewal rate is "then-current list pricing." When it rolls over, you're now at $3,100 a month with no discount, and you found out on the invoice.

What to look for in a vendor agreement:

  • The renewal price. Does it hold your rate, cap the increase (say 5% a year), or reset to list price? A capped increase is worth negotiating for before you sign.
  • The notice deadline, on your calendar. If cancellation requires 90 days notice on a term ending December 31, your real decision date is October 2. Not January 1.
  • How you're allowed to cancel. Email, portal ticket, or certified letter. Do it the way the contract says, and keep the confirmation.
  • Minimum seat or license commitments. Some agreements auto-renew the whole quantity even if you've lost the client those licenses were for.

I've watched MSPs pay for a full extra year of a backup platform they'd already migrated off, because nobody sent the non-renewal notice in time. The software worked fine. The calendar didn't.

The client side: evergreen clauses that protect (and trap) you

Now flip it. Your client MSAs almost certainly auto-renew, and that's usually good for you. Recurring revenue that doesn't require a re-signature every year is the point of the model.

The trap on this side is different. It shows up when a client wants out and you find the clause doesn't actually hold them, or when it holds them so tightly it becomes a fight you don't want.

Things worth checking in your own client contracts:

  • Does the auto-renewal survive a change in ownership? If your client gets acquired, does the MSA carry to the new owner, or does the assignment clause let them walk? Read those two clauses together.
  • Is the notice window symmetric? If you require 90 days from the client but only owe them 30, that's fine until a court or a state consumer statute looks at it. Some states regulate auto-renewal terms tightly, especially for smaller business customers. Ask your lawyer whether your renewal clause is enforceable where your clients are.
  • Does the renewal reset the price or the term commitment? If your MSA renews at the same rate every year, you're absorbing your own cost increases. Building a modest annual escalator (tied to CPI or a flat percentage) into the renewal keeps you from eroding margin on a client who never leaves.
  • What happens between the notice date and the term end? If a client gives notice on day 89, are they still on the hook for the remaining term, or can they stop paying immediately? Spell that out.

A clean client renewal clause does two jobs: it keeps good clients on autopilot, and it gives you a defined, defensible off-ramp when a relationship ends. If yours only does the first job, that's a gap to raise with counsel.

How to spot the evergreen clauses in your vendor and client contracts

Do this as a one-time sweep, then keep it current.

  1. Pull every active contract into one place. Vendor agreements, client MSAs, SLAs, and any order forms. Order forms matter because the renewal terms often live there, not in the master agreement.
  2. Find the term and renewal section in each one. That's where the evergreen language lives. Note the renewal length and the notice window.
  3. Calculate the real deadline for each. Term end date minus the notice window equals your decision date. Write that date down, not the term end date. The decision date is the one that can hurt you.
  4. Flag the renewal price mechanism. Fixed, capped, or reset to list. Reset-to-list contracts are the ones to renegotiate first.
  5. Set reminders 30 days before each decision date. Not the deadline itself. You want time to actually decide, talk to the vendor, or send notice properly.

Doing this in a spreadsheet works until you have thirty contracts and a column of dates nobody checks. The reason auto-renewals bite is that the deadline is quiet and the person who signed the deal may be long gone. A contract system that stores the renewal terms and pushes an alert before the decision date turns a "we forgot" problem into a "we chose" problem.

Two habits that prevent most auto-renewal surprises

Track the decision date, not the renewal date. Every alert should fire before your notice window closes, with enough runway to act. A 90-day notice window means your reminder belongs at 120 days out, not 90.

Read the renewal price before you sign, not when you renew. The single biggest evergreen cost isn't the lock-in, it's the silent price jump baked into "then-current pricing." Negotiate a cap on the way in. It's a normal ask, and most vendors will agree to a 3% to 7% annual cap if you raise it before signing.

Evergreen clauses aren't the enemy. They keep your recurring revenue steady and save everyone a yearly paperwork drill. The damage comes from not knowing the terms and missing the window. Once you can see every renewal date and every price mechanism in one view, these stop being traps and go back to being what they're supposed to be: routine.

Frequently asked questions

It's a term that renews the contract automatically for another period unless one party gives notice to cancel, usually 30, 60, or 90 days before the current term ends. If nobody sends notice in time, the contract rolls over for another full term.

It varies by contract, but 60 and 90 days before the term end are common, and some vendors require 120. The exact window and the required notice method are written in the term or renewal section. Check each contract individually rather than assuming a standard.

Often yes, but several states regulate auto-renewal terms, especially notice and disclosure requirements. Whether yours holds up depends on the language and where your clients are located, so confirm with your own attorney rather than assuming.

Search each document for phrases like 'automatically renew,' 'successive,' 'then-current term,' and 'non-renewal.' Those surface almost every auto-renewal clause. Then note the renewal length, the notice window, and the renewal price mechanism for each one.

Put these contracts to work in XClause.

Build MSAs and SOWs with managed units, send legally binding e-signatures, and track every renewal in one platform built for MSPs.

Free trialCancel anytimeNo long-term contract