Your startup's first hire comes down to three questions. Is it the right time (a need that comes back every week, a founder at full capacity, enough runway to last at least twelve months)? Which profile unlocks the most value (often a senior generalist rather than a narrow specialist)? And what will this employee cost once payroll taxes are included? In France, according to the Urssaf simulator, an employee paid €3,000 gross per month costs their employer about €4,000 per month. Hire too early and you burn runway you don't have; hire the wrong person and you lose months, along with part of your culture. Often, the best first hire is still the one you can put off by staying lean for one more quarter. Below you'll find who to hire, when, at what cost and with how much equity, followed by the most common reasons first hires fail.
Before you hire: the avoidable hire
Before you write a job description, ask yourself: does this work need a full-time employee, right now?
Founders often hire on reflex, because "that's what you do when you grow." They hire a developer when a vibe coding tool would have been enough to ship the MVP, or a salesperson before proving they can sell the product themselves. The result: a fully loaded salary going out every month, shrinking runway, and a new employee waiting for instructions you don't have time to give.
The simple rule: until you've confirmed that a need is recurring, structural and time-consuming, you're hiring too early. For a one-off spike in workload, bring in a freelancer. For a repetitive task, a tool is often enough. For a function you've never done yourself, try it first: without that experience, you won't know how to hire the right profile or how to evaluate them.
Stay lean as long as you can. It's a matter of survival: every month of runway you save gives you one more month to find product market fit before your payroll gets heavier.
When should you make your first hire?
The right moment shows up as a convergence of signals. You're ready to hire when three conditions are met at the same time.
You are the bottleneck. You're turning down opportunities, pushing back deliveries, and working on tasks below your level because nobody else can take them. The need is no longer occasional: it comes back every week.
You have traction. You track your key metrics and you see concrete market signals: paying customers, retention that holds, demand you can no longer serve on your own. Hire to accelerate an engine that already works. Hiring in the hope that an employee will find the market for you is a bet you'll almost certainly lose.
Your runway can carry it. You can cover this fully loaded salary for at least twelve months without putting the company at risk; plug it into the runway calculator to see how many months of cash it takes away. A hire you can only fund for six months is a bet you'll probably lose, with a costly layoff at the end.
If even one of these three conditions is missing, wait. The right moment comes when not hiring costs you more than hiring.
Who should you hire first? Generalist vs specialist
At this stage, the instinct to hire a narrow expert is almost always a mistake. A technical SEO specialist or a growth hacker with ten years of AdWords arrives too early in your story. Look for someone who can do ten things well and learn the eleventh quickly.
The first employee of an early-stage startup is a senior generalist: autonomous, resourceful, and able to own a fuzzy scope without hand-holding. In a five-person company where the job description changes every month, you need someone who shapes their own role rather than asking "what exactly is my job description?"
Also choose based on your own weak spot. If you're a technical founder with little appetite for sales, your first hire is probably on the business side. If you're a business founder who can't own the product, it's the opposite. Aim at the most dangerous gap in the team rather than a second copy of your own strength.
An important nuance: your first hire and a cofounder play different roles. A cofounder shares the risk, the vision and a significant share of the equity; a first employee executes on a defined scope with a salary package plus some equity. Mixing up the two creates expectations you can't manage. If you're looking for a partner, read our guide to finding a cofounder instead, and for a senior technical profile, see how to find a CTO.
What it really costs (salary + payroll taxes + equity)
Check this gap before you promise anything: the advertised gross salary is not what you actually pay.
The fully loaded cost of a first employee
In France, employer social contributions are added on top of the gross salary, and their weight varies with the salary level, status (executive or not) and the applicable collective agreement. According to the Urssaf simulator (calculated in September 2026, with the default settings for a small company), an employee paid €3,000 gross per month costs their employer about €4,000 per month, a multiplier of roughly 1.35 and around €48,000 over the year. For an executive at €5,000 gross, the same simulator gives about €7,100 per month, nearly 1.43 times gross. Before promising a salary, rerun the fully loaded calculation in this simulator with your own parameters.
Add the hidden costs: equipment, software licenses, onboarding time, and the cost of your own time spent recruiting and training. Your first-year budget therefore goes well beyond the fully loaded salary.
Should you give equity to your first hire?
Yes, but in measured amounts. Equity aligns your hire with long-term value creation and makes up for a salary that is often below market. In France, employee equity usually takes the form of BSPCE. With our BSPCE simulator, you can show your hire what they would earn when they sell their shares.
The percentage depends on the role and the stage: the earlier you hire, the more risk the hire takes on, and the more generous their equity should be. Stock options remain less common in Europe than in the United States. In its Rewarding Talent guide (2018), Index Ventures estimates that in Europe, about four of the first ten employees at a seed-stage startup receive options, whereas in the United States almost every job offer at that stage includes them. To choose between a salaried CTO and a partner CTO, read our guide to finding a CTO, which compares profiles by stage.
Always include vesting: the hire earns their shares over the course of their commitment. Index Ventures describes the most common setup: four years of vesting with a one-year cliff. Test early-departure scenarios in our vesting simulator before you write the offer.
A lightweight hiring process for an early-stage startup
Forget the seven-round process of a large corporation: aim for a fast, selective process in three steps.
Job description and scorecard
Before you publish anything, write a scorecard: the mission in one sentence, the three to five outcomes expected over the first six months, and the skills that are truly essential. You describe results to achieve rather than a list of tasks, which forces you to clarify your expectations; you then reuse the same grid to evaluate every candidate.
Sourcing when nobody knows you yet
Nobody applies spontaneously to an unknown startup. Your sourcing starts with your own network and your investors' networks: an introduction converts far better than a job ad. Use LinkedIn, the communities in your sector, and referrals from people you trust. If you publish regularly (founder-led content), candidates who already know your project will also come to you. Treat a job posting as a supplement only. Finally, own your size: a strong senior generalist wants to shape the product and make their own calls more than they want a reassuring brand name, so sell them the project and the scope before security.
Assessing fit (skills + potential + culture)
Evaluate along three axes. Skills (can they do the job today?), potential (do they learn fast and handle ambiguity?), and cultural fit (will they thrive in a company with no processes where everything changes?). At the early stage, a candidate with a bit less experience but high potential and strong adaptability often beats a rigid expert. Have them work on a real case from your company rather than relying on a CV: half a day of hands-on work tells you more than three interviews.
Onboarding and the probation period
Hiring doesn't end at the signature. Whether the hire succeeds is decided in the first few weeks.
Prepare for their arrival before day one: access, equipment, first concrete assignments. A new hire who spends their first week waiting for instructions loses confidence, and you lose money. Give them a clear, achievable goal for the first thirty days, a "small win" that proves they can deliver in your context.
Use the probation period for what it is: a test, in both directions. If the fit isn't there, don't wait until the end of the probation period hoping things will sort themselves out. A bad first hire that drags on costs you more than the hard decision to end it early.
Why so many first hires fail (and how to avoid it)
The reasons a first hire fails repeat from one startup to the next, and you can almost always avoid them.
The founder hires alone, in a rush. With no HR function, the founder handles hiring on top of everything else, quickly and poorly, and ends up hiring the first "decent" candidate under time pressure. The fix: start sourcing before you're at breaking point.
The scope is unclear. You hire "someone to help," with no specific outcome to reach. The hire drifts, the founder gets frustrated, and nobody knows what success looks like. The scorecard solves this upfront.
You hire a senior profile for junior execution, or the reverse. A highly paid expert who spends their days on operational tasks gets bored and leaves; a junior thrown into a fuzzy scope sinks. A seniority mismatch sinks a lot of hires.
You overvalue experience and underestimate fit. A brilliant CV from a large corporation guarantees nothing in a five-person company with no processes. Adaptability and autonomy matter more than pedigree.
A bad first hire costs you a salary, slows your growth and weakens the culture you're building. Better to be a month late with the right person than the other way around.
swanbase supports early-stage founders over the long term, in Paris and remotely, at €0, by application, and takes equity: present your project.
FAQ
When should a startup hire its first employee?
When three signals converge: you've become the bottleneck on a recurring need, you have real traction (paying customers, retention), and your runway lets you carry the fully loaded salary for at least twelve months. If any of the three is missing, it's too early. The right moment comes when not hiring costs you more than hiring.
Who should a startup hire first?
A senior generalist, autonomous and adaptable, rather than a narrow specialist. Pick the profile that fills your biggest weakness: business if you're a technical founder, product or tech if you're a business founder. Your first hire executes on a defined scope, while a cofounder shares the vision and the risk.
How much does a first employee cost in France?
According to the Urssaf simulator (September 2026, default settings for a small company), an employee paid €3,000 gross per month costs their employer about €4,000 per month, or around €48,000 over the year. The multiplier rises with salary: about 1.43 times gross for an executive at €5,000. Add equipment, software and onboarding time to estimate your first-year budget.
How much equity should you give your first hire?
It depends on the role and the stage: the earlier you hire, the more risk the hire takes on, and the more generous their equity should be. In France, employee equity usually takes the form of BSPCE. According to Index Ventures' Rewarding Talent guide (2018), about four of the first ten employees at a European seed-stage startup receive options. Always include vesting, most often over four years with a one-year cliff.
Why do first hires so often fail?
Four main reasons: hiring alone and in a rush, a poorly defined scope, a seniority mismatch between the role and the profile, and overvaluing experience at the expense of cultural fit. All of them can be avoided with a clear scorecard, early sourcing and an assessment based on a real case.
