Startup Hiring Sequencing Playbook

Purpose

This recipe produces a stage-specific hiring priority matrix that tells founders exactly who to hire next based on their business model, current bottleneck, and runway — not a generic org chart. The output is a ranked hire list with bottleneck justifications, timing triggers, compensation ranges, and role specifications for the next 3-5 hires, plus a month-by-month hiring timeline aligned to milestones. [src1]

Prerequisites

• Business model defined — SaaS, marketplace, ecommerce, dev tools, or services with unit economics understood
• Current team audit — list of everyone, their actual responsibilities, and where they spend time
• Runway calculated — months of cash remaining, monthly burn rate, expected revenue trajectory
• Bottleneck identified — the single constraint most limiting growth right now
• Compensation benchmarks — Carta Total Comp or Pave data for target roles at your stage

Constraints

• Every hire must map to a named bottleneck. If you cannot articulate what constraint the hire removes, delay the hire. [src2]
• Do not hire managers before individual contributors. A VP of Engineering with no engineers is a $250K mistake. [src4]
• Pre-PMF startups should stay under 8 people total. Excess headcount burns runway without accelerating learning. [src4]
• Test fractional or contract arrangements before full-time commits for non-core functions pre-Series A. Fractional executives are 60-70% cheaper. [src6]
• Budget 3-6 months of fully loaded cost per hire as reserve — a bad hire costs 1.5-2x annual salary.

Tool Selection Decision

Which path?
├── Non-technical founders, pre-PMF
│   └── PATH A: Technical-first — engineer(s) before everything else
├── Technical founders, pre-PMF
│   └── PATH B: Customer-first — customer-facing generalist before specialists
├── Post-PMF, B2B SaaS or dev tools
│   └── PATH C: Sales/growth-first — revenue function before scaling engineering
└── Post-PMF, marketplace or D2C
    └── PATH D: Operations-first — supply/ops before demand generation

Execution Flow

Step 1: Assess Current Bottleneck

Duration: 1-2 hours · Tool: Spreadsheet + team discussion

Identify the single biggest constraint limiting growth. Score three areas (product/engineering, customer acquisition, retention/operations) with 5 yes/no questions each. The area with 3+ “yes” answers is the bottleneck that determines your next hire. If two areas tie, prioritize the one closer to revenue. [src2]

Verify: One section scores 3+ while others score 0-2. · If failed: If all sections score 1-2, the bottleneck may be process not people — document what 10 more founder hours/week would fix first.

Step 2: Map Hire-by-Stage for Your Business Model

Duration: 30-60 minutes · Tool: Reference matrix + bottleneck assessment

Match business model (B2B SaaS, marketplace, D2C ecommerce, dev tools) and stage (pre-seed, seed, post-PMF, Series A) to the default hiring sequence. B2B SaaS: engineer → generalist → second engineer → AE/growth → designer. Marketplace: engineer → supply ops → second engineer → growth marketer. D2C: designer → paid acquisition → ops coordinator → content creator. Dev tools: second engineer → dev advocate → third engineer → community manager. Override defaults with bottleneck assessment if they conflict. [src1] [src4]

Verify: Next 3 hires identified with business-model rationale, cross-checked against bottleneck. · If failed: For hybrid models, combine sequences and let bottleneck assessment break ties.

Step 3: Create Role Priority Matrix

Duration: 30-60 minutes · Tool: Spreadsheet

Score each candidate hire on four dimensions (1-5): bottleneck impact, revenue impact, runway fit, urgency. Total /20. Score 16-20 = hire immediately. Score 12-15 = plan for next quarter. Score 8-11 = defer or use fractional. Score 4-7 = do not hire, solve with process or tools. [src2]

Verify: Top-ranked hire scores 16+ and maps to the Step 1 bottleneck. No hire ranks above 12 without a named constraint. · If failed: If no role scores above 15, solve the bottleneck with process improvements, automation, or contractors first.

Step 4: Build Hiring Timeline

Duration: 30-60 minutes · Tool: Spreadsheet

