HR for small and growing teams, without the spreadsheet
HR · 8 min read
Most small teams run HR on a spreadsheet until something breaks. Here is what people operations actually needs as you grow, from a real directory to retention and legal hold, and when to stop improvising.
For most small teams, HR starts as a spreadsheet and a shared folder. There is a tab with everyone's start date, a folder of offer letters, and a group chat where people ask for time off. It works right up until it does not. Someone takes leave they did not have, an offer letter goes out with last year's salary band, or a regulator asks for a document you cannot find. The spreadsheet did not fail you. You simply grew past it.
People operations is the quiet function that becomes urgent the moment it is missing. The good news is that the core of it is not complicated once you name the parts. Here is what a growing team actually needs, in roughly the order you will need it.
A real directory, not a list of names
The first thing to outgrow is the name and email list. A real directory holds the full picture for each person. Role, department, manager, status, start date, the equipment they hold, and a pay history with effective dates that only HR and the person can see. The detail that separates a directory from a contact list is the timeline. Every promotion, transfer and change recorded, attributed, and impossible to quietly overwrite.
The nineloops HR module keeps exactly this, with a logged change on every field, so a year from now you can answer who reported to whom in March and what someone's title was when they signed a document. That sounds like too much at five people and feels essential at fifty.
An org chart you do not have to draw
Hand drawn org charts are wrong the week after you make them. Someone joins, someone changes teams, and the diagram in the slide deck quietly lies. The fix is to stop drawing it. When reporting lines come straight from the directory, the chart is always current. Add a person, set their manager, and the hierarchy redraws itself, departments and all.
Time off that follows its own rules
Leave is where the spreadsheet breaks first, because the rules are fiddly and the stakes are personal. A proper system encodes the policy rather than relying on memory. Annual allocation or monthly accrual, carry over caps, minimum notice, and a balance per person per year that updates as requests are approved.
- Policies with allocation or accrual, carry over caps and notice rules.
- A running balance per person, so nobody takes leave they do not have.
- Requests that route through an approval chain, not a chat message.
- A team calendar, so you can see who is off before you plan a sprint.
The point is not to make leave bureaucratic. It is to make the answer to can I take next week unambiguous, for the person asking and the manager approving.
The part most HR tools skip: records and compliance
This is where a directory becomes an HR system. Employee documents are not just files. Many of them carry legal retention duties that depend on the country and on dates like hire or termination. Keep a tax form too briefly and you are not compliant. Destroy something under legal hold and you are in real trouble.
nineloops builds this in. A document store for each employee with retention schedules that follow the right rules and dates, a legal hold that freezes destruction when litigation looms, and a record of what was kept and what was deleted so you can prove it. This is the compliance layer most lightweight HR tools simply do not have, and it is the reason a spreadsheet eventually becomes a liability rather than a convenience.
Stop paying a separate bill to send an offer letter
Signing is its own small tax. Many teams pay a separate electronic signature subscription just to send an offer letter or an NDA. nineloops includes signing built in. Drop signature, initials and date fields onto a document and send it to an employee, a manager, or an outside party, verified with a passcode, with a full audit trail and no extra bill. Offer letter and NDA templates fill from the live employee record, so there is no retyping and no mismatched salary band.
A spreadsheet remembers what you type into it. An HR system remembers what you forgot to, and proves it when someone asks.
When to make the switch
There is no magic headcount, but the signals are clear. You move off the spreadsheet when leave balances start being disputed, when you cannot quickly answer a compliance question, when onboarding a new hire means chasing the same checklist by hand each time, or when sensitive pay data sits in a file more people can open than should. Because the nineloops HR module shares one workspace with the rest of your tools, the people data connects to the work. The same person you manage in HR is the one assigned tasks in projects. You are not adding another silo. You are giving the team you already have a real system to live in.