Software Development Contract: 12 Clauses to Check
Twelve clauses to check before you sign a software development contract: scope, change control, acceptance, IP, warranty, data, liability and exit.
Before you sign a software development contract, check twelve clauses: scope, pricing and payment terms, change control, acceptance, IP assignment, background IP and open source, ownership of accounts and repositories, warranty, data protection, key people and non-solicitation, liability, and termination with handover. Those clauses decide who pays when something goes wrong, and on most vendor drafts at least one of them favors the vendor more than a buyer should accept. Vetting tells you whether a software house is competent; the contract decides what happens when competence isn't enough. Our guide to vetting a software house covers the first part. This checklist covers the second, written from the vendor side of the table, since negotiating these contracts is part of our routine work. We are engineers, not lawyers, so treat this as a list of what to look for and have your own counsel review the final wording.
Scope, Price and Change: Clauses 1 to 3
Clause 1, scope. A fixed-price contract needs a statement of work detailed enough that both sides would agree on whether a feature is in or out: user roles, workflows, integrations, platforms, non-functional requirements such as performance and languages, and an explicit list of exclusions. A time-and-materials or dedicated-team contract should not pretend to that precision; it should describe the team, the working method and how the backlog is prioritized. The mistake is the hybrid, a fixed price attached to a vague scope, which all but guarantees a dispute. Clause 2, pricing and payment terms. Check the rate for every role, how often rates can rise and with how much notice, what counts as a billable hour, and how expenses are handled. Tie milestone payments to accepted working software, not to calendar dates or document deliveries. Clause 3, change control. Every contract needs a written process for changes: who can request one, how it is estimated, who approves it, and what happens to the timeline. Without it, small changes pile up in conversation, and the argument about whether they were in scope happens at the final invoice.
Acceptance and Ownership: Clauses 4 to 7
Clause 4, acceptance. Define what accepted means: tests passing against written criteria in a named environment. Set an acceptance window, commonly 5 to 10 business days, and read the deemed-acceptance wording carefully. Deemed acceptance after a silent window is reasonable; deemed acceptance on first production use, before you have tested anything, is not. Clause 5, IP assignment. The code, designs and documentation should be assigned to you as they are created, not upon final payment. Assignment conditional on final payment turns any billing dispute into a hold over your own product. Clause 6, background IP and open source. Vendors reuse their own libraries and tools, which is fine if the contract grants you a perpetual, royalty-free license to whatever pre-existing code ends up in your product. Ask for a list of open source components and their licenses at handover, and a commitment not to include copyleft code in distributed software without your written approval. Clause 7, accounts and repositories. Source code lives in a repository your organization owns from the first commit. Cloud accounts, domains, app store listings and third-party API keys are registered to you, with the vendor as a user you can remove. Rescue projects where the client does not control its own production database are more common than they should be, and they always begin with a negotiation instead of engineering.
After Go-Live: Clauses 8 and 9
Clause 8, warranty. After acceptance, the vendor should fix defects in the delivered scope at no charge for a defined period, typically 30 to 90 days, with response times by severity. Read the definition of a defect: it should cover any behavior that differs from the agreed acceptance criteria, not only crashes. Keep the warranty separate from ongoing support, which is a paid service with its own service levels, and price that support before you sign, not after launch, when your negotiating position is weakest. Clause 9, data protection and security. If the vendor's engineers will touch personal data, you need a data processing agreement covering what data, for what purpose, where it is stored, which subprocessors are involved, how breaches are reported and how data is deleted at the end. Ask how production access is granted and logged, whether developers work on masked data, and what security baseline the vendor commits to, such as device encryption, multi-factor authentication and access removal on the day someone leaves the project. Regulated buyers should attach their framework's requirements, such as SAMA or NCA controls in Saudi Arabia, as a schedule, so they become contractual instead of assumed. Preparing that schedule is part of what our cybersecurity and compliance team does for GCC clients.
People, Liability and Exit: Clauses 10 to 12
Clause 10, key people and non-solicitation. If you chose the vendor partly because of a named tech lead, name that person in the contract, with a replacement process and notice period if they leave. Non-solicitation clauses are normal in both directions. Check that the duration is reasonable, commonly 6 to 12 months, and that there is a fee for hiring a vendor engineer by agreement instead of a flat ban, which matters if you plan to build your own team later. Clause 11, liability. Most vendor contracts cap liability at the fees paid over a period, often the previous 12 months, and that is standard. Check what sits outside the cap: confidentiality breaches, data protection breaches and the vendor's IP infringement indemnity should usually be uncapped or carry a higher cap. Ask whether the vendor holds professional indemnity insurance, and for how much. Clause 12, termination and handover. You should be able to end the contract for convenience with reasonable notice, often 30 days, and the vendor should be obliged to hand over code, credentials and documentation, plus a knowledge transfer period at standard rates. A contract that allows termination only for cause locks you in for the full term.
For GCC Buyers: Governing Law and Tax
Buyers in the UAE and Saudi Arabia contracting an offshore vendor have two extra items to settle. The first is governing law and disputes. Many Gulf buyers, and their investors, prefer contracts under DIFC or ADGM law, English law, or arbitration at a recognized center, and a vendor in Pakistan should be comfortable with any of them; we contract with DIFC, ADGM and mainland entities as part of our work with UAE businesses. Choose the forum deliberately, because a contract you would have to enforce in an unfamiliar court is a weaker contract. The second is tax. VAT reverse-charge rules and withholding tax on payments to foreign suppliers can change what an invoice costs you, and the contract should state who bears them. Ask your tax adviser before signing, not after the first payment arrives short.
Red Flags in a Vendor's Draft
- IP that transfers only on final payment
- Repositories and cloud accounts in the vendor's name, with access promised at handover
- A fixed price with no statement of work, or a statement of work with no exclusions
- Deemed acceptance triggered by production use
- No warranty period, or a warranty that covers only crashes
- Termination for cause only, with no handover obligation
- A liability cap that also covers data breaches and IP infringement
- A non-solicitation clause with no end date and no buyout option
Have a project that needs this kind of thinking applied to it?