The first HR hire for a SaaS startup: what to hand over and what to keep

A SaaS founder has twenty-six people and a cluttered inbox of leave requests, offer letters and complaints. She decides it is time for a first HR hire. A week later she cannot say what that person should actually do. Some tasks feel too sensitive to hand over, and others feel too dull to keep.

This post separates the work into what to hand over, what to keep and what to ask for help on. It is for founders who want a clear brief before they write the job description.

Headcount alone is a weak signal. Look at what is eating your week. If you spend more than a few hours each week on leave, onboarding paperwork, hiring coordination and employee questions, someone else could take that load. If you worry about fairness in pay or policy, you may need advice more than a full-time person.

Some founders begin with a part-time arrangement. The page on fractional HR management describes how that works, and it can be a bridge until the workload justifies a permanent role.

• Hiring coordination: scheduling interviews, tracking candidates, sending updates, preparing offer drafts for your approval.
• Onboarding: the first week plan, equipment requests, access requests and the thirty day check in.
• Records and leave: employee files, leave balances, attendance sheets and the shared calendar.
• Policy upkeep: keeping the handbook current and answering routine questions.
• Employee questions: the first point of contact for anything about pay slips, leave or benefits.

These tasks are repeatable. They follow a checklist. They do not need the founder's judgement every time.

Some decisions stay with the founder or the leadership team, even with an HR person in place. The HR hire advises. You decide.

• Who to hire and at what level.
• Pay bands, bonus structure and equity.
• Promotions, exits and warnings in serious cases.
• Culture and how you speak to the team during hard months.

An HR person who also holds all these decisions becomes a bottleneck, or becomes the face of choices they did not make. Keep the line clear.

Some work needs specialist input, not a generalist hire. Employment contracts, pay structure design and any dispute involving legal exposure should be reviewed by your own qualified legal adviser. A first HR person cannot be expected to carry those alone.

Purpose of the role in one sentence.
Tasks handed over, in priority order.
Decisions that stay with the founder.
Who the person reports to and how often they meet.
Tools they will use, such as a shared sheet or HR software.
What a good first ninety days looks like.
Who they can call for specialist advice.

1. 1

   Log your own HR hours

   For two weeks, note every HR related task you do and how long it takes. This shows what is worth handing over.

2. 2

   Sort the tasks

   Mark each task as hand over, keep or get advice. Share the sort with your co-founder.

3. 3

   Fix the basics first

   A pay band sheet, a leave policy and an onboarding checklist make the new person effective faster. See the AI product startups page for how product teams handle this stage.

4. 4

   Write the brief

   Use the template above, then turn it into a job description.

5. 5

   Hire for judgement and warmth

   Look for someone who can keep a secret, explain a rule kindly and say no. Technical HR knowledge can be taught on the job.

6. 6

   Give a named mentor

   Pair the person with an experienced adviser for the first six months.

7. 7

   Review at ninety days

   Check what was handed over, what slipped and what to change.

In the first month the person learns the business, meets every team member and reads the existing papers. In the second month they take over one repeatable task, such as the onboarding checklist, and run it once with you watching. In the third month they own the hiring tracker and the leave records. Hold a short weekly meeting throughout. Ask what confused them, which questions they could not answer and where you made a decision without telling them. These gaps become the next items on the list.

Hiring someone senior too early is expensive. Hiring someone very junior with no support leaves them guessing on delicate cases. Giving them recruitment targets before the role scorecards exist produces rushed hires. Bring them in with a plan, not a pile of tasks.

Tell the team why the role exists, what the person will do and what they will not do. People worry when an HR hire arrives. Some assume layoffs are coming. A two minute note at a team meeting prevents rumours. Say that confidential matters stay confidential, and say whom to approach for what.

Share your open roles with the new hire in one list. If hiring is your main load, the guide on a scorecard and skills test for developers gives a method they can run. Also read how to reduce drop-off between offer and joining.