HR for startups: from the first employee onward
The day a startup hires employee number one, it acquires the complete set of employer obligations — contracts, records, pay, and duty of care — with none of the infrastructure. Startup HR is the art of meeting those obligations with minimal overhead while building habits that will not need to be unlearned at 30 employees. The good news: the minimum viable version is genuinely small.
Before employee number one
- A real employment contract — role, pay, hours, notice, IP assignment where relevant. A template reviewed once by a local professional serves for years.
- Registration and payroll basics for your jurisdiction — tax, social contributions, mandatory insurances. This is country-specific; get the list locally and follow it exactly.
- A place for employee records that is not your inbox — even one employee generates documents (contract, ID, certificates) that must be findable in three years.
- Written answers to the five questions every employee asks: working hours, leave, sick days, pay dates, expenses. One page total is fine; existing in writing is what matters.
The minimum viable HR stack
Through roughly the first twenty employees, startup HR needs exactly three systems: payroll that runs correctly every month (outsourcing this early is usually money well spent), structured employee records (profiles, contracts, employment events, documents — EmployDB provides this layer free, with no employee cap, which makes it a natural startup default), and a repeatable hiring checklist so each hire is less improvised than the last. Everything else — engagement surveys, performance frameworks, policy libraries — can genuinely wait; adding them before the basics run smoothly is procrastination wearing a productivity costume.
The founder mistakes that compound
- Handshake employment — months of work before any contract exists. Every later dispute traces back to this.
- Everyone-does-everything titles left unrecorded — eighteen months later, nobody can say who was promoted, when, or from what, and the first formal review has no baseline.
- Pay improvisation — individually negotiated salaries with no internal logic. It feels flexible; it becomes the fairness crisis of year three.
- Deferring the uncomfortable — the underperformer not addressed, the conflict not mediated. Small companies feel these fastest and document them least.
When structure has to grow
The signals that minimum-viable is no longer viable arrive on schedule: hiring becomes constant (a pipeline, not an event), the founder no longer knows every employee’s situation, and questions about fairness — pay, promotion, workload — start arriving faster than ad-hoc answers can hold. That is the window for the first HR hire, and the transition is dramatically easier if the records and habits above already exist: the new HR manager extends a working system instead of excavating a startup’s undocumented history. Structure put in early is invisible; structure put in late is a project.