Signing a Contract With a Software Development Agency in 2026: 10 Pitfalls to Check

A contract with a software agency settles four things you will otherwise argue about later: who owns the code and the accounts, what counts as done, what a change costs, and how you leave. Leave one of them vague and you’ll argue about it when money or time is running short. This guide lists ten pitfalls to check before you sign, with what to ask for and the warning sign in each answer.

It’s a buyer’s checklist, not legal advice. Contract law differs from country to country, so have a lawyer who knows software deals read the final draft. For the working side of the deal, what your team has to own week to week, see how to be a successful partner in software development outsourcing.

The documents you’ll sign

A typical agency deal has three parts:

• An NDA, signed before you share the idea, the code or any data. Ask for it first. A good agency won’t mind.
• A master agreement with the terms that stay the same from project to project: ownership, confidentiality, payment terms, liability and how either side can end the deal.
• A statement of work (SOW) for each piece of work: the scope, the price or rate, the timeline, the team and how you accept the result.

Most of the pitfalls below live in the SOW, or in the gap between the SOW and the master agreement. If the two documents say different things about ownership or payment, ask which one wins before you sign.

The 10 pitfalls at a glance

#	Pitfall	What to ask for	Warning sign
1	Code ownership waits for the last payment	The code in your company’s repository from the first commit, and a clear point when rights pass to you	“You’ll get the source code at handover”
2	Accounts in the agency’s name	Repository, cloud, domain and app store accounts opened under your company	“We’ll transfer them later”
3	No rule for AI-written code	The AI tools the team uses, a human review of every change, a list of open-source licences	“We don’t discuss our tools”
4	Nobody defined “done”	Acceptance checks for each feature and a fixed number of days for you to test	Acceptance by date, not by checks
5	Changes have no process	A written estimate of price and date before any change starts	Changes billed after the fact
6	The price model doesn’t fit the scope	A fixed price only for a clear scope; hourly or a team for a moving one	A fixed price on a one-paragraph brief
7	You don’t know who will build it	Named roles, no subcontracting without your OK, a rule for replacing people	A senior team in the pitch, unknown names in the work
8	Payments tied to dates	Payments tied to working software you can click	A large payment up front for a “phase”
9	Nothing after launch	A period of free bug fixes and a rate for updates	Support “to be agreed later”
10	No way out	Notice period, handover of code, documents and logins, paid hours for questions	Termination only “for cause”

The rest of this guide covers the pitfalls that need more than one line.

Pitfalls 1 and 2: who owns the code and the accounts

Some contracts still hand over the source code only after the final payment. Until then you have paid for most of a product you can’t inspect, give to another team or move. Ask for two things instead. The code goes into a repository your company owns from the first commit, so you can see the work every day. And the contract says when ownership of the code and the designs passes to you, for example as each invoice is paid. Your lawyer will know how to word that where you are.

Accounts matter as much as code. The repository, the cloud account, the domain, the Apple and Google developer accounts and the payment provider should all be opened under your company. If the agency opens them in its own name, you depend on its goodwill on the day you want to leave.

In a classic project with us, the client owns the code, the designs and the accounts, and several clients’ products run on their own AWS accounts. You can ask for an NDA before you share anything. Our outsourcing page lists what we put in writing about IP. There is one exception, and we state it up front: when we pay for a SaaS build ourselves, we keep the code and the IP.

Pitfall 3: a clause for AI-written code

This pitfall is new. In the Stack Overflow Developer Survey 2026, 73% of respondents said they use coding assistants and agents daily. The agency you hire is likely to write part of your code with AI tools, and that raises two questions for the contract.

The first is ownership. In January 2025 the US Copyright Office concluded that copyright does not extend to purely AI-generated material, and that prompts alone don’t give a user enough control to be the author (Copyright and Artificial Intelligence, Part 2). Human selection, arrangement and changes to AI output can still be protected. What that means for your product depends on your country and your deal, which is a question for your lawyer. The question for the agency is simpler: does a person review and edit every change before it’s merged?

The second is licences and quality. In the same survey, 69.3% named “plausible but wrong code” among the AI mistakes that cost them the most time, and 11.4% named uncertainty about licences or sources (Stack Overflow 2026 technology results). So ask for a list of the open-source packages and their licences at every release, and for automated tests that run on every change.

