Hiring Guides

Software Development Contract Checklist for Buyers

A buyer's software development contract checklist: scope, payment, acceptance, IP ownership, warranties, data protection, staffing, exit terms and governing law.

Software Development Contract Checklist for Buyers

A software development contract should cover, at minimum: the scope and specification, milestones and deliverables, the pricing model and payment terms, a change request process, acceptance testing, intellectual property ownership, warranties and remedies, confidentiality and data protection, security, service levels for support, liability and indemnities, staffing, termination and exit, and the governing law. The checklist below explains what to look for in each clause from the buyer's side, which questions to ask, and where vendors commonly push back. This is general information, not legal advice. Have a qualified lawyer in your jurisdiction review any contract before you sign it.

How to use this checklist

Most software development agreements arrive as the vendor's standard template, sometimes as a master services agreement plus a statement of work for each project. Templates are written to protect whoever drafted them. That is normal, not sinister, but it means you need to read with your own interests in mind.

It helps to know what the other side is protecting. Law firm checklists written for developers, such as the pro-developer software development agreement checklist by Kilpatrick Townsend published through LexisNexis Practical Guidance, advise vendors to keep their pre-existing IP, make IP transfer conditional on full payment, limit remedies to fixing and resubmitting defective work, cap liability by reference to fees, and narrow the customer's termination rights. None of that is unreasonable on its own, but you should recognise those positions when you see them and decide which ones you can accept.

LexisNexis also publishes a software development agreement checklist for UK practice covering deliverables and specifications, agile development, IP ownership and licensing, pricing, acceptance testing, service levels, liability, termination and governing law. The sections below follow a similar path, written for buyers.

1. Scope, specification and deliverables

  • Is the scope described in a statement of work, specification or backlog that is attached to or referenced by the contract?
  • Are deliverables listed explicitly: source code, compiled builds, documentation, test scripts, design files, deployment scripts?
  • For agile projects, does the contract describe how scope is managed: sprint length, who sets priorities, how the backlog changes and how progress is reported?
  • Are your own responsibilities clear, such as providing content, access, test data and timely feedback? Vendors will rely on these if a deadline slips.
  • Are third-party components, such as paid APIs, licences or hosting, included or excluded, and who pays for them?

A clear request for proposal makes this section much easier. See our guide on how to write an RFP for software development.

2. Pricing, payment and change requests

  • Is the pricing model clear: fixed price, time and materials, a capped time and materials budget, or a dedicated team rate? Our comparison of fixed price and time and materials contracts explains the trade-offs.
  • Are payments tied to accepted milestones rather than dates alone?
  • Are rates listed by role, with rules for rate increases during a long engagement?
  • Are expenses, travel, licences and hosting costs covered, and do they need your prior approval?
  • Is there a written change request process: who can request and approve changes, how they are estimated and how they affect price and timeline?
  • For time and materials, will you receive timesheets or work logs, and how often?

3. Acceptance testing

Acceptance is where many disputes begin. Check:

  • Objective acceptance criteria for each milestone, linked to the specification.
  • A defined testing period, and what happens if you do not respond within it. Many templates say silence equals acceptance, so make sure the period is realistic for your team.
  • How defects are classified, for example by severity, and which ones block acceptance.
  • How many rounds of fixes are allowed before you can reject the deliverable or end the contract.
  • Whether using the software in production counts as acceptance.

4. Intellectual property ownership

This is the clause buyers most often regret not reading. Questions to settle:

  • Who owns the custom code? Most buyers want the bespoke code and deliverables assigned to them. Check whether ownership transfers on creation or only on full payment.
  • What does the vendor keep? Vendors usually keep pre-existing tools, frameworks and libraries. If so, you need a perpetual, irrevocable licence to use, modify and have others maintain them as part of your software.
  • Open source: require a list of open source components and their licences, and rules about which licences are acceptable.
  • Subcontractors: the vendor must have rights from its own staff and subcontractors so it can pass them to you.
  • Moral rights and further assurances: in some jurisdictions you also need waivers and a promise to sign further documents.

Do not assume that paying for work means you own it. In the United States, the Copyright Office's circular on works made for hire explains that a commissioned work counts as work made for hire only if it falls into one of nine listed categories and a signed written agreement says so. Software is not one of the nine categories, which is why contracts with outside developers normally contain an express assignment of copyright. Rules differ in other countries, so ask your lawyer.

5. Warranties, remedies, liability and indemnities

