⚡ Promptolis Original · Business & Strategy
👥 First 10 Hires Strategy
Startup hiring sequence grounded in Horowitz + Collins + YC patterns — who to hire in what order, how to source, what cultural signals matter.
Why this is epic
Most 'First 10 Hires Strategy' prompts online produce generic, template-quality output. This one is structured like production-grade prompt engineering — role definition, principles, input schema, output format, auto-intake.
Research-backed: Startup hiring sequence grounded in Horowitz + Collins + YC patterns — who to hire in what order, how to source, what cultural signals matter.
Designed for practitioner-level depth, not generalist skim. Works across Claude, ChatGPT, and Gemini with consistent quality.
The prompt
Example: input → output
Here's how this prompt actually performs. Real input below, real output from Claude Opus 4.
Company stage: Early traction — $28K MRR, B2B SaaS, 12 paying customers Current team: 2 cofounders (me - technical founder, cofounder - product/GTM) Capital raised: $1.8M seed round closed last month Business type: B2B SaaS (AI sales tool for small agencies) Next milestone: $200K MRR in 12 months, preparing Series A Current hiring thoughts: Thinking of hiring 2 senior engineers + a designer + a head of sales + a customer success person + a marketing hire Strategy me.
Your First 10 Hires Strategy — B2B SaaS Early Traction
Stage-Appropriate Reality
You're at the critical transition point: you have product-market fit signal ($28K MRR from real customers) but haven't yet built the engine to scale it. The next 12 months determine whether you hit $200K MRR and raise a strong Series A or get stuck.
Your current plan (2 engineers + designer + Head of Sales + CS + marketing) = 6 hires. That's spreading you too thin AND includes a Head of Sales hire that's premature. Let's reorder.
Key constraint: $1.8M seed should last 18-24 months. 6 hires at average $160K fully-loaded = $960K/year burn just on people. Add your founder comp + infrastructure = $1.2M/year. You'd run out in 15 months before Series A. Too aggressive.
Right pace: 4-5 hires in first 12 months. Leave buffer for Series A runway.
Hire Sequence (10 hires over next 12-18 months)
Month 0-2: Hires 1-2 (highest leverage)
1. Senior full-stack engineer — unblocks product velocity
2. Customer Success Manager (not 'CS Engineer') — reduces churn, extends runway
Month 3-5: Hires 3-4
3. Senior ML/AI engineer — your AI moat requires deep expertise
4. Founding Marketer / Content Lead — organic acquisition engine (not paid, not yet)
Month 6-8: Hires 5-6 (approaching PMF consolidation)
5. Senior full-stack engineer #2 — product team of 3 engineers + cofounder-technical
6. Product Designer — UX + brand identity formation
Month 9-12: Hires 7-8 (pre-Series A)
7. Account Executive (first non-founder sales) — if you have repeatable sales motion by Month 9
8. Senior ML engineer #2 OR data engineer — data infrastructure becoming real
Month 12-18: Hires 9-10 (post-Series A)
9. Senior engineering manager — you now have 5+ engineers; someone needs to manage
10. First non-founder GTM leader — Head of Sales or Head of Marketing (NOT both yet)
Role Definitions
#1 Senior Full-stack Engineer
- What they do: ship features 50% of the week, improve infrastructure 30%, code review + quality 20%
- Must-have: 4+ years shipping production code, comfortable with ambiguity, has shipped product to paying users before
- Nice-to-have: SaaS background, previous startup experience
- Profile: can operate independently, doesn't need daily direction, enjoys variety
#2 Customer Success Manager
- What they do: onboard new customers (reduce time-to-value), monitor health scores, drive expansion, front-line customer support
- Must-have: 3+ years in B2B SaaS CSM role, has worked at 10-50 person company, comfortable with customer escalations
- Nice-to-have: has done expansion/renewal motion successfully
- Profile: empathetic, process-oriented, writes clearly, doesn't need to be told to follow up
#3 Senior ML/AI Engineer
- What they do: own model quality, eval harness, fine-tuning (if applicable), prompt engineering rigor
- Must-have: 3+ years shipping production ML/AI features, has built evaluation systems, published or open-source contributions
- Nice-to-have: has worked on LLM-specific products
- Profile: rigorous, evidence-based, comfortable saying 'the data doesn't support that'
#4 Founding Marketer / Content Lead
- What they do: long-form content (blog, guides), SEO strategy, thought leadership, community building
- Must-have: 3+ years in content/inbound at B2B SaaS, can write in your customer's voice, proven SEO wins
- Nice-to-have: has built content engine at startup from scratch
- Profile: writer first, not 'marketer' in the corporate sense; deeply understands the customer
How to Source
For all roles:
1. Your network first (weeks 1-3 of each search)
- Your LinkedIn + your cofounder's LinkedIn — post about the role
- Ask 10-20 people 'who's the best X you know?' — warm intros
- Previous colleagues of cofounders are often the best candidates (know the founders' operating style)
2. Targeted outbound (weeks 2-6 if needed)
- For engineers: search GitHub for contributors to projects you use, look at LinkedIn for specific company alumni (Stripe, Figma, Linear, companies with similar cultures)
- For CSM: find people at 10-100 person SaaS companies in slightly-older stage
- For marketing: look at who writes content you admire, check the 'About' page of content sites
3. Selective sourcing tools (if needed, weeks 4-8)
- AngelList Talent, Wellfound — good for startup-inclined candidates
- GitHub Jobs / Stack Overflow Jobs — specific to engineers
- Avoid recruiters at first 10 hires — their incentive is to close fast, not to find right-fit.
4. Hiring contractors first can de-risk
- For marketing/content especially — a 3-month contract reveals quality better than 10 hours of interviews
Interview Structure per Role
For engineering hires (5-hour process over 2-3 sessions):
- Session 1 (30 min): cofounder screen — why this company, relevant background, what they're looking for
- Session 2 (90 min): take-home project (realistic problem, 4 hours of work), with pair-programming review
- Session 3 (90 min): technical deep-dive on specific systems they've built + architecture discussion
- Session 4 (60 min): cofounder + other team member on cultural fit, working style
- Back-channel references: 2-3 people NOT on their list
For CSM (3-hour process):
- Session 1 (30 min): screen
- Session 2 (60 min): case exercise — given a real customer scenario (onboarding gone wrong), walk through their response
- Session 3 (60 min): reverse — they interview YOU about the product. Good CSMs should be curious.
- Back-channel references: 2-3
For marketing/content (3-hour process):
- Session 1 (30 min): screen
- Session 2 (60 min): writing sample review + discussion — bring 3 of their best pieces, you read, they explain
- Session 3 (60 min): content strategy exercise — given your current state, what's their 90-day plan
- Back-channel references: 2-3
Compensation Framework
Market rate + equity model:
- Base salary: 90-105% of market rate (Levels.fyi or similar for benchmarks)
- Equity: 0.25-1.5% for early engineers, 0.1-0.4% for CSM/marketing, 2-5% for first sales leader (later hire)
- Cliff + vesting: standard 4-year vest, 1-year cliff
Why market rate + equity (not 'below market + big equity'):
- Pre-traction 'below market + equity' works only for believers; usually produces either superstars or mediocre candidates (the middle doesn't take the deal)
- You have $1.8M; you can afford market. Use it.
Equity pools to budget:
- First 10 hires consume 8-12% of company equity total
- Reserve additional 5-7% for future hires
- Total early equity pool: 15-20%
Cultural Alignment Tests
Every interview, assess:
1. Do they actually care about the problem? — they should ask informed questions about customer pain, not just about comp
2. Can they operate in ambiguity? — startup hires who need 'what's my exact job description' flail
3. Do they write/communicate clearly? — writing samples, email exchanges, take-home write-ups all matter
4. Do they push back on founders? — hires who always agree with founders don't bring value. You want intellectual challenge.
5. Do they show ownership? — 'I fixed X' vs 'X got fixed' — the first signals ownership mindset
Red flags:
- Overly polished pitch; rehearsed answers
- Can't explain what they've actually shipped/owned
- Only asks about title, comp, reporting structure — doesn't engage with problem
- Their reference list is all managers, no peers
- Bad-mouths previous employers — they'll bad-mouth you eventually
When to Stop Hiring
Stop and reassess if:
- Burn rate exceeds 2x revenue growth for 2 months
- Team cohesion drops (new hires not engaging, old-team complaints about 'culture changing')
- You're hiring to 'solve' problems that are actually execution problems (more hires won't fix bad prioritization)
- Interview pipeline is thin — you're reaching down your quality bar to fill seats
When you're in good shape:
- Your next hire can point to 2-3 specific problems they'll solve
- Existing team is excited about the hire (not threatened)
- Burn rate is sustainable with current runway + Series A timeline
- You're still saying 'no' to 80%+ of candidates at final-round
Key Takeaways
- First 10 hires define culture. Each hire is a culture-vote — you're picking who you want to work with for 3+ years.
- Hire 4-5 in first 12 months, not 6. Your $1.8M seed should last 18-24 months; over-hiring shortens runway.
- Delay Head of Sales until you have repeatable sales motion (Month 9+). Founders still sell until then.
- Sequence: engineer + CSM → ML engineer + marketer → eng #2 + designer → AE + data. Each hire enables the next.
- Compensation: market-rate base + meaningful equity. 'Below market because equity' attracts wrong people at pre-PMF.
- Back-channel references non-negotiable. 2-3 people NOT on their list, via your network.
- Stop hiring if burn outpaces revenue growth or cohesion drops. More people ≠ more velocity.
- Interview for: curiosity about problem, ownership mindset, clear communication, intellectual honesty. Pedigree is not signal.
Common use cases
- Professionals who need structured thinking on this topic, not vague advice
- Practitioners making specific decisions with real stakes
- Anyone tired of generic AI responses to domain-specific questions
- Users wanting depth over breadth — one thing done well, not 10 things done poorly
Best AI model for this
Claude Opus 4.7 for early-stage nuance. GPT-5 for role definition.
Pro tips
- Paste your real situation (with specific numbers and context), not generic 'help me with X' framing. The prompt rewards specificity.
- If the prompt asks auto-intake questions, answer them fully before expecting output — incomplete inputs produce incomplete outputs.
- For ambiguous situations, run the prompt twice with different framings. Compare outputs. Often reveals the right path.
- Save the outputs you value. Iterate on them across sessions rather than re-running from scratch.
- Pair with a human expert for high-stakes decisions — the prompt is a first-draft tool, not a final authority.
- Share what worked back with us (promptolis.com/contact). Helps us refine future versions.
- The research citations inside the prompt are real — look them up if a specific claim matters for your decision.
Customization tips
- For pre-PMF companies (no real traction yet), the first 10 hires should be 80% technical + product. Don't hire sales/marketing/CS until you've proven something works. 'Head of Growth' at a 5-customer company is theater.
- For consumer (not B2B) companies, first hires shift: designer + community manager come earlier. Engineers still critical but design quality matters more immediately. Paid acquisition expert may come before enterprise sales.
- For marketplace companies, hire for both sides — someone who specifically focuses on supply (seller acquisition) and someone specifically for demand (buyer acquisition). Their skills differ.
- For hardware companies, first 10 hires include manufacturing/supply chain expertise earlier — Months 3-6 at latest. Software-only hiring strategy doesn't apply.
- For deep-tech / R&D companies, first hires skew heavier toward PhD-level researchers / engineers. Revenue-focused hires come later than typical SaaS.
- For remote-first startups, the 10-hires math changes: geographic diversity, timezone considerations, more intentional culture-building needed. Hiring contractors-to-FT is more common.
- For post-Series A (hires 10-25+), entire dynamic changes. Mid-managers start making sense. Specialists over generalists. Hiring 2-3/month becomes possible. Different playbook entirely.
- If burn rate is running hot (6-9 months runway left), STOP hiring. Even if roles are 'essential.' Extend runway through focus > hiring through desperation. Hiring ahead of Series A failure doesn't save the company.
Variants
Default
Standard flow for most users working on this topic
Beginner
Simplified output for users new to the domain — less jargon, more foundational explanation
Advanced
Denser output assuming practitioner-level baseline knowledge
Short-form
Compressed output for quick decisions, under 500 words
Frequently asked questions
How do I use the First 10 Hires Strategy prompt?
Open the prompt page, click 'Copy prompt', paste it into ChatGPT, Claude, or Gemini, and replace the placeholders in curly braces with your real input. The prompt is also launchable directly in each model with one click.
Which AI model works best with First 10 Hires Strategy?
Claude Opus 4.7 for early-stage nuance. GPT-5 for role definition.
Can I customize the First 10 Hires Strategy prompt for my use case?
Yes — every Promptolis Original is designed to be customized. Key levers: Paste your real situation (with specific numbers and context), not generic 'help me with X' framing. The prompt rewards specificity.; If the prompt asks auto-intake questions, answer them fully before expecting output — incomplete inputs produce incomplete outputs.
Explore more Originals
Hand-crafted 2026-grade prompts that actually change how you work.
← All Promptolis Originals