Terminating a Software Development Agreement: When Can Your Business Walk Away?
When a software development project has gone badly wrong, terminating a software development agreement can feel like the obvious solution. Deadlines may have been missed, essential functionality may still be absent, costs may be escalating and confidence in the supplier may have disappeared.
However, deciding that you no longer want to work with a supplier is not the same as having a legal right to terminate.
Ending a software development agreement without a valid contractual or common-law basis, or without complying with the applicable contractual procedure, can expose your business to a claim that it has itself breached the contract. It can also create practical problems involving source code, data, intellectual property and transition to a replacement supplier.
Termination should therefore form part of a wider exit strategy, not simply be treated as a notice-ending exercise.
This article considers business-to-business software development agreements governed by the law of England and Wales.
When can you terminate a software development agreement?
The starting point is the contract.
Software agreements commonly provide express termination rights where particular events occur, such as material breach, persistent breaches, failure to remedy a breach, prolonged delay or insolvency.
Some contracts also allow termination for convenience. This permits one party to end the agreement without establishing fault, usually by giving a specified period of notice. However, the customer may still have to pay for work properly performed, committed third-party costs, demobilisation costs or an agreed termination charge.
The drafting matters. An express termination clause may operate independently of, alongside, or potentially limit common-law termination rights depending on the wording of the agreement.
Insolvency provisions also require particular care. In some contracts for IT goods and services, the Corporate Insolvency and Governance Act 2020 may restrict reliance on termination or suspension rights triggered solely because a customer enters a relevant insolvency procedure. The position depends on the circumstances and any applicable exceptions.
What should you check before terminating a software development agreement?
Before serving notice, establish precisely what agreement governs the project. The relevant terms may be spread across a master services agreement, statement of work, specification, order form, project plan, change requests and later variations.
In particular, check:
- The termination clause. Identify the exact right you intend to rely on and the conditions attached to it. Material breach, persistent breach and termination for convenience may each operate differently.
- Any cure period. The supplier may have a contractual right to remedy the breach before termination becomes available. Ending the agreement before that period expires can undermine an otherwise valid termination.
- The notices clause. The contract may prescribe how notice must be served, where it must be sent and whether email is sufficient. Any notice that does not comply with the contractual requirements may be disputed.
A valid termination notice should therefore be based on the actual contractual wording, not simply on the fact that management has lost confidence in the project.
What amounts to a material breach?
A material breach is generally a breach serious enough to trigger the relevant contractual termination provision. Its meaning depends on the wording and commercial context of the agreement.
Not every defect, missed milestone or disagreement over scope will necessarily be material. Software development projects often involve problems that can be addressed through testing, bug fixing, change control or revised delivery plans.
The position becomes more serious where failures affect the central purpose of the project, for example repeated failure to deliver core functionality, substantial delay to critical contractual milestones or refusal to carry out agreed work.
The evidence matters. A customer alleging that software is simply “unusable” will usually be in a stronger position if it can identify the contractual requirement, explain how the product falls short and demonstrate the significance of that failure.
What is a repudiatory breach?
A repudiatory breach is a sufficiently serious breach that gives the innocent party a choice whether to bring the contract to an end.
It may arise where a party clearly renounces its obligations or commits a breach which deprives the other party of substantially the whole benefit of the contract.
Importantly, a repudiatory breach does not automatically terminate the agreement. The innocent party must decide whether to affirm the contract and keep it alive, or accept the repudiation and end future contractual obligations.
This is a higher threshold than simply proving breach of contract. An isolated software defect may support a damages claim without justifying termination. By contrast, a clear refusal to complete the project or a fundamental failure to deliver the contracted system may potentially amount to repudiation.
A series of repeated failures can also become significant if they indicate that the supplier is unwilling or unable to perform future obligations, but this will depend on the contractual context.
Must you give the supplier a chance to fix the problem?
Often, yes.
Many agreements require the customer to serve a breach notice and allow a defined period for the supplier to remedy the problem.
The notice must comply with the wording of the relevant clause. Depending on the drafting, it should normally identify the breach clearly enough for the supplier to understand what is alleged and what needs to be corrected.
The relationship between contractual cure provisions and common-law termination rights is not automatic. A cure mechanism governing an express contractual right may not necessarily govern a separate common-law right to accept a repudiatory breach. Equally, it should not be assumed that a cure process can safely be ignored.
That question depends on construction of the particular agreement.
What happens if your business terminates unlawfully?
Wrongful termination can significantly weaken the customer’s position.
If a business purports to terminate without the necessary right, that action may itself amount to a repudiatory breach. The supplier may then accept that breach and pursue the remedies available to it.
Those remedies may include recoverable loss of bargain, such as lost net profit or contribution, and potentially wasted expenditure, subject to proof, causation, mitigation, remoteness and any contractual limitation provisions.
This is why termination correspondence needs careful preparation. A notice should identify the legal basis relied upon, comply with the relevant procedure and preserve other rights where appropriate.
Should you stop paying the supplier?
Not automatically.
A dispute over performance does not necessarily give the customer a right to withhold, deduct or set off sums otherwise due.
Before stopping payment, check whether the relevant milestone has actually been achieved, whether acceptance criteria have been satisfied, whether the agreement permits set-off and whether non-payment gives the supplier a right to suspend services.
Also check for any “pay now, argue later” mechanism or contractual deadline for disputing invoices.
Using payment as leverage without first analysing the contract can create a fresh breach at a strategically important point in the dispute.
What losses might be recoverable after terminating a software development agreement?
Termination does not automatically determine what compensation is available.
Depending on the circumstances, a customer may seek reasonable costs of investigating defects, remedial development, engaging a replacement supplier, data migration and disruption directly caused by the breach.
The usual rules on causation, remoteness and mitigation apply. The customer must be able to connect the claimed loss to the supplier’s breach and should take reasonable steps to avoid unnecessary further loss.
In addition, the contract may contain liability caps and exclusions. Their effect depends on construction and, where applicable, statutory controls such as the reasonableness requirements under the Unfair Contract Terms Act 1977 may be relevant.
How the Jonathan Lea Network can help with terminating a software development agreement
A failing software project usually creates two linked questions: whether your business is legally entitled to leave and how it can do so without causing further commercial damage.
JLN can review the software development agreement and project documents, assess the supplier’s alleged breaches and advise on contractual and common-law termination rights. We can also prepare breach or termination notices, advise on payment disputes, assess liability limitations and help protect your position regarding source code, intellectual property, data and evidence.
Where possible, we can support negotiations over remedial work, an orderly exit or settlement before formal proceedings become necessary.
If a dispute cannot be resolved commercially, we can advise on mediation, arbitration, expert determination, adjudication where applicable, court proceedings or other dispute-resolution procedures provided for in the contract.
Technology and software disputes may, depending on their technical complexity, value and the applicable procedural rules, also be suitable for the Technology and Construction Court, a specialist court within the Business and Property Courts. Claims below £250,000 are not normally dealt with there unless there is good reason.
If your business is considering terminating a software development agreement, taking advice before serving notice can help preserve your rights and reduce the risk of turning a supplier dispute into a claim about your own termination.
Contact our dispute resolution team to discuss the agreement, the state of the project and the safest commercial route forward.
Frequently asked questions: terminating a software development agreement
Start with the contract. Software agreements often allow termination for material breach, persistent breaches, failure to fix a breach, long delay or insolvency. There may also be a common-law right to accept a repudiatory breach. However, deciding you no longer want the supplier is not the same as having a legal right to terminate. Identify the exact right you will rely on and the conditions attached to it. Not on that basis alone. A valid termination notice should rest on the actual contract wording, not on the fact that management has lost confidence. Ending the agreement without a valid right may put your business itself in breach. The same applies if you skip the contract procedure. That can expose you to a claim. Check the termination clause, any cure period and the notices clause first. Some contracts let either party end the agreement without proving fault. This is termination for convenience, and it usually needs a set period of notice. However, the customer may still have to pay for work properly done. It may also have to pay committed third-party costs, demobilisation costs or an agreed termination charge. Check what the clause says you must pay before relying on it. It is generally a breach serious enough to trigger the contract’s termination clause. Its meaning depends on the wording and the commercial context. Not every defect, missed milestone or scope disagreement will be material. However, the position is more serious where failures hit the central purpose of the project. Examples include repeated failure to deliver core features or refusing to do agreed work. Gather evidence for each failure. A material breach triggers a termination right in the contract. A repudiatory breach is a common-law idea and sets a higher bar. It arises where a party clearly renounces its obligations. It can also arise where a breach deprives the other party of substantially the whole benefit. A repudiatory breach does not end the contract automatically. You must choose whether to keep the contract alive or accept the repudiation. Often, yes. Many agreements require a breach notice and a set period for the supplier to put things right. Ending the agreement before that period runs out can undermine an otherwise valid termination. The notice should identify the breach clearly enough for the supplier to understand what to correct. Do not assume you can safely ignore a cure process, as this depends on the particular agreement. It depends on the notices clause. The contract may say how to serve notice, where to send it and whether email is enough. The supplier may dispute a notice that does not follow these requirements. A notice should also state the legal basis you rely on and keep your other rights open where appropriate. Prepare termination correspondence carefully, and take advice before you serve it. Wrongful termination can seriously weaken your position. If you try to terminate without the necessary right, that may itself be a repudiatory breach. The supplier can then accept it and pursue its own remedies. These may include its lost net profit and possibly wasted spending. The usual rules and any contract limits still apply. Take advice before serving notice to avoid turning the dispute around. Not automatically. A performance dispute does not necessarily give you a right to withhold or set off money. First check whether the milestone was achieved and the acceptance criteria met. Also check whether the contract allows set-off and whether non-payment lets the supplier suspend services. Look out for any “pay now, argue later” clause or invoice deadline. Otherwise you may create a fresh breach yourself. Not always. In some contracts for IT goods and services, the Corporate Insolvency and Governance Act 2020 may restrict this. It can stop a supplier relying on termination or suspension rights for that reason alone. This applies where the customer enters a relevant insolvency procedure. The position depends on the circumstances and any exceptions that apply. Check the insolvency clause carefully and take advice if your business is in this position.
Contact us
We provide most enquiries with an indicative scope of work and fee estimate, based on the information you share. We aim to respond within one working day.
In the same email you will be invited to arrange a 20-minute complimentary, no-obligation video consultation, should the proposed scope of work and fee estimate be of interest. This initial discussion is designed to better understand your requirements, refine the scope and ensure our approach is fully aligned with your objectives, at the end of which we will email you a definitive formal fee estimate to consider and approve.
Where you would prefer to receive initial advice and guidance from the outset, or where a short introductory call would not be the most appropriate starting point, we may instead recommend a 2.5-hour fixed-fee appointment, starting from £700 + VAT. This enables us to review the information you provide, discuss your situation with you and provide considered, tailored advice at an early stage.
To make an enquiry, please email us at wewillhelp@jonathanlea.net, complete our contact form, or call us on 01444 708640.
VAT is charged at 20%.
This article is intended for general information only, applies to the law at the time of publication, is not specific to the facts of your case and is not intended to be a replacement for legal advice. It is recommended that specific professional advice is sought before relying on any of the information given. © Jonathan Lea Limited.