Software dev template · US · Pro
Software development agreement template for the US
In short
The US variant is governed by the law of the state you choose. Because contractor-written software is rarely a "work made for hire" under the US Copyright Act, the IP clause assigns the code to the client milestone by milestone once paid.
Pro Pro template: USD 5 for 30 days. The outline and explanations on this page are free to read.
What is a software development agreement?
A software development agreement is a services contract built for building software: a fixed price paid in milestones, acceptance testing against a specification, a change-request process, a bug-fix warranty, rules for open-source components and a full handover of source code, repositories and credentials.
It is a Pro template in Legal Drafter. It assigns the client the IP in each milestone once paid, licenses the developer's reusable tools, blocks copyleft surprises, and offers optional source code escrow.
When you need one
- Commissioning a mobile or web app, an MVP or an internal tool from an agency or freelancer.
- Outsourcing development to a team in another country.
- Any project where payment should depend on accepted milestones.
Typical uses: mobile and web app builds, mvps for startups, agency and outsourced development, custom internal tools.
What changes in the US
- Governing law
- the laws of the State of Delaware, without regard to its conflict of laws principles
- Disputes
- Each party irrevocably submits to the exclusive jurisdiction of the state and federal courts located in the State of Delaware for any action arising out of or relating to this Agreement, and waives any objection to venue in those courts
- You fill in
- Governing state (default Delaware)
- Default currency
- USD
- Date style
- October 21, 2026
- Data protection law cited
- all applicable United States federal and state privacy and data security laws, including where applicable the California Consumer Privacy Act as amended by the California Privacy Rights Act
Assignment, not work for hire
Software written by an independent developer generally does not fit the nine work-made-for-hire categories, so the template uses an express assignment.
Open-source licences
GPL and AGPL code can impose source-disclosure obligations depending on how it is used and distributed. The template requires open-source components to be listed and copyleft use approved.
Sales tax
Whether custom software development is subject to sales tax depends on the state. Prices are stated exclusive of tax.
Data security laws
If the software processes personal information, state data security and breach notification laws may apply. The data clause refers to applicable federal and state privacy laws.
Wording that is specific to the US version
Generated live from the template: these are the paragraphs that differ from the generic version. Placeholders in brackets are filled from the form.
Confidentiality and data
Each party shall keep the other's confidential information secret and use it only for this Agreement. Where the Developer processes personal data on the Client's behalf, it shall do so only on the Client's documented instructions, keep it secure, and comply with all applicable United States federal and state privacy and data security laws, including where applicable the California Consumer Privacy Act as amended by the California Privacy Rights Act.
Governing law and disputes
This Agreement and any dispute or claim (including non-contractual disputes or claims) arising out of or in connection with it or its subject matter shall be governed by and construed in accordance with the laws of the State of Delaware, without regard to its conflict of laws principles.
Each party irrevocably submits to the exclusive jurisdiction of the state and federal courts located in the State of Delaware for any action arising out of or relating to this Agreement, and waives any objection to venue in those courts.
Other paragraphs of this clause are the same in every version.
Sample outline
The US Software Development Agreement in clause order. Numbering shifts when optional clauses are switched off.
- Parties and date
- 1.Definitions
- 2.Project
- 3.Fees and milestones
- 4.Acceptance testing
- 5.Change requests
- 6.Intellectual property and source code
- 7.Open-source software
- 8.Warranty
- 9.Source code escrowoptional, off by default
- 10.Confidentiality and data
- 11.Limitation of liability
- 12.Termination
- 13.Governing law and disputes
- 14.General
- Signatures
Key clauses explained in plain English
- Parties and date
- The client commissioning the software and the developer building it.
- 1. Definitions
- Key terms used throughout. The Specification is the yardstick for whether the software works.
- 2. Project
- What is being built and how the client is kept informed.
- 3. Fees and milestones
- A fixed price paid in stages, each stage due only once the client accepts that milestone. Running costs such as hosting are separate.
- 4. Acceptance testing
- How the client checks each stage. Silence or going live counts as acceptance, so projects cannot be held up indefinitely.
- 5. Change requests
- New ideas mid-project are priced and approved in writing before work starts, keeping the budget and timeline under control.
- 6. Intellectual property and source code
- The client owns the code once it has paid, and receives the full source, repositories and passwords at the end. The developer keeps reusable tools but licenses them for this software.
- 7. Open-source software
- Open-source code is fine, but some licences can force you to publish your own code. This clause stops that happening by surprise.
- 8. Warranty
- A free bug-fix period after launch. Problems caused by others' changes or third-party services are excluded.
- 9. Source code escrow
- Optional. Protects the client if the developer disappears before handing over the code.
- 10. Confidentiality and data
- Both sides keep information private, and the developer must handle any personal data in the system lawfully and securely.
- 11. Limitation of liability
- Caps liability at the contract value and excludes knock-on losses, with the usual exceptions.
- 12. Termination
- The client can stop the project, paying for work done. In return it receives everything built so far, including the code.
- 13. Governing law and disputes
- Says which country's (or state's) law applies and where any court case or arbitration happens. It also asks both sides to try talking it through for 30 days first, except in emergencies.
- 14. General
- The standard "boilerplate": this document is the whole deal, changes must be in writing, neither side can hand the contract to someone else without permission, a bad clause does not sink the rest, and how formal notices are sent.
- Signatures
- Where each side signs. For a company, the person signing must be authorised to bind it (for example a director or a manager named on the trade licence).
Common mistakes
- No acceptance criteria. Acceptance is measured against the specification. A one-line spec means arguments at every milestone.
- No specification. Acceptance testing measures the software against the specification. Attach one, even a short one, as Schedule 1.
- Paying everything upfront. Tie payments to milestones that the client accepts. The template invoices each instalment on acceptance.
- Not getting the keys. Make sure repositories, cloud accounts, app-store accounts and domains end up in the client's name. The IP clause requires handover of credentials and administrative control.
- Ignoring open-source licences. Some licences (for example the GPL, used in certain ways) can require you to publish your own code. The template requires open-source components to be identified and copyleft use to be approved.
FAQ
Does paying a developer give me the copyright in the US?
Not automatically. You need a written assignment (or a qualifying work-made-for-hire agreement, which rarely applies to software by contractors).
What warranty period is normal?
Thirty to ninety days of free bug fixes after go-live is common. The template defaults to 90 days.
How is a software development agreement different from a freelance contract?
It adds what software projects need: milestone payments tied to acceptance tests, a warranty period, source code and credentials handover, open-source rules and change control.
Is the software development template free?
No. It is a Pro template. Pro costs USD 5 for 30 days and also removes your personal daily AI limit (a daily AI budget shared by all users still applies) and the export footer. You can read the full clause outline and explanations on this page for free.
Draft your US software development agreement now
Answer a short guided form and watch the draft fill in live. Party details stay in your browser. Edit any paragraph, switch optional clauses on or off, and export to Word, PDF, Markdown or text.
Pro Pro template: USD 5 for 30 days. The outline and explanations on this page are free to read.