Who Actually Needs HR? A Decision Guide for Small Teams

You've got five employees. Maybe twelve. No one's complained about paychecks or time off—yet. But last week you overheard someone ask, 'Who do I talk to about my insurance?' And you realized: that's you. You're the HR department.

This isn't about building a corporate HR tower. It's about deciding, honestly, whether your team needs a dedicated person, a software subscription, or just a better spreadsheet. The choice matters because labor laws don't scale with headcount. One misclassified contractor or missed overtime rule can cost more than an HR salary. So who has to choose, and by when? Let's walk through it.

Who Must Decide on HR—and by When

The 5-Employee Trigger

Most founders treat HR as a someday problem. Then they hire a fifth person—and the seams blow out. That fifth employee is where payroll gets complicated, because now you might cross state lines for remote workers, or simply because the informal 'ask the office manager to handle it' breaks under the weight of one extra W-2. I have seen a six-person agency lose two weeks of productivity because nobody had bothered to set up a simple sick-leave policy. The trigger is not arbitrary: at five employees, most states start applying mini-COBRA rules, and your liability for misclassifying a contractor jumps. You don't need a full HR department at five people. You do need a decision—even if that decision is 'we will use a spreadsheet and a checklist.'

Deferring that decision is the real mistake.

The 15-Employee Cliff

Fifteen is where the federal government starts paying attention. Title VII of the Civil Rights Act kicks in. So do the Americans with Disabilities Act and the Pregnancy Discrimination Act. That sounds fine until a single complaint lands on your desk and you have zero documentation to prove you handled hiring consistently. The catch is that most teams at 12–14 people feel too small to formalize anything, so they delay again—right into the cliff. What usually breaks first is the interview pipeline: one manager asks illegal questions, a candidate complains, and suddenly you're spending $8,000 on a lawyer to explain why your 'culture fit' screening was actually discrimination. By fifteen employees, you need at least a written handbook and a standardized review process. Software alone won't fix this if nobody owns the policy decisions.

Wrong order. Many teams buy an HR tool first, then realize they have nothing to put into it.

Industry-Specific Deadlines

Not every small team hits the same clock. If you handle money—fintech, real estate, property management—your HR trigger might be three employees, not five, because bonding and licensing requirements demand documented background checks and conflict-of-interest policies from day one. Healthcare? The minute you hire a clinician, credentialing timelines dictate your HR calendar. I once consulted for a seven-person construction firm that ignored OSHA recordkeeping until an inspection. The fine was $12,000—more than a year of a part-time HR service. The point is not to panic. The point is to map your industry's actual thresholds against your headcount growth, because the generic advice (five, fifteen, fifty) is a floor, not a ceiling.

'We thought we were too small for HR. Then a former employee filed a wage complaint. The investigation took three months and we had no time logs.'

— founder of a 9-person landscaping company, after settling for $6,200

That anecdote cuts to the chase: the cost of delay is rarely the fine itself. It's the distraction. A two-month investigation against a team of nine means the owner is not selling, the manager is not training, and the admin is digging through text messages to reconstruct hours worked. So ask yourself—honestly—what your actual headcount will be in six months. Not your aspirational headcount, not the one on the pitch deck. The real number. If it crosses five or fifteen, this week is the right week to decide. Not next quarter.

Three Roads Into HR: DIY, Software, or Hire

Do-it-yourself with templates

The cheapest path isn't cheap—it's just money you don't spend today. You grab employment contracts off a legal site, copy a vacation policy from a friend's startup, and track sick days in a shared spreadsheet. That sounds fine until an employee quits and claims unpaid overtime. I have seen founders spend an entire weekend reconstructing time logs because nobody wrote down the overtime approval rule. The template itself isn't the problem. The gap between what the template says and what your team actually does—that's where the seams blow out. Most teams skip this: you need someone to own the template, update it when labor laws shift, and enforce it when a top performer wants to bend the rules. DIY works for maybe three people. Past that, the overhead of fixing mistakes dwarfs the money you saved.

HR software platforms

Software promises a dashboard, automated reminders, and a single source of truth. The catch is implementation. You buy a platform, import your team data, and suddenly every employee has a login they never use. The useful stuff—PTO requests, document signing, performance review cycles—sits behind a setup wizard that takes three hours you don't have. We fixed this by assigning one person to configure the system for exactly one week, then running a twenty-minute live demo for the whole team. The trick is resisting feature creep. Do you need the learning module? The engagement survey tool? Probably not. What usually breaks first is payroll integration: a mismatched deduction code can delay everyone's paycheck by a day. That hurts. Software is a middle road: more reliable than sticky notes, less flexible than a real person who can say "here's what we actually need right now."

