From 10 to 100 Employees in India: The Operations Playbook Every Global Company Needs

Scaling a team in India from 10 to 100 people is one of the most operationally complex phases any global company faces. The challenges aren't just about hiring - they're about building the compliance infrastructure, process discipline, and operational systems that prevent a fast-growing India entity from becoming a liability.

Most companies get the hiring part right. What trips them up is everything underneath it: statutory registrations that were never renewed, payroll run off a spreadsheet that quietly breaks at 30 people, an IT function that doesn't exist until someone asks “who manages our laptops?” By the time the gaps surface, they're expensive to fix and sometimes impossible to fix quietly.

This playbook walks through what changes at each stage of growth; from the first 15 hires to the 100-person mark, and what a global company scaling operations in India needs to have in place before it becomes a problem, not after.

The Foundation Phase (1–15 Employees)

Every India entity's operational health is set in this phase, whether anyone realizes it or not. The decisions made here, often by a small founding or country-launch team focused on speed, tend to resurface as constraints two or three years later.

Legal entity registration and the mistakes that haunt you later

The structure chosen at incorporation (wholly owned subsidiary, branch office, liaison office) determines what the entity can and can't do commercially, how it's taxed, and how much regulatory overhead it carries. Getting this wrong doesn't just mean paperwork - it can mean re-incorporating, which is slow, costly, and disruptive to a team that's already operating. Common mistakes at this stage include registering in a state that doesn't match where the actual workforce will sit, misjudging the entity type against long-term commercial plans, and treating registration as a one-time task rather than the first link in an ongoing compliance chain.

Essential statutory registrations

A functioning India entity needs several registrations in place before the first payroll cycle runs cleanly:

• PAN (Permanent Account Number) - the entity's tax identity.
• TAN (Tax Deduction and Collection Account Number) - required to deduct and deposit TDS.
• GST (Goods and Services Tax) registration - mandatory once turnover or activity thresholds are crossed.
• PF (Provident Fund) - mandatory once employee count crosses the statutory threshold.
• ESI (Employee State Insurance) - mandatory based on employee count and wage thresholds.
• PT (Professional Tax) - a state-level levy, with rules that vary by state.

Each of these has its own filing calendar, its own penalties for delay, and its own renewal or update triggers when the business changes. Missing one doesn't usually cause an immediate problem — it causes a delayed one, discovered during an audit or a due diligence process, by which point interest and penalties have compounded.

Getting employment agreements right from hire one

Employment contracts drafted for the first few hires are often reused, unedited, for the next fifty. That's a problem when they were written quickly, don't reflect state-specific labour law requirements, or don't anticipate scenarios like probation extensions, notice period disputes, or IP assignment. Getting the template right early avoids renegotiating with an entire existing workforce later.

Payroll compliance setup - why spreadsheets are the wrong answer

Payroll in India isn't just “calculate salary and pay it.” Every cycle involves TDS calculation, PF and ESI contributions, PT deductions, statutory filings, and Form 16 issuance at year-end - each governed by rules that update periodically. A spreadsheet can survive 10 employees. It cannot survive the state-by-state variation, exception handling, and audit trail requirements that show up by month 12. Companies that start with a compliant, systemized payroll process; even a lightweight one - avoid the retroactive cleanup that un-systemized payroll almost always requires.

The Infrastructure Phase (15–40 Employees)

Somewhere between 15 and 40 employees, informal arrangements stop scaling. The person who was “handling HR on the side” now has a full-time job they were never hired for. This is the phase where functions need to become functions.

When to formalise HR, Finance, and IT as distinct functions

In the foundation phase, one generalist - often the country lead - can plausibly touch all three areas. By 20–25 employees, that stops being true. Each function has its own cadence: HR runs on hiring, onboarding, and people cycles; Finance runs on monthly closes and statutory deadlines; IT runs on provisioning, security, and support tickets. Trying to run all three through one person, even a capable one, creates a bottleneck that shows up as delayed onboarding, late filings, and unresolved access requests.