Pitfalls 4 to 6: what “done” means and what a change costs

Write acceptance as checks, not dates. For each feature the SOW should say what a user can do when it works, and give you a fixed number of working days to test it. Then ask for a simple rule: if you find nothing in that window, the feature counts as accepted, and if you find a bug against the agreed checks, the agency fixes it at its own cost.

Every project changes along the way. The contract should say that a change gets a written estimate, with the price and the effect on the date, before anyone works on it, and that nothing outside the SOW gets billed without your OK.

How much this matters depends on the price model. Fixed prices are common for small first versions: in our research, 20 of the 41 agencies that state their own MVP price sell it at a fixed price (Rocketech MVP Price Index 2026). On a fixed price every change reopens the price, which is why fixed price often fails on custom software when the scope is still moving.

Pitfall 7: the team in the pitch and the team in the work

Some agencies sell the project and pass the work to another company. Others put their best people in the sales call and different people on the project. Ask who exactly will work on your product, whether they are the agency’s own staff, and whether the agency may subcontract without your written OK. Check on LinkedIn that the people you met work there, and name the main roles in the SOW.

Then ask what happens when someone leaves, because people do leave in the middle of projects. When a developer dropped out mid-project on Traza, we covered the cost and gave the work to the other developer, so the client’s budget and launch date stayed the same. That is the kind of answer to get in writing.

Pitfalls 9 and 10: after launch and on the way out

Platforms change their rules after you launch. Since 28 April 2026, Apple requires apps uploaded to App Store Connect to be built with Xcode 26 or later (Apple upcoming requirements). Somebody has to do that work and somebody has to pay for it. The contract should say how long bugs in delivered work get fixed for free, and what rate applies to updates nobody could foresee.

Then write the exit while everyone is still friendly. Agree on a notice period, a handover list (code, documents, deploy scripts, logins and the list of outside services) and a number of paid hours for the old team to answer the new team’s questions. If you’re already past that point, our software project rescue page lists what to get back first.

How we would estimate the work before you sign

A scope written as user stories makes most of these clauses easier to write and to keep.

1. Our project estimate turns your brief into user stories. You confirm what’s in scope, and every hour in the budget traces back to a story you kept. That list can become the scope section of the SOW.
2. We check the hours the model suggests against what our team actually books on finished projects, then multiply by our published rate of $39-55 an hour. It’s a planning range, not a fixed quote.
3. When a story changes later, uncheck it and its hours come off, so you can see what a change costs before you raise it.
4. For a new product, the estimate also suggests customer groups and gives each a TAM, SAM and SOM with a note on what the number covers. Treat them as hypotheses to test, not verified demand.

You can run your idea through our project estimate and attach the result to any agency’s SOW, ours included.

What we would do

1. Sign an NDA before you share the idea, code or data.
2. Open the repository, cloud, domain and store accounts under your company before work starts.
3. Turn the scope into acceptance checks, feature by feature.
4. Pick the price model that fits the scope, and write down how changes get priced.
5. Add the AI clause: which tools, human review of every change, a licence list at each release.
6. Write the exit: notice period, handover list and paid hours for questions.
7. Have a lawyer read the final draft.

FAQ

Who owns the code a software agency writes?

It depends on the contract and on the law where you sign it, so put it in writing. Ask for the code to live in your company’s repository from the first commit, and for the contract to say when ownership passes to you. In a classic project with us, the client owns the code, the designs and the accounts.

What should a statement of work include?

The scope as a list of features with acceptance checks, the price or the rate, the timeline, the team and its roles, what’s excluded, how changes get estimated and approved, and how many days you have to test each delivery.

Should a software contract mention AI-generated code?

Yes. Most developers in the 2026 Stack Overflow survey use AI coding tools daily. Ask which tools the team uses, whether a person reviews every change before it’s merged, and for a list of open-source licences at each release. The US Copyright Office said in 2025 that purely AI-generated material isn’t protected by copyright, so ask your lawyer how that affects your deal.

What if the agency won’t open the accounts in my company’s name?

Treat it as a warning sign. You can ask the agency to work inside accounts you create and pay for, and to add its people as users. If it refuses, ask why before you sign, because getting those accounts back later is slow.