Outsourcing guide
Outsourcing software development to India: a practical playbook for buyers
Outsourcing software development to India works when you choose the right engagement model, own the code and accounts from day one, assign IP in writing, pay per milestone and agree a daily overlap window. Most failures trace back to vague scope or weak contracts, not to geography. This guide covers each step, from contract to the first 30 days.
- Time zone
- IST is UTC+5:30
- Safest start
- One paid milestone
- Must have in writing
- IP assignment to you
- Pay
- Per milestone, never all upfront
Updated · By the Codebrix team
What to be realistic about
Buyers in the US, UK, EU and Australia usually look at India for the price and the size of the developer market. Both are real. What is also real is that quality ranges from excellent to very poor, and the price alone tells you little about which end you are dealing with. The vendor's process, the people who will actually write your code and the contract you sign decide the outcome far more than the country does.
Treat the decision the way you would treat hiring a contractor at home. Check work, talk to the engineer, start small and keep control of everything that matters: the repository, the cloud accounts, the domain and the app store listings.
Engagement models: fixed price, time and materials, dedicated team
| Model | How you pay | Best for | Risk sits with | Watch out for |
|---|---|---|---|---|
| Fixed price | Agreed price split into milestones | Clear scope: a website, an MVP with a written feature list | Vendor, for delivering the agreed scope | Padding in the quote, and change requests for anything unlisted |
| Time and materials | Hours or days worked, invoiced regularly | Evolving products, research, unclear scope | You, for how long it takes | No ceiling on cost; ask for a cap and weekly hour reports |
| Dedicated team | A monthly fee per person | Long-running product work with your own product manager | You, for direction and output | You must manage them like your own staff, or output drifts |
A common pattern is to start fixed price for a defined first release, then move to a monthly retainer or dedicated arrangement once both sides understand the product. If you cannot yet write down what the first release includes, pay for a short discovery phase first. Our MVP scoping guide shows how to get to that list.
Contracts and IP: what to put in writing
Most buyers sign a master services agreement (the legal terms) plus a statement of work for each project (the scope, milestones and price). Whatever the format, these clauses matter most:
- Assignment of IP: an explicit clause assigning copyright and other rights in the code, designs and documents to you, effective on payment for each milestone.
- Do not rely on 'work made for hire' wording alone. Under US law, a commissioned work only counts as work made for hire if it falls in one of nine listed categories and both sides sign a written agreement saying so, and software is not one of those categories. Use an assignment clause as well.
- Third-party and open-source code: a list of libraries used and their licences, so nothing incompatible ends up in your product.
- Confidentiality: covering your data, your users' data and your business plans.
- Accounts and access: repositories, cloud, domains and store listings created in your organisation's name, with the vendor added as a user.
- Termination and handover: your right to stop after any milestone, keep the work done and receive documentation and credentials.
- Warranty: a bug-fix period after launch and what counts as a bug versus a new request.
- Governing law and disputes: which country's law applies and how disagreements are settled.
- Data protection: what personal data the vendor will touch and how, written with your privacy obligations in mind.
Payments, currency and invoicing
- Pay per milestone, after you have seen and approved the delivered work. Never pay the full amount upfront.
- A small deposit to book the team is normal. A large one before any work exists is a warning sign.
- Agree the invoice currency. Invoicing in your currency moves the exchange-rate risk to the vendor; invoicing in INR moves it to you.
- Ask how you will pay: card or payment platform, or an international bank transfer. Bank transfers can carry fees at both ends, so agree who pays them.
- Ask your own accountant about any withholding tax or reporting your country requires on payments to an overseas supplier.
- Keep the milestone list and the invoice schedule in the same document, so every invoice maps to delivered work.
Codebrix invoices in INR, USD, GBP, EUR, AED and AUD. International clients pay via Stripe or bank transfer, and every payment is tied to a delivered milestone.
Time zones: making the overlap work
Indian Standard Time is UTC+5:30, maintained by CSIR-National Physical Laboratory. The UK moves its clocks on the last Sunday of March and October, and the US moves on the second Sunday of March and the first Sunday of November, so your overlap with India shifts by an hour twice a year. Put both dates in the shared calendar.
| IST | London in winter (GMT) | London in summer (BST) |
|---|---|---|
| 10:00 | 04:30 | 05:30 |
| 13:30 | 08:00 | 09:00 |
| 15:30 | 10:00 | 11:00 |
| 19:00 | 13:30 | 14:30 |
From the UK and Europe there is a natural morning overlap. From the US East Coast, your working day starts as India's ends, so one side has to flex for a short daily call. From Australia, India's morning is your afternoon. Whatever the gap, set these rules early:
- One fixed overlap window of 30 to 60 minutes, used for questions and decisions, not status.
- A written async update at the end of every Indian working day: done, next, blocked.
- A shared channel for quick questions and a project board you can open at any time.
- One weekly demo of working software on a staging link, recorded for anyone who misses it.
Our location pages work out the overlap for clients in the USA, the UK and Australia.
Red flags when choosing a vendor
| Red flag | Why it matters | What to ask |
|---|---|---|
| Price quoted before any questions | They are guessing scope, so change requests follow | What assumptions is this price based on? |
| You never meet the developers | Seniors sell, juniors build | Can I speak to the person who will write the code? |
| Code in their repository until final payment | You cannot inspect or recover the work | Can the repo sit in our organisation from day one? |
| Large upfront payment | Little reason for them to finish | Can we pay per delivered milestone? |
| Portfolio with no live links | The work may not exist or may not be theirs | Which of these are live, and can I contact the client? |
| 'Yes' to every request | Nobody is thinking about trade-offs | What would you cut to hit our date? |
| No written scope or exclusions | Every disagreement becomes an argument | Can you list what is not included? |
How to run the first 30 days
The first month tells you almost everything about a vendor. Structure it so you can stop cleanly at the end if it is not working.
| Week | What should happen | What you check |
|---|---|---|
| 1 | Kick-off call, access set up in your accounts, scope and milestone list confirmed, communication rules agreed | Repository and cloud accounts are yours; the developer you met is on the project |
| 2 | Designs or technical plan shared; first working screens on a staging link | Questions are specific; progress is visible, not just reported |
| 3 | First milestone delivered for your review | It matches the written scope; issues you raise are fixed quickly |
| 4 | Milestone approved and invoiced; short retrospective on what to change | You decide: continue, adjust the process, or stop and keep the work |
- Test on your own devices, not only in the vendor's screen recordings.
- Ask one question that needs a judgement call and see how it is answered.
- Read a pull request or ask an engineer you trust to look at the code for an hour.
- Write down anything that surprised you and raise it in week four, not month four.
We built our own process around this: a 30-minute discovery call, a written fixed-price proposal in two to four days, weekly demos and the option to start with a single paid milestone. See our web app development service for product builds, or get in touch to start with a discovery call.
Frequently asked questions
Is it safe to outsource software development to India?
It can be, if you control the risk the same way you would with any contractor. Keep the code, cloud accounts and domains in your own name, assign IP in writing, pay per delivered milestone and see working software every week. The country matters less than the vendor's process and your contract.
Which engagement model should I choose for a first project?
If you can write down what the first release includes, choose a fixed price split into milestones. If you cannot, pay for a short discovery phase that produces that list, then fix the price. Time and materials suits ongoing work once trust exists. A dedicated team suits companies with their own product manager.
Who owns the code when I outsource to an Indian company?
Whoever the contract says, so make it say you. Include an explicit assignment of copyright and other rights in the code and designs, effective on payment. Do not rely only on US 'work made for hire' wording, which does not cover commissioned software. Keep the repository in your organisation from day one and have your lawyer review the clause.
How do I handle the time difference with India?
Agree one short daily overlap window for decisions, a written update at the end of each Indian working day, and a weekly demo. From the UK and Europe the overlap falls in your morning. From the US East Coast one side must flex. Remember your overlap moves by an hour when your own clocks change.
What currency should I pay an Indian software company in?
Many Indian vendors invoice in USD, GBP, EUR or AUD as well as INR. Paying in your own currency puts the exchange-rate risk on the vendor. Agree who pays bank transfer fees, and ask your accountant whether your country requires withholding tax or reporting on overseas supplier payments.
How do I test a vendor before committing to a big project?
Buy one small, paid milestone: a discovery phase, a design sprint or one feature. Judge the questions they ask, how often you see working software, how they handle feedback and whether the code is in your repository. If it goes well, sign the next milestone. If not, you keep the work and leave.
Sources
Related
Web applications
Custom web application development for portals, dashboards and internal tools
Custom web application development for portals, dashboards and internal tools: roles, Postgres, integrations and tests. Fixed price, code in your name.
Read moreUnited 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 moreUnited Kingdom
Outsourcing web development to India from the UK, without the usual surprises
Outsource web development to India from the UK with GBP invoices, 4.5 to 5.5 hours of daily overlap, and builds planned around UK GDPR and PECR cookies.
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 moreProduct guide
How to scope an MVP you can build in about eight weeks
How to scope an MVP: pick the one assumption to test, prioritise with MoSCoW, cut the rest, follow a sample 8-week plan and track the right metrics.
Read moreAustralia
Offshore web development for Australian businesses, with the small time window planned in
Offshore web development for Australian businesses: AUD invoices, a mapped 2 to 5 hour overlap by city and season, and builds planned around the APPs.
Read more