Part-time or fractional HR consultant

This is the option most teams forget exists. You hire an experienced HR person for ten to twenty hours a month. No benefits, no desk, no long-term commitment. They write your handbook, handle a termination conversation, and tell you which compliance filings you missed last quarter. Wrong order? They also train you to take over routine stuff after six months. The trade-off is cost—somewhere between a SaaS subscription and a junior full-time hire—and availability. A fractional consultant juggles multiple clients. When a harassment complaint lands on a Friday afternoon, they might not reply until Monday. I have seen that delay escalate a fixable misunderstanding into a lawyer's letter. Still, for a team of eight to fifteen people, a good part-timer catches problems before they compound. They don't replace a culture of direct communication. They just prevent the culture from getting you sued.

'We paid a consultant for twelve hours and she found three wage-and-hour violations in our first month. The spreadsheet crowd never would have caught those.'

— Operations lead, 14-person agency

Odd bit about resources: the dull step fails first.

Odd bit about resources: the dull step fails first.

All three roads require maintenance. DIY frays without a steward. Software rots when nobody updates the permission settings. A consultant delivers only as much as the hours you buy. The real question is not which tool looks best on paper—it's which one your team will actually touch, question, and improve over the next ninety days. Pick the road that matches the energy you have right now, not the one you wish you had.

How to Compare HR Options Without Getting Lost

Cost per Employee per Month — the Trap of 'Free'

Most teams start by asking “What’s the monthly price?” and stop there. Wrong order. A $5-per-seat tool looks cheap until you realize it covers zero compliance docs and your first payroll error costs $2,800 in penalties. I have seen founders sign up for a free HR platform, then spend six hours manually mapping wage notices. That “free” hour? Pricier than a $30 plan that auto-files. Run the math on total cost: subscription + lost time + legal risk. A spreadsheet with that column usually flips the decision.

The catch is hidden fees. Some software charges extra for each W-2 at year-end. Others lock basic features—like PTO accrual—behind a “Growth” tier that doubles your bill the moment you pass ten employees. Ask vendors: “What changes when I hit 15 people?” If they dodge, walk. An honest provider will say “Your cost climbs $2 per head, but you gain ACA tracking.” That’s fine. Surprise overage charges are not.

Legal Compliance Coverage — the Difference Between Safe and Sorry

“The first time a former employee files a wage claim, you realize your ‘HR solution’ was just a calendar with a pay stub attachment.”

— Founder of a 12-person agency, after a $4,300 settlement

Compliance is not a feature list—it’s a liability map. A DIY folder of PDFs covers nothing when a state updates its paid-leave law overnight. Software that auto-updates I-9 forms? That reduces risk. Software that only stores them? You’re still on the hook for missing a deadline. Compare options by asking: “Who corrects me if I’m wrong?” Human experts fix mistakes before they happen. Tools flag errors after—or not at all.

What usually breaks first is termination paperwork. A small team fired someone verbally, no final check generated, no COBRA notice sent. The lawsuit took eight months. Their “HR software” had a termination checklist buried in a menu. They never saw it. That seam blows out fast. Choose an option that forces the steps, not one that hopes you remember them.

Employee Experience — the Feature Nobody Puts on a Spreadsheet

Your team notices when HR is broken. Payroll glitches, late offer letters, a PTO request that vanishes into a void—each one chips away at trust. A cheap solution that frustrates employees costs you turnover. And turnover hurts. I watched a seven-person startup lose two engineers because their “HR bot” rejected a holiday request on a public channel. Humiliating. The fix cost $35 a month for a human-backed service.

Test the employee side yourself. Sign up for a trial, request time off, then check how the system handled it. Did it auto-approve? Notify a manager? Send a confirmation? If the experience feels like filing taxes, your people will resent it. The best option makes a new hire feel welcomed, not processed. That’s a concrete win—no one quits because onboarding was too smooth.

Scalability to 50+ People — the Stress Test

