Outsourcing software development to India: a practical guide for overseas companies

Quick answer

Overseas companies work with Indian software partners in three main ways: a defined project against a specification, a dedicated team that works on your backlog, or engineers embedded in your own team. The essentials are the same for each: a written definition of done, IP that passes to you, an agreed overlap of working hours, data protection terms that match your law, and payment tied to accepted work. Start with one fixed block of work, review the result and the way the team works, then decide whether to grow.

Engagement models

• Defined outputs. You describe the work, the partner commits to outputs against a signed specification, and you pay as each one is accepted. Code Colonies calls this Output Oriented Engagement (O2E).
• Dedicated or embedded team. Engineers and strategists work inside your tools and rituals on problems that are still being shaped. Code Colonies calls this Forward Deployed Engineering (FDE).
• Build partnership. For early stage founders who want a partner across product and engineering, as in The Startup Engine.

Time zones and communication

India Standard Time is UTC+5:30. Agree overlap hours at the start, typically two to four hours a day with your core team, and fix the rhythm: a short daily update, a weekly demo, and a named lead on each side. Written specifications and acceptance criteria matter more across time zones, because they settle questions without a meeting.

Contracts and intellectual property

Your contract should cover, at a minimum:

1. IP assignment. Code, designs and documents pass to you on payment, with repository access from week one.
2. Confidentiality. A mutual NDA signed before you share anything sensitive.
3. Acceptance. How each output is tested and accepted, and what happens if it fails.
4. Payment terms. When invoices are raised and what triggers them. Under 2good.dev there is no advance, and you pay after acceptance.
5. Governing law and disputes. Which law applies and where disputes are heard.
6. Replacement and exit. How a person is replaced and how work is handed over if you end the engagement.

Data protection

If your partner handles personal data, the contract needs data processing terms. For personal data from the European Economic Area, transfers to India rely on safeguards such as the European Commission's standard contractual clauses, because India has no adequacy decision. India's own DPDP Act also applies to processing carried out in India. Keep production personal data out of development where you can, and use masked or synthetic data for testing. See DPDP Act and GDPR.

Invoicing and tax

Indian partners usually invoice overseas clients in US dollars or another agreed currency. Services exported from India are generally zero rated for GST, so no Indian GST appears on the invoice when the export conditions are met. Withholding tax and the treatment of the expense in your own country are questions for your tax advisor.

How to test a partner

• Start with one block of work with a clear output, such as a feature, an integration or a prototype.
• Check the code, the tests and the documentation, as well as the demo.
• Watch how the team handles a change of scope and a missed assumption.
• Talk to the people who will actually do the work, as well as the sales lead.

At Code Colonies, one block is 150 hours at USD 2 an hour, USD 300 before tax, with senior review, testing and project management included.

Questions and answers

Is outsourcing to India still cost effective?

Rates vary widely between firms. The Instant Estimate shows hours and cost for your project at the published 2good.dev rate, so you can compare like for like.

How do I protect my code?

Own the repository, give the partner access, and make IP assignment on payment a contract term. Remove access when the engagement ends.

Can the team visit us?

Forward deployed engineers and strategists can work on site when the work needs it. Travel is agreed in advance.