when-to-make-first-hires

Installation
SKILL.md

When to Make Your First Hires — Sequence for Leverage

Overview

Early hires are the highest-variance, highest-cost decisions a small founder makes: too early burns runway on unvalidated work; too late caps growth and burns the founder out. The discipline is to hire against a validated, repeatable need that frees the founder's highest-leverage time — and to first ask whether the work should be hired, automated, outsourced, or eliminated.

The Process

  1. Identify the constraint — what is actually capping growth or consuming the founder's highest-value hours? Hire against that, not general busyness.
  2. Validate the need is real and repeatable — is there steady, documented work? Gate: hiring for a role you haven't done/validated yourself transfers an unsolved problem (see founder-led-sales).
  3. Run the hire-vs-alternatives test — could this be automated (agent), outsourced (contractor/fractional), or eliminated before a full-time hire?
  4. Write the SOP first — you can't onboard (or automate) what isn't documented (see sop-systemization).
  5. Sequence by leverage — hire the role that most frees the founder's scarce time or unblocks the constraint; avoid hiring comfort roles.
  6. Protect runway — model the hire against default-alive date. Gate: a hire that pushes profitability past runway needs an explicit funding plan.

When to Use

  • Founder overloaded, considering first/next hire
  • Deciding hire vs contractor vs automate
  • Sequencing the first few roles
Installs
1
GitHub Stars
10
First Seen
5 days ago
when-to-make-first-hires — deciqai/knowledge-skills