A head of people becomes necessary when managerial load and employment administration both exceed what founders can absorb, which usually coincides with the emergence of a management layer rather than with a specific headcount. Before that point, most of the work is administrative and is better served by a people operations hire, an outsourced payroll provider, and local employment counsel.
The people function is the one founders most often hire either too early, at a seniority the company cannot use, or far too late, after several avoidable problems have already happened. Part of the confusion is that the title covers at least three distinct jobs: administering employment correctly, supporting managers who are new to managing, and designing how the organization works. Those arrive at different times and are done well by different people. This guide separates them so you can hire the one you actually need.
At the strategic end, the role owns how the organization is designed and how people move through it: what levels exist and what they mean, how performance is assessed, how managers are developed, how compensation philosophy is applied consistently, and how the company responds when something goes wrong between two people. This is judgment work that scales poorly and matters enormously once there are managers.
At the operational end, the role owns the machinery: employment contracts, onboarding, payroll accuracy, benefits administration, leave tracking, record keeping, and compliance with employment obligations that vary by jurisdiction and change over time. This is precision work with an unforgiving failure mode, since payroll and statutory errors damage trust immediately and can create legal exposure.
The two ends require genuinely different people. A senior organizational thinker who is bored by payroll accuracy will let it drift, and a meticulous operator asked to design a management development approach will produce something copied from a previous employer. Deciding which end your company needs first is the whole decision, and most early companies need the operational end.
The clearest trigger is a management layer existing. Once you have people managing people, you have created a set of problems that did not exist before: inconsistent expectations between teams, managers who have never managed making predictable mistakes, and employees whose experience of the company now depends on which manager they got. Somebody has to make that consistent, and it is not a part-time founder activity.
The second trigger is administrative surface area, which grows with jurisdictions rather than with headcount. Ten people in one country is manageable with a payroll provider and occasional counsel. Ten people across four countries involves four sets of employment rules, four payroll arrangements, and four sets of statutory obligations, and it needs someone whose job is to keep track.
The third trigger is frequency of judgment calls. Count how many times last quarter someone brought you a question about pay fairness, a difficult conversation between colleagues, a leave situation, a performance concern, or a policy that did not exist. When those arrive weekly rather than occasionally, and each one consumes a founder afternoon plus a call with an advisor, the load has become a role.
For most companies, yes. A capable people operations hire handles the machinery: onboarding that works, contracts issued correctly, payroll running on time, records that survive scrutiny, and the day-to-day questions that currently interrupt a founder. That removes the majority of the volume at a fraction of the cost of a senior leader.
The limit of that hire is judgment on contested questions. When two managers disagree about a level, when a compensation decision has fairness implications across a team, or when a serious employee relations matter arises, an operations-focused hire will correctly escalate rather than decide. If those situations are frequent, you have outgrown the operations-only structure.
A common intermediate arrangement is an experienced people operations hire supported by an external advisor or fractional senior person for the judgment questions, with employment counsel retained for anything with legal implications. This buys most of the capability at a fraction of the commitment, and it works well until the volume of judgment questions makes the advisor arrangement the bottleneck.
Put the hiring plan into a system your team can actually run
Free 1-user plan · No credit card
Payroll processing and statutory filings are specialist, jurisdiction-specific, and unforgiving, which makes them a natural fit for a provider. Benefits administration and employment contract templates are similar. What you cannot outsource is deciding what your company does, which means someone internal still owns the choices even when the execution sits outside.
Where you employ people in a country you have no entity in, an employer of record arrangement handles the legal employment relationship on your behalf, with the associated cost and the constraint that some terms are set by the provider rather than by you. Whether this fits depends on your headcount in that country, how long you expect to be there, and local rules, and it is a decision to make with advice rather than from a general principle.
Employment law advice should be bought locally and specifically rather than generalized. Rules on notice, termination, working time, classification, data handling, and mandatory benefits differ substantially between countries and sometimes between regions, and a policy copied from another market is a liability rather than a shortcut. Budget for counsel in each jurisdiction where you employ anyone.
Match seniority to the decisions you actually need made, not to the title of the person who held the role at a company you admire. Hiring a leader whose experience is in running a function of thirty into a company of thirty total produces someone with no team, no budget, and a mandate to build process the company is not ready to absorb.
The failure mode with an over-senior hire is process arriving before it is needed. Performance cycles, competency frameworks, and engagement programs are useful at a certain scale and are overhead below it, and a senior hire will build what they know how to build. The failure mode with an under-senior hire is escalation: every judgment call still lands on you, which was the load you were trying to remove.
A workable test is to write the five hardest people decisions you expect in the next year and ask whether the candidate has personally made decisions of that kind, at roughly that scale, with those constraints. Not whether they have worked somewhere that had them. Personally made.
Give them a real situation from your company, anonymized, and ask what they would do and what they would need to know first. The quality of the questions they ask before answering is more revealing than the answer, because good people leaders are conspicuously reluctant to prescribe before understanding, and weak ones reach immediately for a framework.
Probe operational precision separately from strategic thinking, because interviews naturally drift toward the strategic and the operational failures are what hurt soonest. Ask how they have handled a payroll error, what they check before an offer goes out, how they keep records that would withstand scrutiny, and what has gone wrong on their watch and what changed afterward.
Test their posture toward risk and jurisdiction. Ask what they would do about a policy question in a country where the company has never employed anyone. The answer you want involves finding out what applies locally before acting. An answer that confidently generalizes from another market is the specific failure mode that creates exposure.
An accurate picture first. Every employment contract located and checked, payroll and statutory filings verified as current in each jurisdiction, records consolidated, and a written list of what is missing or inconsistent. This is unglamorous and it is where the real risks are found, usually in contracts issued at different times with terms nobody remembers agreeing.
Then the highest-frequency process fixed. Usually that is onboarding, because it happens repeatedly, it is visible to every new joiner, and it is the process most likely to be a founder improvising each time. A written onboarding sequence that runs without founder involvement pays back within a handful of hires.
Resist a full framework rollout in the first quarter. A new leader introducing levels, a performance cycle, and a compensation structure simultaneously will spend all their credibility on process rather than on becoming the person managers bring problems to. Ask instead for the two changes that would most reduce risk and the two that would most help managers, and sequence the rest across the year.
Pitch N Hire is an applicant tracking system. Run job posting, screening, structured interviews, and offers from one pipeline — starting free for 1 user.
Free for 1 user · No credit card · Talk to a real hiring expert
Pitch N Hire gives a founder-led hiring process the structure it needs — one pipeline, structured interviews, and a record of every candidate. Start free with the 1-user plan.
Prefer to talk? Book a demo · Talk to sales · View pricing
Free 1-user plan · No credit card · Talk to a real hiring expert
See your true cost-per-hire and how much Pitch N Hire could save you — our free Recruitment ROI Calculator gives you the numbers in under a minute. No signup required.
Open the free ROI calculatorPrefer a tailored walkthrough on your real roles? Drop your work email:
★ Free 1-user plan · No spam · Talk to a real hiring expert
