पाठशाला Pathshala · दल Dal, The team · Lesson 07 · Start

The first ten hires: who, in what order and why

The first ten hires decide the habits a company keeps. How to order them against the constraint that actually limits growth, the sequences that recur by business model and what the tenth hire changes.

Pathshala, The Founder Library · 11 October 2026 · 8 min read

Hand tools for woodturning and carving laid out on a workbench in a Bengaluru workshop. — Photograph: Ketan Shanker · Pexels

Ten people is the size at which a company stops being the founders and a few friends and becomes an organisation with habits. The order in which those ten arrive decides which habits form, how fast the product moves and how much of the runway the payroll eats. Most founders copy the order from a company they admired. The order that works comes from the company’s own constraint.

This lesson gives a method for choosing the next hire from where the founders’ time and the company’s constraint actually sit, the sequences that recur by business model, a figure that ranks the next hire from your own week, and what changes legally and operationally as the tenth person joins.

Why the order matters more than the roles

Sam Altman’s Startup Playbook opens its section on hiring with the advice not to do it, and observes that the most successful companies Y Combinator worked with waited a relatively long time before hiring employees. Employees are expensive, they add complexity, and a larger team finds it harder to change direction. The first ten are where that cost is highest per head. Each early hire is a tenth of the company’s capacity and a tenth of its culture, and each constrains the next: the first engineer chooses the stack the next three must like, and the first salesperson decides what kind of customer the company learns to sell to.

The usual failure is not a bad hire. It is a good hire made in the wrong order: a marketing manager before anyone can close a sale, an operations lead before there is anything to operate, a head of people at eight. Each is a reasonable box on an org chart. Each, made early, puts salary against a problem the company does not yet have while the problem it does have waits.

Find the constraint before the job title

At any moment one thing limits how fast a young company grows. It is usually one of three: the product cannot be built fast enough, demand cannot be found or closed fast enough, or what is sold cannot be delivered fast enough. Occasionally it is cash collection or compliance, but less often than founders fear. The next hire should relieve whichever of these binds this quarter, either by adding capacity to it directly or by taking other work off the founder whose hours the constraint needs.

Hands choosing a chisel from a set arranged on a rack in a woodworking studio. — The craftsman picks the chisel the cut needs next. The next hire is chosen the same way: by the work that is holding everything else up. Photograph: Ono Kosuki · Pexels

Two questions find it. If the company had twice as much of one thing tomorrow, which would most increase revenue: engineering hours, qualified conversations with buyers, or delivery capacity? And which founder hours go on work someone else could do at eighty per cent of the founder’s quality? The intersection is the hire. A founder who spends eighteen hours a week onboarding customers while deals sit unclosed has found it: hire for onboarding so the founder can sell.

Note what the rule excludes. It excludes hiring for a function because a competitor has one, because an investor asked whether you have a head of marketing, or because a talented friend is free. A talented friend who relieves the constraint is the ideal hire. One who does not is an expensive favour to both of you.

The sequences that recur

No order is universal, but the constraint method produces recognisable sequences by business model. They are worth knowing as a check on your own answer, not as a template.

B2B software. Engineers first, usually two or three, because the product is the constraint until customers pay. Then the first person who sells or implements beside the founder, because the founder becomes the constraint on closing and onboarding. Then customer success once the founder’s week fills with existing accounts. Marketing arrives around hire eight to ten, when the sales process is repeatable enough that more leads would convert. A typical ten: five or six in product and engineering, two or three in sales and success, one in operations or finance.

D2C and consumer brands. Operations and supply first: sourcing, quality, warehousing and returns, because a brand that cannot fulfil reliably burns its acquisition spend. Then performance marketing, often as an agency or contractor at first. Then customer service, which in India means voice and WhatsApp in more than one language. Engineering is often bought as a service until the storefront becomes the difference.

Marketplaces. Supply first, usually people on the ground in one city, because demand without supply churns at once. Then an engineer to build the internal tools that make supply onboarding cheap. Then demand. The first ten are often half field team.

Services and agencies. Delivery first, because every rupee of revenue is someone’s hours. The founder sells until the founder’s own delivery hours run out. The trap is that the company hires delivery indefinitely and never hires the person who would let the founder stop delivering and sell.

Index Ventures’ Rewarding Talent handbook models a typical seed team at about ten employees and expects a company to hire roughly forty to fifty more between Series A and Series B. The ten here are the team a seed round pays for. Plan them against the round you have, not against the org chart you will need after the next one.

