ProjekinAja. Founder's Playbook Stage 5 · Growth Retention Metrics Lesson 5.7
● Stage 5 · Lesson 5.7

Hiring Your First 10

Early hires are not employees — they are the people who set the ceiling of organizational capability; most founders hire too early, in the wrong order, and for the wrong reasons.

⏱ ~22 min read 🏗 Org design ⚙ Interactive widget

🎯 By the end you'll understand

Why each early hire should be defined by the bottleneck it removes, not the title it carries — the seven most common hiring-sequence mistakes that stall companies before they find scale — the economic test for hire timing (when the cost of not hiring exceeds the cost of hiring plus the management overhead it introduces) — and the canonical failure mode: the first sales hire who fails not because they are bad at sales, but because the founder has not yet built a sales playbook. You will also use the Hiring Sequencer to model Forge's exact hiring path given its current ARR, headcount, and founder time allocation.

KEY INSIGHTEvery early hire is either removing a bottleneck or creating one

A company that depends entirely on the founder to close every deal, solve every support ticket, and make every product decision is not a company — it is a very expensive job with a large number of co-workers.

The question "should we hire someone?" is the wrong question. The right question is: "what specific decision or action can the founder no longer make at the quality and speed the company needs — and does a hire remove that constraint, or just add complexity?" Every hire that does not answer a specific bottleneck is a hire that consumes management time, dilutes culture, and adds burn without proportional output. The discipline of the first ten hires is the discipline of constraint identification, not headcount planning.

🔑 The sequencing principle

Hire in the order that removes the most critical founder-as-bottleneck. That order is almost never the order that feels natural. Founders hire for comfort (someone who thinks like them) rather than for constraint (someone who does what they cannot). The result is a team of nine generalists who all need the founder's direction, where six domain specialists would have each removed the founder entirely from one function. Each hire should make the next hire cheaper, faster, or more effective — that cascade is what makes the sequence matter.

CORE CONCEPTThe founder-as-bottleneck audit

Before any hire, the founder should be able to complete this sentence with specificity: "I am the bottleneck in [specific function], which means [quantified consequence] is not happening, and a hire in [role] would remove me from that function within [time]." If the sentence cannot be completed, the hire is premature — or is solving for the wrong problem.

The eight functional areas where founders typically become bottlenecks, in rough order of when they appear:

# Function Symptom: founder is bottleneck What breaks if left unresolved
1 Customer Success / Support Founder handles every support ticket and onboarding call personally Response SLAs slip; churn rises; NRR degrades; founder has zero time for product or sales
2 Engineering / Product Build Founder is the only engineer or the only one who can review PRs Roadmap velocity collapses; technical debt accelerates; ship time extends to weeks per feature
3 Sales (Execution) Founder closes every deal; pipeline stalls when founder travels or is in product mode Revenue ceiling = founder's calendar; deal velocity is non-scalable
4 Marketing / Demand Generation All content, SEO, and top-of-funnel effort depends on founder personally creating it Inbound pipeline dries up when founder is in sales or product mode; brand stagnates
5 Finance / Operations Founder handles invoicing, payroll, vendor contracts, and compliance personally Financial reporting delays; cash-flow surprises; operational errors as scale increases
6 Recruiting Founder is the only one sourcing, screening, and closing candidates Hiring velocity becomes self-limiting; each hire requires 30–40 founder hours
7 Partnerships / BD All partnership conversations require founder presence and sign-off Deal paralysis; partnerships stall between founder availability windows
8 Data / Analytics Founder is the only one who can interpret the metrics dashboard or run analysis Decision-making centralizes; team cannot self-diagnose or act on data independently

The sequencing of which bottleneck to remove first depends on three variables: current ARR (which functions can the company afford to professionalize), headcount (which functions have already been delegated to non-founders), and where the founder actually spends most of their time (which function is consuming the resource that has highest opportunity cost).

CORE CONCEPTThe seven most common sequence mistakes

These are not theoretical — they are observed patterns in early-stage companies that hire in the wrong order and pay for it in stalled growth or elevated burn. Each mistake has a specific failure signature.

1

Hiring a VP of Sales before documenting the sales playbook

The most common, most expensive, and most destructive mistake in early hiring. A senior sales executive is an optimizer — they take a working process and make it more efficient. They are not a process inventor. If the founder has not yet closed 20 deals, documented the patterns in win/loss, established an ICP, and scripted the first three discovery questions, there is no playbook to hand over. The VP shows up, cannot replicate the founder's results, and is blamed for failure that was structurally guaranteed. This is not a talent problem — it is a sequencing problem. (More on this in the Mistakes section.)

