Most pre-seed startups raise a Series A with somewhere between three and twelve people on the team, and a large share do it with fewer than eight. The number that matters is not headcount but whether the team you have can produce the growth curve a Series A investor needs to see — so hire the smallest group that can build, sell, and keep the product running, then stop.
Pre-seed is the earliest institutional money a startup takes, usually a few hundred thousand to around $2 million, raised before the company has proven that customers will pay repeatedly. Series A is the next round, typically raised against evidence of real traction. The hires between those two points exist to produce that evidence, which is why "how many" is downstream of "for what.".
Table of Contents
- Why headcount is the wrong starting number
- What a Series A actually requires you to have built
- Hires that usually pay for themselves, and hires that usually do not
- Sector changes the answer more than stage does
- A practical sequence for deciding
- What to do when the round is running short
- Frequently Asked Questions
Why headcount is the wrong starting number
A pre-seed round buys months, not people. If you raise $1.5 million and want 24 months of runway, you have roughly $62,000 a month for everything — salaries, cloud bills, tools, contractors, legal. A fully loaded engineer in a high-cost market can consume a third of that alone once payroll taxes, benefits, equipment, and software seats are counted. That arithmetic sets your ceiling before any judgment about talent enters the picture.
Founders who hire to a target headcount tend to discover the constraint late, when the runway left is too short to either reach milestones or raise on the ones they have. Working backwards from runway instead gives you a defensible number: total cash, minus non-payroll burn, divided by the months you need, divided by a realistic loaded cost per person. Investors read the same math in reverse. A pre-seed company with twelve people and five months of runway reads as a team that spent its round on salaries rather than on learning. The same twelve people with a growth rate that explains them reads as a company that found something and staffed it.
What a Series A actually requires you to have built
Series A investors are underwriting a repeatable growth engine, not a headcount. In practice that means a product real customers use without hand-holding, revenue or usage that compounds month over month, a sense of which acquisition channel works, and retention that shows the problem was worth solving. Each of those is a capability, and each capability implies a person or a founder's time. Map the capability list before the hiring list.
A typical pre-seed B2B software company needs: someone who can ship product end to end, someone who can close customers, someone who can keep existing customers successful, and someone who owns the numbers. On a small team those four roles usually collapse into two founders plus one or two hires, with contractors covering the edges. The useful test for any proposed hire is whether the Series A story is weaker without them. If you cannot name the metric that person moves and the month you would expect to see it move, the role is premature. That test kills most of the hires founders feel pressure to make — a full-time designer before the product has users, a marketing generalist before you know the channel, a head of anything before there is anyone to head.
Hires that usually pay for themselves, and hires that usually do not
Early-stage hiring mistakes cluster into predictable shapes. The pattern below is the one most experienced seed investors describe, and it holds across most software and consumer businesses.
Generally worth it at pre-seed: Usually premature: The underlying rule: at pre-seed you want people who do several jobs adequately, and at Series A you start wanting people who do one job exceptionally. Hiring the Series A profile early is how teams end up with high burn and slow output.
- Engineer two and three, when a founder-engineer is the bottleneck on shipping and the roadmap is customer-driven rather than speculative.
- A first dedicated salesperson or founding account executive, once a founder has personally closed enough deals to know the pitch, the objections, and the price.
- A customer success or support generalist, once churn or response time is visibly costing you revenue.
- Fractional or contract finance, legal, and recruiting — real expertise, a fraction of the cost, no equity.
- A senior executive hire (VP of Sales, CTO, CMO) before there is a team and a process to manage. Executives are expensive, they expect infrastructure, and they are frequently mis-fit at this stage.
Sector changes the answer more than stage does
A deep-tech, biotech, or hardware startup cannot run the lean playbook, because the thing being proven is technical rather than commercial. If your Series A milestone is a working prototype, a validated model, or a regulatory step, the team is concentrated in technical roles and the headcount is set by what the build requires. These companies often look more specialized at pre-seed than a software company does at Series A. Software and marketplace startups sit at the other end.
Modern tooling, cloud infrastructure, and a mature contractor market mean two or three people can carry a product to meaningful revenue, and there are credible examples of very small teams raising substantial rounds. Consumer startups fall in between: they tend to need design and growth capability earlier than B2B, because distribution is the hard part rather than the product. Services-heavy and operations-heavy businesses carry a third pattern — headcount scales with customers served, so early hires are delivery staff rather than builders. The important consequence is that your burn grows with revenue instead of staying flat, which changes both the runway math and what investors will consider a healthy gross margin.
A practical sequence for deciding
Run this before you post a job: Two warning signs are worth watching for. If your team is growing faster than your revenue or usage, you are converting cash into people without converting people into traction. And if founders have stopped doing customer-facing work because someone was hired to do it, you have outsourced the one job that cannot be delegated before Series A — understanding exactly why people buy.
- Write down the two or three claims you want to make in your Series A pitch. Be specific: a revenue figure, a retention rate, a named channel with a cost per customer.
- For each claim, name the work required and who does it today. Founder time counts, and the hours are finite.
- Find the gap that most delays the claims. That is your next hire, and only that one.
- Price the hire fully loaded, add it to burn, and recompute runway. If the result leaves under nine months at the point you want to raise, the hire is too expensive or too early.
- Try the cheapest version first. A contractor for a month, a part-time specialist, or a scoped project tells you whether the role is real before you commit salary and equity.
What to do when the round is running short
If runway is tight and the milestones are not in reach, the lever is usually scope rather than people. Cutting a secondary product, narrowing to one customer segment, or dropping a channel buys months without the damage of a layoff at a ten-person company, where losing two people can remove an entire capability. A bridge round or a seed extension is common and not a mark of failure, but it is priced on the same traction evidence as a Series A, so it does not relieve the underlying pressure.
Existing investors are the realistic source, which means telling them early rather than at the point where the decision is already made for you. If you do need to reduce the team, do it once and do it deeper than feels comfortable. Sequential small cuts destroy trust with the people who remain, and the remaining team is the asset the next round is being raised against.
Frequently Asked Questions
Can two founders raise a Series A with no employees at all?
It happens, particularly in software, but it is uncommon and the traction has to be unusually strong. Investors will also ask how you plan to deploy a much larger round, so having at least a hiring plan with named candidates helps.
Should early hires take equity instead of salary?
Early employees normally get both — a below-market salary plus meaningful equity, typically vesting over four years with a one-year cliff. Equity-only arrangements tend to create unclear expectations and are better handled as advisor grants or contractor agreements with explicit scope.
Does hiring a co-founder count as a hire?
No, and the distinction matters. A co-founder takes founder-level equity, usually a lower salary, and shared responsibility for the company's direction; adding one after a pre-seed round is a cap-table decision rather than a headcount one, and it needs investor conversation.
How long before Series A should the hiring freeze start?
Many founders slow hiring three to six months before a raise so that burn is stable and the metrics in the deck are not distorted by recent spend. The exception is a hire that directly produces a milestone you are raising on.