Accidental HR: The Foundation You Didn't Choose

You Already Have HR. The Question Is Whether You Built It on Purpose.

Where the people function is hiding in your 10–50 person company, and what to do once you can see it.

At 22 people, your CFO has accidentally become your comp policy.

Your EA has accidentally become your culture officer.

Your head of ops has accidentally become your people manager, running performance reviews, mediating Slack fights, and writing offer letters at 11pm.

You, the founder, are doing the highest-stakes HR work in the company. None of this is by accident; those calls always land on you, and you’re telling yourself it’s not HR.

You don’t have a People function, but you do have HR.

You have it spread across four people who didn’t sign up for it, who don’t talk to each other about it, and who are each making decisions that will compound for the next three years.

None of those decisions feels like a problem in the moment. Each one is the right call by the person making it, with the information they have. The problem is the shape they make together.

• A comp policy nobody designed.

• A culture nobody named.

• A people function with no architect.

• A founder pretending the people work isn’t people work.

  
  

None of it shows up in your numbers. All of it shows up in who quits.

That’s the shape of the problem.

Until you see it, you can’t choose whether to fix it.

Where your HR is hiding right now

Every Series A company I work with has the same pattern. The HR function is already running. It’s just been built by accident, by accretion, by whoever raised their hand in a meeting two years ago.

Here are the four places it’s usually hiding.

1. The CFO who’s setting comp policy by approving offers

Picture a Friday afternoon. Your VP of Engineering candidate has come back asking for a stretch on the offer. Your CFO is in the loop because the number is real money. He says yes, partly because he believes in the candidate, partly because he doesn’t want to lose the close.

That decision just became your comp philosophy.

The next person who asks for a stretch will quote that offer. The next leveling decision will reference that base. Six months from now you’ll have a comp band that nobody designed, anchored to one Friday-afternoon approval.

What he’s absorbing: comp philosophy by precedent.

What it costs: eighteen months later you have fourteen different deals and no one can explain the bands. Your top performer asks for parity, finds out what someone else makes, and quits.

2. The EA who’s quietly the culture officer

She knows every birthday. She remembers the anniversary of your engineer’s mom passing away. She picks up signals in Slack, the quiet engineer who used to post jokes and went silent three weeks ago. She catches the tension between two senior leaders before either one says anything.

Nothing in her job description mentions any of this.

She is the social fabric of your company.

When she leaves, and she will, because she’s good, and she’ll find a role that names what she actually does, the fabric goes with her. You’ll feel the tear and not understand what happened.

What she’s absorbing: emotional labor, retention signal, internal communications.

What it costs: a culture you can’t reproduce, because you didn’t know it was being held together.

3. The Head of Ops running people work on the side

I wrote about this one on LinkedIn last week. The story keeps coming back because it keeps coming up.

The pattern: she’s good. That’s why it lands on her. She runs onboarding because nobody else thought to. She handles offer letters because legal wasn’t fast enough. She mediates the Slack dispute because she happened to see it.

Six months in, she’s spending forty percent of her time on people work and her actual ops job is suffering. She’s not telling you yet. She’s still the one who raises her hand.

What she’s absorbing: systems work, employee relations, hiring logistics.

What it costs: either she quits, or she becomes your unofficial HR director and resents you for not naming it.

4. The founder doing the highest-stakes HR

You.

The exec who isn’t working out and needs to go. The comp escalation from your best engineer. The co-founder conflict you’ve been managing through 1:1s. The first real performance plan, which you wrote yourself because you didn’t know who else should.

You spend 15-25% of your time on people work. You also tell yourself you don’t have time for HR.

Both things can’t be true.

What you’re absorbing: anything no one else will touch.

What it costs: the strategy work you’re not doing, the board meetings you’re prepping at midnight, and the version of the company you’re not building because you’re too busy holding the one you have together.

The diagnostic

Five questions. Answer them honestly. If different people in your company would answer differently, you don’t have a clarity problem. You have HR, and it’s distributed.

1. If your VP of Engineering asked for a twenty percent raise tomorrow, who decides and on what basis?

2. Who would notice, within the first week, if your top engineer was disengaged?

3. What is the difference between Senior and Staff at your company? Could three of your hiring managers give the same answer?

4. When was the last person you let go, and who actually made the call?

5. If your EA gave notice tomorrow, what would break that you didn’t know was load-bearing?

If you can answer all five cleanly, and they all match what your team would say, you have intentional HR. Even if no one in the company has the title.

If you can’t, you have accidental HR. Which is fine. Most companies your size do.

The question is what you do with that information.

Accidental HR vs. intentional HR: The actual difference

Here’s the part most founders miss.

Every people function starts accidental. The instinct to read “accidental” as failure and “intentional” as success is too clean. Real companies don’t skip the accidental phase. The work is to know when you’re in it, and to choose the moment to make the transition.

Accidental HR is what you have when no one is the designer. It’s a system that emerges from individual decisions, each one defensible in the moment, that compound into something nobody would have chosen on purpose.

Intentional HR is when one person’s job is to look at the whole shape and ask the question your CFO and your EA and your Head of Ops can’t ask because they’re each inside their own piece of it: is this the system we’d want if we were starting from scratch, and if not, what’s the shortest path to get there?

That person doesn’t have to be a full-time Head of People. At twenty-five, thirty, even forty employees, they probably shouldn’t be.

What the founders I work with actually need is five to twelve hours a week of someone who’s done this five times before. Someone who can name what’s been built by accident, design what should be built on purpose, and put the foundation down before the cracks show.

Not an HR Manager. Not an admin layer. A designer.

The cost of waiting

The trap of accidental HR is that the cost isn’t visible until it’s already paid.

You won’t see it in this quarter’s numbers. You’ll see it in:

• The senior engineer who quietly accepts an offer at a competitor because she finally found out what the new hire makes.

• The re-leveling exercise at year three that takes six months and three departures.

• Your CFO, eighteen months from now, telling you he doesn’t want to be the comp police anymore.

• Your Head of Ops sitting down in a 1:1 and saying, “I think I need to move on.”

• The version of your company you didn’t build because you spent 20% of your time on people work and called it something else.

• 
  

By the time those costs land, the foundation has already set. You can re-pour it. Most companies do, eventually. But the re-pour is always more expensive than building it on purpose the first time.

Where to go from here

You don’t need to hire HR at twenty-two people.

You need to look at where HR is already happening in your company, name the people quietly absorbing it, and decide whether the system they’re building by default is the one you’d choose by design.

If it isn’t, the move is not to add a person. The move is to add a designer.

That’s the transition from accidental to intentional. It happens earlier than most founders think and costs less than they fear, if you do it before the cracks show.

If you’re in that stretch and want a second set of eyes, I do short strategy calls with seed and Series A founders working through exactly this transition.

The people work is going to happen either way.

The only question is whether you’re the one designing it.