The question arrives as a headcount question. Are we big enough for HR yet.
Headcount is the weakest available signal. A 40-person company in one state with one entity and low turnover has less people work than a 25-person company across four states that hired 15 people last quarter. Volume of change drives the load, not the size of the org chart.
Four better triggers, and the work worth doing before anyone starts.
The four signals
Compliance surface is growing faster than anyone is tracking it. New states, new registrations, notices and postings that vary by jurisdiction, thresholds that switch on new obligations as you cross them. This one is dangerous because it is silent until it is not, and the person who would notice is the person you have not hired.
Managers are making people decisions alone. Compensation set by whoever negotiates hardest, performance conversations that never happen, terminations handled by instinct. The cost lands later as attrition and occasionally as a claim.
Founders are doing the work badly and at the wrong price. A founder spending eight hours a week on payroll queries and onboarding is the most expensive administrator in the company.
Someone asked for the data and it took a week. Headcount by department, attrition, cost per hire, open roles against plan. If assembling that is a project, you have outgrown the current arrangement regardless of headcount.
Two or more of these together is the signal. One on its own usually is not.
What the role actually absorbs
Be specific before writing a job description, because "HR" covers at least four jobs that rarely sit in one person:
- People operations. Onboarding, offboarding, payroll input, benefits administration, records, compliance calendar. Recurring, systematic, and most of it can be automated.
- Talent. Sourcing, interviewing, closing. Spiky, and driven by the hiring plan rather than headcount.
- Manager enablement. Training, performance frameworks, compensation structure. Judgement work.
- Employee relations. Investigations, difficult conversations, exits. Low volume, high consequence, and the one where inexperience costs most.
Most first hires are asked to do all four. Most can do two well.
Fix this before they start
Hiring into broken systems produces a well-paid administrator, and it is the most common way this decision goes wrong. Someone joins to build the people function and spends their first two quarters reconciling spreadsheets and chasing approvals that should be automatic.
Before anyone starts:
One system of record. If employee data lives in a payroll system, a spreadsheet and a folder, your new hire's first job is reconciliation rather than the work you hired them for.
Automated onboarding and offboarding. These are the highest-volume, most error-prone, most automatable tasks in people ops. Automating them before the hire is what frees the role to be about judgement.
A working compliance calendar. Registrations, filings, notices and renewals, with dates and owners.
Reporting that produces itself. Headcount, attrition and cost, generated rather than assembled.
Do that first and the role you are hiring for changes shape. It becomes a person who builds and advises, which is a better job, attracts a better candidate, and is worth what you will pay for it.
Seniority, and the mistake in both directions
Hiring too junior gets you someone who can run the admin but cannot advise a founder on a termination or design a compensation band. Hiring too senior gets you someone who will spend a year on tasks a system should be doing, and who will leave.
The pattern that works at this size is usually a strong people operations hire once the systems are in place, with senior judgement available on demand for the low-volume, high-consequence work. That gives you daily capability and expertise at the moments it actually matters, which is the shape most companies of 25 to 250 need.
That is the arrangement our people advisory and managed people ops offers exist to cover, either instead of the hire while you grow into it, or alongside a first hire who should not be carrying employee relations alone.
On one page
- Judge by change volume and compliance surface, not headcount.
- Two or more of the four signals means it is time.
- Name which of the four jobs you are actually hiring for.
- Put the system of record, automation, compliance calendar and reporting in place first.
- Hire operations capability, and buy senior judgement by the hour until the volume justifies it.
If you are weighing the hire against fixing the systems first, that is a 20-minute conversation and the answer is usually clearer than it looks from inside. Book a call.
Download this guide
Take the whole thing with you.
The whole guide as one PDF you can send to your team. We email it over.
One email, with the PDF attached. Nothing else.
Common questions
Is there a headcount that triggers the first HR hire?
Not a reliable one. A single-state company with low turnover carries less people work than a smaller company hiring fast across several states. Judge by volume of change and compliance surface instead.
Should the first hire be senior or junior?
At 25 to 250 employees the pattern that works is a strong people operations hire once the systems are in place, with senior judgement available on demand for employee relations and compensation design. Too junior leaves you exposed on the high-consequence work, and too senior leaves them doing tasks a system should be doing.
What should be in place before they start?
One system of record, automated onboarding and offboarding, a compliance calendar with dates and owners, and reporting that generates itself. Hiring into broken systems turns the role into reconciliation work, which is why those first hires leave.