How to Set Up an HR Department from Scratch in a Small Business

Most small businesses do not decide to build an HR department. They get forced into it. Something goes wrong, or a few things go wrong around the same time, and it becomes impossible to keep pretending that managing 40 people the same way you managed 10 is going to keep working.

The payroll run took four hours this month because nobody could remember what leave Ahmed took in March. The manager handled a disciplinary situation badly enough that the employee is now talking to a lawyer. 

The new hire who showed up on their first day and spent most of it waiting for a laptop. The resignation that came out of nowhere and turned out not to be out of nowhere at all, it had been building for months, but nobody had a system for catching that kind of signal.

These are not disasters. But they accumulate. And at some point, the founder or the ops lead or whoever has been absorbing people management alongside everything else looks up and realizes they need actual infrastructure for this.

What follows is a practical guide to building that infrastructure in a small business. Not a large enterprise HR function scaled down. A version that fits the actual size and needs of a business with 20 to 100 people.

Figure Out What An HR Department Actually Needs to Cover in Your Business

The scope of HR is broader than most founders expect when they first start thinking seriously about it. You have payroll, which everyone knows about. You have leave management, which is connected to payroll in ways that make both harder when either is handled badly. 

You have hiring, onboarding, performance management, employee documentation, the handling of complaints and disputes, and a set of policies that are supposed to tell everyone, managers and employees alike, how things are supposed to work.

In a large organization, those are separate departments. In a small business, they are one person’s job, often one person who is also doing three other things. 

The goal is not to replicate enterprise HR. It is to make sure each of those areas has enough structure that it does not depend entirely on the availability and memory of one specific person.

One thing worth being honest about: the scope of this work tends to surprise founders who have been thinking of HR as mainly a hiring and payroll function. It is much wider than that, and the gaps in the non-hiring, non-payroll areas are often where the expensive problems live.

The piece on Key HR Functions in Growing Companies is useful for understanding how these functions connect to each other and how the HR role evolves as a business grows.

Start With Legal Compliance, Even if It Is Uncomfortable

This is the answer to where to start that you don’t want to hear, and it is the right one.

In Egypt, there are minimum requirements that apply to every employer regardless of size. Employment contracts must be in writing and include specific terms. Employees need to be registered with the social insurance authority. 

Minimum wage requirements apply. Working hours have legal limits. When someone leaves, their final settlement, including accrued leave, has to be calculated correctly and paid in a reasonable time frame.

A lot of small businesses are non-compliant on at least one of these without being aware of it. 

The risk is real. A labor authority complaint filed by a departing employee costs time, money, and management attention that a small business can ill afford. 

Getting advice from a labor law specialist early, before you think you need it, is much cheaper than getting it after a complaint is filed.

The other thing legal compliance does is give you a foundation. Everything else in the HR function, the policies, the processes, the documentation, builds on top of the legal baseline. If the baseline is wrong, everything built on top of it is on shaky ground.

Get the Basic Documentation in Order

Employee files. Every employee should have one. It should contain their contract, their identification documents, payroll records, records of any performance or disciplinary processes they have been through, and their leave history. 

This sounds obvious. In practice, many small businesses have employment contracts for some employees but not others, payroll records in a spreadsheet that two people maintain inconsistently, and leave history that exists mainly in a WhatsApp group.

Core HR policies need to be written down. Not an elaborate policy manual on day one, though that should come eventually. 

At a minimum, documented answers to the questions that managers ask most often and that produce the most inconsistency when left to individual judgment. How does leave work, and how is it requested? 

What is the process when someone is underperforming? What happens when an employee raises a complaint? These need to exist somewhere other than the founder’s head.

Write them in language that a manager can read and understand without needing a legal background to interpret. Vague policies sound safer than specific ones, but they produce more disputes, not fewer. 

The more specific the documentation, the less room there is for anyone to later claim they understood it differently.

Payroll and Leave Are More Connected Than They Look

Payroll errors are one of the fastest ways to damage employee trust. When someone gets paid the wrong amount, or when it takes two weeks to correct a mistake, the signal that sends about how the organization operates is disproportionately negative. 

It does not read as an administrative slip. It reads as a signal about how seriously the business takes its commitments.

Getting payroll right requires accurate inputs. What leave did each employee take this month? Are there any changes to salaries or allowances? 

What deductions apply? When that information is spread across different systems or lives in different people’s heads, payroll becomes a monthly investigation rather than a calculation, and investigations produce errors.

Leave balances are the input that most often goes wrong. When employees do not know how many days they have left, they ask HR. 

When HR does not know either, or when the answer differs from what the employee remembers, it creates a problem. 

Setting up centralized leave tracking early, before the accumulation of inconsistencies makes it a difficult retrospective exercise, is one of the higher-value early decisions a small business HR function can make.

Hiring and Onboarding Are Part of HR, and They Need a Process

Small businesses tend to treat hiring as something that happens to them rather than something they do with intention. 

A need becomes urgent, someone posts a job quickly, a few interviews happen, and an offer goes out. This produces hires that look fine under time pressure and reveal themselves as problems over the following months.

A repeatable hiring process does not have to be long. It has to be consistent. The same criteria applied to everyone. Interviews designed to test for what the job actually requires rather than for whatever questions the interviewer finds comfortable. 

Written records of why each decision was made. These things improve the quality of decisions and protect the business legally.

Onboarding is the step after the offer, and it is where small businesses most commonly underinvest. When a new employee’s first few days involve sitting around waiting for access and not knowing who to talk to about basic things, it sets a tone. 

That tone affects how quickly they get productive, how they talk about the organization to people they know, and whether they decide in the first few weeks that they made a mistake accepting the offer.

You can find it on this blog: Employee Onboarding Process in Egypt. It covers what a structured onboarding process looks like in the Egyptian employment context, including the documentation, the legal steps, and the practical things that make a difference to new employee experience.

Tools: The Two Mistakes Small Businesses Make

The first mistake is staying on spreadsheets too long. Excel is a fine tool for a lot of things. It is a genuinely bad tool for payroll, leave management, and employee records at any meaningful scale. 

The errors compound, the version control is a nightmare, and the information that should be centralized is instead scattered across files that different people maintain differently.

The second mistake is buying enterprise software. A 50-person business does not need a system built for a company with 5000 employees. It needs payroll, leave tracking, attendance records, and centralized employee documentation. 

A system that does those things well and that non-technical people can actually use is worth far more than a platform with a hundred features that the business will never touch.

This blog on Manual HR Costs Explained: Time, Trust, and Turnover makes the case in more concrete terms for why staying manual past a certain point is more expensive than the cost of changing. Worth reading if you are still weighing that decision.

Conclusion

Building an HR function from scratch is a sequencing problem as much as anything else. Legal compliance before policies. Policies before you try to manage performance consistently. 

Payroll and leave infrastructure before you scale hiring. Each step makes the next one more effective, and skipping a step to save time tends to create problems that cost more time to fix than the step would have taken.

None of this requires a team. It requires putting the right things in place in the right order and making sure someone owns each area with enough clarity to maintain it as the business grows.

Bluworks is built for businesses at exactly this stage, past the point where informal people management works, not yet at the point where enterprise HR infrastructure makes sense.

Frequently Asked Questions