The GM problem: why your country lead shouldn't own operations

Country managers and GMs are hired to drive commercial outcomes - revenue, partnerships, market strategy. When they're also the de facto owner of HR compliance and finance operations, two things happen: operational work gets deprioritized in favor of commercial work, and the GM ends up accountable for domains they weren't hired to run and may not have deep expertise in. Separating the operations mandate from the commercial mandate isn't just about workload; it's about clarity of ownership when something goes wrong.

HR infrastructure: leave management, performance cycles, grievance mechanisms

At this headcount, HR needs actual infrastructure, not goodwill. That includes a documented leave policy that accounts for state-specific statutory leave requirements, a performance review cycle that's consistent rather than ad hoc, and, critically, a grievance mechanism, including a functioning Internal Committee for POSH compliance, which is a legal requirement once an organization crosses a small headcount threshold, not an optional HR nicety.

Finance infrastructure: monthly accounts, GST, audit readiness

Finance at this stage needs a monthly close process, not a quarterly scramble. That means GST filings happening on schedule, books reconciled monthly rather than retroactively, and documentation maintained in a form that would survive a statutory audit without weeks of reconstruction. Companies that defer this tend to find out how expensive deferral was when the first audit or funding due diligence process arrives.

The Scale Phase (40–100+ Employees)

Past 40 employees, complexity stops growing linearly. State variation, functional depth, and the sheer number of moving parts compounds.

Labour law compliance at scale - state variations, POSH, CLRA

India's labour law framework is not uniform across states - shops and establishments rules, professional tax rates, and specific compliance obligations vary by jurisdiction, which matters as soon as a company has employees or offices in more than one state. POSH compliance needs to move from “a policy exists” to “the Internal Committee is active, trained, and has handled real cases if needed.” Where the entity uses contract labour, CLRA (Contract Labour Regulation and Abolition Act) obligations apply and are frequently missed by companies that assume the compliance burden sits entirely with the staffing vendor.

Finance controls: expense policy, approval matrix, inter-company billing

At 40+ employees, informal expense approval (“just ask your manager”) breaks down. This phase needs a documented expense policy, a formal approval matrix tied to spend thresholds, and for entities that are part of a larger global group - a clean inter-company billing and transfer pricing process that will hold up to scrutiny from both Indian and home-country tax authorities.

IT governance: MDM, access management, quarterly reviews

IT at scale is a governance function, not just a help desk. Mobile Device Management (MDM) becomes necessary once laptop and data volumes make ad hoc device management unmanageable. Access management - who has access to what, and why; needs periodic review, not a one-time setup. Quarterly access and security reviews catch the accumulation of permissions that nobody remembers granting, which is exactly the kind of gap that turns into an incident.

HR formalisation: compensation bands, career frameworks, statutory optimisation

Ad hoc compensation decisions made hire-by-hire in the foundation phase create inequities that surface painfully at scale. This phase needs defined compensation bands, a career framework that gives employees a visible growth path, and statutory optimisation; structuring compensation and benefits in a way that's both compliant and efficient for both the company and the employee.

The Build vs. Partner Decision

Every scaling India entity eventually faces the same question: build the operations function in-house, or partner with a specialist who already runs this infrastructure for other companies.

The true cost of hiring HR, Finance, and IT managers (fully loaded)

Three functional managers - one each for HR, Finance, and IT - represent a meaningful, fully-loaded cost once salary, benefits, tools, training, and management overhead are accounted for. That cost is fixed whether the entity has 40 employees or 90, and it's incurred before any of the three managers has necessarily built mature processes, since each is typically building their function from scratch.

What a single operations partner covers vs. three separate hires

A dedicated operations partner typically covers HR, Finance, and IT operations as an integrated service - with the process maturity, tooling, and compliance calendars already built, rather than being assembled function-by-function over 18–24 months. The comparison isn't just cost; it's time-to-maturity. Three new hires need to build playbooks. A partner already has them.

Compliance continuity during transitions - the hidden risk of in-house models

