The first HR hire at a startup tends to happen six months too late. By the time someone says “we need an HR person,” there’s already an inherited mess: an offer letter template that doesn’t match the most recent grant policy, a handbook that’s two states behind, three open performance issues nobody documented, and a 401(k) compliance gap that the founder doesn’t know exists.
This is not a failure of judgment. It’s that founders look for HR the same way they look for any other hire — when the work piles up enough to justify a headcount. The problem is that the work HR actually does is mostly invisible until something breaks, and by the time something breaks the cost of cleanup is meaningfully larger than the cost of having had the role in place.
This post is about the timing question and the scope question. When should you hire your first dedicated HR person? What should they actually own? And — just as important — what should they not yet own?
What the founder, ops lead, or COO can actually run alone
Up to about 15 employees, you do not need a dedicated HR person. The work is small enough that an operations lead or a founder can absorb it with the help of an integrated payroll stack and a benefits broker. The specific tasks that fit inside this absorption capacity:
- Running payroll every two weeks (15-30 minutes if your stack is set up correctly — see how to administer payroll and 401(k) plans)
- Approving new hire offer letters using a standard template
- Onboarding new employees through Rippling or Gusto’s built-in flow
- Handling benefits open enrollment once a year with broker support
- Approving PTO requests and tracking sick leave
- Filing the annual ACA reporting and W-2 distribution (your payroll provider handles the mechanics)
What allows this to work is the integration of the underlying systems. Rippling, Gusto, Guideline, and a competent broker like Newfront together produce a stack where most of the administrative work runs itself. The founder or ops lead is the human in the loop, not the engine.
This breaks at roughly 15-25 employees. Not because the existing systems stop working — they don’t — but because three new categories of work appear that don’t fit any existing system.
The signals that say it’s time
When founders ask us when to hire HR, we look for these signals. Two or three of them simultaneously usually means it’s time.
You’ve hired in more than 5 states. Each state adds tax registrations, unemployment insurance setup, state-specific paid leave requirements, and minimum-wage compliance. Modern payroll providers handle the mechanics, but somebody has to track the changes — including when an employee moves between states, which triggers a whole separate workflow. Multi-state employment compliance becomes a real operational load somewhere around the fifth state.
You’re approaching 50 employees. A handful of federal laws kick in at this threshold (FMLA, EEO-1 reporting, ACA Applicable Large Employer status). State equivalents kick in earlier in some places (California at 5; New York at 4). The 25-employee mark is when state-level paid leave and harassment training requirements typically activate. You need somebody whose job is to track these triggers and act on them in advance, not after the fact.
You’ve had your first real employee relations issue. A performance management situation that requires documentation. A harassment complaint that needs investigation. A termination that creates legal exposure. The first time one of these happens, founders learn that “we’ll just figure it out” is not a defensible posture. Every subsequent issue requires consistent process applied consistently — which is what HR builds.
Recruiting is consuming more than 10 hours a week of leadership time. Sourcing, scheduling, candidate evaluation, offer negotiation, reference checks. Below 10 hours a week, founders and hiring managers can do this themselves. Above 10 hours a week, it’s eating product or sales time and the ROI of a recruiting-capable HR hire is positive.
You’ve completed a Series A and are planning to scale headcount past 40 within the next 12 months. The hire that takes you from 25 to 50 is dramatically harder operationally than the hire that took you from 5 to 25. Get the function in place before the scaling, not after.
The right first hire: People Operations Manager, not Head of People
The most common mistake we see is hiring too senior, too soon. Founders think they need a “Head of People” or a “VP of HR” because that’s what their later-stage friends have. At Series A and early Series B, that’s the wrong hire.
The right first HR hire is a People Operations Manager — typically 4-8 years of experience, hands-on, operational. Someone who has done payroll, run benefits open enrollment, written handbook updates, managed an HRIS, and handled employee relations cases without needing to delegate any of it. Not a strategist; an operator.
Compensation for this role at Series A/B startups in major U.S. markets typically ranges from $110K-160K base plus equity. Below that range, you’re getting an HR coordinator who needs supervision. Above that range, you’re paying for strategic capability you don’t yet need.
The Head of People hire — strategic, executive-level, equity-band hire — usually makes sense post-Series B, when headcount is over 75 and the operational work has multiplied enough to justify a layer beneath them.
What this role should actually own
A well-scoped first People Ops hire owns:
The HRIS and payroll relationship. Rippling or Gusto as the system of record, with the People Ops manager as the primary admin. This means employee onboarding/offboarding, payroll review and approval, payroll provider escalations, and the integration health with the GL.
Benefits administration and the broker relationship. Quarterly check-ins with the broker, annual open enrollment, plan changes, employee benefits questions, dependent verification. The broker (Newfront, Sequoia, or regional) does the heavy lifting on plan design; the People Ops manager is the broker’s day-to-day counterpart.
401(k) and retirement administration. Working with Guideline (or Vestwell at 100+) on participant enrollment, nondiscrimination testing follow-up, Form 5500 coordination, and contribution remittance monitoring. This is mostly a passive job if the stack is set up correctly — the People Ops manager confirms the automation is working, not running the remittances manually.
Handbook, policies, and compliance calendar. Maintaining the employee handbook, updating policies as laws change, owning the compliance calendar (W-2s, ACA, EEO-1, state-specific obligations), and partnering with employment counsel when needed. See building an employee handbook that actually protects you for the handbook scope.
Employee relations. First point of contact for performance management documentation, leave requests, accommodations, complaints, and terminations. Coordinating with employment counsel on anything legally sensitive.
Recruiting operations. Not necessarily executing the recruiting (that may be a separate hire or contract recruiter), but owning the ATS, the offer letter templates, the equity grant approvals, the reference-check process, and the onboarding handoff.
Performance management cadence. Annual or semi-annual review cycles. 360 feedback. Performance improvement plan documentation. Comp review process support.
What this role should not yet own
Founders often try to load the first HR hire with strategic work they’re personally tired of doing. That’s a mistake. The first People Ops hire is not yet:
- A compensation strategist. Banding, leveling, market data, total rewards philosophy. That’s a Series B/C function. At Series A, you have a published equity band by role and a competitive salary range pulled from data, and you stick to it.
- A culture officer. Engagement surveys, values workshops, off-sites. These are nice-to-haves and they often signal the org is trying to manufacture what should emerge from how leadership operates day-to-day.
- A learning and development function. Training programs, leadership development, career pathing. These start to matter at 75-100 employees, not before.
- A DEI officer. A serious DEI function is a real role and a real budget. Tacking it onto a People Ops manager’s job description as a “and also…” signals it’s not actually a priority. Either hire for it or don’t claim it.
The way to think about scope is: the first HR hire should make 80% of the operational work disappear, and the strategic work should stay with founders or surface as discrete projects the People Ops hire can execute against.
What changes at Series B
The Series B transition is where the function expands. Headcount typically grows past 50 in the year following the raise, multi-state spread accelerates, and the operational load on a single People Ops manager starts to crack.
The natural progression: the People Ops Manager who scaled with you now reports to a Head of People hire (or in some companies, gets promoted into that role if the strategic capability is there). Recruiting moves to a dedicated recruiter or recruiting lead. Compensation strategy becomes its own workstream. The handbook and compliance work might justify part-time employment counsel.
The signals that this transition is overdue:
- Your People Ops manager is consistently working more than 50 hours a week
- Hiring has slowed because the recruiting workflow is bottlenecked
- Performance management is inconsistent across teams
- You’ve had two or more compliance surprises (state law change, audit finding, comp survey result) that should have been anticipated
Plan the upgrade in advance, not in crisis. A Head of People hire takes 4-6 months to source and onboard; the People Ops to Head of People transition takes another 3-6 months to settle.
A note on PEOs and the in-house question
If you’re on a PEO like Justworks, some of what we just described — handbook, benefits admin, compliance — is handled by the PEO. That extends the runway before you need your first in-house HR hire by roughly 6-12 months. The tradeoff: PEOs are expensive at scale (typically $150-200/employee/month or 2-4% of payroll), and they don’t integrate cleanly with modern payroll stacks. Most companies migrate off a PEO in the 25-50 employee range, which is also when the first People Ops hire becomes necessary. See the Series A/B benefits stack for the PEO transition timing.
When to bring in operator support
You probably don’t need outside help if you’re under 15 employees on an integrated payroll stack with a PEO or a competent broker. The HR work is small enough to absorb.
You likely want operator input if:
- You’re trying to decide whether the first HR hire should be a People Ops manager or a Head of People — and the wrong choice will cost you 18 months
- You’re scoping the role itself and don’t want to load it with strategic work that should stay with founders
- You’re transitioning off a PEO and need to set up the in-house function in parallel
- You’ve inherited an HR function from a prior People hire who’s leaving and need to figure out what to keep and what to redesign
- You’re 6-12 months out from Series B and need to plan the People Ops → Head of People transition
Pegacorn Group works with venture-backed Series A and B startups on exactly these transitions. If you’re getting ready to make your first HR hire and want to make sure the scope, level, and timing are right for your stage, let’s talk.
This post pairs with: How to administer payroll and 401(k) plans at a startup, The Series A/B benefits stack, Building an employee handbook that actually protects you, and Multi-state employment compliance.