When Does a Startup Need a People Team?

"People team," "people ops," "HR" — whatever you call it, every startup eventually needs someone to own the function. The hard questions are when, what they should own first, and whether it has to be a full-time hire at all. Get the timing wrong in either direction and you pay for it: too early and you've added six-figure overhead with not enough to do; too late and you've absorbed compliance, retention, and culture costs that were entirely avoidable.

The stages, roughly

People needs scale with headcount, but not linearly — they jump at predictable thresholds.

Under ~10 employees

At this size a founder or office manager can usually handle people work off the side of their desk, with good tools doing the heavy lifting. What matters most here is not building a team but not building bad habits: get your classification right, set up a real payroll/HRIS, and don't make informal promises that become problems later. The risk at this stage isn't volume — it's foundational mistakes that compound.

~10 to ~35 employees

This is where it breaks. People questions start arriving daily, you're likely hiring across state lines (which quietly triggers obligations founders rarely see coming), onboarding is improvised, and the first real employee-relations issues appear. The people work is now genuinely a part-time job — but rarely a full-time one. This is the single most common stage at which companies turn to fractional support, because the work clearly exists but a full-time hire would be underutilized.

~35 to ~75 employees

The function becomes continuous and increasingly strategic — performance systems, comp structure, manager development, culture as the team grows past what everyone-knows-everyone can sustain. Somewhere in this range, a dedicated full-time people hire usually starts to pencil out.

What the function should own first

When you do build the function, sequence it by risk, not by what's most fun:

• Compliance and classification first. This is the highest-stakes, lowest-visibility risk — the stuff that becomes a six-figure problem if ignored. Lock it down before anything else.
• Payroll, benefits, and the right HRIS — the operational backbone everything else runs on.
• Onboarding — because the fastest retention win is not losing people you already hired in their first 60 days.
• Then the people-ops layer — performance, manager enablement, comp structure, culture — once the foundation is solid.

Notice that the glamorous "culture and experience" work comes last, not because it doesn't matter, but because building it on an unstable compliance-and-payroll foundation is building on sand.

Hire, or fractional?

This is the question most founders skip, and it's the one that saves the most money. A full-time people hire at the 10–35 stage is often a poor fit: you pay a $70,000–$90,000 fully loaded salary for a generalist who may be junior relative to your hardest problems (multi-state compliance, a tricky termination) and underutilized relative to your volume. Fractional HR exists precisely for this gap — senior judgment, at the fraction of the volume you actually need, for roughly a quarter of the cost. Many companies run fractional through this entire stage and only hire full-time once the work genuinely fills a role.

The decision framework is simple: if you need senior judgment at low volume, go fractional. If you need daily, embedded, full-time presence, hire. Most startups under 50 employees are squarely in the first category and talk themselves into the second.

The bottom line

You need a people function the moment people work starts pulling a founder away from the business — usually around 10–15 employees. You need a full-time people hire considerably later, usually past 50. In between sits a long stretch where the right answer is senior, part-time, fractional support that keeps you compliant and builds the foundations — without the cost of a department you can't yet justify. Whatever you call it, build it in the right order: risk first, experience second.