Guide for US companies
A software development contract checklist for US companies hiring an outside team
A software development contract checklist for a US company should cover ten clauses: IP assignment, open-source use, source-code access or escrow, acceptance criteria, warranty, limitation of liability, governing law and disputes, confidentiality, a data protection addendum, and termination with handover. Below we explain what each should say and what to ask. Have your attorney review the final draft.
- IP
- Signed written assignment
- Code
- In your repository from day one
- Our warranty
- 30 days of free bug fixes
- Final check
- Your attorney
Updated · By the Codebrix team
How the contract documents fit together
Most software engagements use two or three documents. A master services agreement (MSA) holds the legal terms that apply to every project: IP, confidentiality, liability and disputes. A statement of work (SOW) for each project holds the scope, milestones, acceptance criteria and price. Where the vendor will handle personal data, a data protection addendum (DPA) sets the privacy terms, and in US healthcare a business associate agreement may be required on top.
Two clauses tie the documents together and are easy to forget. An order-of-precedence clause says which document wins if they conflict; commonly the MSA wins on legal terms and the SOW on scope. A change-order clause says how scope changes are requested, priced and approved in writing, so new work never starts on a verbal yes.
Intellectual property: assignment, not just 'work made for hire'
Many US templates say deliverables are 'work made for hire'. For software built by an outside contractor, that phrase often does less than buyers expect. The US Copyright Office's Circular 30 explains that a work is made for hire in only two situations: when an employee creates it within the scope of employment, or when a specially ordered or commissioned work falls into one of nine categories and both parties sign a written agreement saying it is a work made for hire.
The nine categories are a contribution to a collective work, part of a motion picture or other audiovisual work, a translation, a supplementary work, a compilation, an instructional text, a test, answer material for a test, and an atlas. Software is not on the list, so a contractor's code will usually not qualify, and the Circular is clear that if any requirement is missing, the work is not made for hire.
The fix is an assignment. Under 17 U.S.C. section 204(a), a transfer of copyright ownership is not valid unless it is in writing and signed by the owner of the rights or their authorised agent. Contracts commonly keep the work-made-for-hire wording and add an assignment as well. Points to check with your attorney:
- The assignment covers code, designs, documentation, test scripts, database schemas and every other deliverable, not only 'the software'.
- It takes effect on payment for each milestone, so ownership does not wait for the final invoice.
- The vendor confirms it holds the rights from its own engineers and any subcontractors, so it actually has something to assign.
- Pre-existing vendor tools or code reused in your project are either assigned or licensed to you permanently, with the licence terms written down.
- Open-source components are listed with their licences at handover, and nothing with terms that conflict with your plans goes in without your approval.
- The vendor agrees to sign any further documents needed to record the transfer.
Source code, escrow and handover
Source-code escrow means a neutral third party holds a copy of the code and releases it to you if an agreed trigger occurs, such as the vendor ceasing to trade or dropping support for a product you depend on. It matters most when you license a vendor's own platform and never receive the source.
For a custom build there is a simpler protection: the code lives in your repository from the first commit. If the repository sits in your GitHub or GitLab organisation, hosting runs in your cloud account and you hold admin rights, there is little left to escrow. Write that into the contract rather than relying on goodwill.
Termination and handover
- Either side can end the engagement on written notice, and you can stop after any milestone and keep everything delivered and paid for.
- On termination, the vendor hands over the latest code, documentation, any credentials it created, and a list of every third-party service in use.
- Infrastructure is described well enough for another team to deploy it: environment variables listed, build steps written, infrastructure-as-code included where used.
- The vendor removes its own access to your systems and confirms it in writing.
- Data the vendor held on your behalf is returned or deleted, with written confirmation.
- An optional, paid transition period is available if a new team needs walkthroughs.
Acceptance criteria and warranty
Many disputes in software projects come down to whether something is finished. Acceptance criteria settle that before work starts. Each milestone in the SOW should state what will be delivered, how you will test it and what counts as a pass.
- Testable criteria: 'a user can reset a password by email and the link stops working after one use', not 'password reset works well'.
- Where testing happens: a named staging environment, and the browsers and devices in scope.
- A review window: a fixed number of business days for you to accept or list defects.
- Deemed acceptance: what happens if the window passes without a response, so milestones cannot stall indefinitely.
- Defect versus change: a defect is a failure to meet the written criteria; anything else is a change request, priced separately.
The warranty covers defects found after acceptance. Check how long it lasts, what it covers and what voids it, such as changes made by someone else or a third-party service changing its API. Our own warranty is 30 days of free bug fixes after launch; after that, fixes and changes fall under an optional month-to-month retainer or a new SOW.
Liability, indemnities and disputes
A limitation of liability clause caps how much either side can claim. A common structure ties the cap to the fees paid under the contract and excludes indirect or consequential losses. Whether that is acceptable depends on your risk: a marketing site and a payments system are not the same. Ask your attorney which claims should sit outside the cap, for example breach of confidentiality, or an IP infringement indemnity under which the vendor defends you if delivered code infringes someone else's rights.
Ask what insurance the vendor holds and whether it would respond to a claim from a US client. Do not assume; ask for the answer in writing.
Governing law and disputes with an overseas vendor
The contract should name the law that governs it and where disputes are heard. With an India-based vendor, ask your attorney a practical question too: if you won, how would a court judgment or arbitration award actually be enforced against the vendor where its assets are? The answer often shapes the choice between courts and arbitration. Add an escalation ladder before any formal step, such as project leads, then senior people on both sides, then mediation, each with a time limit.
Confidentiality, data protection and security
Confidentiality should cover your business information, your code and any data the vendor sees, survive the end of the contract, and allow disclosure only to people who need it for the work. If the vendor will handle personal information about your customers, a data protection addendum sets out what it may do with it.
If the CCPA applies to you, California's regulations list what a service provider contract must contain, including a ban on selling or sharing the data, a specific description of the business purpose, a duty to give the same level of privacy protection the law requires of you, your right to take reasonable steps to check and stop misuse, and a duty to tell you if the vendor can no longer meet its obligations. The regulations add that a person without a compliant contract is not a service provider, so disclosing data to them may count as a sale or sharing. Our CCPA website checklist goes further.
In healthcare, HHS guidance says a written business associate agreement must be in place before a business associate creates, receives, maintains or transmits electronic protected health information for you. If our team would touch PHI, we settle how that is handled during discovery, and we prefer designs where our engineers work only with synthetic or test data and never with production PHI. See HIPAA app development for how we approach those builds.
Security terms worth writing down
- Vendor staff get named accounts with the least access they need, never shared logins.
- Production data is not copied to developer machines or test environments without your written approval.
- Secrets live in a secrets manager or the hosting provider's environment settings, never in the repository.
- The vendor tells you about any security incident affecting your systems or data within a time the contract states.
- Access is removed within a stated time when a person leaves the project.
The full checklist
| Clause | What good looks like | Red flag |
|---|---|---|
| IP assignment | Signed written assignment of all deliverables, effective per paid milestone | Only 'work made for hire' wording, or ownership only after final payment |
| Background IP and open source | Reused vendor code licensed to you permanently; open-source list with licences at handover | A proprietary vendor framework with no licence terms |
| Code and accounts | Repository, hosting, domains and store accounts in your name from day one | Code kept in the vendor's repository until the end |
| Escrow | Unnecessary for custom code you already hold; needed if you license a vendor platform | A licensed platform with no escrow and no exit plan |
| Scope and change control | An SOW per milestone; written change orders with price and time impact | Scope described in one paragraph |
| Acceptance criteria | Testable criteria, a review window and a deemed-acceptance rule | 'To the client's satisfaction' with no definition |
| Warranty | A stated bug-fix period after launch, with exclusions listed | No warranty, or one that ends before you can test |
| Limitation of liability | A cap and carve-outs your attorney has reviewed | A cap so low it excludes the risks that matter to you |
| Governing law and disputes | Named law and forum, an escalation ladder and an enforcement plan | Silent on disputes |
| Confidentiality | Covers code, business data and personal data; survives termination | A one-way NDA that protects only the vendor |
| Data protection | DPA with service-provider terms; BAA where PHI is involved | Vendor may use your data to 'improve its services' without limits |
| Termination and handover | Stop after any milestone, keep paid work, documented handover, access removed | Termination fees, or handover only on full payment |
We work to this list ourselves: a written proposal with a fixed price and milestones, code and accounts in your name from day one, payment per milestone and 30 days of bug fixes after launch. How we work with US companies is on our US location page, and the paperwork for paying us is in our guide to paying foreign contractors. Whoever you hire, have your attorney review the contract before you sign.
Frequently asked questions
Is 'work made for hire' wording enough to own software a contractor writes?
Usually not on its own. The US Copyright Office's Circular 30 lists nine categories of commissioned work that can be made for hire, and software is not among them. For code written by an outside contractor, ask for a written assignment signed by the vendor, which 17 U.S.C. section 204(a) requires for a valid transfer of copyright. Have your attorney confirm the wording.
Do I need source-code escrow?
For custom software where the repository sits in your own organisation from the first commit, escrow adds little because you already hold the code. Escrow matters when you license a vendor's proprietary platform and never receive the source: it gives you a route to the code if the vendor stops trading or stops supporting the product.
What should acceptance criteria look like?
Specific and testable for each milestone: what the feature does, on which devices and browsers, and what counts as a pass. Add a review window in business days, a rule for what happens if the window passes without a response, and a definition of a defect versus a change request. Vague criteria are what turn invoices into arguments.
What is a reasonable warranty period for custom software?
There is no single standard; it depends on the size and risk of the work. What matters is that it starts when you can actually use the software in production, lists what is covered and excluded, and says how quickly defects are fixed. We include 30 days of free bug fixes after launch, with an optional monthly retainer after that.
Which law should govern a contract with a vendor in India?
That is a question for your attorney. US buyers often ask for their own state's law, and vendors may prefer theirs. Beyond the choice itself, ask how a judgment or arbitration award would be enforced against the vendor in practice, and include an escalation ladder so most disagreements are settled long before anyone starts formal proceedings.
Do I need a data protection addendum with a development agency?
If the agency will access personal information you hold, such as customer records or form submissions, in practice yes. If the CCPA applies to you, California's regulations list specific terms a service provider contract must include. If the agency would handle protected health information, HIPAA requires a business associate agreement before it does.
Sources
Related
United States
An offshore web development company in India for US businesses
Offshore web development company in India for US businesses: USD pricing, Stripe or wire payment, IP assigned to you, and a planned ET and PT overlap.
Read moreOutsourcing guide
Outsourcing software development to India: a practical playbook for buyers
Outsourcing software development to India from the US, UK, EU or Australia: engagement models, IP, payments, time zones, red flags and a 30-day plan.
Read moreGuide for US companies
Paying foreign contractors from the US: forms, withholding and payment rails
Paying foreign contractors from the US: which W-8 form to collect, when withholding and Form 1099 apply, wire vs Stripe, and what a USD invoice shows.
Read moreGuide for US companies
CCPA website requirements: what your site needs if California's privacy law applies
CCPA website requirements: privacy policy contents, opt-out links, Global Privacy Control, request methods and vendor contracts, with a full checklist.
Read moreHealthcare apps
HIPAA compliant app development: what we build, and what stays your job
HIPAA compliant app development explained: the Security Rule safeguards we build in, BAAs with AWS, Google Cloud or Azure, and PHI kept to the minimum.
Read moreBuying guide
Choosing a web development company: questions, red flags and a scoring sheet
How to choose a web development company: the questions to ask, red flags to spot, and a weighted scoring table for comparing proposals side by side.
Read more