2

Hiring a Head of Marketing before product-market fit is confirmed

A Head of Marketing can amplify a signal — they cannot create one. Spending $180K/yr on a senior marketing hire when you have not yet confirmed which customer segment actually buys, which message converts, and which channel produces repeatable pipeline is spending amplification budget on a signal that does not yet exist. The correct sequence: confirm fit, identify at least one repeatable channel at the founder level, then hire someone to scale that specific channel.

3

Hiring for cultural density ("someone like me") rather than functional gap

Technical founders hire engineers when the bottleneck is in customer success. Sales-oriented founders hire business development when the bottleneck is in product. The hire feels productive because the work is familiar, but the bottleneck that was actually stalling the company remains unaddressed. The discipline: hire for the role that makes you most uncomfortable, because that is the role where you are creating the most organizational drag.

4

Hiring too senior too early

A Chief Revenue Officer at $800K ARR is likely to spend their time building strategy decks when what the company needs is someone to make 40 outbound calls per week. Seniority brings leverage — leverage is irrelevant if there is nothing yet to leverage. Early-stage companies typically need people who can do the work themselves first and manage later, not people who manage other people who do work. A senior hire at the wrong stage costs 2–3x a mid-level hire and produces a fraction of the hands-on output.

5

Hiring to solve a cash-flow problem you should not have

Founders sometimes hire a CFO or finance head because the company has lost track of its burn rate or cannot produce a reliable P&L. This is solving a symptom of a governance failure, not a hiring problem. A $24K/yr bookkeeper and a $500/month accounting software subscription solves this for 95% of early-stage companies. Hiring a VP Finance at $220K/yr to solve what a better process would fix is one of the most expensive sequencing errors in early-stage operations.

6

Backfilling departed co-founders with employees

When a co-founder leaves, founders often hire a senior person into that function to replace them. But a hired executive is not structurally equivalent to a co-founder — they do not have the equity incentive, the cultural context, or the decision-making authority to operate equivalently. More importantly, the gap a departed co-founder leaves is usually a cultural and judgment gap, not a functional one. Hiring quickly to fill it produces a hire with mismatched authority and unrealistic expectations.

7

Hiring before the management system exists to onboard the hire

A new hire takes 30–90 days of founder time to onboard properly in a company with fewer than 20 people. If the founder is already at capacity, that management overhead is borrowed from the bottleneck the hire is meant to solve — producing a temporary worsening before improvement. The paradox: the more you need a hire, the less time you have to onboard them. The solution is not to delay hiring, but to create onboarding documentation before the hire starts.

SEE ITHiring Sequencer — priority order given your current state

⚙ Interactive · Hiring Sequencer

Set Forge's current ARR, headcount, and where the founder spends most time. Enter the 12-month hiring budget. The tool ranks 8 functional roles by hiring priority, shows the do-not-hire threshold for each, estimates founder hours recovered per week, and reveals how each hire unlocks or accelerates the next.

$780K
4 people
$800K
Founder hrs recovered / wk
—
Recommended hires (NOW + SOON)
—
Budget utilisation
—
Remaining budget
—

Two things to notice in every scenario. First, the customer success hire almost always ranks first when the founder spends significant time in support — because support is the function that most directly degrades NRR when it is founder-dependent, and NRR is the most important growth lever at this stage. Second, the sales hire almost always requires the playbook threshold: the widget signals DO NOT HIRE until the ARR threshold that implies founder-led validation is complete. That threshold is not arbitrary — it is the signal that the founder has closed enough deals to have patterns worth handing over.

HOW IT WORKSThe hire timing test

The correct framing for hire timing is not "can we afford this person?" — it is an economic comparison between two costs that are both real and often ignored.

Monthly cost ($) Company growth / time → Cost of NOT hiring Cost of hiring Hire here Too early: cost of hiring exceeds benefit Too late: opportunity cost exceeds hire cost
The hire timing crossover: the cost of not hiring (lost revenue, churn, founder-as-bottleneck opportunity cost) rises with company scale. The cost of hiring (salary + management overhead + ramp time) is roughly fixed. The optimal hire date is where the curves cross — earlier means burning cash for negative net return; later means leaving compounding opportunity cost on the table.

In practice, computing the cost-of-not-hiring requires estimating four things: (1) the revenue you are failing to close because you do not have this function covered, (2) the churn you are incurring because customer success is under-resourced, (3) the founder hours consumed in this function multiplied by the founder's opportunity cost per hour, and (4) the quality degradation of work being done by a non-specialist. Most founders only look at (1). A rigorous hire decision includes all four.

