--- # === IDENTITY === id: business/startup-hiring/startup-hiring-sequencing-playbook/2026 canonical_question: "Who should I hire first at each stage — decision logic by business model, hire for bottleneck not org chart?" aliases: - "Startup hiring sequence by stage 2026" - "First hires decision framework by business model" - "Hire for bottleneck not org chart playbook" entity_type: execution_recipe domain: business > startup-hiring > startup hiring sequencing playbook region: global jurisdiction: global temporal_scope: 2025-2026 # === VERIFICATION === last_verified: 2026-03-12 confidence: 0.88 version: 1.0 first_published: 2026-03-12 # === TEMPORAL VALIDITY === temporal_validity: status: evolving last_breaking_change: "AI-augmented roles (AI-assisted SDRs, AI-first customer support) reduced headcount requirements for early-stage startups in 2025-2026; fractional executive hiring became mainstream pre-Series A" next_review: 2026-09-08 change_sensitivity: high # === CONSTRAINTS === constraints: - "Every hire must map to a specific bottleneck — if you cannot name the bottleneck the hire solves, do not hire" - "Do not hire managers before individual contributors — first hire in any function must be a doer, not a leader" - "Pre-PMF startups should not exceed 5-8 people total — excess headcount burns runway without accelerating learning" - "Fractional or contract roles should be tested before full-time commits for non-core functions pre-Series A" - "Compensation must be benchmarked against stage-appropriate data — seed-stage startups cannot match Series C salaries but can offer meaningful equity" # === SKIP CONDITIONS === skip_this_unit_if: - condition: "User needs help with a specific job description or interview process" use_instead: "business/startup-hiring/recruiting-strategy-for-startups/2026" - condition: "User needs compensation and equity benchmarks only" use_instead: "business/startup-hiring/compensation-equity-guide-for-startups/2026" - condition: "User is scaling past 50 employees and needs org design" use_instead: "org design framework for companies scaling past 50 employees" # === AGENT HINTS === inputs_needed: - key: business_model question: "What is the startup's business model?" type: choice options: ["B2B SaaS", "Marketplace / platform", "D2C ecommerce", "Developer tools / API", "Services / agency", "no preference — show all models"] - key: current_stage question: "What stage is the startup at?" type: choice options: ["Pre-seed / idea (0-2 people)", "Seed / pre-PMF (2-5 people)", "Post-PMF / pre-Series A (5-15 people)", "Series A+ / scaling (15-50 people)"] - key: technical_founders question: "Are the founders technical (can build the product)?" type: choice options: ["Yes — founders can build and ship", "Partially — founders can manage technical work but not build solo", "No — founders are non-technical"] - key: runway_months question: "How many months of runway does the startup have?" type: choice options: ["< 6 months", "6-12 months", "12-18 months", "18+ months"] # === EXECUTION METADATA === execution: required_inputs: - name: "Business model and revenue stage" source: "founder or business plan" format: "business model type, current MRR/ARR, growth trajectory" - name: "Current team composition" source: "founder" format: "list of current team members with roles and capabilities" - name: "Runway and budget" source: "financial plan or bank statement" format: "months of runway remaining, monthly burn, hiring budget" outputs: - name: "Hiring priority matrix" format: "document" description: "Ranked list of next 3-5 hires with bottleneck justification, timing triggers, and role specs" - name: "Hiring timeline" format: "spreadsheet or document" description: "Month-by-month hiring plan aligned to milestones and runway" - name: "Role specification templates" format: "document" description: "Job descriptions for the next 3 priority hires with comp ranges and success metrics" tools_required: - name: "Carta Total Comp" purpose: "Startup compensation benchmarks by role, stage, and geography" tier: "free" cost: "$0 (free benchmarking tool)" alternatives: ["Pave ($0 for benchmarks)", "Levels.fyi (free)", "Glassdoor (free)"] - name: "Dover or Ashby" purpose: "ATS and recruiting automation for early-stage startups" tier: "free" cost: "$0 (free tier) to $300/mo" alternatives: ["Lever ($0-399/mo)", "Greenhouse ($0-499/mo)", "Notion (manual tracking)"] - name: "LinkedIn Recruiter Lite" purpose: "Sourcing candidates and market mapping" tier: "paid" cost: "$170/mo" alternatives: ["Apollo.io ($0-49/mo)", "Wellfound (free)", "personal network (free)"] credentials_needed: - service: "Carta Total Comp" type: "username+password" where_to_get: "https://carta.com/total-comp/" free_tier_limits: "Unlimited benchmark lookups" - service: "LinkedIn" type: "username+password" where_to_get: "https://www.linkedin.com" free_tier_limits: "Basic search free; Recruiter Lite for advanced search" estimated_duration: "2-4 hours for initial assessment and priority matrix; ongoing quarterly reviews" estimated_cost: "$0 (free tools for assessment) to $500/month (paid recruiting tools)" # === DISTRIBUTION === canonical_source: "https://knowledgelib.io/business/startup-hiring/startup-hiring-sequencing-playbook/2026" suggested_citation: "Source: knowledgelib.io — AI Knowledge Library (verified 2026-03-12)" # === RELATED UNITS === related_kos: depends_on: - id: "business/startup-planning/startup-idea-structuring-template/2026" label: "Business model must be defined before sequencing hires" - id: "finance/modeling/startup-financial-model/2026" label: "What a standard startup financial model contains — P&L, cash flow, runway projections" feeds_into: - id: "business/startup-hiring/recruiting-strategy-for-startups/2026" label: "Executing startup recruiting — sourcing across Wellfound/LinkedIn/referrals, ATS setup, structured interview process and scorecards, cost per hire" - id: "business/startup-operations/employee-onboarding-playbook-for-startups/2026" label: "Startup employee onboarding — first day/week/month/quarter, tool provisioning, buddy system" related_to: - id: "business/startup-sales/sales-strategy-early-stage-startups/2026" label: "Sales hire timing depends on founder-led sales progress" - id: "business/startup-marketing/marketing-strategy-framework-for-startups/2026" label: "Marketing hire timing depends on go-to-market model" alternative_to: [] # === SOURCES === sources: - id: src1 title: "First 5 Hires for Seed Startups (January 2026)" author: Dover url: https://www.dover.com/blog/first-5-hires-seed-stage-startups type: industry_report published: 2026-01-15 reliability: high - id: src2 title: "How to Hire a Strong Founding Team" author: Andreessen Horowitz url: https://a16z.com/how-to-hire-a-strong-founding-team/ type: technical_blog published: 2025-06-01 reliability: authoritative - id: src3 title: "State of Startup Compensation: H1 2025" author: Carta url: https://carta.com/data/startup-compensation-h1-2025/ type: industry_report published: 2025-07-01 reliability: authoritative - id: src4 title: "Stages of Startups: YC Startup Job Guide" author: Y Combinator url: https://www.ycombinator.com/library/Ek-stages-of-startups type: official_docs published: 2025-01-01 reliability: authoritative - id: src5 title: "The Playbook for Hiring the Right Marketer at the Right Time" author: First Round Review url: https://review.firstround.com/the-playbook-for-hiring-the-right-marketer-at-the-right-time-for-your-startup/ type: technical_blog published: 2025-03-01 reliability: authoritative - id: src6 title: "The State of Startup Hiring — 2026 Talent Trends Report" author: Ashby url: https://www.ashbyhq.com/talent-trends-report/reports/startup-hiring type: industry_report published: 2026-01-01 reliability: high --- # 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 on the team, their actual responsibilities (not titles), and where they spend time - [ ] **Runway calculated** — months of cash remaining, monthly burn rate, and expected revenue trajectory - [ ] **Bottleneck identified** — the single constraint most limiting growth right now (shipping speed, customer acquisition, retention, operations) - [ ] **Compensation benchmarks** — Carta Total Comp or Pave data for target roles at your stage and geography ## 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 you have individual contributors in that function. A VP of Engineering with no engineers to manage is a $250K mistake. [src4] - Pre-PMF startups (pre-seed through seed) should stay under 8 people total. Excess headcount increases burn without accelerating the learning loops that produce PMF. [src4] - Test fractional or contract arrangements before committing to full-time hires for non-core functions (finance, HR, legal, marketing) pre-Series A. Fractional CMOs and CFOs are 60-70% cheaper than full-time equivalents. [src6] - Budget 3-6 months of fully loaded cost per hire as reserve — a bad hire costs 1.5-2x annual salary when you include recruiting, onboarding, lost productivity, and severance. ## 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 ``` | Path | First Hire | Second Hire | Third Hire | Monthly Burn Impact | |------|-----------|-------------|------------|-------------------| | A: Technical-first | Founding engineer | Customer-facing generalist | Second engineer | +$12-18K/mo | | B: Customer-first | Customer/sales generalist | Designer or second engineer | Operations/growth | +$10-15K/mo | | C: Sales/growth | Full-cycle AE or growth marketer | Second engineer | Customer success | +$12-20K/mo | | D: Operations | Operations/supply manager | Growth marketer | Data analyst | +$10-18K/mo | ## Execution Flow ### Step 1: Assess Current Bottleneck **Duration**: 1-2 hours **Tool**: Spreadsheet + team discussion Identify the single biggest constraint limiting growth right now. Do not hire for theoretical future needs — hire for today's bottleneck. [src2] ``` Bottleneck Assessment Framework: ────────────────────────────────────────────────── Answer each question — the function with the most "yes" answers is your bottleneck and determines your next hire. PRODUCT/ENGINEERING BOTTLENECK: □ Features are shipping slower than competitors □ Bug backlog is growing and affecting retention □ Founders spending >50% of time coding instead of selling/learning □ Technical debt is blocking new feature development □ You have more customer requests than engineering capacity CUSTOMER ACQUISITION BOTTLENECK: □ Product exists but pipeline is empty — nobody knows about you □ Founders are the only ones doing sales/outreach □ Inbound leads exist but nobody follows up within 24 hours □ You know who the customer is but cannot reach them at scale □ Free trial signups exist but conversion to paid is below 5% RETENTION/OPERATIONS BOTTLENECK: □ Customers churn within first 90 days □ Onboarding takes more than 7 days and requires founder involvement □ Support tickets pile up with >48 hour response times □ Fulfillment/delivery errors exceed 5% □ Manual processes consume >20 hours/week of founder time SCORING: 3-5 "yes" in a section = Critical bottleneck → hire here first 1-2 "yes" = Growing pain → plan to hire in 3-6 months 0 "yes" = Not a bottleneck yet → do not hire here ``` **Verify**: One section scores 3+ while others score 0-2. If two sections tie, prioritize the one closer to revenue (acquisition > product for post-PMF, product > acquisition for pre-PMF). **If failed**: If all sections score 1-2, you may not need to hire yet — the bottleneck might be process, not people. Document what 10 more hours per week of founder time would fix first. ### Step 2: Map Hire-by-Stage for Your Business Model **Duration**: 30-60 minutes **Tool**: Reference matrix below + your bottleneck assessment Match your business model and stage to the hiring sequence below. These are default sequences — override with your bottleneck assessment from Step 1 if they conflict. [src1] [src4] ``` B2B SaaS HIRING SEQUENCE: ────────────────────────────────────────────────── Pre-seed (0-2 people): Hire #1: Founding engineer (if non-technical founders) Hire #2: Product-minded generalist who talks to customers Seed / pre-PMF (2-5 people): Hire #3: Second engineer (backend or frontend, complement #1) Hire #4: Customer-facing generalist (support + sales + success) Post-PMF / pre-Series A (5-10 people): Hire #5: Full-cycle AE (if ACV > $5K) OR growth marketer (if PLG/self-serve) Hire #6: Designer (product + marketing) Hire #7: Third engineer OR DevOps/infrastructure Series A (10-20 people): Hire #8-10: Sales team (2 AEs + 1 SDR) OR growth team (2 marketers + 1 analyst) Hire #11: Engineering manager (when team hits 6-8 engineers) Hire #12: Head of Customer Success (when 50+ active customers) MARKETPLACE / PLATFORM HIRING SEQUENCE: ────────────────────────────────────────────────── Pre-seed: Hire #1: Engineer (marketplace infrastructure — search, matching, payments) Hire #2: Supply-side operations person (onboarding supply) Seed / pre-PMF: Hire #3: Second engineer (mobile or growth engineering) Hire #4: Community/supply manager Post-PMF: Hire #5: Growth marketer (demand generation) Hire #6: Data analyst (marketplace health metrics) Hire #7: Trust & safety or operations lead D2C ECOMMERCE HIRING SEQUENCE: ────────────────────────────────────────────────── Pre-seed: Hire #1: Designer/brand (product + visual identity) Hire #2: Paid acquisition specialist (Meta/Google ads) Seed / pre-PMF: Hire #3: Operations/logistics coordinator Hire #4: Content creator (social media + email) Post-PMF: Hire #5: CX/support lead (when >100 orders/week) Hire #6: Supply chain manager Hire #7: Retention/email marketing specialist DEVELOPER TOOLS / API HIRING SEQUENCE: ────────────────────────────────────────────────── Pre-seed: Hire #1: Second engineer (API design + DX) Hire #2: Developer advocate / technical writer Seed / pre-PMF: Hire #3: Third engineer (infrastructure + reliability) Hire #4: Community manager / developer relations Post-PMF: Hire #5: Solutions engineer (enterprise onboarding) Hire #6: Growth marketer (developer marketing) Hire #7: Full-cycle AE (enterprise deals) ``` **Verify**: Your next 3 hires are identified with clear business-model rationale. Cross-check against bottleneck assessment from Step 1 — the bottleneck assessment takes priority over the default sequence. **If failed**: If your business model is a hybrid (e.g., SaaS with marketplace dynamics), combine the relevant sequences and let the bottleneck assessment break ties. ### Step 3: Create Role Priority Matrix **Duration**: 30-60 minutes **Tool**: Spreadsheet or document Build a ranked priority matrix for your next 3-5 hires with quantified justification. [src2] ``` Role Priority Matrix Template: ────────────────────────────────────────────────── For each candidate hire, score on four dimensions (1-5 each): | Role | Bottleneck Impact | Revenue Impact | Runway Fit | Urgency | Total | Rank | |------|------------------|----------------|------------|---------|-------|------| | {Role A} | {1-5} | {1-5} | {1-5} | {1-5} | {/20} | {#} | | {Role B} | {1-5} | {1-5} | {1-5} | {1-5} | {/20} | {#} | SCORING GUIDE: Bottleneck Impact (1-5): 5 = Directly removes the #1 growth constraint 3 = Removes a secondary constraint 1 = Nice to have, no immediate constraint addressed Revenue Impact (1-5): 5 = Directly generates or enables revenue within 90 days 3 = Indirectly enables revenue within 6 months 1 = Cost center with long-term payoff Runway Fit (1-5): 5 = Fully fundable within current runway with 12+ months buffer 3 = Fundable but reduces runway below 12 months 1 = Requires additional funding to sustain Urgency (1-5): 5 = Needed this month — every week of delay costs measurable revenue 3 = Needed this quarter 1 = Needed within 6-12 months DECISION RULES: Score 16-20: Hire immediately — start sourcing today Score 12-15: Plan for next quarter — begin passive sourcing Score 8-11: Defer — revisit in 6 months or use fractional Score 4-7: Do not hire — solve with process, tools, or founder effort ``` **Verify**: Top-ranked hire scores 16+ and maps directly to the bottleneck identified in Step 1. No hire ranks above 12 without a named bottleneck. **If failed**: If no role scores above 15, the current bottleneck may be solvable without hiring. Consider process improvements, automation, or contractor support first. ### Step 4: Build Hiring Timeline **Duration**: 30-60 minutes **Tool**: Spreadsheet Map hires to milestones and runway, not calendar dates. Each hire should be triggered by a milestone, not a feeling. [src6] ``` Hiring Timeline Template: ────────────────────────────────────────────────── | Hire | Trigger Milestone | Start Sourcing | Target Start | Loaded Monthly Cost | Runway Impact | |------|------------------|----------------|--------------|--------------------:|---------------| | #1 {Role} | {e.g., "10 paying customers"} | {Month} | {Month} | ${X,XXX} | -{N} months | | #2 {Role} | {e.g., "$10K MRR"} | {Month} | {Month} | ${X,XXX} | -{N} months | | #3 {Role} | {e.g., "50+ support tickets/week"} | {Month} | {Month} | ${X,XXX} | -{N} months | MILESTONE TRIGGERS BY STAGE: Pre-PMF hiring triggers: - "Cannot ship fast enough" → engineer - "Cannot talk to enough customers" → customer generalist - "Cannot keep existing customers happy" → support/success Post-PMF hiring triggers: - "Pipeline exceeds founder capacity" → AE or growth marketer - "Churn rate > 5% monthly" → customer success - "Engineering tickets > 3 month backlog" → engineer - "Founder spending > 10 hrs/week on ops" → operations hire Scaling triggers: - "Engineering team > 6" → engineering manager - "3+ AEs hitting quota" → sales manager - "50+ inbound leads/week" → marketing ops or SDR RUNWAY RULES: Never hire if it reduces runway below 6 months Plan for 4-6 weeks sourcing + 2-4 weeks notice period Budget 3 months ramp time before measuring new hire productivity Include benefits overhead: add 20-30% to base salary for fully loaded cost ``` **Verify**: Timeline shows each hire triggered by a specific milestone, not a date. Total hiring plan does not reduce runway below 6 months at any point. Sequence matches the priority matrix from Step 3. **If failed**: If the timeline creates a runway crunch, defer lower-priority hires, explore fractional alternatives, or adjust revenue projections. ### Step 5: Define Success Metrics Per Hire **Duration**: 30 minutes **Tool**: Document Every hire must have measurable 30/60/90-day success criteria defined before the role opens. This prevents ambiguous performance evaluation and enables fast decisions on bad hires. [src2] ``` Success Metrics Template (per hire): ────────────────────────────────────────────────── Role: {title} Reports to: {name/title} Bottleneck solved: {specific constraint} Day 30 — Onboarding Complete: □ {Metric 1: e.g., "Completed product training and can demo independently"} □ {Metric 2: e.g., "Met with 10+ existing customers"} □ {Metric 3: e.g., "First independent deliverable shipped"} Day 60 — Contributing: □ {Metric 1: e.g., "Handling 100% of inbound support tickets independently"} □ {Metric 2: e.g., "Closed first deal or shipped first feature"} □ {Metric 3: e.g., "Identified and proposed one process improvement"} Day 90 — Full Productivity: □ {Metric 1: e.g., "Meeting 75% of full quota or velocity targets"} □ {Metric 2: e.g., "Operating independently without daily founder oversight"} □ {Metric 3: e.g., "Named bottleneck measurably improved by X%"} Red Flags (terminate if seen by Day 60): - Cannot operate without daily direction on basic tasks - No evidence of self-driven initiative or problem-solving - Culture or values misalignment observed by 2+ team members - Quality of work consistently below acceptable standard after feedback ``` **Verify**: Each priority hire has concrete 30/60/90 metrics that tie back to the bottleneck. Metrics are measurable, not subjective. **If failed**: If you cannot write specific success metrics, the role is not well-defined enough to hire for. Return to Step 3 and clarify what the hire actually does. ## Output Schema ```json { "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 | Quality Metric | Minimum Acceptable | Good | Excellent | |---------------|-------------------|------|-----------| | Hires with named bottleneck justification | 100% | 100% | 100% | | Time to fill (sourcing to start) | < 90 days | < 60 days | < 45 days | | 90-day retention rate (new hires) | > 80% | > 90% | > 95% | | Hiring plan runway buffer | > 6 months | > 9 months | > 12 months | | Success metrics defined pre-hire | 100% | 100% | 100% + quarterly review | | Bottleneck improvement within 90 days | Measurable | > 25% improvement | > 50% improvement | **If below minimum**: If time to fill exceeds 90 days, the role spec may be too narrow or compensation is below market. If 90-day retention is below 80%, reassess interview process and onboarding quality. If bottleneck does not improve within 90 days, the hire may not be addressing the real constraint. ## Error Handling | Error | Likely Cause | Recovery Action | |-------|-------------|----------------| | Cannot identify a single bottleneck | Multiple constraints of similar severity | Rank by revenue impact — hire for the constraint closest to revenue first | | Top candidate rejects offer | Compensation below market or equity story unclear | Benchmark comp on Carta Total Comp, strengthen equity narrative, consider signing bonus | | New hire underperforms at Day 60 | Wrong skills for stage or insufficient onboarding | Increase founder-led onboarding time, provide explicit 30-day improvement plan with weekly check-ins | | Runway drops below 6 months after hire | Revenue growth slower than projected | Freeze non-critical hires immediately, explore fractional or contract downgrades for non-core roles | | Co-founder disagrees on hiring priority | Different bottleneck perceptions | Use the scoring matrix from Step 3 — data-driven ranking resolves subjective disagreements | | Hired for org chart instead of bottleneck | Following generic startup hiring advice | Revisit Step 1 bottleneck assessment, verify the hire maps to a named constraint | ## Cost Breakdown | Component | Bootstrap | Seed-Funded | Series A | |-----------|-----------|-------------|----------| | Recruiting tools (ATS, sourcing) | $0 (Notion + LinkedIn free) | $170-300/mo (LinkedIn Lite + ATS) | $500-1,000/mo (full ATS + sourcing) | | Recruiter fees per hire | $0 (founder-sourced) | $0-5,000 (fractional recruiter) | $15,000-36,000 (agency at 15-25%) | | Compensation benchmarking | $0 (Carta free, Levels.fyi) | $0 (Carta free, Pave) | $0-500/mo (Pave premium) | | First engineer (annual loaded) | $120-160K + 1-3% equity | $140-180K + 0.5-1.5% equity | $160-220K + 0.25-0.75% equity | | First sales/growth hire (annual loaded) | $80-120K + 0.5-1% equity | $100-150K OTE + 0.25-0.75% equity | $140-200K OTE + 0.1-0.5% equity | | **Total first 3 hires (annual)** | **$280-440K** | **$360-530K** | **$460-700K** | ## Anti-Patterns ### Wrong: Hiring for the org chart instead of the bottleneck Founders copy Series B org charts and hire a VP of Marketing, VP of Sales, and Head of People before they have 10 customers. These leaders need teams, processes, and budgets that do not exist yet. They spend months building strategy documents instead of executing. The startup burns $400K+ on roles that cannot produce results at this stage. [src2] ### Correct: Hire individual contributors who solve today's constraint Every hire should be able to produce output on Day 1 without a team. A generalist who does customer support, sales, and success is more valuable at seed stage than a VP of Customer Success who manages a team of zero. ### Wrong: Hiring a technical co-founder equivalent as Employee #1 Non-technical founders often try to hire a CTO or VP Engineering as their first hire. Senior technical leaders expect strategic scope, team building, and architecture decisions — not grinding through a backlog alone. They quit within 6 months because the role is actually "solo engineer." [src4] ### Correct: Hire a strong senior engineer who enjoys building The first technical hire should be a senior full-stack engineer who ships fast and thrives with autonomy. Title them "Founding Engineer" with a path to CTO. They should want to build, not manage. ### Wrong: Delaying the first customer-facing hire because "the product isn't ready" Founders who are engineers often defer hiring anyone who talks to customers, believing one more feature will unlock growth. The product is never "ready" — customer conversations reveal what to build next. [src5] ### Correct: Hire a customer-facing generalist within the first 5 hires Someone who talks to customers daily (support, sales, success) provides the feedback loop that makes engineering productive. Without this role, 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 as inputs. This recipe produces a prioritized hiring plan — not job descriptions, interview processes, or compensation packages, which are separate execution recipes. ## Related Units - [Sales Strategy for Early-Stage Startups](/business/startup-sales/sales-strategy-early-stage-startups/2026) — sales hire timing depends on founder-led sales progress - [Marketing Strategy Framework for Startups](/business/startup-marketing/marketing-strategy-framework-for-startups/2026) — marketing hire timing depends on go-to-market model - [Startup Idea Structuring Template](/business/startup-planning/startup-idea-structuring-template/2026) — business model definition feeds into hiring sequence - [Personal Financial Planning for Founders](/business/startup-readiness/personal-financial-planning-for-founders/2026) — runway and burn rate constrain hiring pace