Contracts2 min read
What to check before you sign with a developer.
Code ownership, accounts, milestones and the lines that save you later.
Read this before the contract, not after a problem
Most disputes between founders and developers aren't about bad intentions. They come from things nobody wrote down. A few clear lines in the agreement save a lot of stress later.
This isn't legal advice. For anything serious, have a lawyer read the contract. But these are the points worth checking yourself first.
Who owns the code
The agreement should say that the code, designs and everything made for your product belong to you once you've paid for them. It should also say you'll get the full source code, not just a working app.
Whose name the accounts are in
Domain, hosting, app store developer accounts, payment gateway, email service, analytics. All of these should be registered to you or your company, with the developer added as a user.
If they're in the developer's name and the relationship ends, getting them back can be slow and painful.
What's included, and what isn't
The scope should list the main features and screens. Look for what's missing as much as what's there. Common gaps: design, testing on different phones, publishing to the stores, content entry, and fixes after launch.
Pay in steps tied to working software
Avoid paying most of the money up front. Split payments across milestones, and tie each milestone to something you can actually use and check, not "backend 50% done".
A small first milestone also shows you what working together is like before the big commitment.
Changes and extra work
Your plans will change once you see the product. That's normal. The agreement should say how changes are estimated and approved, so a new request doesn't turn into a surprise bill.
After launch
- How long are bugs fixed for free after launch?
- What does ongoing support cost, and what does it cover?
- How fast will they respond if the app goes down?
If things don't work out
Check how either side can end the agreement, what you pay for work done so far, and that you get the code and accounts handed over either way. Nobody likes thinking about this at the start. It's still the easiest time to agree on it.