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.

A better fix than an HR generalist at employee five: a people-ops agent that runs the process the same way from hire number one. The paperwork, the onboarding and the compliance tracking then exist before you need them, instead of 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.

That caution is correct. The conclusion founders draw from it is wrong: that HR can't be automated at all, so nothing gets built until something forces it. The process pieces of HR (screening, scheduling, onboarding, compliance tracking) are repeatable, rules-based work that 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 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 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, and never reject anyone silently.

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

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

Offer letter drafting from an approved template. Once a human has decided compensation and terms, generating the letter is a fill-in-the-template task. The agent drafts it. A human 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. These details slip when a founder tracks them from memory. An agent doesn't forget them once the dates live in a system.

Answering repeated policy questions. "How much PTO do I have left," "what's our parental leave policy," "how does the 401k match work." If the answer is documented, an agent can give it in seconds, 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 call on who joins the team, and the read that only comes from a real 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. The decision and the conversation are never automated.

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

Complaints and disputes between people. If two employees have a conflict, or someone raises a complaint about a colleague, a human has to listen and investigate. An agent answering with a template makes it worse.

Anything jurisdiction-specific. Employment law varies by state and country, and getting it wrong carries real liability. An agent can flag "this employee is in a different state, check the leave policy." The determination itself goes to a PEO or an employment lawyer.

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 treats people inconsistently, which is its own liability. Write these down before you automate 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. A pile of email threads forces it to rebuild context every time.

3. A PEO or payroll platform for 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 or payroll platform (Justworks, Rippling, Gusto, or similar) for this layer. The agent handles 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 that need a professional: a termination, a complaint, a jurisdiction question. Know who that person is before you need them.

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

Stage-by-stage: what to automate when

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

First 1-5 hires. The 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. It isn't worth doing yourself, even at this size.

5-15 people. Compliance tracking (PTO, benefits renewals, policy questions) runs fully on the agent. By now it answers enough repeated policy questions that the founder time saved is real. Hiring decisions and terminations stay human.

15+ people, or your first employee outside your home state. This is usually when a founder brings in a fractional HR consultant or a part-time HR hire. The agent still runs the process underneath. What changed is case complexity: multiple states, a first real dispute, a first layoff. Those need a person with employment-law judgment reviewing decisions.

What this looks like in practice

Picture a six-person startup hiring its first account executive. The agent publishes the role from the approved template, screens 140 applications against the written rubric, and sends the founder a shortlist of eight with a reason next to each name. It books the interviews, collects the scorecards, and drafts the offer once the founder has picked a candidate and set the salary. After the signature, onboarding runs from the checklist: accounts, laptop, a benefits enrollment reminder, a first-week plan. The founder's hours went to interviews and the decision.

Before you open a sales role like that one, look hard at the work it covers. If the job is mostly finding prospects and starting conversations, hand that part to Pancake first. Pancake is an AI GTM team whose agents track who posts about the problem you solve, who engages with a competitor, and which companies have open roles that match your buyer. Every lead reaches you with the signal behind it. Approve it, and Pancake opens the conversation from your own account with a question about that signal. One plan covers every agent at $99/month flat, and Pancake vs hiring a BDR sets it against the salary line.

Solo or multiplayer, the split between process and decisions doesn't change. What grows is the amount of process to run, and that is the part an agent absorbs without adding headcount.

---

Further reading: How to Run Marketing Without a Marketing Team • How to Run Customer Support Without a Support Team • How to Run Finance Without a Finance Team • How to Run Legal Without a Legal Team • How to Run Engineering Without a Dev Team