Free contract exit plan
Stuck in a contract? Find your way out.
Upload the contract — GitLaw finds your exit routes (termination clause, notice window, auto-renewal, cure periods) and drafts the letter that uses them. US & UK. Free.
5.0 out of 5 on Google
Read reviewsAs featured in








The exit plan
Four ways out — in the right order.
Terminate wrongly and you can put yourself in breach. The ladder starts safe — review, negotiate — and only escalates when they've left you no choice.
Previewing for a software services agreement with [Counterparty Name] · 60 days' notice
Contract exit review — software services agreement What GitLaw found in your contract: ✓ Termination clause — either party may terminate on 60 days' written notice (cl. 12.1) ⚠ Auto-renewal — renews for 12 months unless notice lands at least 60 days' before the renewal date (cl. 2.4) ✓ Cure period — 14 days to remedy a material breach after written notice (cl. 12.3) ✓ Notice method — written notice by post or email to the registered address (cl. 15) Your exit routes, safest first: 1. Negotiated exit — propose a mutual termination now (step 2) 2. Clean termination — serve 60 days' notice under cl. 12.1 (step 3) 3. Breach route — only if they aren't delivering: notice of breach, cure period, then termination for cause (step 4)
15 September 2026
To: The Directors [Counterparty Name]
Re: software services agreement — proposal to end our agreement early
Dear Sirs, We have valued working with you, but our requirements have changed and we would like to bring the software services agreement between our companies to an early, orderly close. Rather than each of us sitting out the notice period, we propose a mutual termination on the following terms: the agreement ends on a date we agree together; we pay for all work properly performed to that date; both parties waive further claims under the agreement; and we complete a short handover of materials and access. We would rather agree this together than serve formal notice, and we are open to discussing the details. Please let us know within 14 days whether you agree in principle, and we will send a short mutual termination agreement for signature.
15 September 2026
To: The Directors [Counterparty Name]
Re: Notice of termination — software services agreement
Dear Sirs, We refer to the software services agreement between Example Company and [Counterparty Name], and to the clause permitting either party to terminate on 60 days' written notice. This letter is our formal notice of termination under that clause. The notice period runs from the date of this letter, and the agreement will end on its expiry. We will continue to perform our obligations during the notice period and expect the same of you, including any handover obligations. Please acknowledge receipt of this notice in writing and confirm the termination date. For the avoidance of doubt, this notice is served by the method the agreement requires. This notice is given without prejudice to our accrued rights and remedies under the agreement.
15 September 2026
To: The Directors [Counterparty Name]
Re: Notice of material breach — software services agreement
Dear Sirs, We write regarding the software services agreement between our companies. You are in material breach of that agreement: the services it requires have not been delivered as promised, despite our written requests. You have 14 days from receipt of this notice to remedy the breach in full. If it is not remedied within that period, we will terminate the agreement for cause with immediate effect and pursue the remedies available to us, including recovery of sums paid for services not delivered and the cost of replacing them. We would prefer to see the agreement performed. If you dispute what is set out above, or wish to propose how you will put it right, reply in writing within the same 14 days. This notice is given without prejudice to any other rights or remedies, all of which are expressly reserved.
Not another template site
Meet GitLaw — your legal AI agent
Template sites hand you a blank termination letter and wish you luck with your own contract. GitLaw reads your contract first — and drafts from what it actually says.
Built for your legal work,
with practicing lawyers
Trained on 5,500+ clauses and specialist areas of law. Built with a standards committee of independent lawyers.



Trusted by 5,000+ businesses


Frequently asked questions
Sometimes — but not just because you changed your mind. Once signed, a contract binds unless you have an exit: a termination clause, a mutual agreement, a serious breach by the other side, or (more rarely) grounds like misrepresentation or impossibility. Step one is always the same: read what your contract actually allows — that's the exit review.
Almost never — that's the biggest myth on this topic. The US FTC Cooling-Off Rule covers door-to-door and certain off-premises consumer sales, and the UK's 14-day right under the Consumer Contracts Regulations 2013 applies to consumers. A business signing a B2B contract gets no cooling-off period by default.
That's a breach, not an exit. The other side can sue for the sums due — often the whole remaining term — plus any late fees or recovery costs the contract provides. Walking away is usually the most expensive route out; serving proper notice is almost always cheaper.
No. Where an ongoing contract is silent on termination, both US and English law generally allow termination on reasonable notice. What counts as reasonable depends on the relationship's length and how much the other side relies on it — GitLaw drafts the notice conservatively so you don't under-serve.
Maybe not. Check the renewal clause: many require reminder notices or renew only for short periods. Several US states restrict silent renewals (California's Automatic Renewal Law among them) while the federal rulebook is in flux, and the UK is tightening consumer subscription traps under the DMCC Act 2024. At minimum, serve your non-renewal notice now so the next window can't be missed.
Exactly what the notice clause says: the length, the method (email? post? registered address?) and the recipient all matter. Terminations have failed because the notice went to the wrong place or by the wrong method. GitLaw drafts the letter and the service instructions from the clause itself.
If the breach is serious enough (material — or, in England, repudiatory) you may terminate, but tread carefully: terminating for a breach that doesn't qualify can itself be a wrongful termination, putting you in breach. The safe sequence is a written notice of breach with a cure period first — that's step four of the ladder.
A pre-agreed charge for leaving early. Reasonable ones are generally enforceable in both countries; charges far beyond any genuine loss may be attackable (as penalties in England, or as unconscionable in some US states) — and they're almost always negotiable. A mutual-exit proposal often lands below the stated fee.
Out is a letter away.
Upload the contract, see your exit routes, and serve the notice that actually ends it. Free.
