Your first HR hire: what the role actually is

A founder of a fifty-five-person business hired an HR executive. She was capable, organised, and within three months was running onboarding paperwork, maintaining the attendance sheet and coordinating interviews. A year later the founder was still approving every leave exception, still deciding every salary personally, and still the only person who knew why two people in similar roles were paid differently.

The hire had not failed. She had done exactly the job that was described. The problem was that the job described was administrative, and the thing that was actually hurting was that nobody had built a system for any of it.

The real trigger

Headcount thresholds are the usual rule of thumb and they are a poor guide, because businesses differ enormously in how much people-work they generate. A fifteen-person business with three shifts and high turnover needs HR capability earlier than an eighty-person professional firm with stable, senior staff.

The reliable signals are behavioural rather than numerical.

• The founder is the bottleneck. Leave exceptions, salary decisions and hiring approvals all queue behind one person's availability.
• Nobody can answer a policy question consistently. Two managers give different answers about notice or probation, both in good faith, because there is no written position.
• Decisions are undocumented and unrepeatable. Why this person is paid what they are paid exists only in one head, which is a risk as well as a workload.
• Things are being discovered late. A resignation that surprises everyone, a compliance date missed, a manager who has not had a conversation with their team in months.

Any two of these together means the capability is already needed. Waiting for the fourth means the first year of the hire is spent on remediation rather than on building.

Builder or operator: decide before writing the advert

This is the decision that determines whether the hire works, and it is usually made implicitly by whoever writes the job description.

OPERATOR  (HR executive / coordinator)
  Runs what exists. Onboarding paperwork, records,
  scheduling, leave administration, coordination.
  Needs: reliability, organisation, follow-through.
  Right hire WHEN THE SYSTEM ALREADY EXISTS.

BUILDER   (HR manager / HRBP)
  Decides what should exist and builds it. Policies,
  pay structure, hiring process, manager capability.
  Needs: judgement, ability to say no to a founder,
  experience of having done it before.
  Right hire WHEN THERE IS NOTHING TO OPERATE.

MOST FIRST HIRES SHOULD BE BUILDERS.
MOST FIRST HIRES ARE OPERATORS, BECAUSE THE PAIN
IS ADMINISTRATIVE AND THE BUDGET IS TIGHTER.

The mismatch is understandable. Administrative pain is what the founder feels daily, so the request is for help with it. But an operator hired into an environment with no defined processes will invent them ad hoc while under pressure, and the business ends up with a system that nobody designed and that is hard to change later.

A builder costs more and is harder to find at this level, particularly someone willing to work without a team. The compensating factor is that the administrative load can often be absorbed by a part-time person or a system, whereas judgement cannot. Where neither option is affordable outright, the split is worth considering explicitly rather than defaulting to the cheaper hire — bringing in HR management consulting to design the system once, then hiring an operator to run it, costs less in total than hiring a builder and frequently less than hiring an operator and living with what they improvise.

What the first ninety days should produce

The most common failure after a good hire is an unclear first quarter. A capable person arrives, finds twelve things wrong, and starts all of them.

1. 1

   Weeks 1-3: find out what actually happens

   Not what is supposed to happen. Sit with payroll at month-end, watch an onboarding, talk to six managers. The gap between the described process and the real one is the map.

2. 2

   Weeks 4-6: fix the two things that hurt most

   Visibly, and finish them. Usually leave and attendance, because they touch everyone and generate the most queries. Two finished processes buy the credibility for everything after.

3. 3

   Weeks 7-10: get the employee data right

   Unglamorous and blocking. Accurate records, reporting lines confirmed by each manager, one source of truth. Every later project depends on it and it never gets easier to do.

4. 4

   Weeks 11-13: agree the next two quarters with the founder

   A short written plan with two priorities, not twelve. This is also where the builder-versus-operator question gets settled in practice, whatever the job title said.

What should not appear in the first ninety days is a strategy document, a competency framework, or an engagement survey. All three are reasonable later and all three, done first, produce a well-regarded new joiner with nothing working.

What the founder has to give up

The hire only works if some decisions actually move, and this is where it most often quietly fails. A founder who hires an HR manager and continues to approve every exception has bought a coordinator at a manager's salary.

The useful conversation before the hire is specific: which decisions will this person make without me. Leave exceptions, probation confirmations, offers within an agreed band, disciplinary process up to a defined point. Written down, as a list, before they start.

Founders find this harder than expected, because people decisions feel personal in a way that operational ones do not, and because the founder has historically been the fairness mechanism. Naming a small set to begin with and extending it is more realistic than attempting a clean handover. Where the difficulty is really that no decision rights are defined anywhere in the business, this is a symptom rather than the problem, and organisation design work addresses it more directly.

The alternatives worth considering first

A permanent hire is not the only route and is not always the right first one.

A fractional or part-time senior HR person gives a business access to judgement it cannot yet justify full-time, which is frequently the better fit at forty to eighty people — the need is for decisions and design rather than for daily throughput. That is the case for fractional HR management at this stage, and the common pattern is a senior person two days a month building the system alongside a junior person operating it.

A consulting engagement to build the foundations, followed by an operator to run them, also works and is sometimes cheaper. It suits businesses that need a defined body of work done once — policies, pay structure, hiring process — rather than continuing capability, and it is the shape most first HR management consulting engagements take.

What rarely works is asking the office manager or a finance person to add HR to their role. It is not a capacity question; it is that the judgement calls in HR are specific and the consequences of getting them wrong are not obvious until later.

Assessing candidates for a first HR role

The distinguishing question is whether they have built rather than administered. Ask for a specific instance: a process they designed from nothing, what the first version got wrong, and what they changed. Someone who has only operated inherited systems will describe how things worked rather than how they were decided, and the difference is audible within two minutes.

Ask also how they have disagreed with a founder or managing director. A first HR hire who cannot say no to the person who hired them will ratify existing practice rather than improve it, which is the most expensive way to fill the role — and it is worth testing directly, because almost everyone claims the capability in the abstract. What you want is an account of a specific occasion, including how it was received.