💡 The management overhead cost founders forget

Every hire adds approximately 4–8 founder hours per week during the ramp period (weeks 1–12) and 2–4 hours per week ongoing. If you have five direct reports, you are spending 10–20 hours per week on people management alone before doing any actual work. This is not a bad thing — it is a structural cost that must be explicit. The decision to hire is also the decision to spend management hours, and those hours must be accounted for against the bottleneck being removed.

The concrete trigger test: hire when the following three conditions are simultaneously true — (a) you can describe the exact function the hire will own in a one-paragraph job spec, (b) the cost of the function being unowned for another 90 days is quantifiably greater than the hire cost plus 90 days of management overhead, and (c) you have enough documentation to onboard the hire without re-creating institutional knowledge from scratch in every meeting.

FORGEForge's first ten — the actual sequence

Forge is at $780K ARR, 18 customers, NRR at 112%, and has just made its first customer success hire. The founder has exited day-to-day support. Let us trace the actual hire sequence that produced this outcome — and what comes next.

1

Customer Success Engineer — Hire 1 (made at ~$320K ARR, ~12 customers)

The trigger: the founder was spending 18 hours per week on onboarding calls and support tickets, and NRR was degrading because response times were exceeding 24 hours. The hire removed the founder from day-to-day support entirely within 8 weeks. Outcome: founder recovered 18 hrs/wk; NRR stabilized at 108% and then improved to 112% over the next quarter as onboarding quality increased. This is the hire that allowed everything else to accelerate.

2

Second Engineer (Full-stack, product focus) — Hire 2 (at ~$480K ARR)

The trigger: the roadmap was a 14-week queue and the founder was the only engineer who could review PRs or make architectural decisions. A second engineer cut ship time by 40% within 90 days. The founder moved from doing engineering to reviewing and directing — still a bottleneck, but a narrower one that a third engineer can eventually resolve.

3

Sales Development Representative — Hire 3 (at $600K ARR, after sales playbook documented)

Critical note: Forge did NOT hire an AE or VP Sales first. The founder documented 22 closed deals — the ICP, the discovery questions, the objection map, the proposal format, the pricing conversation — before this hire. The SDR's job was top-of-funnel prospecting: delivering qualified meetings to the founder, who continued to close. The SDR was hired at $65K base + commission, not $180K VP Sales. This is the correct sequence.

4

Account Executive — Hire 4 (pending, ~$900K ARR)

The next hire. The trigger will be: the SDR is generating more qualified meetings than the founder can take, and the founder has documented a full sales playbook with at least 3 deal archetypes. The AE takes over the mid-market segment (<$60K ACV) while the founder continues to close enterprise accounts (>$80K ACV) — the ones where founder presence adds the most value and competitive differentiation.

5

Third Engineer, Marketing Lead, Finance/Ops — Hires 5–7 (at $1.2M–$1.8M ARR)

These three can happen in parallel as ARR crosses $1M+ and the company has a customer base large enough to generate inbound demand worth amplifying. The finance/ops hire is typically a manager-level hire (not a CFO), covering bookkeeping, vendor management, and basic financial reporting. A fractional CFO at $5K–$10K/month often makes more sense than a full-time hire until $3M ARR.

🔑 The Forge milestone at Stage 5

Forge has 18 customers, $780K ARR, NRR at 112%. The first customer success hire has been made and the founder has exited day-to-day support. Growth is predictable within 15% month-over-month. A dashboard exists that tells any team member whether the business is healthy without asking the founder. The next constraint is sales capacity — not product, not support, not engineering. That determines the next hire.

$0 $320K $480K $600K $780K $900K $1.2M+ 1 CS Eng −18 hrs/wk 18h 2 Eng −12 hrs/wk 12h 3 SDR −8 hrs/wk 8h NOW 4 AE −14 hrs/wk 5–7 Mktg, Eng, Ops
Forge's hiring timeline against ARR milestones. Solid dots = made; dashed = planned. Bar height below the timeline = founder hours recovered per week. The "NOW" marker sits at $780K ARR — the company's current position. The next critical hire (AE) is gated on ARR reaching $900K and the sales playbook being complete.

WEAKNESSWhere this bites

✗ The canonical failure: the first sales hire who fails because the playbook does not exist

