Three open roles, eight months of runway, and a founder who just realized the spreadsheet says "hire 4 engineers" but the bank account says otherwise. I've sat in that meeting. Twice. The first time, we hired anyway and ran out of cash eleven months later. The second time, I built a plan on one page and we survived.
A lean hiring plan for startups is not a list of roles you'd like to fill. It's a cash-flow document disguised as an org chart—a sequencing decision that ties every hire to a trigger, a cost ceiling, and a date. Most founders skip this because it feels bureaucratic. That's exactly backwards: the smaller the runway, the more the plan matters.
Key takeaways
- A lean plan answers three questions per role: what triggers the hire, what it costs all-in, and what breaks if you wait.
- Fully loaded cost runs 25–40% above salary once you add payroll taxes, tools, and equipment.
- Sequence the first 8–10 hires by bottleneck, not by job title prestige.
- Every role needs a "kill date"—if the trigger hasn't fired by then, the hire is off the table.
- Measure time-to-hire and 90-day failure rate, not headcount growth.
The lean hiring plan founders actually use (and why one page beats twenty)
Here's the thing: I've seen hiring plans that run 30 slides and get ignored within a week. The one that works fits on a single sheet. Four columns, one row per role, nothing else.
The four columns
| Column | What goes in it | Example |
|---|---|---|
| Trigger | The measurable signal that opens the role | Backlog exceeds 6 weeks of work |
| All-in monthly cost | Salary + payroll taxes + tools + equipment amortized | $9,800/month |
| Runway impact | Months of runway consumed if hired now | −1.4 months |
| Kill date | Date after which the role is dropped if trigger hasn't fired | 1 March 2026 |
That's it. No competency matrices. No nine-box grids. The kill date is the part everyone forgets, and it's the part that saves you—because a hiring plan without expiry dates quietly becomes a wish list that drains your bank account one approval at a time.
Why triggers beat job titles
When you write "hire a Head of Sales," you've committed to a person. When you write "hire a first salesperson when inbound leads exceed 40 qualified per month for two consecutive months," you've committed to a condition. The second version survives a market shift. The first one doesn't.
I learned this the hard way. In early 2024, we opened a customer success role because we "felt understaffed." Three months in, the hire was great—and we still couldn't tell whether she'd moved a single metric. No trigger meant no way to evaluate. We'd hired on vibes, and vibes don't show up in the P&L.
How to build a lean hiring plan for startups, step by step
The process takes about four hours if you have your financials open. Budget half a day.
Step 1: Map the bottleneck, not the org chart
Write down the three things slowing your company down right now. Be brutally specific. "We can't ship fast enough" is vague. "Our one backend engineer spends 60% of her week on support tickets instead of the new API" is a bottleneck you can act on.
Rank them by revenue impact. The bottleneck that touches money gets the next hire; the one that touches comfort waits. Sounds obvious. Almost nobody does it.
Step 2: Price the role fully, not nominally
A $90,000 salary is not a $90,000 decision. Add employer payroll contributions, health coverage, a laptop, software seats, and a recruiting fee if you use an agency. Across the small companies I've helped, the multiplier lands somewhere between 1.25 and 1.4 of base salary. For senior roles with equity and agency fees, I've seen it touch 1.5.
- Base salary: the number you negotiate
- Employer contributions and benefits: usually 15–25% of base
- Equipment and software: $3,000–6,000 one-time, then $150–400/month
- Recruiting cost: zero if sourced in-network, 15–20% of first-year salary through an agency
Multiply by 12 and subtract from your runway. If the hire consumes more than 10–12% of remaining runway, it needs an exceptional trigger—not a good one.
Step 3: Sequence the first hires by stage
Pre-seed and seed companies make the same mistake: they hire generalists because generalists feel safe. In practice, the first eight hires should be almost painfully specific.
- Engineer who owns the core product—if you're technical, this may be you for a while
- Person who talks to customers daily (founder-led until it isn't)
- Second engineer once shipping cadence caps out
- Generalist operator for finance, ops, and HR admin
- First revenue-facing hire, only when you can articulate the sales process yourself
- Specialist in whatever is now the biggest bottleneck
Notice what's missing: no marketing hire before product-market fit, no chief of staff, no head of people. Those roles solve problems that only exist after you have a working machine.
Step 4: Attach a kill date to every row
Pick a date 60–90 days out. If the trigger hasn't fired by then, cross the role off and reallocate the budget. This single discipline saved us roughly $110,000 over two quarters—we'd planned two hires that never cleared their triggers, and instead of hiring "just in case," we extended runway by three months.
Was that fun? No. The team was tired. But cash is the only resource that compounds against you.
What a lean hiring plan looks like in practice
Here's a stripped-down example for a seed-stage company with $1.4M in the bank and 14 months of runway. Names changed, numbers approximate.
A worked example
| Role | Trigger | All-in monthly | Kill date |
|---|---|---|---|
| Backend engineer | API backlog > 6 weeks | $11,200 | April 2026 |
| Support specialist | >120 tickets/week for 3 weeks | $4,900 | June 2026 |
| Account executive | Founder closes 5 deals solo | $12,600 | September 2026 |
| Designer (contract→FTE) | Two product launches shipped | $7,300 | December 2026 |
Total committed if all four fire: roughly $36,000/month, or about 2.6 months of runway per quarter. That's the number that matters. Not the headcount. The burn.
Make vs. buy: when a contractor beats a hire
Not every bottleneck deserves a full-time employee. I use a rough rule: if the work is predictable and bounded, contract it. If it's ambiguous and compounding, hire it.
- Design sprint for a landing page → contractor
- Ongoing product design ownership → hire
- Six weeks of data cleanup → contractor
- Data infrastructure you'll live with for years → hire
Contractors cost more per hour and less per commitment. For a startup with uncertain demand, that trade is usually worth it.
The metrics that keep a lean plan honest
Three numbers, reviewed monthly, tell you whether your plan is working.
Time-to-hire
From role opened to offer accepted. For engineering roles, six to nine weeks is a reasonable band for a small team; anything past twelve weeks means your process, not the market, is the problem.
90-day failure rate
Percentage of hires who leave or are managed out within three months. If it climbs above 10%, your triggers or your interview loop are miscalibrated. I've been there—two bad hires in one year taught me more about hiring than any framework.
Cost per productive hire
Total recruiting spend divided by hires who are still performing at six months. Agencies love quoting cost-per-hire; cost-per-productive-hire is the honest version.
Track these in the same sheet as your hiring plan. One document, one source of truth. If a role's numbers don't justify it, the date on the kill column will end the argument for you.
The founders who survive the lean years aren't the ones who hire the fastest. They're the ones who can name, out loud, exactly what would have to be true before the next hire gets signed—and who are willing to close the requisition when it never becomes true.
