How to Run HR Without an HR Team in 2026

Most solo founders treat HR as something that starts once they have five employees. Before that, hiring happens over DMs, onboarding is a Slack message with a Notion link, and nobody tracks PTO because nobody has taken any yet. This works right up until the first dispute, the first missed compliance deadline, or the first hire who asks a question nobody wrote an answer to.

The fix is not hiring an HR generalist at your fifth employee. It is building a people-ops agent that runs the process consistently from hire number one, so the paperwork, the onboarding, and the compliance tracking exist before you need them, not after something goes wrong.

Why HR is different from other functions you can automate

HR has a property that makes founders more cautious about automating it than marketing or finance: every mistake involves a person, and some mistakes carry legal exposure. A marketing agent publishes a mediocre post. An HR process that mishandles a termination or misclassifies an employee can turn into a lawsuit.

This is the correct instinct, but it leads founders to the wrong conclusion: that HR can't be automated at all, so it doesn't get built until it's forced. That's backwards. The process pieces of HR, screening, scheduling, onboarding, compliance tracking, are exactly the kind of repeatable, rules-based work agents handle well. The pieces that need a human are the decisions, not the paperwork around them.

The founders who get this right separate the two cleanly from day one: an agent runs the pipeline and the checklist, a human makes every call that affects someone's job, pay, or standing.

What a people-ops agent can actually own

Resume screening against a rubric. If you've written down what a good candidate looks like for a role, an agent can screen a stack of resumes against it faster and more consistently than a founder doing it between meetings. It should surface the top matches with reasoning, not silently reject anyone.

Interview scheduling and coordination. Chasing calendar availability across a candidate and two or three interviewers is pure logistics. An agent can own this end-to-end, including reminders and reschedules.

Onboarding checklists. Laptop and account provisioning, benefits enrollment reminders, first-week task lists, intro Slack messages to the team. This is a documented sequence with no judgment call, which makes it one of the highest-leverage things to hand off immediately.

Offer letter drafting from an approved template. Once compensation and terms are decided by a human, generating the letter itself is a fill-in-the-template task. The agent drafts, a human still signs off before it goes out.

PTO, compliance deadline, and policy tracking. Who is due for a benefits renewal, whose visa or contractor agreement needs review, which state's leave law applies to which employee. This is exactly the kind of detail that quietly slips when a founder is tracking it by memory, and exactly the kind of detail an agent tracks perfectly.

Answering repeated policy questions. "How much PTO do I have left," "what's our parental leave policy," "how does the 401k match work." If it's documented, an agent can answer it instantly instead of a founder digging through a Notion doc for the third time this month.

Where people ops still needs a human

The final hiring decision. An agent can build the shortlist and summarize interview feedback. The judgment call on who joins the team, and the culture fit read that comes from an actual conversation, stays with a person.

Any termination. This needs a human conversation, full stop. An agent can prepare the paperwork and the compliance checklist that goes with it, but the conversation itself, and the decision to have it, is never automated.

Compensation changes. Raises, promotions, equity grants. These are judgment calls with financial and legal weight that belong to a founder, not a rubric.

Complaints and disputes between people. If two employees have a conflict, or someone raises a complaint about another person, this needs a human who can actually listen and investigate. An agent routing this to a template response makes it worse, not better.

Anything jurisdiction-specific. Employment law varies by state and country in ways that carry real liability if you get it wrong. An agent can flag "this employee is in a different state, check the leave policy," but the actual determination should go to a PEO or employment lawyer, not a generated answer.

The people-ops stack that makes this work

1. Written policies before the agent goes live. PTO policy, remote work policy, a documented hiring rubric per role. An agent with no written policy improvises, and an improvising HR process is how inconsistent treatment happens, which is its own liability. Spend the time writing these down before automating anything.

2. An ATS or lightweight hiring tracker the agent can read and write to. The agent needs a system of record for candidates and their status, not a set of email threads it's trying to reconstruct context from every time.

3. A PEO or payroll platform handling the compliance-heavy mechanics. Payroll, tax withholding, and benefits administration are heavily regulated and not worth building in-house even with agents. Use a PEO (Justworks, Rippling, Gusto, or similar) for this layer; let the agent handle the coordination around it, not the compliance itself.

4. A clear escalation line to an employment lawyer or fractional HR consultant. Not for daily use, for the handful of moments a year, a termination, a complaint, a jurisdiction question, that need a professional. Know who that is before you need them, not after.

5. A human review cadence, even at tiny scale. A 15-minute weekly check on what the agent handled, what it escalated, and any policy question that came up more than once. This is where a founder catches a subtle problem, a rubric that's screening out good candidates, a policy nobody wrote down, before it becomes a pattern.

Stage-by-stage: what to automate when

Pre-hire (0 employees, contractors only). Get the hiring rubric and offer template written before your first hire, not during. This is the cheapest time to do it.

First 1-5 hires. Agent runs screening, scheduling, and onboarding. Every hiring decision and every offer still goes through the founder personally. A PEO handles payroll from hire one, this is not worth DIY-ing even at this size.

5-15 people. Compliance tracking (PTO, benefits renewals, policy questions) fully automated. The agent is now handling enough repeated policy questions that documenting and automating answers saves real founder time. Still no automated hiring decisions or terminations.

15+ people, or first jurisdiction beyond your home state. This is usually the point a founder brings on a fractional HR consultant or part-time HR hire, not because the agent stopped working, but because case complexity (multiple states, a first real dispute, a first layoff) now needs a person with employment law judgment reviewing decisions, with the agent still running the process underneath.

What this looks like in practice

Pancake runs on Pancake: hiring, onboarding, and policy tracking for the team building this product go through an agent-run process, with every hiring decision, offer, and anything involving a person's standing still made by a human. The pattern holds whether you're a solo founder hiring your first contractor or a ten-person team onboarding your fifth engineer: agents run the process, people make the decisions.

Solo or multiplayer, the split doesn't change. What changes is how much process there is to run, which is exactly the part an agent scales without adding headcount.