This is the most expensive and most common early hiring mistake in B2B startups, and it follows a predictable pattern. The founder is closing deals through force of personality, deep domain knowledge, and the implicit authority of being the CEO. At some ARR threshold (usually $400K–$700K), the company hires a VP Sales or AE to "scale" what the founder is doing. The new hire is given a quota, a Salesforce login, and access to the same LinkedIn. They fail to close deals at the founder's rate. The founder concludes the hire was bad and fires them — often within 6 months. The correct diagnosis: the founder never documented the qualification criteria, the three-stage discovery process, the champion-building sequence, the pricing conversation script, or the technical objection map. There was no playbook to hand over. The hire was premature, not the person's fault. This mistake typically costs $120K–$250K in fully-loaded salary plus 4–6 months of lost pipeline.

✗ Treating headcount as a proxy for organizational health

Early-stage companies sometimes hire to appear credible — to investors, to enterprise prospects, to themselves. A 12-person company feels more "real" than a 6-person company. But headcount without functional clarity is organizational debt: each person who does not have a clear, measurable function becomes a coordination overhead that scales with the square of headcount. The question is not "do we look like a real company?" — it is "does every person on this team know exactly what they own, how it is measured, and what success looks like in 90 days?" If not, the next hire makes the problem worse, not better.

✗ Waiting until a crisis to hire customer success

Customer success is the hire most frequently made reactively — after NRR has started degrading, after a key customer churns, after the founder has spent three consecutive weeks on support calls. At that point, the hire is fixing damage rather than preventing it. The economic cost of reactive CS hiring includes the churn already incurred plus the cost of rebuilding customer relationships in parallel with onboarding a new team member. The correct trigger is forward-looking: hire CS when the founder can identify more than 10 accounts that have gone more than 3 weeks without a proactive touchpoint — before churn manifests.

KEY INSIGHTHow this connects

  • 4.2 · Founder-Led Sales — Why You Cannot Delegate This Yet — the pre-condition for the first sales hire is completing founder-led sales long enough to build the playbook. Lesson 4.2 is the discipline that makes this hire safe to make; skipping it is the root cause of the canonical failure described above.
  • 5.1 · Product-Market Fit — The Measurable Version — the sequencing of your first hires should be governed by where you are in the PMF journey. Before fit is confirmed, the priority is roles that generate signal (product, CS) — not roles that amplify scale (sales, marketing). The hiring sequencer in this lesson uses ARR as a proxy for PMF stage.
  • 5.6 · Growth Loops — Designing Compounding Acquisition — a growth loop is only as durable as the team running it. The marketing and CS hires sequenced in this lesson are the human infrastructure of the growth loops built in 5.6. A loop without an owner is a theory, not a system.
  • 5.8 · The Operating Cadence — Running a Company Without the Founder in Every Room — the next lesson covers how to build the meeting structure, dashboard, and decision framework that allow the team hired in this lesson to operate without the founder in every decision. The hire sequence is the input; the operating system is the output.

The organizational layer — who you hire, in what order, for what function — is the mechanism that converts the growth levers covered in Stage 5 into durable company performance. NRR does not improve because you measured it; it improves because a customer success professional owns it. Pipeline does not scale because you designed a growth loop; it scales because a marketing hire runs the content flywheel that feeds it. The hiring sequence is not HR — it is product strategy applied to the company's own operating system.

GLOSSARYKey terms introduced

Founder-as-bottleneck
The condition in which a specific company function cannot progress without the founder's direct involvement — not because the founder is the best at it, but because no one else has been hired to own it. Every early-stage company has multiple founder-as-bottleneck conditions; the sequencing question is which one to remove first.
Hiring sequence
The deliberate ordering of hires based on which function, if professionalized, removes the most critical constraint on the company's growth rate. Distinct from headcount planning, which counts bodies without specifying which bottleneck each body resolves.
Sales playbook
A documented record of the founder's proven sales process: ICP definition, qualification criteria, discovery question sequence, objection map, proposal format, pricing conversation script, and champion-building sequence. The minimum viable handoff artifact before the first sales hire. Without it, any sales hire is premature by definition.
Do-not-hire threshold
The specific ARR, headcount, or operational condition that must be met before a given hire can succeed. The do-not-hire threshold for a VP Sales is typically $1M+ ARR with a documented playbook; for a Head of Marketing it is confirmed PMF and at least one repeatable channel. Hiring before the threshold is met produces a predictable failure that is mistakenly attributed to the hire.
Cost-of-not-hiring
The total economic cost of leaving a function unowned: lost revenue from deals not closed, churn from accounts not managed, opportunity cost of founder hours consumed, and quality degradation from non-specialist execution. Most founders calculate only one of these four. A rigorous hire decision requires estimating all four and comparing the total to the hire cost plus management overhead.
Management overhead
The founder hours required to hire, onboard, direct, and develop a new employee — typically 4–8 hrs/wk during ramp (0–12 weeks) and 2–4 hrs/wk ongoing. This cost is real and must be accounted for in the hire timing calculation. A founder at capacity cannot absorb high management overhead without temporarily worsening the bottleneck being addressed.
Ramp time
The period from hire start date until a new employee is fully productive in their role — typically 30–60 days for individual contributors and 60–120 days for management hires in early-stage companies. During ramp, the hire's output is less than their cost, and management overhead is highest. The ramp must be funded in the hire timing calculation.
Functional clarity
The condition in which each team member can precisely articulate what function they own, how it is measured, and what success looks like in 90 days — without asking the founder. Functional clarity is the output of good hiring sequencing; its absence is the primary diagnostic of a team where headcount has outrun organizational design.

