Recruitment Is Not HR Strategy
When growing companies talk about HR, the conversation almost always centers on hiring. Roles open. Candidates in pipeline. This is recruitment. It is not HR strategy.
Summary
- Growing companies often judge HR by how quickly seats get filled, which measures recruitment rather than the strategy that decides which roles should exist at all.
- Hiring without that upstream design leaves new hires in ambiguous scopes, keeps output per person flat or declining, and lets compensation costs rise faster than revenue.
- A real HR business partnering function asks whether a problem needs a hire, maps roles to business outcomes, and links workforce planning to financial scenarios.
When growing companies talk about their HR function, the conversation almost always centers on hiring.
How many roles are open. How many candidates are in the pipeline. How fast offers are converting. Which agencies are working. Whether the careers page is doing its job. The HR leader's effectiveness is measured against how quickly seats get filled.
This is recruitment. It is necessary work. It is not HR strategy.
Confusing the two is one of the most common patterns in scaling companies, and it produces a recognizable failure mode. The company fills seats efficiently. Headcount grows. Offers convert at a healthy rate. And the underlying business problems that hiring was supposed to solve do not actually get solved, because nobody was asking whether hiring was the right answer in the first place.
Recruitment is the operational output of an HR function. It is the part that closes requisitions. HR strategy is the upstream work that decides which requisitions should exist, what outcomes those roles need to drive, how they fit into the organizational structure, and what capabilities the company will need to add at each stage of growth.
Recruitment is execution. HR strategy is design.
What Mistaking the Two Produces
Companies that mistake the two end up with a recognizable pattern:
- Roles are opened because someone said they needed help, not because the role's outcome was clearly defined.
- New hires arrive into ambiguous scopes and spend their first quarter figuring out what they are supposed to own.
- Headcount grows but the organization's output per person stays flat or declines.
- Senior leaders find themselves spending more time on coordination than on the work they were hired for, because the structure was never designed to absorb the new people.
- Compensation costs rise faster than revenue, and quietly deteriorate without anyone identifying the cause.
Each of these is a symptom of the same underlying issue. The company has invested in recruitment without investing in the strategy work that should sit upstream of it.
A real HR business partnering function exists to do that upstream work. It asks whether the underlying problem is actually a hiring problem before recommending a hire. It maps roles to business outcomes rather than to org-chart slots. It links workforce planning to financial scenarios so headcount decisions are made with their cost consequences visible. It treats org design as a strategic activity, not an administrative one.
What to ask before you approve the next hire
A founder operating with a real HRBP function can ask:
- What specific business outcome is this new role supposed to drive, and how will we measure it in 90 days?
- Is the underlying issue actually solvable by a hire, or is it a process problem disguised as a capacity problem?
- How does this hire fit into the leadership layer we will need in twelve months, not just the gap we feel today?
- What does our workforce plan look like in three growth scenarios, and how does this hire survive in each?
- Are we designing structure before filling seats, or filling seats and hoping structure emerges?
These questions are rarely asked in companies where HR has been positioned as a recruitment function. They start to get asked when the function has been positioned as a strategic one.
Why finance and people cannot plan separately
At SRF Capital Studio, this is one of the most consistent themes we see in growth-stage companies. The finance function and the people function operate in parallel, and the link between hiring decisions and financial reality stays loose. We work to integrate them. Workforce planning gets built on the same scenarios as the financial plan. Headcount is treated as a strategic investment rather than a tactical fill. Leadership bandwidth is mapped as a real constraint rather than assumed away.
People decisions are capital decisions. Treating them otherwise is one of the most expensive errors a scaling company can make.
Recruitment fills seats. HR strategy decides which seats are worth filling and what they need to deliver to make the company actually scale.
A full org chart is not a built company. It is a list of bets.
The strength of the company is in whether those bets were designed or whether they were just accumulated.
How useful was this article?
One tap. It tells us what to write more of.
The next one
Get what we publish next, by email.
Working notes on raising, borrowing, protecting, growing and structuring capital in India. One email a week at most, and you can leave any time.
We use your address only to send this. See our privacy policy.
We store your address to send you these emails and nothing else. See our privacy policy.
The services behind this article
What we do about it, for founders and finance teams. Each has its own page.
HR Business Partnering
Strategic people operations that align org design and hiring with what the business is actually trying to do.
