Why fifty is where most companies first feel the HR gap.
Companies grow through informal systems until those systems break. At ten employees, the founder knows everyone's name, family situation, salary, and aspiration. At twenty-five, things still mostly work through trust and direct communication. At fifty, the organisation has crossed a threshold: the founder can no longer be the HR function, and the company has not yet built a formal one. It is too large to run on relationships and too small to have built the structures that large organisations rely on. This is the zone where most HR problems take root.
The common response is to hire one HR manager, hand them a checklist of tasks, and expect the function to sort itself out. This approach fails not because the HR manager is inadequate but because the organisation does not understand what it is actually asking them to build — or in what order. The result is an HR function that is reactive, perpetually under-resourced, and perceived by the business as a source of administrative friction rather than strategic value.
Scaling HR well — from fifty to two hundred employees — requires understanding what changes at each inflection point and what the HR function needs to look like to support those changes. The four inflection points are at approximately fifty, one hundred, one hundred and fifty, and two hundred employees. Each one changes the demands on the HR function in a predictable way.
The 50-employee stage: build the foundations.
At fifty employees, the priority is to build the baseline HR infrastructure that the organisation has been operating without. This means, in order: a documented policy library, proper employment contracts, statutory compliance processes (PF, ESI, PT, TDS), an HRMS that can handle payroll and basic records, and an onboarding process that is consistent rather than ad hoc.
The mistake companies make at this stage is trying to do everything at once. The founder or the first HR hire attempts to launch a performance management system, a learning programme, an engagement initiative, and a hiring process simultaneously, and finishes none of them properly. The discipline required is ruthless sequencing. Compliance and policy first — because the legal exposure of getting these wrong compounds as the organisation grows. HRMS second — because everything else depends on clean data. Onboarding third — because the experience new employees have in their first thirty days determines retention at the six-month mark. Performance and engagement wait.
The first HR hire at this stage is typically a generalist. They should be operationally strong — able to run payroll, manage vendor relationships, handle statutory filings, and write clear policies — rather than strategically sophisticated. The strategic layer comes later. Hiring a Head of HR at fifty employees because the role sounds important is a common and expensive mistake: the organisation needs someone who can execute, not someone who needs a team to execute for them.
The 100-employee stage: add capability building.
Between fifty and one hundred employees, the organisation typically adds two to four managers per year, runs its first structured performance reviews, begins to notice that some people are growing faster than others, and starts losing people for reasons that have nothing to do with pay. This is the stage at which the HR function needs to move from administration to capability building.
Three things become urgent at one hundred employees. First, manager development. The managers hired at this stage are typically first-time managers — strong individual contributors who have been promoted into leadership without any structured support for the transition. The gap between what they need to do as managers and what they have been trained to do is substantial, and it shows in the engagement data of their teams. Investing in a structured manager development programme at one hundred employees prevents a significant proportion of the attrition that will otherwise occur between one hundred and one hundred and fifty.
Second, structured performance conversations. At fifty employees, performance is managed through direct relationships and informal feedback. At one hundred, the organisation is too large for this to work consistently. Some managers give rich, regular feedback; others give none. The disparity in experience between teams becomes a retention issue. A simple, consistent performance framework — not necessarily ratings, but documented conversations with clear development commitments — creates the floor of consistent practice that the organisation needs.
Third, learning and development investment. At one hundred employees, the organisation typically has enough scale to run internal learning programmes and enough variety in role to create genuine career pathways. Investing in this infrastructure — even modestly — signals to employees that the organisation is committed to their growth, which is a retention signal that matters independently of the content of the programmes themselves.
The 150-employee stage: build talent infrastructure.
The transition from one hundred to one hundred and fifty employees is where organisations either begin to build real talent infrastructure or fall into the pattern of firefighting that defines the next growth phase. The specific challenge is that the organisation is now large enough to have meaningful internal talent — people who have grown in role, developed expertise, and earned the trust of teams — but small enough that there is no formal system for recognising, developing, or retaining that talent.
Internal mobility becomes critical at this stage. The question "what is the next role for this person?" needs to have an answer, and that answer should, wherever possible, be an internal one. Companies that are unable to offer their best people a visible path forward lose them to competitors who can. Building an internal mobility culture — actively surfacing internal candidates before going external, communicating role openings to existing employees first, and building the development conversations that make people ready for lateral moves — is the HR priority at one hundred and fifty that pays dividends for years afterward.
Succession planning, in a rudimentary form, also belongs at this stage. Not the formal talent review processes of large multinationals, but a simple discipline: for every key role in the organisation, who is the person most likely to step into it if the current holder leaves or is promoted? If the answer to that question is consistently "no one," the organisation is building a talent risk that compounds as it grows.
The 200-employee stage: invest in the HR function itself.
At two hundred employees, the HR function is ready — and the organisation typically requires — a more senior, strategically capable leader at its head. The first HR hire, who built the foundations and has been running the function through the growth phase, may or may not be the right person for this role. The question is not one of loyalty or performance, but of capability match: the skills required to build an HR function from nothing are different from the skills required to lead a people strategy at scale, and the organisation needs to be honest about which skills it now needs.
The two-hundred-employee HR function should have: a Head of People with business credibility and a direct line to leadership; an HR business partner aligned to each major function; a talent acquisition capability that can run structured searches without constant external support; an analytics capability — even a basic one — that can track attrition, engagement, and hiring quality over time; and a culture and organisational development practice that is proactive rather than reactive.
“The companies that scale their HR well are not the ones that invest the most. They are the ones that invest at the right moment, in the right sequence, for the right reasons.”
The discipline of right-sequencing — building foundations before capability, capability before infrastructure, infrastructure before strategy — is the single most important principle in scaling an HR function. Companies that try to skip stages create gaps that they spend years trying to close. Companies that sequence well create HR functions that become genuine business assets rather than necessary overhead.
