Build vs. Partner vs. BOT: How Mid-Size Companies Should Build a Tech Team in India
A practical decision guide for CTOs: when to set up your own Indian entity, when to use a partner, and when Build-Operate-Transfer gives you the best of both.
If you run engineering at a company with a few hundred people, India probably came up the last time a senior role sat open for a quarter. The talent is there. The hard question is how: set up your own entity, hire through a partner, or do something in between.
This guide compares the three realistic routes (build, partner and Build-Operate-Transfer (BOT)) on the factors that matter to a mid-size company: speed, control, risk, cost and long-term ownership. It is written by a firm that offers the partner and BOT routes, so we have tried to be explicit about when building yourself is the better answer.
Option 1: Build your own Indian entity
Building means incorporating a company in India (usually a private limited company that is a subsidiary of your parent) and employing people directly.
What it involves
- Incorporation, with a registered office, directors and statutory filings
- Tax registrations (including GST where applicable) and a transfer-pricing policy between parent and subsidiary
- Payroll registrations and compliance with Indian labour law, including provident fund and gratuity rules
- A bank account, an accountant, a company secretary and an annual audit
- HR policies, employment contracts, leave and holiday calendars, and a way to recruit at all
When it makes sense
Building is usually right when you are confident you will have a large, permanent team in India, when you already have people who know Indian compliance, or when you want India to become a full site with its own leadership. At scale, running your own entity removes a partner’s margin.
The catch
You take on the setup time, the fixed costs and the compliance risk before you know whether the model works for your team. For a company that needs five engineers, the overhead of an entity can be out of proportion to the team it supports.
Option 2: Partner with a provider
“Partner” covers very different models, and the difference matters more than the label.
- Project outsourcing: the vendor delivers a scope and directs the people. You buy outcomes, but you lose day-to-day control, and the team often rotates.
- Staff augmentation: the vendor places people from its bench on your work. It is fast, but people may be shared, swapped or chosen for availability rather than fit.
- Dedicated team (employer-of-record style): the partner recruits people specifically for you, employs them in India, and they work only on your team, under your direction. The partner handles hiring, payroll, HR, devices and compliance.
For most product companies, the dedicated model is the one that fits, because it keeps the thing you care about (who is on the team and what they work on) in your hands.
When it makes sense
Partnering is the faster, lower-risk route when you need a handful of engineers now, want to test India before committing, or simply don’t want to run an Indian company.
The catch
You pay a management fee for as long as the arrangement runs, and you depend on the partner’s hiring quality and retention. Read the contract closely on IP ownership, exclusivity and what happens if you want to leave.
Option 3: Build-Operate-Transfer
BOT combines the two. A partner builds the team, operates it for an agreed period, then transfers it (people, devices and work IP) to your own Indian entity for a fee agreed at the start.
The appeal is sequencing. You get a working team in weeks instead of waiting on an entity, you learn how India works for your company, and you set up your own entity only once you know you want one. The transfer is planned from day one, so ownership isn’t an afterthought.
What to pin down in a BOT contract
- The transfer fee, or the formula for it, and how it changes over time
- The earliest and latest transfer dates, and the notice needed
- What transfers: employees (with their consent), devices, documentation, and confirmation that IP was assigned to you all along
- What doesn’t: the partner’s other business, contracts or liabilities should never come with the team
- Continuity: how employees’ service, leave balances and benefits carry over
How to decide
A simple way to frame it is to answer three questions honestly.
- How sure are you that India is long-term? If you’re very sure and expect a large team, building may pay off. If you’re still testing, partner first.
- How fast do you need people? Hiring in India takes time whichever route you choose, because notice periods are often 30–90 days. Entity setup adds to that. A partner removes the setup time, not the notice periods.
- Do you want to own the team eventually? If yes, but not now, BOT is designed for exactly that.
| Situation | Usually the best fit |
|---|---|
| 2–10 roles, need people this quarter, no India presence | Dedicated team via a partner |
| Expect 20+ people within a few years, want your own site eventually | BOT |
| Large, certain, long-term plan with in-house India expertise | Build your own entity |
| A one-off, well-defined deliverable | Project outsourcing |
These are rules of thumb, not formulas. Your tax position, existing entities and regulatory constraints can change the answer, so involve your finance and legal advisers early.
Questions to ask any partner
- Do engineers work only for us, full-time? Are they employees or subcontractors?
- Do we interview and approve every hire?
- Who owns the IP, and when does it pass to us? Do repos and accounts stay in our name?
- What devices do engineers use? Are they managed, encrypted and protected?
- What happens when someone resigns, and how fast is a replacement?
- Can we see a line-item cost breakdown?
- Can we transfer the team to our own entity, and on what terms?
- Which certifications do you actually hold, and what will you put in the contract?
A good partner will answer all of these in writing. If one won’t, that tells you something.
Where we fit: Jetani Technologies offers dedicated teams, managed GCCs and Build-Operate-Transfer for IT roles in India. If you’d like to talk through your situation, including whether building yourself is the better answer, book a 20-minute call.
This article is general information, not legal, tax or financial advice. Figures marked as illustrative are examples, not market data or a quote.