Does your nonprofit need an HR person yet? (And what to build first if not)

There's a moment most growing organizations hit without noticing.

Someone on your team — usually the person running operations, sometimes finance, occasionally you — has quietly become the place where every people question lands:

How do we write this job posting. What do we pay the new hire.

Why are two people doing similar work on different salaries.

A manager just came to them with a conflict on their team and they had no process to offer, so they improvised one.

None of this is in that person's job description. All of it is now their job.

If that's familiar, you've probably started asking whether it's time to hire someone for HR. It's the right instinct, but it's not quite the right question — and answering the wrong question is how organizations end up spending a year and a salary solving the wrong problem.

The standard answer, and why it's incomplete

Search this question and you'll get a fairly consistent reply: hire a dedicated HR person somewhere around 50 employees, or sooner if compliance risk is keeping you up at night.

That advice isn't wrong. The legal obligations are real, and they don't wait for you to feel ready — the moment you have one employee, you're subject to labor law, and the exposure compounds as you grow. And there is a genuine inflection point in the 40-to-60-person range where the volume of people work simply exceeds what anyone can carry on the side.

The problem is that this framing treats hiring a person as the only available move. For most organizations asking the question — the ones between roughly 15 and 45 staff — a full-time HR hire might be premature, but continuing as you are is quietly expensive. You're stuck between an answer that's too big and an answer that's "wait." Neither is right.

The useful question isn't when do we hire the HR person? It's when do the ad-hoc systems we've been running on start costing us more than they save? — and what do we do about it that isn't just a job posting.

What's actually happening: people systems debt

When an organization grows without building its people systems on purpose, it accumulates what I call people systems debt — the compounding cost of decisions you kept deferring because there was always something more urgent.

It shows up in three forms.

Clarity debt. Roles, expectations, and decision rights were never written down. People are unclear on what they own, where their authority ends, and who to go to. Work falls through gaps, or three people do it twice.

Manager debt. People were moved into management because they were good at the job below it, and then handed no standards, no training, and no support. They're managing the way they were once managed, or the way they're guessing they should.

Consistency debt. Hiring, feedback, promotions, and pay happen differently every time, depending on who's in the room and how busy they are. There's no logic anyone could explain to a new employee — or a funder.

Like any debt, this one charges interest. You pay it in the hours your operations lead spends on work they weren't hired for. You pay it in turnover you can't fully explain. You pay it in the slow drift between the organization you meant to build and the one that's actually running — and, eventually, in the confidence your funders have that you can steward growth responsibly.

Most organizations don't decide to take on this debt. They accrue it one reasonable postponement at a time.

Signs you've outgrown informal HR

You don't need a headcount milestone to know you're carrying too much of this. You need an honest look at how the work actually happens. A few signals:

• Your operations or finance lead is the de facto HR person, and it isn't in their job description.
• Onboarding a new hire depends on who has time that week and what they remember to cover.
• Two people doing comparable work are paid differently, and no one can walk you through why.
• You've lost someone in the last year and couldn't give a clear account of what drove it.
• A manager brought you a people problem and you realized there was no process to hand them — you had to invent the response on the spot.
• Your team gatherings — the retreats, the shared meals — feel like they're standing in for something more intentional you haven't had the bandwidth to build.
• Every people decision escalates to you or one other person, because the judgment lives in their head, not in a system.

One or two of these is normal for a young organization. Four or five means the informal approach has stopped serving you, and the cost is already being paid — just not on a line item you can see.

Person, or system? A decision framework

The choice isn't "hire or wait" — and headcount won't settle it. Two 30-person organizations can be in different places entirely: one still runs every decision through the founder and lives grant-to-grant; the other has a leadership team and commitments that outlast any single funder. They need different things.

What moves the answer is organizational maturity — roughly three stages:

The through-line: a person hired after the systems are defined can succeed. A person hired instead of defining them usually can't — no matter the headcount.

What "build the systems first" actually means

This can sound abstract, so here's the concrete version. When organizations build their people foundation, the work tends to go in roughly this order:

1. Role clarity and decision rights. What each person owns, where their authority ends, and who decides what. Almost everything else gets easier once this exists.
2. A repeatable hiring process. A defined sequence — how roles get opened, how candidates are assessed, who's involved, how the decision gets made — so hiring stops consuming your operations lead.
3. Compensation logic. Not a rigid banding structure, but a rationale you could explain out loud: why this role pays what it pays, and how that relates to the roles around it.
4. Manager expectations. A shared, written standard for what a manager here is responsible for — one-on-ones, feedback, development — so managing stops being improvised per person.
5. A feedback and check-in rhythm. A predictable cadence for how people hear where they stand, so it isn't only happening when something has gone wrong.

None of this requires a large team or a big budget. It requires deciding to build it on purpose, once, rather than rebuilding it informally every time the question comes up.

The cost of "we'll figure it out later"

It's worth putting a number on what the informal approach costs, because it usually feels free and isn't.

Say your operations lead earns $60,000 yearly and spends 30% of their time on ad-hoc people work — hiring, onboarding, smoothing over conflicts, answering benefits questions. That's roughly $18,000 a year in salary pointed at work they weren't hired to do, and weren't trained for. And that figure is before you count the cost of a hire that doesn't work out, or someone good leaving because the manager relationship was never set up to succeed.

The other common version of "later" is "we'll handle it internally." Someone will look into it. IT will build the tracker. The umbrella org's HR office will take it on. Sometimes that's real. Often, six months later, nothing has been built, the same person is still carrying the same load, and the organization has simply lost half a year. The gap between "we'll handle it" and anything actually getting handled is where the quiet cost lives.

Where to start

If you recognized your organization somewhere in this, the next step is small.

The People Systems Snapshot is free, self-guided, and takes about three minutes. It won't sell you anything — it's a way to see which of the three debt types is weighing on you most, so you can have a clearer internal conversation about what to do next.

If you already know you need to prioritize and sequence the work, that's what the People Systems Assessment is for: a three-week diagnostic that ends in a 90-day roadmap you can actually act on.

I spent a decade in people and culture roles inside mission-driven organizations, including as HR Director at an international NGO, before starting this practice. I've been the person carrying the ad-hoc systems, and I've built the ones that replaced them. If it would help to talk it through, that's the work.

---