Termination for Cause

What is termination for cause?

Termination for cause is the right to end a contract early because the other side broke it in a serious way. Unlike termination for convenience, you need a reason, and the contract defines what counts. Insolvency (the other side going bankrupt) is often a second trigger.

For a SaaS buyer, it is often the only way out of a prepaid term. Atlassian (section 12.3) and Salesforce (section 11.4) both refund prepaid, unused fees when the customer ends the contract for the vendor's breach.

Why it matters to you

The right works both ways. A vendor can end your contract for your breach, such as unpaid fees or a policy violation, and some vendors add extra triggers. HubSpot (section 4.3) may also end the contract on 30 days' notice for conduct that "may negatively reflect on or affect us."

Leaving for cause also takes time, because of the notice and cure steps below. Plan for that before a failing vendor becomes urgent.

What to check

• Confirm the right is mutual, and list any extra triggers only the vendor has.
• Check whether you get a refund of prepaid fees if you leave for the vendor's breach.
• Note the cure period and how notice must be given.
• Check how long you can export your data after termination, and which duties continue under the survival clause.

Material Breach

Read the full page on Material Breach

In plain terms, a material breach is a serious failure that goes to the heart of the deal, not a small slip. Most SaaS agreements we read let either side terminate only for a material breach, not for every breach.

The contract rarely defines the word, so it often comes down to facts and state law. Clear examples are a vendor that stops delivering the service, or a customer that stops paying. Less clear examples are repeated outages under the SLA or a missed security promise.

You can make it clearer. Ask the vendor to list specific failures that count as material, such as missing the uptime target in several months or failing to report a data breach in time. That turns an argument into a checklist.

Cure Period

Read the full page on Cure Period

A cure period is the time the breaching side gets to fix the problem after receiving notice. If it fixes the breach in time, the contract continues. If not, the other side may terminate.

Thirty days is common in the agreements we read. Salesforce, Atlassian, HubSpot and AWS all use 30 days. Zoom uses 30 business days, which is about six weeks.

The steps usually run like this:

1. You send written notice describing the breach, using the method the contract requires.
2. The cure period starts when the vendor receives it.
3. If the breach is not fixed in time, you send notice that you are terminating.

Keep copies of every notice and reply. If the vendor disputes the breach later, your record of dates is what shows the cure period ran out.

How Venpo helps

Venpo watches your vendors' terms and emails you when termination triggers, cure periods or refund rules change, with a plain-English note on what it means. The change history keeps the wording you can rely on.