Onboarding runs
Sends the welcome, walks each new hire through the checklist, collects documents, and nudges anything outstanding.
How-to — — by Mahmoud Zalt
Automate HR for a small team: hire an AI Employee to run onboarding, answer policy questions, and track time off, without a full HR hire.
Small teams hit an awkward HR stage early. You are too big to run onboarding from memory and too small to justify a dedicated people-ops hire. So the work lands on a founder or an office manager who never signed up for it: chasing new-hire paperwork, answering the same questions about vacation policy, remembering whose contract renews when. None of it is hard, but all of it is easy to drop, and dropped HR work is the kind that quietly turns into a resentful employee or a compliance gap.
An AI Employee fits this stage well because most early HR work is process, not judgment. Onboarding is a checklist. Policy questions have documented answers. Time off follows a rule. Those are exactly the tasks that reward consistency and follow-through over discretion, and they are the ones a busy founder is most likely to let slip. The Employee owns the process so nothing falls through, and the genuinely human parts of managing people stay firmly with you.
The safe zone is everything repetitive and rules-based. Onboarding is the clearest win: the Employee sends the welcome, walks the new hire through the checklist, collects the documents, and nudges anything outstanding, so week one is the same smooth experience whether you are watching or not. Policy questions are the next: it answers from your actual handbook instead of forwarding every how-many-sick-days email to you. Time-off tracking, document organization, and renewal reminders round it out. These are the tasks that eat an afternoon and add up to a real drag.
The line you do not cross is judgment about people. Compensation decisions, hiring and firing, performance conversations, and anything involving a conflict or a complaint stay with a human, full stop. The Employee can organize the information that feeds those decisions, but it never makes them. That boundary is not a limitation to work around, it is the design: automate the process, keep the people judgment, and you get the structure of an HR function without handing sensitive calls to software.
A fair worry at this stage is privacy, because HR data is sensitive by nature. The answer is to give the Employee only what it needs for the process work and nothing more. It can run an onboarding checklist and answer handbook questions without ever touching salary figures or performance notes, and those sensitive records stay in systems only you access. Scope it to the repetitive tasks, keep the confidential material out of its reach, and you get the time savings without widening your exposure.
Setting up an HR AI Employee is mostly about handing it your existing process once, so it can run it every time after. The longest part is writing down the onboarding steps and pointing it at your handbook, which is worth doing anyway because a documented process is more valuable than one that lives in your head. The five steps below take a day for a small team and need no HR background, just clarity about how you already do things.
Two warnings from doing this for a small team. First, be explicit about the boundaries in step four, because the whole trust of the system rests on the Employee reliably escalating the sensitive topics instead of trying to answer them. Second, keep a human name attached to the experience: onboarding should feel like joining a company that cares, so the Employee handles the logistics while you personally send the real welcome. The automation carries the checklist, not the relationship.
Sends the welcome, walks each new hire through the checklist, collects documents, and nudges anything outstanding.
Responds to routine handbook questions from your real policies so the same questions stop landing in your inbox.
Logs requests, applies your rules, and keeps a clear record so nobody loses track of who is out and when.
Keeps contracts, agreements, and renewal dates tidy and reminds you before anything important lapses.
Automation covers the process layer, not the people layer, and it is honest to name where a human professional is still the right call. Complex compliance in a regulated industry, a workforce spread across many jurisdictions, a serious conflict or investigation, and the strategic side of building culture and compensation all need real HR expertise. The AI Employee does not replace that, it clears the administrative floor beneath it so that when you do bring in HR help, they spend their time on the hard, human work instead of chasing onboarding documents.
The through-line is that HR for a small team fails from neglect, not from bad intent. The founder means to run clean onboarding and answer questions promptly, then the week gets busy and it slips. An AI Employee fixes the neglect problem specifically, because it does the follow-through you keep postponing without ever getting busy or forgetting. You supply the process and the judgment, it supplies the consistency, and the two together give a small team the structure it needs long before it can afford a full people-ops hire.
Picture the result after a few new hires. Every person joins to the same warm, organized first week. Nobody emails you to ask how vacation works, because the answer is a message away. Time off is tracked, contracts are current, and renewal dates never sneak up on you. You still make every call that matters about your people, but the administrative weight that used to make HR feel like a chore has quietly moved off your desk. That is what automating HR for a small team actually looks like.
No, and it should not try. It handles the repetitive process work: onboarding checklists, routine policy questions, time-off tracking, and document organization. Decisions about pay, hiring, firing, performance, and conflict stay with a human. For a team too small to justify a full HR hire, it provides the structure without taking over the judgment.
It is when you scope it correctly. Give the Employee only what it needs for the process work, such as onboarding steps and handbook policies, and keep sensitive records like salaries and performance notes in systems only you access. It can run the repetitive tasks without ever touching the confidential material, which keeps the time savings without widening your exposure.
Onboarding, because it is the most process-heavy and the most visible to a new hire when it goes wrong. Once the onboarding flow runs cleanly, add routine policy answers from your handbook, then time-off tracking and document organization. Save anything involving judgment about people for a human every time.
No. The setup is mostly writing down the onboarding steps you already follow and pointing the Employee at your existing handbook. That documentation is valuable on its own, and the Employee turns it into a repeatable process. You describe how you already do things in plain language rather than learning any HR system.
The entry plan starts at 49 per month with credits bundled in, and there is no per-seat surcharge as your team grows. That is a fraction of the cost of a dedicated HR hire, which is what makes it a fit for the awkward stage when you have outgrown running HR from memory but cannot yet justify a full role.
The honest takeaway is that automating HR for a small team is not about removing the human from people-ops, it is about removing the busywork that keeps the human from doing people-ops well. Hire the role, hand it your onboarding process and handbook, draw a clear line around the sensitive decisions, and test it on one real onboarding before you trust it fully. Do that, and the administrative drag disappears while every call that actually affects your people stays exactly where it belongs, with you.