There's a pattern almost every startup follows. In the early days, "HR" means one thing: hiring. Once you have a team, you trust people to figure things out. Then somewhere between employee 8 and employee 15, something breaks — a performance issue nobody knows how to handle, a dispute about leave, a resignation from someone who felt undervalued and never said so. And suddenly the founder is spending three weeks on people problems that a basic process would have prevented.

The issue isn't malice or incompetence. It's timing. People ops infrastructure feels unnecessary until the moment it's urgently necessary — and by then, you're building it under pressure.

Here's a stage-by-stage framework for what to put in place and when.

67%
of startup founders say they wish they'd formalised HR processes earlier than they did
3×
more likely to retain employees when onboarding is structured vs ad-hoc, per research
~6 mo
the average lag between when founders should build HR infrastructure and when they actually do

Stage 1: 1–5 employees — the fundamentals

At this stage you probably don't need an HR system. But you do need three things in writing, because verbal agreements create disputes and unwritten norms become assumptions.

1–5 people What to put in place now
Written offer letters / employment agreements
Even a one-page document. Cover role, compensation, working hours, and notice period. Without this, the "agreement" is whatever each party remembers.
A leave policy (even a simple one)
How many days per year, how to request, who approves. "Just be flexible" creates resentment when people perceive inconsistency.
A basic onboarding checklist
System access, introductions, first-week goals. The first impression a new hire gets of how organised you are shapes how much they trust the company long-term.

Stage 2: 6–15 employees — where most startups stall

This is the danger zone. The team is big enough that informal coordination no longer works, but most founders haven't made the mental leap from "we're a small team" to "we're an organisation that needs operating infrastructure."

The specific problems that surface in this range:

6–15 people What to add at this stage
An HR system with a single source of truth
Employee records, leave balances, documents, and org chart all in one place. Spreadsheets are not a source of truth — they're a divergence mechanism.
A lightweight performance feedback cycle
Doesn't need to be formal or annual. Even quarterly 1:1 check-ins with documented outcomes. The goal is that nobody is surprised by their performance review.
Compensation bands (informal is fine)
A rough framework for how pay relates to level and scope. Even unpublished, this forces consistency in how you make offers and promotion decisions.
A documented offboarding process
People will leave. Access revocation, knowledge transfer, final pay, exit interview. Handled well, a departure is neutral. Handled badly, it's a brand and legal risk.
The inflection point: Around employee 10, the cost of not having HR infrastructure starts to exceed the cost of building it. Before this, it's optional. After this, you're accumulating technical debt on your people systems just like you can on your codebase.

Stage 3: 16–25 employees — intentional culture

At this size, culture stops being something that happens organically and starts being something you actively manage — or fail to. The founders are no longer in every meeting. Managers are starting to make decisions on behalf of the company without direct oversight. New hires are being shaped by the team culture they encounter, not by the founders' intent.

16–25 people What becomes critical here
Manager enablement
Your first managers are probably great individual contributors you promoted. They need explicit guidance on what "good management" looks like at your company — it won't happen by default.
Pulse surveys or informal sentiment checks
At 20 people, the founder can no longer sense team morale from casual observation. A quarterly 5-question survey gives you signal before problems become resignations.
A documented promotion and levelling process
Once you have multiple layers, people will compare. Documented criteria make advancement feel earned and fair rather than political.

The most common mistake: waiting for a crisis

The trigger for most founders to finally build people infrastructure is a crisis: an unexpected resignation, a team conflict that escalates, a compliance audit, or a failed hire that cost six months of salary. At that point, they build it — but under pressure, reactively, and often with trust already eroded.

The better approach is to treat people ops like product engineering: ship early, iterate, don't wait for perfect. A simple leave policy written today is infinitely better than a comprehensive one written the week after a dispute.

The specific things to prioritise, in order of impact:

  1. Written agreements before verbal commitments go stale. Memories diverge fast.
  2. A system that removes manual reconciliation. Spreadsheets are a coordination tax you pay daily.
  3. One feedback touchpoint per quarter per person. This alone prevents most surprise departures.
  4. A documented process for the things you dread. Performance improvement, offboarding, pay decisions — write the process before you need it.

People ops isn't about adding bureaucracy. It's about removing ambiguity. Every process you put in place answers a question your team is currently answering informally — inconsistently, invisibly, and often in ways that don't reflect your actual values.

Workived gives small teams a single place to manage employee records, leave, attendance, documents, and org chart — all in one tool, free for up to 25 employees.