India capability centres fail for boringly consistent reasons. Not cost, not talent supply, and almost never technology. They fail because the first five hires were mediocre, because the parent company treated the site as a cost centre for eighteen months, or because nobody owned compliance until the first notice arrived.
What follows is the plan we use with clients standing up sites of thirty to three hundred people. It assumes you want a genuine capability centre, a place that owns outcomes, rather than a staff-augmentation arrangement wearing a nicer name.
Decision one: entity or employer-of-record
You do not need a legal entity to start hiring in India. An employer-of-record arrangement lets you make offers within days while incorporation proceeds in parallel, and it is the right choice for the first six to eighteen months in most cases.
| Factor | Employer of record | Own entity |
|---|---|---|
| Time to first hire | 2–3 weeks | 10–16 weeks |
| Setup cost | None | Moderate, plus ongoing statutory audit |
| Per-head cost | Premium of 8–15% | Lowest at scale |
| Break-even | N/A | Typically 45–70 people |
| Employer brand | Weaker, hiring under a third party | Full control |
| Best for | Months 0–12, proving the model | Committed sites past first cohort |
The mistake we see most often is choosing the entity route first and losing four months of hiring momentum to paperwork. Start on employer-of-record, incorporate in parallel, and transfer employment when the entity is ready. Candidates accept this readily when it is explained honestly.
Decision two: which city
Location choice should follow talent density in your specific discipline, not aggregate market size. A firm hiring embedded and automotive software will do better in Pune than in Bengaluru, whatever the headline numbers say.
- Bengaluru: deepest product engineering and platform pool in the country. Highest cost and highest attrition; expect to compete with every well-funded company on the subcontinent.
- Hyderabad: strong across cloud, data and enterprise, with a meaningfully lower attrition profile and a state administration that is genuinely easy to work with. Our most common recommendation for a first site.
- Pune: the strongest bench in embedded systems, automotive and industrial software, with good depth in payments engineering.
- NCR: product, fintech and design talent, with the largest concentration of consumer-internet experience.
- Chennai: deep enterprise applications, QA and BFSI operations at the lowest cost of the major hubs.
Decision three: the first ten hires
This is the decision that determines everything downstream, and it is where most parent organisations under-invest. Your first ten people set the technical standard, the cultural norms and, critically, the calibre of everyone they will subsequently attract.
Hire a site leader first, and hire someone who has built a site before rather than someone who has only run a team inside one. Then two anchor engineers of unambiguous seniority, because strong engineers join places where strong engineers already work. Only then start on the broader cohort.
Sites that hired their first two senior engineers below the 75th percentile of the band took, on average, seven months longer to reach forty people.
The twelve-month plan
| Phase | Focus | Outcome |
|---|---|---|
| Months 0–1 | Location study, compensation benchmarking, EOR selection, role architecture | Signed plan and budget |
| Months 1–3 | Site leader search; employer brand foundations; entity incorporation begins | Site leader offer accepted |
| Months 3–5 | Two anchor senior engineers; office or flexible workspace secured | Technical standard established |
| Months 4–8 | First cohort of 10–25; onboarding and buddy programme; work transfer begins | First outcome owned locally |
| Months 6–9 | Entity operational; employment transferred from EOR; payroll and statutory in-house | Full local employment |
| Months 8–12 | Scale to target; local leadership layer; retention and career frameworks | Self-sustaining site |
The compliance calendar
India's statutory obligations are not difficult, but they are unforgiving about dates. If you take nothing else from this piece, take the fact that these need an owner from the first employee, not the fiftieth.
- Provident Fund and ESI: monthly contribution and filing, with employer registration required before the first payroll run.
- Professional tax: state-specific, with different rates and calendars in each state you employ in.
- TDS on salaries: monthly deposit and quarterly returns, plus annual Form 16 issuance.
- Shops and Establishments registration: municipal, required per premises.
- POSH compliance: an internal committee and an annual report are mandatory above ten employees, and this one is checked.
- Gratuity provisioning: accrues from day one even though it vests at five years.
What makes a site stick
- Give it a real charter. A site that owns a product area retains people. A site that receives tickets from headquarters does not, at any salary.
- Put a decision-maker in the timezone. If every meaningful call waits for a call with the parent country, your best people will leave inside eighteen months.
- Invest in the employer brand locally. Your global reputation means little in a market where nobody has heard of you. Engineering blogs, meetups and a visible local leadership presence move response rates more than any recruiter can.
- Build the career framework early. Levels, expectations and a visible path to the next one. Ambiguity here is the most common reason strong second-year engineers start listening to calls.
Planning an India site?
Memsolos has stood up eleven capability centres from first hire to steady state. We can run the location study, benchmark your compensation, handle employment through our employer-of-record partners and deliver the hiring, or simply advise and let your own team execute.
