Imagine a restaurant kitchen where one cook handles the grill, the fryer, the prep, and the plating. Service goes fine on a quiet Tuesday. On a Saturday night, every dish waits on the same pair of hands. HR in a small or mid-sized company runs on the same arrangement.
One person (or one founder, three evenings a week) carries recruiting, payroll questions, contracts, onboarding, and the awkward conversations, and the load shows once something piles up. You can spot the pile-up from outside, too. A job post that sits open for months, a leave request answered in a hallway, a contract that exists as a screenshot.
Hiring happens in the gaps between other work
A role opens, and the posting goes onto LinkedIn on a Thursday afternoon because that is when someone had twenty minutes. Applications land in a shared inbox, or in Greenhouse or Lever if the company has paid for one, and because nobody owns the follow-up, candidates wait for a reply that never comes and accept another offer instead.
The fix is dull, and it works. Pick one owner per open role, give them a fixed weekly slot for screening, and write the scorecard before the first interview rather than after the third. A scorecard with four criteria beats a gut feeling from a founder who has also spent the morning on a customer escalation. It also gives the second interviewer something to disagree with, which is how a panel finds out what it actually thinks. You also learn more from a candidate’s questions about the first ninety days than from their rehearsed answers about the last job, so leave room for them.
Small companies lose candidates in the offer stage as well. The salary conversation gets postponed until a final round; the candidate has already mentally spent the number, and the gap between the two figures turns into a week of silence. Putting a range in the posting removes that conversation from the critical path.
Records scatter across too many places
Offer letters sit in someone’s Google Workspace folder. Leave balances live in a spreadsheet a former office manager built. Onboarding steps are in Notion, and the questions about them arrive in Slack direct messages. It works until an auditor, a lender, or an employee asks for a document and nobody can say which version is current.
Scattered records also create a privacy problem. Under GDPR, an employee’s personal data needs a stated reason for being held, secure storage, and deletion when that reason ends. A spreadsheet emailed around as an attachment struggles with all three. Moving to a single system of record, even a modest one, is a larger job than it sounds, because the first week goes on discovering what data exists and who holds copies. A useful first step is a one-page list: what you hold on each person, where it lives, who can open it. The list surprises you, and the surprise is the point.
Contractor or employee is a decision with consequences
A company that cannot afford a full-time designer brings in a freelancer. Six months later, the freelancer works fixed hours, uses the company laptop, sits in team meetings, and has no other clients. That is the moment the label stops matching the reality.
In the United States, the difference shows up as IRS Form W-2 versus Form 1099, and the IRS looks at how the relationship works in practice. In the UK, IR35 asks HMRC’s version of the same question for contractors working through their own companies. Different countries, same trap: the contract says one thing and the daily routine says another.
Once the freelancer lives in another country, the question gets harder, because local labour law decides the status, whatever the paperwork you signed says. Teams that start hiring across borders quickly find that global employment compliance covers more ground than a contract template, from statutory contributions to notice rules to what a country treats as an employment relationship in the first place. Ask the question before the second invoice arrives. By the twentieth, it is a back-pay conversation.
One hire abroad changes the job
The first employee in another country exposes how much a home-country HR routine takes for granted. India has EPF contributions. Singapore has CPF. Some countries expect 13th-month pay, and a payroll built for monthly salaries misses it. Germany has works councils with consultation rights that can shape how changes get introduced, and the UK has TUPE, which protects staff when the business or service they work in moves to a new employer.
None of this is exotic for a specialist. All of it is new to a three-person people team, and it lands in the same week as a product launch. A company can learn about a mandatory contribution from an employee’s payslip query three months in, and then spend the next quarter backfilling paperwork. The hire was fine. The setup around the hire was the gap.
Time zones add a quieter version of the same problem. A manager in Toronto schedules the weekly check-in for the hour that suits Toronto, and the new colleague in Singapore attends at the end of her evening. Within a few weeks, she is the person who never speaks, and the manager reads that as a performance signal when it is a calendar choice.
Reviews and engagement run on goodwill
First days set the tone before any review cycle exists. The laptop arrives on day two, the Google Workspace account is not provisioned, nobody sent the Slack invite, and the new hire spends the morning reading a handbook that describes a company from two years ago. Nothing about that is a scandal. It still tells the person how much the company has thought about them.
Without a system, performance reviews happen when a manager remembers them. Engagement gets measured by whether people seem cheerful in Slack. Both can drift for a year before an exit interview or a Glassdoor review puts words on it.
New managers deserve a word here too. A strong engineer gets promoted to lead a team of five, receives no training, and learns about feedback by giving it badly. Ten minutes of coaching before the first hard conversation does more than a leadership course six months later.
Lightweight tools help. Lattice and Culture Amp both run review cycles and pulse surveys, and OKRs give managers a shared way to say what good looks like in a quarter. The tool is the smaller half. The larger half is a manager who holds the one-to-one on the calendar even in a bad week, because people read that habit as respect. If you have energy for just one fix here, pick the recurring one-to-one, since everything else in a review cycle is built from what gets said in those rooms.
Where to start when everything feels urgent
Not every problem deserves the same first move. This table sorts the common ones by what breaks if they wait.
| Challenge | What breaks if ignored | First move |
|---|---|---|
| Ownerless hiring | Offers go to the first available candidate | One owner per role, written scorecard |
| Scattered records | Audit or data request stalls | One system of record, one naming rule |
| Misclassified contractor | Back pay and penalties arrive together | Review the working pattern, not the contract |
| Cross-border hire | Contributions missed from day one | Local checklist before the offer is signed |
| Unstructured reviews | Quiet attrition | Fixed cadence, one template |
Pick the row that would hurt most this quarter and fix that one. The others can wait their turn, and a fix that finishes beats five that stall halfway.
Keep it in-house, or hand parts of it off
Growing companies hit a point where in-house HR management starts to be a question of coverage, since effort alone no longer closes the gap. One generalist cannot also be the local expert in four labour codes. Larger companies solve this with a Workday rollout and a team of specialists, which is out of reach at a small company’s size. Smaller ones keep a generalist, bring in outside payroll or legal help for the countries where they hire, and keep the culture work, the one-to-ones, and the judgment calls close to home.
The split gets clearer once you list each recurring task and ask who loses a night’s sleep if it goes wrong, then write that list on one page with a name next to every line. Culture, hiring decisions, and manager coaching stay near the founders. Statutory filings, local payslips and country-specific notice rules suit someone who reads the local rules for a living.
A security questionnaire from a customer pushes on the same boundary. Buyers ask about SOC 2 or ISO 27001, and the HR half of that answer covers background checks, onboarding and offboarding access, and training records. Those are people processes, so they land on the same desk.
What I would still get wrong
I have drawn this as a tidy list, and real companies do not hit these problems in order. Two land in the same fortnight, a third arrives in the middle of a funding round, and the person responsible for fixing them is also covering a parental leave. Records clean-ups run longer than anyone plans for, and the first cross-border hire is the easiest of all of them to underestimate. What I do trust is the order of operations: name the owner, find the records, check the contractor, then add a country. The kitchen never gets a second cook overnight, but the cook can at least know which burner to watch.





