Skip to main content

Team planning

A first-ten-hires planning framework for technology startups

A practical framework for planning the first ten hires in a technology startup: constraint mapping, sequencing, interview capacity and cash shape.

In short

Plan the first ten hires as a sequence of constraints removed, not as an org chart filled in. For each proposed role, name the constraint it removes, the evidence that the constraint is real now, who will assess the candidates and what it costs in the month it starts. Roles that cannot answer all four are not ready, whatever the org chart says.

Key facts

Plan by
Constraints removed, in order
Each role needs
Constraint, evidence, assessor, month-one cost
Hardest limit
Interview and onboarding capacity
Deliberately absent
Stage-specific headcount benchmarks

Why we do not publish a stage-by-stage template

There are plenty of "first ten hires by funding stage" lists online. We do not publish one, because the right first ten depends on what you are building, what the founders already do well and where the delivery is genuinely stuck. A hardware company and a B2B SaaS company at the same stage need almost nothing in common.

What does transfer is the method: identify the constraint, prove it is real, decide who can assess for it, and sequence against cash and interview capacity.

The framework

  1. 1. List the constraints, not the roles

    Write the five things currently slowing the business down in plain language — "we cannot ship to enterprise customers without SSO" rather than "we need a backend engineer".

  2. 2. Test whether each constraint is real now

    What evidence exists that it is blocking something this quarter? A constraint that only appears in next year's plan does not justify a hire this quarter.

  3. 3. Ask what else removes it

    Process change, a contractor, a tool, or narrowing scope. If one of those genuinely removes the constraint, the hire can wait.

  4. 4. Translate the survivors into roles

    Write two sentences on what this person will have delivered in six months. If you cannot, the role is not defined enough to search for.

  5. 5. Name the assessor for each role

    Who is credible enough to judge depth? If nobody internally can, arrange a borrowed assessor before opening the role, not after the first shortlist.

  6. 6. Sequence by dependency

    Leaders and multipliers before the people they will lead, onboard or interview.

  7. 7. Cost the sequence month by month

    Fees, salaries, employer costs and equipment on one timeline. Look at the worst month, then adjust the sequence rather than the ambition.

  8. 8. Set review points

    Decide now what would pause hires six to ten: a missed milestone, a funding change, or ramp-up taking longer than planned.

The one-line test for every role in the plan

A role should be able to fill every column before a search starts.

Readiness test for each planned role
ColumnWhat good looks like
Constraint removedA specific thing that is blocked today
Evidence it is realSomething that has actually slipped or been turned down
Six-month successTwo sentences anyone in the team would recognise
AssessorA named person who can judge the depth required
Month-one costFee, salary, employer costs and equipment, in cash
What we do instead if we waitAn honest answer, even if it is "we go slower"

Interview capacity is the hidden ceiling

A ten-role plan sounds like a funding question and is usually a calendar question. Each open role consumes screening, interviews, debriefs and decisions from the small number of people who also build the product.

Count the panel hours a plan requires per month. If the answer exceeds what the panel can give without delivery suffering, the plan needs resequencing regardless of the budget.

Common questions

How many people should a startup hire in its first year?
There is no defensible general answer, and figures quoted as norms usually come from a specific sample that may not resemble your business. Hire in the order that removes real constraints, at the pace your panel can assess and your runway can absorb.
Should the first hires be generalists or specialists?
Generalists early tend to survive changes of plan better; specialists become necessary once a constraint is genuinely deep and permanent. Map it to your constraint list rather than to a rule.
When should we hire someone to run hiring?
When the founders' time spent on recruitment is measurably displacing product or customer work, and there is a steady flow of roles rather than an occasional one.

Plan several hires together

Add the roles you expect to hire, phase them across the year and see the combined monthly cost of the whole plan.

Open the team hiring planner

Any percentages or figures shown in this article are illustrative examples used to explain the model. They are not quoted rates, market benchmarks or salary data.