Most tools work fine at ten heads. At twenty, cracks appear. At forty? The seams blow. Run a worst-case scenario: “What happens when I hire five people in one week?” Does your option handle bulk onboarding? Generate offer letters? Enroll everyone in benefits without you manually copying data? If the answer is “I’ll figure it out,” you’ve chosen a short-term fix that will break mid-growth.

Here is the real test: Export your current employee roster, then imagine doubling it. Does your HR setup still fit in one spreadsheet tab? Does your provider charge per file upload? Does your DIY binders multiply? A system that scales well looks boring—no drama, no migration panic at 28 employees. One founder I know switched at 32 people, after their payroll software refused to process a third state’s tax rules. That cost them a weekend and a contractor’s late fee. Don’t wait for the seam to blow. Pick an option that handles 50 on day one, even if you’re only at 12 now. You’ll thank yourself in eighteen months.

Trade-Offs: What You Gain and What You Lose

Cost vs. compliance depth

DIY looks free. You pay zero monthly, no software license, no retainer. That math works—until you face your first unemployment claim, or a former employee files a wage complaint, or a well-meaning manager writes a performance review that reads like a confession. I have watched a five-person team spend eighteen unpaid hours untangling a single misclassified contractor. The real cost of DIY is not money; it's time you never get back, diverted from product, sales, service. Software costs between fifteen and fifty dollars per employee per month. That feels steep for a startup. But the same platform auto-generates offer letters, tracks I-9s, and flags state-law changes before you miss a deadline. Hire a fractional HR person—think twenty hours a month—and you pay roughly the same as a mid-range SaaS subscription, but you buy judgment, not just checkboxes. The catch is simple: cheap compliance buys you a form; expensive compliance buys you a fix.

— founder, 12-person agency, after a six-month DIY experiment

Control vs. convenience

DIY gives you total control. You write the handbook the way you want. You decide which policies matter. You skip everything that feels like corporate theater. That sounds wonderful until the seam blows out—say, an employee requests an accommodation under the ADA and you have no documented interactive process. Then control becomes liability. Software removes that control but delivers consistency. Every new hire follows the same workflow. Every termination checklist completes the same steps. Every document lives in one place, timestamped, immutable. What you lose is the ability to make exceptions on a whim. Worth flagging: convenience can feel like a straitjacket when you're used to doing things your way. But the teams that survive their first lawsuit or their first state audit rarely yearn for the old flexibility. They wish they had put the guardrails up sooner.

Speed vs. thoroughness

DIY is fast. You draft a policy in twenty minutes, post it in Slack, call it done. Software takes a day to configure, a week to adopt, a month to trust. Hiring a person takes longer still—posting, interviewing, onboarding, ramping. Most teams skip this trade-off entirely. They assume speed is always better. Wrong order. A hastily written expense policy can cost you thousands before you notice the leak. A one-page employee handbook that forgets to mention your state's sick-leave law is not a policy; it's a trap. The thoroughness payoff appears later: when a dispute arises and your documentation holds up, when an audit passes without a finding, when a new manager joins and actually reads the playbook before making a mistake. What usually breaks first is the gap between how fast you grew and how thoroughly you built the structure underneath. That gap is where the real cost lives.

Not every human checklist earns its ink.

Not every human checklist earns its ink.

The trick is not to pick the fastest road. Pick the road that survives the mistake you haven't made yet.

After You Choose: The First 90 Days of Implementation

Setting Up Payroll and Time Tracking First

Your first paycheck run will expose every gap in your system. Not ready? Too bad—the calendar doesn't wait. I have seen teams spend weeks debating which PTO policy to adopt, only to realize they can't figure out how to deduct a lunch break. Start with the mechanics: who gets paid what, how hours are captured, and where the money actually goes. For small teams using software, the first week should be mapping wage codes, testing one dummy paycheck, and verifying tax withholdings. For DIY teams—this means manually double-checking your spreadsheet formulas against state wage laws. The catch is that errors here compound fast. One wrong overtime multiplier can cost you a weekend of rework and an angry employee. Set a hard deadline: day seven, a real payroll test with real data. Not optional.

Time tracking feels simpler than it's. Most teams skip this: they assume everyone will log hours honestly. Then the seam blows out when a contractor disputes a 50-hour week. Your move—choose a single method (app, punch clock, paper log) and use it every time. No exceptions. That clarity saves you from he-said-she-said fights later.

Writing an Employee Handbook Before You Need It