The risk that's easy to underweight: what happens when the in-house HR manager or Finance lead resigns? In-house models concentrate institutional knowledge - filing calendars, vendor relationships, historical context - in individuals. When they leave, continuity breaks, often right when a filing deadline or audit is due. A partner model is structurally resilient to individual attrition because the knowledge sits with the organization, not one person.

How SLA-backed operations prevents the coverage gaps that create penalties

Where in-house teams can have coverage gaps - during notice periods, medical leave, or simple overload - an SLA-backed operations partner has accountability built into the engagement itself. Deadlines are contractual commitments, not dependent on one person's bandwidth that week.

Real Patterns from India Operations Scaling

Certain failure patterns repeat across fast-scaling India teams, almost regardless of industry.

What the first compliance crisis looks like

It rarely announces itself. It's usually a missed PF deposit deadline, discovered months later, a POSH complaint with no functioning Internal Committee to handle it, or a GST filing that was “someone's job” until that someone left. The common thread: the gap existed for a while before anyone noticed, and by the time it surfaces, penalties or reputational cost have already accumulated.

The IT onboarding bottleneck - why Day 1 matters more than you think

New hires who don't have a working laptop, email access, and system logins on day one form an early impression of the company that's disproportionately hard to undo. As hiring velocity increases, IT onboarding is one of the first processes to buckle, because it depends on coordination across procurement, access provisioning, and security - three things that are easy to keep informal at 10 employees and impossible to keep informal at 60.

Payroll errors at scale - frequency and cost impact

Payroll errors don't stay isolated. An error in how a deduction rule is applied doesn't affect one employee - it affects everyone processed under that rule, that cycle. At scale, a single misconfiguration can mean dozens of affected employees, corrective filings, and a trust cost with the workforce that's harder to fix than the numbers themselves.

How rapid hiring outpaces compliance infrastructure without a dedicated partner

Hiring plans are usually set by commercial targets - revenue goals, delivery capacity, market expansion. Compliance infrastructure doesn't scale on the same timeline unless someone is deliberately building it ahead of headcount. Without a dedicated owner, the two timelines diverge, and the gap between “employees hired” and “compliance infrastructure that can support them” is exactly where risk accumulates.

Building for 100+ Without Rebuilding from Scratch

The goal isn't just to reach 100 employees - it's to reach 100 without needing to rebuild the operational foundation to get to 200.

Operations infrastructure that scales without proportional cost increase

Infrastructure built well the first time - documented processes, systemized payroll, a real compliance calendar - doesn't need proportional new investment at each headcount milestone. Infrastructure built reactively does, because each new stage exposes limitations in the last one.

SLA-driven metrics that give leadership visibility without micromanagement

Leadership at global HQ needs visibility into how the India entity is actually performing operationally - not anecdotes, but metrics: filing timeliness, onboarding turnaround, ticket resolution times, audit readiness scores. SLA-driven reporting gives that visibility without requiring HQ leadership to manage India operations day-to-day

Annual compliance reviews as a scalability audit

An annual compliance review shouldn't just be a checklist exercise - it's an opportunity to audit whether the operational model itself is still fit for the entity's current size, or whether it was built for a 20-person team that's now 80. Treating it as a scalability audit, not just a compliance formality, is what catches structural gaps before they become incidents.

Transitioning from startup-mode to enterprise-grade delivery

The final shift, somewhere around the 100-employee mark, is cultural as much as operational: moving from “we'll figure it out” to “we have a system for this.” That shift is what separates India entities that scale smoothly from 100 to 300 employees from those that hit the same compliance crisis at every new milestone.

Scaling in India Cleanly Requires Deliberate Architecture

Scaling in India cleanly requires deliberate operational architecture - not reactive hiring. The companies that do it well have one thing in common: they partnered with an operations specialist early and gave them the infrastructure mandate, rather than assembling one function at a time under pressure.

OpsMaven has guided many global companies through every phase of India operations scaling - from the first statutory registration to enterprise-grade delivery at 100+ employees.

Visit opsmaven.com to speak with our team about your specific situation.