How to Choose a Software Development Contract: A Checklist for Buyers
A buyer's checklist for software development contracts: fixed scope vs time and materials, milestones, IP, NDA, acceptance criteria and change requests.
A software development contract is where a friendly scoping conversation turns into obligations. Most disputes trace back to a handful of clauses that nobody read closely: what “done” means, who pays for changes, who owns the code, and what happens if the project stops halfway. Those clauses are easy to fix before you sign and expensive to argue about afterwards.
This guide is a buyer’s checklist: how to choose the contract model, which clauses matter most, which red flags to look for in a draft, and how to prepare for a lawyer’s review. It is general information, not legal advice. Terms and enforceability vary by jurisdiction and by project, so have a lawyer review any agreement before you sign it. We are a New York product engineering studio, so we have an interest; where it helps, we say how we handle each point so you can compare. If you are still comparing vendors, start with How to Choose a Software Development Company; this guide picks up when you have a draft in front of you.
Fixed scope, time and materials, or retainer: choosing the model
Choosing a software development contract starts with how you will pay, because that decides who carries which risk.
| Model | Works best when | Main risk | Ask about |
|---|---|---|---|
| Fixed scope | The deliverable can be written down and has an end date | Vague scope becomes a dispute, or the quote is padded to cover unknowns | What is in, what is out, how changes are priced |
| Time and materials | You are still discovering what to build | Open-ended spend if nobody is watching | Estimates, a budget ceiling, weekly demos, how to stop |
| Retainer or embedded engineer | Ongoing feature work, or extra capacity for your own team | Paying for capacity you do not use | Notice period, what a month of capacity buys |
Fixed scope (often called fixed price) moves estimating risk to the vendor, but only if the scope is real. That means a written scope that names what is in and what is out, plus a way to price changes. Time and materials suits discovery, where you cannot know the destination yet, but it needs a budget ceiling and regular demos, or the meter just keeps running. A retainer fits the stage after launch, when the work is a steady stream of improvements. Many healthy projects combine them: a fixed-scope first phase to ship something real, then a retainer to iterate.
If you are unsure, ask each vendor which model they would choose for your project and why. A good answer refers to how well defined your scope is, not to what is easiest for them to sell. Our own models are fixed-scope projects billed in milestones, a monthly retainer, and an embedded engineer, laid out on the process page. What a project costs depends on its scope, and How Much Does It Cost to Build an MVP or Web App in 2026? explains what moves the number.
The clauses that matter
These are the clauses we would read twice. None is exotic; the trouble is that they are missing, vague, or buried in an appendix.
Scope and deliverables
Attach a written scope (often called a statement of work) that says what is being built, what is explicitly not, and what you must provide, such as access, content, and decisions. “Website as discussed” is not a scope. If something is not written down, assume it is not in the price.
Acceptance criteria
Acceptance criteria are how both sides agree that a deliverable is finished. Good ones are testable (“a user can reset a password by email”) rather than subjective (“intuitive login”). The contract should say how long you have to review, what happens when something fails, and how many rounds of fixes are included. Be wary of any clause that treats silence as acceptance after a very short window.
Milestones and payment
For fixed-scope work, tie payments to delivered, working software, not to the calendar. Milestones you can see and test protect both sides: you pay for progress you can verify, and the vendor is not financing your project. Check the invoice terms, what a late payment triggers, and whether any deposit is credited against the first milestone. Our fixed-scope projects are billed in milestones tied to delivered work.
Change requests
Every project changes, so the contract should say how. Look for a written process in which a change is described, quoted, and approved by a named person before any work on it begins, with its effect on the timeline stated. A contract that lets scope grow informally is how a fixed price becomes an open-ended one. We quote a change on its own, in writing, before it starts, so it never quietly expands the current milestone’s price or timeline.
Intellectual property
If you read only one clause closely, make it this one. In many jurisdictions, a contractor who writes code can own the copyright unless the agreement assigns it to you in writing, so “you own it” on a sales call is not enough. Check that the assignment is explicit, when it takes effect (on creation, on each paid milestone, or on final payment), and what the vendor keeps. Vendors often reuse their own tools and libraries, so a fair contract separates what they bring from what they build for you, and gives you a license to anything of theirs that ends up inside your product. Ask for a list of third-party and open-source components too, because their licenses travel with your code. For comparison, our terms are that you own the IP in full on final payment, and code delivered against paid milestones is yours in the meantime.
Confidentiality and NDA
Most engagements involve business data or a live codebase, so a mutual non-disclosure agreement (NDA) before detailed discussions is normal. Check what counts as confidential, how long the duty lasts, what happens to your data and credentials at the end, and whether the vendor may name you as a client or show the work in a portfolio. A mutual NDA before the scoping call is standard for us.
Warranty and support after launch
Software has bugs. The contract should say whether defects against the agreed acceptance criteria are fixed at no extra charge for a defined period after launch, what is excluded (for example, changes made by other developers, or a third-party service that changes underneath you), and what ongoing support costs afterwards. A defined support window belongs in the proposal, not in a conversation after the final invoice.
Timeline, dependencies, and delays
Dates should hang off milestones and list what you owe: content, access, and decisions. Late inputs from you reasonably move the dates. When the vendor is late, look for a commitment to tell you early and offer options (extend, cut scope, or add capacity) rather than a silent slip.
Termination and handoff
Either side may need to stop. The contract should explain how to give notice, what you keep and what you owe, and what handoff is included: repositories, cloud accounts, domain, credentials, and documentation. A fair pattern is that you keep everything delivered through the last completed milestone and owe only for that work. That is how ours works.
Also ask your lawyer about
- Liability and indemnities. Limits on what either side can owe, and who is responsible if the software infringes someone else’s rights.
- Data and security terms. Who can access your systems, how credentials are shared and revoked, where personal data is stored, and whether work may be subcontracted on the same confidentiality and IP terms.
- Governing law and disputes. Which jurisdiction applies and how disagreements are escalated before they reach a court.
- Renewal and exclusivity. Automatic renewals, minimum terms, and anything that restricts working with others.
Red flags in a draft agreement
- Payment for time, not delivery. A large upfront payment, or invoices that arrive whether or not anything has shipped.
- A scope that says “as discussed.” If you cannot point to the page that defines done, neither side can.
- No clear IP assignment. Watch for an assignment that applies only after a long list of conditions, or a vendor-owned framework you cannot run without them.
- Deemed acceptance after a few days of silence.
- Changes at the vendor’s discretion, with prices and dates set after the work is done.
- Verbal side agreements. If it matters to either side, it belongs in the document.
What to bring to your lawyer
A lawyer can sharpen the wording, but cannot make an unclear scope clear. Before the review, gather:
- The written scope and the proposal the contract refers to.
- A list of what is sensitive: customer data, credentials, regulated information.
- Your must-haves in plain language, such as the IP outcome you need, a firm launch date, or the right to leave.
- The name of the person on your side who can approve changes.
- This checklist, with a note beside every item the draft is silent on.
Bottom line
A good software development contract is boring: a written scope, payments tied to working software, changes priced before they start, IP that ends up with you, and a clean exit. Pick the model that matches how certain your scope is, read the IP and acceptance clauses twice, and have a lawyer review the final draft. This guide is general information, not legal advice.
If you are comparing agreements for a custom web, mobile, or AI project and want to see how we handle scope, milestones, and handoff, we are glad to walk you through it on a scoping call.
Next step
See how a fixed-scope engagement runs, then talk scope.
- How we work, step by step: /process
- Web & Product Engineering: /services/web-product-engineering
- Related reading: How to Choose a Software Development Company
- Start a project: /contact