ClauseWhat buyers usually wantWhat vendors often propose
Performance warrantySoftware conforms to the specification for a defined period after acceptanceA short warranty period with fix-and-resubmit as the only remedy
Professional standardsWork done with reasonable skill and care by suitably qualified staffGeneral industry standard wording
Third-party IPVendor indemnifies you if its code infringes someone else's rightsIndemnity excluding open source, your materials and modifications
Malicious codeNo viruses, backdoors or time locksUsually accepted
Liability capA cap that reflects the real risk, with carve-outs for confidentiality, data protection and IP indemnitiesCap equal to fees paid in a recent period, excluding indirect loss

Liability clauses are where legal advice pays for itself. The right cap depends on what could go wrong, your insurance and local law.

6. Confidentiality, data protection and security

  • Confidentiality obligations that cover your business information, code and data, and survive the end of the contract.
  • If the vendor will handle personal data, a data processing agreement. Under the EU GDPR, Article 28 lists what a processor contract must include, such as acting only on documented instructions, confidentiality of staff, security measures, conditions for using sub-processors, help with data subject requests, deletion or return of data at the end, and support for audits.
  • Security requirements: secure development practices, access control, how secrets are stored, vulnerability handling and breach notification times.
  • Where data and code will be stored and who can access them, including from which countries.
  • Insurance: ask what professional indemnity and cyber cover the vendor holds.

7. Staffing, support and service levels

  • Key personnel: named roles who cannot be replaced without notice, and your right to request replacement of someone who is not working out.
  • Subcontracting: whether the vendor may subcontract, and whether it needs your consent.
  • Non-solicitation: usually mutual. Check whether it would stop you hiring a developer you would like to keep after the project.
  • Support and maintenance: if included, response and resolution times by severity, support hours and time zone, and how service credits work.
  • Reporting and governance: status reports, steering meetings and escalation routes.

8. Termination, exit, governing law and disputes

Termination and handover

Plan the ending at the start. The contract should say:

  • Whether you can terminate for convenience, with what notice, and what you pay for work in progress.
  • What counts as material breach and how long the vendor has to fix it.
  • That on termination you receive all code, documentation, credentials and data, in a usable form.
  • That the vendor will provide reasonable transition assistance at agreed rates.
  • That accounts, repositories and infrastructure are in your name from the beginning, so exit does not depend on goodwill.
  • Whether source code escrow is needed, typically only when you license the vendor's product rather than own the code.

If you are already in a difficult exit, our guide on how to switch software development vendors includes a handover checklist.

Governing law, disputes and signatures

  • Which country's or state's law governs the contract, and where disputes will be heard. With offshore vendors this matters a great deal.
  • Whether disputes go to negotiation, mediation, arbitration or court, and in what order.
  • Order of precedence when the master agreement, statements of work and attachments conflict.
  • That the people signing have authority to bind their organisations, and that all attachments are signed or referenced.

What to do next

Quick buyer checklist

  1. Scope and deliverables written down and attached
  2. Pricing model, rates and payment milestones clear
  3. Change request process agreed
  4. Objective acceptance criteria and a realistic testing period
  5. Custom code assigned to you, with a licence for vendor tools
  6. Open source list and licence rules
  7. Warranty period and remedies
  8. Liability cap and carve-outs reviewed by a lawyer
  9. Confidentiality, data processing and security terms
  10. Key personnel, subcontracting and non-solicitation
  11. Support levels, if included
  12. Termination rights, exit deliverables and transition help
  13. Governing law and dispute process

Use this checklist when you compare proposals, not only at signing: a vendor's response to these points tells you a lot about how it will behave during the project. Our guide on how to compare software development quotes shows how to line up offers. To build a shortlist, browse software development companies on Trusted IT Firms. Remember that this article is not legal advice: ask a qualified lawyer to review the final agreement.

Frequently asked questions

Who owns the code in a software development contract?

Whoever the contract says. Buyers usually want custom code assigned to them, with a licence to any vendor tools built in. Do not assume payment alone transfers ownership.

Is software a work made for hire in the US?

Not when commissioned from an outside developer. The US Copyright Office lists nine categories of commissioned work that can be works made for hire, and software is not one of them, so contracts use an express assignment.

Do I need a data processing agreement with my developer?

If the vendor will handle personal data on your behalf and the GDPR applies, yes. Article 28 lists what the contract must contain.

No. It is general information to help you prepare. Ask a qualified lawyer in your jurisdiction to review any contract before you sign.

Sources

Add Trusted IT Firms to your preferred sources

Add trusteditfirms.com as a preferred source on Google, or open this page in your AI assistant to use it as a source.

· Trusted IT Firms Team

The Trusted IT Firms editorial team writes guides to finding and working with IT companies.

Keep reading

List your IT company for free

Create a profile in minutes, get reviewed by our editors and start receiving enquiries from clients looking for your skills.