Map hires to milestone triggers, not calendar dates. Pre-PMF triggers: “cannot ship fast enough” (engineer), “cannot talk to enough customers” (generalist). Post-PMF: “pipeline exceeds founder capacity” (AE), “churn > 5% monthly” (CS). Include loaded monthly cost and runway impact for each hire. Never hire if it reduces runway below 6 months. Plan 4-6 weeks sourcing + 2-4 weeks notice period + 3 months ramp. [src6]

Verify: Each hire triggered by a milestone, total plan never drops runway below 6 months. · If failed: Defer lower-priority hires, explore fractional alternatives, or adjust revenue projections.

Step 5: Define Success Metrics Per Hire

Duration: 30 minutes · Tool: Document

Define measurable 30/60/90-day criteria for each hire before opening the role. Day 30: onboarding complete, first deliverable shipped. Day 60: contributing independently, first measurable output. Day 90: full productivity, named bottleneck measurably improved. Include red flags for early termination: cannot operate without daily direction, no self-driven initiative, culture misalignment by Day 60. [src2]

Verify: Each priority hire has concrete 30/60/90 metrics tied to the bottleneck. · If failed: If you cannot write specific success metrics, the role is not defined enough — return to Step 3.

Output Schema

{
  "output_type": "hiring_priority_plan",
  "format": "document + spreadsheet",
  "columns": [
    {"name": "role_title", "type": "string", "description": "Job title for the hire", "required": true},
    {"name": "priority_rank", "type": "number", "description": "Rank from 1 (most urgent) to N", "required": true},
    {"name": "bottleneck_solved", "type": "string", "description": "Named constraint this hire removes", "required": true},
    {"name": "priority_score", "type": "number", "description": "Score from role priority matrix (4-20)", "required": true},
    {"name": "trigger_milestone", "type": "string", "description": "Milestone that triggers sourcing", "required": true},
    {"name": "compensation_range", "type": "string", "description": "Base salary + equity range for stage", "required": true},
    {"name": "hiring_approach", "type": "string", "description": "Full-time, fractional, or contract", "required": true},
    {"name": "success_metrics_90d", "type": "string", "description": "Key Day 90 success metric", "required": true}
  ],
  "expected_row_count": "3-5",
  "sort_order": "priority_rank ascending",
  "deduplication_key": "role_title"
}

Quality Benchmarks

If below minimum: If time to fill exceeds 90 days, role spec may be too narrow or comp is below market. If 90-day retention < 80%, reassess interview process and onboarding. If bottleneck does not improve within 90 days, the hire may not address the real constraint.

Error Handling

Cost Breakdown

Anti-Patterns

Wrong: Hiring for the org chart instead of the bottleneck

Founders copy Series B org charts and hire VP-level roles before 10 customers exist. These leaders need teams and budgets that do not exist yet. The startup burns $400K+ on roles that cannot produce results at this stage. [src2]

Correct: Hire individual contributors who solve today's constraint

Every early hire should produce output on Day 1 without a team. A generalist doing support, sales, and success is more valuable at seed than a VP managing nobody.

Wrong: Hiring a CTO as Employee #1 for non-technical founders

Senior technical leaders expect strategic scope and team building. The actual job is solo engineering. They quit within 6 months. [src4]

Correct: Hire a strong senior engineer titled Founding Engineer

Find someone who ships fast, thrives with autonomy, and wants to build — not manage. Offer a path to CTO as the team grows.

Wrong: Delaying customer-facing hire because the product is not ready

Engineers defer hiring anyone who talks to customers, believing one more feature unlocks growth. The product is never ready — customer feedback reveals what to build. [src5]

Correct: Hire a customer-facing generalist within first 5 hires

Someone talking to customers daily provides the feedback loop that makes engineering productive. Without this, engineers build features nobody asked for.

When This Matters

Use this recipe when a founder needs to decide who to hire next and in what order, considering their specific business model, stage, and current growth constraint. Requires a defined business model, team audit, and runway calculation. This recipe produces a prioritized hiring plan — not job descriptions, interview processes, or compensation packages.