ACTIVE RECALLCheck your understanding

Answer in your own words first, then reveal.

1Forge just hired its first customer success engineer at $480K ARR. The founder is now considering a VP Sales hire. What specific conditions must be true before this hire is safe to make?›

At minimum, three conditions must be met: (1) The sales playbook must exist and be documented — the founder must have closed at least 15–20 deals and written down the ICP, discovery question sequence, qualification criteria, objection map, pricing conversation, and proposal format. Without this, the VP Sales has nothing to learn from and nothing to scale. (2) ARR and pipeline velocity must be sufficient to give a new sales hire a credible chance — at $480K ARR with 12 customers, Forge likely needs a higher ARR threshold (most practitioners suggest $600K–$900K for an AE and $1M+ for a VP Sales). (3) The founder must have capacity to onboard the hire — if the founder is still handling support, building product, and closing sales simultaneously, there is no management bandwidth to ramp a new sales executive. The correct sequence at $480K ARR is probably the second engineer hire, not a VP Sales hire. Hiring VP Sales now would likely produce the canonical failure pattern described in the Mistakes section.

2What is the "cost-of-not-hiring" and why do most founders underestimate it?›

The cost-of-not-hiring is the total economic cost of leaving a function unowned, comprising four components: (1) revenue not captured because the function is a bottleneck (deals not closed, partnerships not developed), (2) revenue lost because the function is under-resourced (churn from poor support, NRR degradation), (3) founder opportunity cost — the hours the founder spends in the unowned function multiplied by the hourly value of founder time in the company's highest-leverage activity, and (4) quality degradation from non-specialist execution. Most founders calculate only component 1 (missed revenue) and sometimes component 2 (churn). They systematically ignore component 3 because founder time does not appear as a line item in the P&L, and component 4 because quality degradation is hard to quantify. The result is that the cost-of-not-hiring is systematically underestimated, making hires appear more expensive relative to the alternative than they actually are. This produces the failure mode of hiring too late, particularly for support and customer success roles.

3Why is hiring too senior too early a sequencing mistake, not just a budget mistake?›

Because seniority brings leverage — and leverage requires something to be leveraged. A Chief Revenue Officer's skills are: hiring and managing a sales team, building territory models, designing compensation plans, running QBRs, and managing board-level revenue conversations. None of these skills are useful when the company needs someone to make 40 outbound calls per week, handle objections in live demos, and iterate on the first-call pitch. The senior hire will produce strategy decks when the company needs deals. More critically: a senior hire at the wrong stage often requires the company to build the organizational infrastructure to deploy their skills — headcount, systems, budgets — that the company does not yet have and cannot yet afford. The hire creates its own organizational debt. A correctly sequenced mid-level hire (AE over VP Sales, marketing manager over CMO) does the work at a lower cost, and the company can hire up later when there is something to manage.

4What is the operational sign that it is time to hire a customer success person — and why is the correct trigger forward-looking rather than reactive?›

The forward-looking trigger: when the founder can identify 10 or more accounts that have not had a proactive touchpoint in the last 3 weeks — not because the accounts are low-priority, but because there is no bandwidth to reach them. This is the leading indicator of future churn; the churn itself has not yet occurred. The reactive trigger — hiring after NRR has started degrading, after a key account churns, after the founder has spent three consecutive weeks on support calls — means the hire is now performing damage control simultaneously with their primary job, which degrades both. The economic argument for the forward-looking trigger: the cost of preventing churn (CS hire at $80K–$120K/yr) is dramatically lower than the cost of re-acquiring lost ARR ($150K–$400K in new pipeline effort, plus the lost compounding expansion revenue that a retained customer would have generated). The forward-looking hire prevents a predictable, quantifiable future cost; the reactive hire mitigates a cost already incurred.

Next: building the operating cadence that runs the company without the founder in every room →