By Rakibul Hasan, Moonlab
To outsource software development safely, write a clear scope, agree who owns the code in a contract, keep the code and servers in your own accounts from day one, pay in stages against working deliverables and check references. Most horror stories come from vague scope and no access to the code.
This guide is for owners hiring a freelancer, studio or overseas team. It covers scoping, contracts and IP, working across time zones and the red flags to watch for. This is not legal advice, so have a solicitor or attorney review any contract of real size.
Write a clear scope first
A good brief reduces most risk. Describe the problem, the users, the must have features, integrations, platforms and any deadlines. Add examples, sketches and links to systems you use.
Split the work into phases. Ask for a fixed price for a first phase with defined deliverables, instead of an open ended time and materials arrangement for the entire project. See moonlab.space/guides/mvp-development-guide.
Contracts and IP ownership
Put it in writing. A contract should say what is delivered and when, how and when you pay, how changes are handled and what happens if either side stops.
Intellectual property rules differ by country. In many places, by default the creator, not the client, may own the copyright in custom software unless a written agreement assigns it. Make sure the contract states that you own the code and deliverables on payment, and that the developer has the right to give them to you. Check any open source licenses used. A professional should review this.
- Ownership or assignment of code, designs and documents.
- Confidentiality and data protection terms.
- Payment schedule linked to milestones.
- Acceptance testing and a warranty period for bugs.
- Termination and handover terms.
- A data processing agreement if personal data is handled.
Keep everything in your own accounts
Create the accounts yourself: the code repository (such as GitHub), cloud hosting, domain, app store developer accounts, analytics and any third party services. Invite the developer as a collaborator. Never let the code or hosting live only in the developer's accounts.
This is the single best protection. If the relationship ends, you keep the work. Ask for regular access to the repository so you can see progress as it happens.
Payment and milestones
Pay in stages tied to delivered, working pieces that you can test. Avoid paying everything up front. A modest deposit is normal. Keep a final payment until handover is complete.
Ask for a demo at each milestone, and test it yourself before you pay.
Time zones and communication
Working across time zones can work well with some planning. Agree overlap hours, a main contact, a weekly call and a shared task board. Written updates and short videos help.
Clarify language expectations, working hours and holidays. Communication quality matters as much as coding skill.
Security and data protection
Give the minimum access needed and use separate accounts, not shared passwords. Ask how they handle secrets and customer data. If the developer handles personal data of UK or EU people, GDPR requires a proper agreement and care about where data goes.
Ask for the use of test data, not live customer data, during development.
Red flags to watch for
Be cautious if you see any of these during the sales process.
- A very low price with a vague scope.
- Reluctance to put things in writing or sign a contract.
- No portfolio or references you can contact.
- Pressure to pay a large amount up front.
- The code or hosting only in their accounts.
- No testing or no plan for support after launch.
- Promises that sound too good, such as everything in a week.
A worked example and common mistakes
Here is a made-up example. A recruitment agency in Birmingham wants a candidate portal. They get three quotes, one very cheap, one mid range and one expensive. The brief was one page, so the quotes differ because each team assumed different features. The owner rewrites the brief with user stories, screens and an integration list, and asks all three to quote again.
The mid range studio provides a fixed price for phase one, a milestone plan, a sample contract that assigns the code to the agency on payment, and two references. The owner phones one reference. She creates the GitHub organization and cloud account herself and adds the studio as collaborators. She pays a deposit, then a payment at each milestone after a demo and her own test.
The team works in a different time zone, so they agree a daily written update and a weekly video call at an hour that suits both. Test data is used, not real candidate data. At the end she receives the repository, setup notes and a recorded walkthrough, and asks a freelance developer to do a one hour check that the code runs from her accounts.
These are the errors that cause trouble later.
- Choosing on price alone.
- A one page brief that leaves scope open.
- No written assignment of intellectual property.
- Hosting and repository in the vendor's name.
- Paying most of the fee before seeing working software.
- Real customer data used for testing.
- No handover documentation.
- Ignoring the time zone gap until it causes delays.
How to decide and what to do this week
Before you sign, check each of these items. If any answer is unclear, ask for it in writing and give it time before you pay a deposit.
- Does the contract assign ownership of the code to you on payment?
- Are the repository, hosting and domain in your accounts?
- Is the first phase fixed price with clear deliverables?
- Have you spoken to at least one past client?
- Is there a warranty period for bugs after delivery?
- Is there a handover plan and documentation in the price?
How Moonlab can help
Moonlab builds in your own accounts with a fixed price and handover. See moonlab.space/services/custom-build, moonlab.space/services/app-development and moonlab.space/guides/mobile-app-development-cost.
A free 30-minute automation audit at moonlab.space/contact is a low risk way to see how we work.