Subscribe

Hiring Your First Employee: A Field Guide

Nobody feels ready for their first hire. Revenue feels too fragile, the tasks feel too personal, and the payroll paperwork feels like joining a different species of company. Founders routinely wait a year past the point where the math already worked.

The readiness test isn’t revenue — it’s repetition

Track one ordinary week. If ten or more hours went to tasks that follow a written procedure (see: SOPs), you have a job description hiding in your calendar. You’re not hiring someone to be you. You’re hiring someone to run the documented 40% of your week so you can sell, build, or rest.

Scope the role around outputs, not hours

  • Write the role as five recurring outcomes, not a list of traits.
  • Hire for reliability over brilliance — the job is consistency you can build on.
  • Part-time first is fine. A great 20-hour hire beats a mediocre 40-hour one.

The first hire doesn’t double your capacity. It returns your attention — and attention is the only thing that was ever actually scarce.

Month one will feel slower, not faster. That’s the training cost, and it’s normal. Month three is where the math you didn’t believe in starts showing up in the calendar.