The question arrives as a search for software and it is really a question about timing. The spreadsheet that holds everyone's start date, salary, leave balance and emergency contact has worked since the company was twelve people. It still works at sixty, in the sense that nothing has visibly broken. The owner wants to know whether an HRIS is a thing a company this size buys, or a thing that enterprise companies buy and small ones are sold.
The honest answer is that the spreadsheet stops being free at a point you can count, and the point is not a headcount.
A spreadsheet costs nothing in licences. It costs three other things, and all three rise with the company.
The first is the person. Somebody maintains it, and that somebody is usually the office manager, the finance lead or a founder, which means the spreadsheet is maintained in the gaps of a job that is not HR. At twelve people the gaps are enough. At sixty they are not, and the spreadsheet's accuracy starts to depend on who was busy that week.
The second is the handoffs it cannot carry. Every change to a person, a start, a leave request, a salary change, a move between teams, a leaver, has to reach IT, the manager, payroll and the books. The spreadsheet records the change. It cannot tell anyone. Each notification is an email somebody remembers to send, and the ones they forget are the failures we listed in the onboarding piece in this series: no laptop, no login, no pay.
The third is the errors it hides. A leave balance that was never decremented. A salary change recorded in the spreadsheet and not in payroll, or the reverse. A leaver still on the insurance. None of these announce themselves, because the spreadsheet is the record and the record says what it was last told.
Add the three lines up and the spreadsheet stops being free when the handoffs per month exceed what one person can carry by memory. In practice that is a number you can get from last quarter's calendar: starts plus leavers plus moves plus salary changes plus leave requests, divided by three.
Under about twenty changes a month, one careful person carries it and the errors are rare. Between twenty and fifty, the errors become monthly and someone starts a second spreadsheet to track the first. Over fifty, the company is running an HR function on a tool that cannot send a message, and the cost is being paid by IT, payroll and the new hires rather than by HR, which is why it does not appear on anyone's budget.
That is the test. Not sixty people or a hundred. Changes per month, counted.
Companies usually find out they crossed the line a year after they did, because the costs land elsewhere. There are three early signs worth checking for.
The first is a second spreadsheet. When someone starts a tracker to track the tracker, a leave spreadsheet beside the people spreadsheet, or a starters-and-leavers tab that IT keeps separately, the handoffs have already outgrown the record. Two spreadsheets about the same people never agree, and the disagreement is a new monthly job.
The second is a question nobody can answer quickly. How many people do we have today, by team, with their start dates? What is our total leave liability? Who still has access from a team they left? If the answer takes a day and a conversation, the record is not a record.
The third is an error with a cost attached: a leaver paid for a month after leaving, a new hire underpaid for two, a salary change applied in one place and not the other. One such error is bad luck. Two in a quarter is the spreadsheet telling you it has reached its limit, and the amount involved is usually more than a year of the licence the company was hesitating over.
Any one of the three means the count has already crossed twenty, whatever the calendar says.
An HRIS gives the person a record instead of a row: start date, role, manager, salary history, leave, documents, with a workflow around each change so that a leave request is an approval rather than an email and a salary change is an event with a date. It fixes the first hidden line, because the record is maintained by the people whose changes they are, and it fixes part of the third, because the record holds its own history.
We set out when the Zoho version of this is worth adopting in Zoho People for a growing team, and the reasoning there holds for any HRIS at this size: it is worth it when the changes exceed the person.
The second hidden line, the handoffs, is the one an HRIS does not fix on its own, and it is the one that was costing the most.
An HRIS that holds the person's record and sends an email to IT when a hire is created has moved the spreadsheet into a nicer screen. The handoff is still a message; the laptop is still ordered when someone reads it; payroll still finds out at the cut-off. The small-business HRIS pitch rarely mentions this because the wires to IT, to payroll and to the books are integration work, and integration is not in the licence.
The wires are what make the HRIS worth the change. A hire in the HRIS creates the IT tasks with due dates counted back from the start. A role on the record sets the CRM access, which is the step we laid out in the Zoho CRM user onboarding checklist. A salary change writes to payroll as a dated event rather than a note. A leaver closes the accounts and stops the pay. The HRIS becomes the system of record for the person, and the other systems receive its facts rather than being told about them.
Without the wires, the company has bought a licence and kept the failures. With them, the failures stop, because the handoffs are states that the receiving systems set.
Count the changes per month from last quarter. If it is under twenty, keep the spreadsheet and give it a named owner with time to maintain it. If it is over, buy the HRIS and budget the wires as the larger half of the project, because they are. And insist on seeing the wires in the proposal: which systems receive which facts, and how the company will know when a handoff did not happen.
The HRIS is a licence. The wires are integration work by engineers, which we do under a guaranteed estimate. Discovery is no-risk: we count your changes, map the handoffs, and you pay only if you go ahead.
In a no-risk discovery we look at your CRM, finance and operations systems and who owns each part, and show what a connected system would do differently. You pay only if you proceed. Or see how we approach it.
More on the same problem:
"Something isn't working." "We're outgrowing our tools." "We're afraid to make the wrong move." No-Risk Discovery is a short, practical conversation that gets you clarity before you commit to anything big. We'll tell you if we're a fit. If we're not, we'll tell you that too.
Say who you are and ask. A person replies within one business day.