Where the founders’ week actually goes

The figure turns the method into arithmetic. Set the hours a week the founders together spend on each kind of work, and say which constraint binds this quarter. Work on the constraint counts double; administration counts half, because it is usually better bought from an accountant, a payroll service or a company secretary than hired. The ranking is the order in which hires would return the most founder hours to the constraint.

Read it with two cautions. The figure ranks work to take off the founders, not roles to fill: the same hours of selling might go to an inside salesperson or a solutions engineer, and choosing between them is the second decision. And when the top two bars are close, hire for the one whose work is easier to describe in writing, because a role you cannot describe is a role you cannot interview for. At the defaults selling is the constraint, yet the founders spend eighteen hours a week onboarding and ten selling, under a fifth of their week; the first hire takes onboarding. Set the constraint to building and the product work moves to the top, with onboarding second.

Hire against the constraint, not against the org chart. The org chart is what the company looks like after the constraint has moved ten times.

Generalists first, specialists when the work repeats

A specialist is worth hiring when the work has become repeatable enough to fill a whole job and valuable enough that doing it well rather than adequately changes the numbers. Before that, a generalist who can sell on Monday, fix onboarding on Tuesday and write the help pages on Wednesday is worth more than a specialist who does one of those very well and waits for the rest. The test: can you write down what this person will do every week for the next six months? If the list is long and varied, hire a generalist. If it is one thing that recurs, hire the specialist.

Seniority follows the same logic. A senior hire brought in to build a function that does not exist often struggles, because they are used to managing a team and inheriting a process. The early hire who works is usually someone who has done the work themselves recently and wants to build the process for the first time. Hire the head of a function when there is a function to head: at three or four people doing the work, not at zero.

Altman’s note on how to hire names the best source of the first ten plainly: friends and friends of friends. Harj Taggar’s guide for Y Combinator adds the cost: a founder working their network should expect to spend at least a third of their time on it, and cold outreach can take up to six months to produce a hire. Ten hires through the network is most of a founder’s year. Sequence them so the hire that frees the most founder time comes first, because that time is what recruits the rest.

What the tenth hire changes

Somewhere between the sixth and the tenth person, three things the founders did by instinct need writing down. Each is small. Each, left late, becomes a problem at twenty.

Paperwork. Since the four labour codes came into force on 21 November 2025, an appointment letter is mandatory for every worker, and fixed-term employees get parity with permanent staff and gratuity after one year rather than five. Each of the ten needs a letter stating role, pay and terms, a signed IP assignment (the [IP lesson](/library/ip-assignment-company-owns-what-you-built) has the clauses) and a grant letter if they hold options. Provident fund and ESIC registration follow headcount and wage thresholds; check the current ones on the EPFO and ESIC portals as the team grows rather than discovering them in due diligence. The [contractors lesson](/library/contractors-interns-employees-who-should-be-what) covers which of the ten should be employees at all.

Management. At ten, one founder cannot hold every one-on-one, review every pull request and approve every expense. Decide who manages whom before the tenth person arrives, and say it out loud. The first manager is usually the strongest early hire in the largest function, promoted because the function needs one rather than as a reward.

Pay and equity. By ten, people talk. Two engineers on very different salaries for the same work will find out. Write levels and bands before hire six, and size the option pool so that the tenth grant is not taken from the eleventh; the [compensation bands lesson](/library/compensation-bands-for-startup) and the [ESOP lesson](/library/esop-design-pool-grants-strike-price) carry the method.

The hiring plan, reviewed monthly

Keep a one-page hiring plan with three columns: the next three hires in order, the constraint each relieves, and the month each must start for the plan to hold. Review it with the co-founders on the first Monday of every month and ask four questions. Has the constraint moved? After a good hire it usually has, and the next hire changes with it. Where did founder hours go last month, measured from the calendar rather than from memory? Can the role at the top of the list be written down as six months of weekly work? And does the runway still carry the payroll at ten, with the [runway lesson](/library/runway-how-many-months-you-really-have) applied to salaries that start three months after each search begins?

Then act on the top line only. Start the search for the first hire on the list the day the plan is agreed, through the network first, and do not open the second search until the first has an offer out. A founding team that makes ten hires in the right order in eighteen months has done better than one that makes fifteen in the order a template suggested.

Nothing here is legal advice. Labour-code rules and registration thresholds change; check the current position before each hire.