The steps
About 12 hrDefine the role's first 90 days
Before writing the JD, write three sentences: what this person ships in their first 30 days, their first 60, and their first 90. If you cannot answer any of the three, the role is not ready to hire. The 90-day plan is the hiring brief and the onboarding plan, written once.
Write the rubric before the JD
Pick 3 to 5 evaluation dimensions for this role and anchor each one 1 to 5 with named criteria. Every interviewer scores against the same rubric, and any AI screening you use gets the same rubric as input. Without a rubric, decisions slide toward the loudest interviewer.
Write the JD and post it
Use the rubric and the 90-day plan as the JD's backbone. Avoid generic culture copy; specify the work. Post on your branded career page first (free distribution via Google for Jobs), then on one paid board, then via the founder's personal LinkedIn. Three channels are enough.
Screen applications against the rubric
Triage applications in 30-second passes — yes, maybe, no. Aim for a shortlist of 10 from the first 50 applicants. If the maybe pile is bigger than 30 percent of the total, the rubric is too vague and you should tighten it before continuing.
Run a 30-minute founder screen
First conversation is the founder's. 10 minutes on the candidate's recent work, 10 minutes on the role and the 90-day plan, 10 minutes for their questions. Score against the rubric within an hour of the call ending — memory decays fast.
Run the deep-dive with the most relevant teammate
The teammate who will work most closely with this hire runs a 90-minute deep-dive. For engineering, this is usually paired-coding or system-design. For sales, a role-play. For ops, 'walk me through a real problem you solved.' Score within 48 hours.
Make the decision in one synchronous meeting
Once all interviewers have submitted feedback, convene a 30-minute decision meeting. Everyone shares rubric scores and recommendations first, then discusses. No 'I just got a feeling' allowed — the rubric is the contract. Decision lands the same meeting.
Send the offer within 48 hours of the decision
Strong candidates have other offers. Every day between the decision and the offer letter loses candidates. Use a standard offer template, a pre-calibrated salary range, equity expressed as both percent and shares. Make the first money conversation feel as professional as the first work conversation.
Hiring without an HR team is the default mode for almost every company under 30 people. The founders who do it well are not heroes; they are running a small, repeatable system. This playbook is that system — eight steps, twelve hours of founder time per hire, no enterprise software.
What does "hiring without HR" actually look like in practice?
For a startup or SME under about 30 employees, hiring is a part-time function owned by the founder or by an early operations hire. There is no dedicated recruiter, no separate sourcing team, no HR business partner. According to the U.S. Small Business Administration, small businesses (under 500 employees) employ nearly half of the private U.S. workforce, and the overwhelming majority of those companies hire without a dedicated HR function for their first decade. The pattern is normal. The risk is treating it as ad-hoc instead of systematic.
The eight-step playbook above is what an effective system looks like at this scale. It assumes one founder is the hiring owner, one teammate runs the deep-dive, and the rest of the team rotates in for culture-fit conversations. It assumes a sub-$20-per-month software budget. It assumes the hiring owner has read the JD, written the rubric, and done at least one reference call themselves. None of those assumptions costs money. All of them cost discipline.
TIP — The single most-skipped step Most founders skip step 2 (write the rubric before the JD) because it feels academic. It is the one step that compounds across every subsequent hire — the same rubric, lightly modified, runs your hire-three through hire-thirty. The team that writes the rubric once saves three hours on every hire that follows.
How should the first 10 hires be sequenced?
One role at a time is the rule, until you have hired three people. The founder's attention is the binding constraint, and parallel searches produce worse hires across both. After hire three, parallel searches become viable if a second teammate (or an early head of operations) shares the load.
The shape of the first ten:
- Hires 1–2: revenue-adjacent or product-adjacent generalists who can do three jobs at once. The JD writes itself if the 90-day plan is clear.
- Hires 3–5: specialists who fill the gaps the generalists exposed. By hire five, you are starting to see role categories repeat.
- Hires 6–10: specialists with a more obvious bar. By now the team is calibrated and the interview rubric is on its third iteration. This is where the bar can rise without slowing the process.
This shape is well-documented in startup operating literature; the Y Combinator startup library and First Round Review both publish recurring guidance along the same arc. The specifics differ by company; the order rarely does.
What is the right tool stack for hiring without HR?
Three categories of tooling, plus one optional fourth.
- An applicant tracking system (applicant tracking system or ATS — software for managing applicants from application through hire, with built-in screening, pipeline, and reporting). Even on a free tier, an ATS prevents the cracks that show up around hire three.
- A scheduling tool. Calendly, Cal.com, or the built-in scheduler of an ATS. Manual scheduling consumes a startling fraction of a founder's hiring time.
- A note-taking tool. Notion, Linear, or simply the comment thread on the candidate card inside the ATS. The note tool you actually use is better than the one you do not.
- (Optional) An AI screening assistant. Most modern ATS tools include this. It is the lift between "I read 100 resumes this weekend" and "I read 10 reasoned summaries this weekend."
Notably absent from this list: a dedicated CRM, a sourcing platform, an employer-branding tool, a video-interview platform. Each is genuinely useful at scale; none is required under hire ten.
| Stage of hiring | Spreadsheet-only | Free ATS | Free ATS + AI screening |
|---|---|---|---|
| Hire 1 | Works, painfully | Works smoothly | Overkill |
| Hire 2 | Cracks showing | Works smoothly | Useful on volume roles |
| Hire 3 | Cracks visible | Works smoothly | Saves 2-3 hours per role |
| Hire 5 | Dropped candidates likely | Works | Pays for itself |
| Hire 10 | Untenable | Bumping up against limits | Standard kit |
The pattern: spreadsheet hiring is viable for one or two hires and stops being viable around hire three. The free tier of a small-team ATS extends viability to roughly hire ten on most teams. After that, the limits start to bite — see free ATS vs paid ATS for the four limits that decide when to upgrade.
How do you calibrate the rubric without prior hires?
The chicken-and-egg problem of first-time hiring: the rubric is supposed to be calibrated against prior hires, and you have no prior hires. Two workarounds.
The first is the anti-rubric: write down the three things that disqualify a candidate regardless of how strong everything else looks. Communication clarity, ownership signal, and shipping evidence are the three that most first-time founders converge on. The anti-rubric is easier to write than the positive rubric and almost as valuable.
The second is the borrowed rubric: ask three founders one stage ahead of you what their rubric for the equivalent role was. Most will share it. Modify, do not copy. The borrowed rubric gets you to a calibration starting point in 30 minutes instead of three weeks of trial and error.
"The first rubric is always too vague and the third rubric is always too specific. The one that ships is the second one — written, used on a real role, tightened once."
— Collin, Founder, RecruitIn
What's the founder's hiring time actually spent on?
Twelve hours per hire is the realistic budget. Roughly:
- 1 hour: writing the 90-day plan and the rubric
- 1 hour: writing the JD
- 1 hour: posting and promoting the role
- 2 hours: triage of incoming applications (less with AI screening)
- 2 hours: founder screens (4 candidates × 30 minutes)
- 2 hours: deep-dive interviews observed or attended
- 1 hour: reference calls (2 candidates × 30 minutes)
- 1 hour: decision meeting + offer prep
- 1 hour: contract back-and-forth + close
This excludes the deep-dive interview itself (90 minutes per candidate, ideally led by the most relevant teammate), and excludes any time spent sourcing passively. Add 2 to 4 hours per hire for active sourcing on roles where inbound traffic is light. According to LinkedIn Talent Solutions' Global Talent Trends reports, time-to-hire for small-business hires has trended toward 4 to 6 weeks of calendar time for most non-executive roles, which aligns with the 12-hour founder budget spread across that window.
Closing thought
A startup that treats hiring as a system instead of a series of one-off scrambles outperforms its scrambling peers within ten hires. The system does not require an HR person, a dedicated recruiter, or expensive software. It requires a rubric, a sequence, and a $0-to-$10-per-month tool that prevents candidates from falling through cracks. The founders who do this well are not better at people. They are more disciplined about process.
If you are starting your hiring system today, create a free RecruitIn workspace — a branded career page, an AI screener, and a real pipeline, no credit card. To plan the upgrade trigger before you hit it, read free ATS vs paid ATS. If you have not yet picked an ATS at all, the buyer's guide to free and affordable ATS is the place to start. Pricing details are on the pricing page.
