HR System for a Small Business: What You Need and How to Choose

While a company has five people, HR records live in the ownerʼs head and in a single spreadsheet. At twenty employees the spreadsheet breaks down: nobody remembers how many vacation days a manager has left or where the signed contract is stored. Letʼs look at which HR features a business of 5-50 people actually needs, and which ones are not worth paying for.

What HR System a Small Business Really Needs

The main mistake at the start is choosing a system by its feature list. Large platforms sell dozens of modules: competency reviews, KPI matrices, talent pools, turnover analytics by department. For a team of 15 people most of those modules will stay empty, yet you will pay for them every month and spend weeks on setup.

The minimum useful set looks simpler: a single employee profile, a history of roles and salaries, absence tracking, document storage, plus a basic hiring and onboarding process. That covers about 90 percent of the daily questions currently handled through chat messages. Everything else can be added later, when the team grows to a hundred people and a separate HR department appears with its own reporting needs.

The second criterion is who will actually use it. Small businesses rarely have a dedicated HR manager, so the system is maintained by an accountant, an office manager or the owner. If adding a new employee takes more than five minutes, the system will not stick and within a month the old spreadsheet is back.

Staff Records: One Profile Instead of Five Files

Staff records start with the employee profile. It should hold contacts, start date, role, department, manager, employment type, rate and the history of rate changes. Payroll data and bank details are stored separately, with access limited to the finance team. Access rights matter from day one: a department lead should see their team, an accountant should see the numbers, and an employee should see only their own data.

History matters more than it seems. When a year later you need to know since which month a person holds a new role and when their rate was last raised, a single «current salary» field will not help. A proper structure stores every change with a date, a reason and the author of the record.

Documents belong here too: contracts, orders, applications, ID scans, NDAs. Keeping them in a shared cloud folder is risky because random people gain access. In a system a document is attached to a profile, has a type, a date and an expiry, and a reminder about a contract ending arrives in advance.

Vacations and Sick Leave: Requests, Balances, Team Calendar

This is the part small businesses most often adopt a system for. The flow is simple and works: an employee submits a request, a manager approves it, the day balance recalculates automatically, and the event appears on a shared calendar. No messenger threads and no year-end arguments. In practice this is the block employees start using on their own, without reminders, because seeing the remaining balance in their profile is easier than asking the accountant about it.

The key detail is the accrual rules. In most teams it is 24 calendar days a year, that is 2 days per month, plus separate unpaid days, sick leave and time off. If the system can track several absence types under different rules, you get rid of manual recalculations in December.

The absence calendar is useful beyond HR. A department lead sees that two of four developers are away in the same week and plans the release differently. A simple month view is enough, where each row is a person and coloured bars are absence types.

Onboarding and Recruiting: Hiring and the First Weeks

Recruiting in a small business rarely needs a full ATS. A list of openings, a candidate database and a simple four or five stage pipeline are enough: application, screening, interview, test task, offer. The main value here is the communication history, so that six months later you can find a strong candidate you turned down back then. It also helps to record the candidate source and the time spent at each stage: after half a year you can see which channels bring people and which only eat up CV screening time.

Onboarding is best described as a checklist with owners. A typical set: prepare the workplace and hardware, grant access to email and the task tracker, sign documents, introduce the team, assign a mentor, and hold feedback meetings on day 14 and day 60. Every item has an owner and a deadline. The same checklist works in reverse when someone leaves: collect the hardware, close the accounts, hand over the work.

Automation pays off fastest here. When a candidate moves to the «hired» status, the system creates the employee profile itself, launches the checklist and sends tasks to the admin and the manager. Instead of an hour of manual work per new hire you spend a few minutes on review.

Off-the-Shelf or Custom: How to Plan the Rollout

A ready-made service wins on speed: a subscription, a few days of setup, and the system runs. It is the right choice if your processes are standard and the team is ready to adapt to the productʼs logic. The downsides are known too: limited reports, someone elseʼs data structure and pricing tied to headcount growth. Check upfront whether you can export all the data in a readable format, in case you decide to move to another solution a year later.

A custom build is justified when there are specifics: shift schedules, work with contractors, several legal entities, integration with an accounting system or a need to keep personal data on your own server. Then the system is built around your processes rather than the other way round, and it grows into adjacent tasks easily.

Whatever you choose, roll it out in stages. First migrate staff records and documents, two or three weeks later add leave tracking, and only then recruiting and onboarding. This way the team gets used to it gradually and you see real value before the whole budget is spent. Plan a separate day for migrating the old data: this is usually where duplicates, empty fields and contracts nobody can find come to the surface. If ready-made services do not cover your processes and spreadsheets no longer cope, it makes sense to look at your own solution. At Devlly we build HR systems for a specific business: from employee profiles and absence tracking to onboarding with Telegram reminders and integrations with your accounting services.