.png)
How Can Operations Leaders Scale an India Team Beyond 25 Employees?
Twenty employees is the exact headcount at which the Employees' Provident Funds and Miscellaneous Provisions Act, 1952 becomes mandatory for most Indian establishments. This is why operations leaders scale an India team beyond 25 employees only to discover that the informal setup built for 15 people, a shared spreadsheet, one payroll contact, a WhatsApp update group, cannot legally or practically support 30.
Why Do India Teams Hit a Wall Past 20 Employees?
Most India teams crossing 25 people are Global Capability Centers (GCC) or offshore engineering arms of a US or European parent, concentrated in Bengaluru, Pune, and Hyderabad, cities that together hold well over half of India's GCC headcount. Demand has also shifted: companies are no longer just scaling generic software teams, they are scaling AI and machine learning platform teams, cloud infrastructure teams, and data engineering teams, often faster than compliance processes can keep pace.
The wall shows up in three places at once. Registrations ignored under a smaller headcount become mandatory and get audited, the Karnataka Shops and Commercial Establishments Act, 1961 licence is a common gap we find past 20 employees. Payroll built for 15 people starts producing errors, ESI filings get missed because nobody tracks which employees cross the ₹21,000 gross monthly wage threshold. And managers who comfortably led 8 people suddenly manage 20, with no added support.
We saw this with a UK enterprise software company scaling its Pune team from 18 to 34 engineers in nine months. Payroll compliance was handled correctly by its EOR partner. The real problem was structural: every hiring and performance decision still routed through one manager in London. By the time headcount hit 30, three senior engineers had resigned in a single quarter, all citing the same reason, no local leadership.
Which Indian Cities Can Support a Team Beyond 25 Employees?
Bengaluru has the deepest mid to senior engineering bench for cloud, backend, and AI platform roles, built by years of GCC presence from major global tech companies. Hyderabad has similar depth in SAP, enterprise Java, and data engineering, driven by long-established GCCs. Pune is strong in embedded systems, automotive software, and full-stack engineering, though its senior bench thins out past 40 to 50 employees, often requiring a second hiring channel in Bengaluru or Chennai.
This is also where contract hiring and full-time hiring start to matter differently. Contract hiring suits short-term ramps, a launch, a migration, or a temporary skill gap, adding capacity fast without long-term statutory obligations. Full-time hiring suits core, retained roles, the engineers and leads still on the team two years from now, since it builds institutional knowledge and lowers the attrition risk that comes from repeatedly re-onboarding contract talent into a growing structure.
What we test for also changes here. Below 20 employees, we vet individual skill. When operations leaders scale an India team beyond 25 employees, we vet whether a candidate has actually worked inside a structured, process-driven team, sprint cadence, on-call rotation, formal code review, because the most common failure is a strong contributor who has only worked informally and struggles once structure appears.
What Legal Rules Apply When Operations Leaders Scale an India Team Beyond 25 Employees?
Three laws govern almost everything that changes past 20 to 25 employees in India.
The Employees' Provident Funds and Miscellaneous Provisions Act, 1952 becomes mandatory at 20 employees and stays mandatory permanently, even if headcount later drops. Registration with the EPFO should follow within roughly 15 working days. The most common mistake is counting only full-time engineers toward this threshold and missing that contractors and interns on payroll count too.
The Payment of Gratuity Act, 1972 applies at 10 or more employees, so most teams are already covered before 25. What changes at scale is exposure, gratuity accrues at roughly 4.81 percent of basic salary per year of service, and a 25-plus employee team with multi-year tenure needs that liability tracked through an approved gratuity trust rather than paid from working capital when someone leaves.
This is also where contract versus full-time hiring carries legal weight. A genuine contract arrangement, structured through a staffing partner, does not automatically trigger EPF or gratuity obligations on the client company. But if a "contractor" is functionally an employee, fixed hours, direct supervision, no independent business risk, labour authorities can reclassify the relationship, making EPF, ESI, and gratuity liabilities retroactive.
If you are approaching this compliance threshold, reach our team directly for a structured audit before your next hiring round.
20 to 50 Employee Scaling Checklist for India Teams
This is the exact checklist we use whenever operations leaders scale an India team beyond 25 employees. Use it as a gating list before signing your next batch of offer letters.
Headcount Trigger | What Becomes Mandatory | Who Owns It | Lead Time |
10+ employees | Payment of Gratuity Act applies | Finance / HR | Track from day one |
10 to 20 employees | ESI Act applies up to ₹21,000/month gross | HR / Payroll | 15 working days |
20+ employees | EPF Act becomes mandatory permanently | HR / Finance | 15 to 30 working days |
20+ employees | Dedicated HR or compliance headcount justified | Operations leader | 4 to 6 weeks |
25+ employees | Second-line engineering management needed | Engineering leadership | 8 to 12 weeks |
30+ employees | State Shops and Establishments, Professional Tax filings get audited | Legal / Finance | Should already be filed |
40 to 50+ employees | EOR-to-entity cost crossover point | Finance and operations leader | 3 to 4 months |
Almost every trigger between 10 and 25 employees is a compliance trigger. Almost every trigger between 25 and 50 is a people-structure trigger. Tracking only one leads either to an audit or a burned-out management layer, so review both monthly, since a threshold can be crossed mid-quarter and the compliance clock starts immediately.
How We Help Teams Scale Past 25 Employees Without Compliance Gaps
At AnjuSmriti Global, we run this transition in three stages.
Stage one, in the first two weeks, is a compliance audit against current and projected headcount, mapped to the thresholds above. Stage two, over the following four weeks, is structured hiring against a deliberate seniority mix, for every 6 to 8 engineers, we bring in one lead-level hire directly rather than promoting internally under pressure. Stage three is an ongoing monthly compliance and attrition review, because past 25 employees, attrition shifts from individual to structural, and catching a pattern in month one is cheaper than catching it in month four.
Here is one scenario, anonymised by industry and size. A European enterprise software company scaled its Bengaluru product engineering team from 22 to 48 people over eight months using an EOR model. At week 14, with headcount at 34, we flagged that ESI filings for 11 new hires had been submitted under the wrong wage bracket, because joining bonuses temporarily pushed first-month gross pay above the ₹21,000 threshold while steady-state pay fell below it.
Left uncorrected, this would have caused a mismatch at the client's next statutory audit. We corrected the filings within the same pay cycle, and the team reached 48 employees on schedule with zero compliance flags at its year-one audit.
What Does It Cost to Scale an India Team Beyond 25 Employees?
For a Bengaluru-based engineering team on an EOR model, a mid-level engineer with 3 to 5 years carries a CTC of roughly ₹18 to 26 lakh annually, or ₹1.5 to 2.2 lakh per month gross, plus EPF at 12 percent of basic and gratuity accrual. A senior engineer or tech lead with 6 to 9 years sits at ₹32 to 48 lakh annually. An engineering manager or principal engineer with 10-plus years typically commands ₹55 to 85 lakh annually.
On top of this, an EOR fee usually runs 8 to 12 percent of CTC per employee, or a flat fee between ₹15,000 and ₹30,000 per employee per month, with volume rates improving past 25 employees. Setting up your own entity instead costs roughly ₹3 to 6 lakh one-time plus ₹12 to 20 lakh annually in ongoing compliance and payroll costs, this is where the EOR-to-entity crossover typically sits, below 40 to 50 employees EOR is usually cheaper per head, above it an owned entity generally wins.
Hiring mix affects this too. Contract hires reduce short-term statutory overhead and add flexibility to scale down, but cost more per person on assignment and carry weaker retention. Full-time hires cost less monthly but carry EPF, gratuity, and notice-period obligations from day one. Most operations leaders reinvest EOR-to-entity savings directly into the second-line management layer rather than into additional headcount.
Conclusion
Demand for AI and cloud platform talent is pushing India teams to scale faster than compliance processes are typically built to handle, and Karnataka and Telangana have both increased enforcement around Shops and Establishments and Professional Tax filings for GCCs that scaled quickly without formalising paperwork. In live mandates right now, we see more operations leaders bring us in at the 12 to 15 employee mark to plan this roadmap in advance, rather than fixing it after the fact. Operations leaders scale an India team beyond 25 employees most successfully when they treat 20 employees as a planning trigger, not a surprise.
If you are approaching this threshold, talk to our team before your next hiring round and get a compliance and structure audit before it becomes a problem.
Interesting Reads:
FAQs
1.When does the EPF Act become mandatory for an India team?
The Employees' Provident Funds and Miscellaneous Provisions Act, 1952 applies the moment an establishment crosses 20 employees, counting contractors and interns on payroll, not just full-time staff. Registration with the EPFO should happen within roughly 15 working days of crossing that number. Once applicable, the obligation continues permanently, even if headcount later drops below 20, which surprises many fast-scaling teams that assume compliance shrinks back down with headcount.
2.What is the difference between contract hiring and full-time hiring past 25 employees?
Contract hiring suits short-term capacity, project ramps, or temporary skill gaps, without immediate long-term statutory obligations attached to the client. Full-time hiring suits core, retained roles that need institutional knowledge and lower attrition risk over time. Past 25 employees, most teams need a deliberate mix of both, since leaning too heavily on contract staff at this scale weakens continuity, team cohesion, and delivery consistency across sprints.
3.At what headcount does an EOR cost more than an owned India entity?
For most mid-market teams, the crossover point sits between 40 and 60 employees. Below that, an EOR's per-head fee is usually cheaper than the fixed cost of running your own entity, payroll, and compliance function. Above it, fixed entity costs spread across enough employees to beat EOR pricing per head, though entity setup removes the flexibility to scale down quickly if plans change.
4.Does the Payment of Gratuity Act apply before 25 employees?
Yes. The Payment of Gratuity Act, 1972 applies once an establishment employs 10 or more people, so almost every team scaling toward 25 is already covered well before it happens. What changes past 25 is financial exposure, since gratuity liability accrues per employee across tenure and needs proper tracking through a gratuity trust rather than being paid from working capital when someone eventually resigns.
5.What compliance registrations are needed to scale an India GCC team?
Beyond EPF and gratuity, teams need ESI registration once headcount crosses 10 to 20 depending on power usage, a state Shops and Establishments licence, and Professional Tax registration in every state where employees are based. Multi-city teams, such as Bengaluru plus Hyderabad, need separate filings, deadlines, and slab rates tracked for each state individually, since none of these registrations transfer automatically between locations.
6.How long does converting from EOR to a full India entity take?
A clean conversion realistically takes 3 to 4 months: 4 to 6 weeks for incorporation and PAN or TAN allotment, 3 to 4 weeks for EPFO, ESI, and Shops and Establishments registrations under the new entity, and 2 to 4 weeks of parallel payroll to confirm every employee's records migrated correctly before the EOR contract formally ends. Rushing this timeline is the most common cause of payroll continuity gaps we see.
7.What management structure do operations leaders need past 25 employees?
Past 25 employees, teams typically need a second-line engineering management layer, roughly one lead for every 6 to 8 engineers, hired directly rather than promoted under pressure during a growth phase. Without this layer, escalations keep routing through one distant manager, which is the most common cause of clustered resignations we see once teams cross this exact headcount threshold in a short span of time.
8.Which Indian cities support scaling an engineering team beyond 25 employees?
Bengaluru has the deepest senior engineering bench for cloud and AI platform roles, built over years of sustained GCC investment. Hyderabad offers strong depth in SAP, enterprise Java, and data engineering. Pune is solid for full-stack and embedded roles but has a thinner senior bench past 40 to 50 employees, often requiring a second hiring channel in Bengaluru or Chennai to keep pace with delivery timelines.
Comments