Nobody reads a handbook until something goes wrong. Then it's the first document a lawyer requests. A short, plain-language handbook—15 pages max—covers your bases without overwhelming new hires. Include: work hours, pay periods, holiday schedule, remote work rules, and a simple anti-harassment policy. Don't copy-paste from a template you found online. State laws vary wildly; a California clause about meal breaks won't protect a Texas team. Dedicate days 15 through 30 to drafting, then run it past a local employment attorney. One-time cost, permanent shield.

'Your handbook is not a mission statement. It's a liability map. Write it like you expect to defend it.'

— Employment lawyer who reviewed my team's first draft

The tricky bit is tone. Too rigid, and you sound like a corporation of 5,000. Too loose, and you create implied promises—like 'we always allow remote work Friday,' which then becomes a right. Balance: use 'generally' and 'at company discretion' for flexibility. Hard lines only where the law demands them. That nuance takes time, but rushing here invites future grievances.

Running Your First Compliance Audit (Day 60–90)

Wrong order. Most small teams do this only after a complaint or a tax penalty. Don't be them. By day 60, schedule a two-hour compliance review. Pull your I-9 forms, check that W-4s are legible, verify unemployment insurance is active in every state where you have a remote worker. What usually breaks first is multi-state registration—that remote hire in Oregon? You likely owe Oregon payroll tax from day one. The penalty for missing it's back taxes plus interest. Not a fine you want to explain to your co-founder.

Audit also means looking at your actual practices versus your written policies. Handbook says 30-minute lunches? Are people actually taking them? If not, you have a liability gap. Fix the practice or fix the policy—choose one by day 75. I have fixed this for teams by simply deleting an unenforceable rule and replacing it with something they could actually monitor. No shame in admitting you over-promised.

By day 90, you should have: payroll running smoothly, a handbook you trust, and a compliance checklist you actually use. That's not perfection—it's a foundation. Everything else—performance reviews, promotion tracks, culture initiatives—can wait. Get the bones right first. The next 90 days will tell you what hurts.

Risks of Getting HR Wrong—or Delaying It

Wage and Hour Lawsuits—The Cost of ‘We’ll Figure It Out Later’

The fastest way to bleed cash in a small team? Misclassify an employee as a contractor or skip paying overtime. I have watched a 12-person startup lose $48,000 in back wages because they let a ‘salaried’ designer work 55-hour weeks for six months without tracking hours. The Department of Labor doesn't care that you're friends with the team. They care about the timecard. That sounds fine until a former employee files a complaint—then you're looking at double damages, plaintiff attorney fees, and a federal investigation that eats two months of your calendar. One misstep on overtime exemptions and your quarterly profit vanishes.

The catch is enforcement is often triggered by something small—a disgruntled ex-contractor, a random audit, or a competitor’s tip. Most small teams never budget for this risk. They should. A single wage claim can cost more than a year of basic HR software. And the headache? That's free.

Misclassification Penalties—When Labels Cost You

Call someone a ‘freelancer’ but control their hours, provide their equipment, and dictate their workflow? You have an employee—in the eyes of the IRS and most state labor boards. The penalty for misclassification runs roughly $5,000 per worker per return, plus back payroll taxes, plus interest. For a team of three misclassified people over two years, that's north of $30,000 before you pay a lawyer. I fixed this once for a 15-person agency by reclassifying four roles and setting up proper time tracking. It was awkward. It was also cheaper than the lawsuit they dodged three months later.

Worth flagging—the IRS offers a voluntary classification settlement program, but you typically can't use it after an audit begins. The window is small. Most teams skip this step until it's too late. Don't be most teams.

Reality check: name the resources owner or stop.

Reality check: name the resources owner or stop.

Low Morale and Turnover Costs—The Hidden Bleed

Bad HR doesn't always explode in a lawsuit. Sometimes it leaks quietly through turnover. One person quits because they never received a clear performance review, never felt trusted with time off, or watched a colleague get promoted unfairly. Replace that person? Recruiting costs alone run 20–30% of annual salary. For a $60,000 role, that's $12,000 to $18,000—plus lost productivity for four to six weeks while the new hire ramps up. Multiply that by two departures per year and your HR failure just cost more than a part-time HR consultant would have.

Morale is harder to quantify but faster to crater. I have seen a five-person team lose two members in three months because nobody knew who to ask for a simple sick-day policy. The remaining three? They stopped suggesting ideas. They stopped staying late. They started interviewing. The cost was invisible until the revenue slipped.

