Why 20-Person Startups Need an HR System (Not Another Spreadsheet)

A spreadsheet is a brilliant way to begin. It is inexpensive, familiar, and flexible enough to hold an employee list, leave balances, onboarding tasks, and equipment assignments. For a five-person startup, that may be all the system you need.

The problem appears when the team reaches roughly 20 people. The spreadsheet has not technically stopped working, but the operating cost around it has increased. Managers ask which file is current. HR copies the same details between tabs. A new hire waits because one onboarding task had no owner. Sensitive salary or ID data is shared more widely than intended.

An HR system becomes useful at this point not because the company wants “enterprise software,” but because the team needs one reliable way to run repeated work.

The real threshold is coordination, not headcount

Twenty employees is not a magic number. A distributed team with contractors may feel operational strain at 12 people, while a team in one room may reach 30 before the cracks show. Look at coordination instead.

Count how many people update employee information, approve leave, prepare onboarding, assign equipment, or retrieve documents. If several people depend on the same record and the same deadlines, you have a workflow rather than a personal spreadsheet.

The risk grows when one change must be reflected in several places. A department transfer might require updates to the employee file, manager list, access permissions, payroll note, and reporting dashboard. Every duplicate entry creates another chance for inconsistency.

Five signs the spreadsheet has become a hidden system

First, the team asks “which version is correct?” more than once a week. A shared sheet does not guarantee shared understanding when people export copies, add private tabs, or use different naming conventions.

Second, reminders live in someone’s memory. Probation reviews, contract renewals, document expiries, and onboarding tasks should have dates and owners. If a task happens only because one careful person remembers it, the process is fragile.

Third, approvals happen in chat. A message saying “approved” may be enough today, but it becomes difficult to find later. You need the request, evidence, decision, approver, and timestamp together.

Fourth, access is all or nothing. Employee records contain personal and sometimes sensitive information. Managers may need visibility into their teams without receiving access to every employee document.

Fifth, reporting requires a cleanup project. If a headcount answer takes an afternoon of reconciling sheets, the data is not operationally ready.

What a right-sized HR system should include

A startup does not need every HR feature on day one. Begin with a controlled employee database: name, role, department, manager, employment status, start date, and the documents required for the job. Define who owns each field and who may view or edit it.

Add one high-friction workflow. For many Thai startups, that is onboarding, leave requests, probation reminders, or employee document requests. The workflow should state the trigger, required information, owner, approver, due date, and completion evidence.

Then add a small operating view. It might show people starting this month, probation reviews due, incomplete onboarding tasks, and pending employee requests. The goal is not a beautiful dashboard; it is a reliable list of what requires attention.

What not to automate yet

Do not automate a process that the team cannot explain. If managers disagree about who approves a request, software will make the disagreement faster, not solve it.

Avoid migrating years of inconsistent spreadsheet history into the first release. Decide what historical information is genuinely useful, clean that subset, and archive the rest safely. Also resist adding every optional field. Each field requires an owner and a reason to stay current.

Integrations should follow adoption. Connecting payroll, accounting, messaging, and identity systems can be valuable, but only after the core employee record and workflow are stable.

A practical four-week preparation plan

In week one, map the current files and repeated tasks. Identify the employee record that should become the source of truth. In week two, agree on owners, approvals, and access rules. In week three, clean active employee data and test the workflow with a small group. In week four, train managers, publish a simple operating guide, and review exceptions.

This preparation is useful whether you buy a product or commission a custom system. It reduces scope, migration cost, and implementation surprises.

How to judge the result

Measure operational outcomes rather than the number of features. Can a manager find the current employee status without asking HR? Are onboarding tasks completed on time? Can HR see every probation review due in the next 30 days? Can the company produce a decision history when required?

If the answers improve, the system is doing its job.

The best first HR system is not the one with the most modules. It is the smallest reliable system that removes repeated checking and gives every important task an owner.

Ready to define that first phase? Build your system plan and get an instant estimate, or review the Backoffice Builder pricing options.