‘The team didn't leave because of the work. They left because nobody managed the people part. That was entirely preventable.’

— Operations lead, 12-person SaaS firm, reflection after losing their third hire in eight months

So what does delaying HR actually cost? Add up the wage claims, the misclassification fines, and the quiet churn. The number is almost always larger than the price of getting HR right on day one. Your move.

Mini-FAQ: Quick Answers to Common HR Questions

Can I just use spreadsheets for HR?

You can. Plenty of teams do—until they can't. A spreadsheet handles names, start dates, and even vacation days if you're meticulous. The catch is what happens when you miss a line. I once watched a founder manually reconcile PTO across three tabs, only to accidentally delete a row. That's a lawsuit waiting to happen. Spreadsheets are fine for a team of three where everyone trusts everyone. Past seven people? The seams start to blow. Missing a compliance deadline because your formula broke isn't a spreadsheet problem—it's a liability problem. The cheapest option isn't free if it costs you a wage claim.

When is the right time to hire an actual HR person?

Not when you feel overwhelmed—that's too late. The right time is when you catch yourself answering the same people question three times in one week. Payroll errors. Confusion about overtime. Someone asking if they can work from another state. Those are signals. Most teams I've worked with waited until they hit twenty-five people. Bad move. At fifteen, you're already spending eight hours a week on HR admin. That's a day you're not selling, building, or leading. Hire an HR generalist when the cost of their salary is less than the value of your lost focus. Run the math—it usually flips around twelve to eighteen people.

What's the cheapest way to stay compliant?

A Professional Employer Organization (PEO) that bundles payroll, tax filings, and compliance into one monthly fee. You co-employ your team through their infrastructure. That sounds expensive until you price out a single misclassification penalty, which can hit $1,000 per worker per violation. The trade-off: you lose some control over benefits and policy decisions. But for a team of five to fifteen, it works. We fixed this for a client who was six months behind on state filings—the PEO caught everything in their onboarding review. Cheaper than a lawyer. Faster than learning labor law yourself.

“I thought compliance was a later-stage problem. Then I got a notice from the Department of Labor. That letter is still on my desk.”

— Founder of a 14-person agency, two years ago

That hurt. Don't let it be you.

So What Should You Do? A Calm Recommendation

For teams under 5

Keep it simple—almost absurdly simple. You don't need a system yet. I have watched three-person shops waste forty hours wrestling with an ATS when a shared spreadsheet and a group chat would have done the job. Your real risk? Not documentation, but distraction. A single bad hire hurts badly at this size, but over-engineering hurts worse. Use a checklist template. Payroll via your bank or a basic app like Gusto. Store signed documents in a single folder. That's it. You fix HR problems by talking, not by buying.

What usually breaks first is time-off tracking. Someone takes a Friday, someone else assumes they were sick, resentment simmers. Solve that with a shared calendar note. One line. No software needed.

For teams 5-15

This is the danger zone—too big for tribal knowledge, too small for a dedicated HR person. The trap is buying a platform designed for a company of 200. Don't. You want something that handles compliance paperwork and PTO accrual without needing an admin to babysit it. Rippling or BambooHR lite works. But here is the trade-off: you will still handle messy human conversations yourself. Software can't mediate the clash between your best salesperson and the quiet engineer who is quitting because of them.

We fixed this by splitting the difference—payroll and policy templates in one tool, the actual people-problems handled in a monthly thirty-minute standup with no agenda except "what feels off." That sounds thin. It works. The catch is that you must actually hold those meetings. Miss two in a row and you're back to guessing.

For teams 15-50

Now you need structure. Not bureaucracy—structure. At this scale, inconsistency costs you legally and culturally. One manager lets people roll in at 10am, another demands 8:30 sharp; the grievance files start stacking. You need someone who owns this, even if it's a fractional HR consultant (twenty hours a week is enough). Your roadmap: a clear handbook, documented performance reviews, and one person who can say "no" to the founder's pet hire when the background check flags a red light.

'The hardest part was hiring an HR person before we felt ready. We waited until a lawsuit threat forced us. That was stupid.'

— Operations lead, 28-person agency, 2024

Don't wait for the threat. If you're at twenty people and growing, hire the HR function before you need it. Not a VP—just someone with a SPHR certification and a spine. They will cost you maybe $40k part-time. One compliance fine or wrongful-termination settlement runs triple that. The math is not close.