Module 9 of 9 · 20 minutes
Hire and lead your first team
A first hire plan covering the role, its six-month outcomes, sourcing, assessment, pay, the first 30 days and feedback.
Know when to make your first hire
This module helps you decide when to hire, choose someone fairly and lead them well once they join. You'll finish with a written plan for your first hire.
Your first hire is one of the biggest decisions you'll make. It commits you to paying someone, often for years, and the first people to join shape how the company works long after. Hiring too early burns cash; hiring the wrong person costs months.
A first hire tends to make sense when most of these are true:
- there's recurring work that clearly matters to customers or revenue, not just a general feeling of being busy
- you've done the work yourself, or understand it well enough to say what good looks like
- you can pay the person reliably, ideally for at least a year, from money you already have
- you've considered the alternatives: dropping the work, automating it, or hiring a contractor for a defined project
A fictional founder of a meal-planning app for people with diabetes spends 15 hours a week answering support emails from paying users. The work repeats every week, it keeps customers happy, and she knows what a great reply looks like. That's a well-defined first hire. Hiring a marketer to "fix growth" before she knows which channel works would be much riskier.
Becoming an employer also brings legal duties, such as registering with tax authorities, running payroll and, in many places, providing insurance and written contracts. These vary by country and sometimes by region, so read your government's guidance for new employers before you make an offer.
Write the role around outcomes
Most job descriptions list tasks and years of experience. A better starting point is what must be true six months after the person joins. Outcomes tell candidates what success looks like and tell you what to assess.
Instead of "Answer customer emails; three or more years of support experience," try "Within six months, every customer gets a first reply within four working hours, our help center answers the 20 most common questions, and you run a monthly session sharing what customers are asking for."
From the outcomes, work out the few skills someone must have on day one. Keep this list short and testable, around three to five items, and treat everything else as nice to have. Requirements such as a particular degree or a set number of years often screen out good people without predicting who will do well, so include them only if the job truly needs them.
A good job post explains what the company does, the outcomes, the must-have skills, how you'll assess candidates, the pay range, where and when the work happens (including time zones, if remote) and how to apply. Some places legally require you to publish a pay range, and even where it isn't required, it saves everyone time.
Find and assess candidates fairly
Look beyond your immediate network. Friends and former colleagues are a fine place to start, but relying only on them tends to produce a team that thinks and looks like you, and it limits who gets a chance. Widen the search deliberately:
- your own users, who already understand the problem
- communities, meetups and online groups for the kind of work you're hiring for
- job boards that people in your region actually use
- university career services, and programs that help underrepresented groups into your industry
- referrals from mentors and advisors
Decide how you'll assess people before you meet anyone. A fair process looks something like this:
- Write down the criteria from your must-have list, and what a strong, acceptable and weak answer looks like for each.
- Ask every candidate the same core questions, mostly about what they've actually done, such as "Tell me about a time a customer was angry with you. What did you do?"
- Use a short work sample that resembles the real job, such as replying to five anonymized customer emails. Keep it brief, and pay candidates for anything more than an hour or so.
- Score each criterion on your own before discussing candidates with anyone else, so the first opinion voiced doesn't sway the rest.
- Check references with specific questions, such as what the person did best and where they needed support.
Be wary of choosing on "culture fit" as a gut feeling, which often just means "similar to me." Write down the behaviors you need instead, such as "raises problems early" or "writes clearly," and assess those. Many countries have laws against discrimination in hiring that limit what you may ask, for example about age, religion, pregnancy or family plans, so ask only about the job. And reply to every candidate promptly, including those you turn down.
Pay, equity and contractors
This section describes how things commonly work. It isn't legal or tax advice, the rules vary widely by country, and you should have a lawyer, and ideally an accountant, set up any equity plan or employment contract.
Employee equity. Many startups give employees a stake in the company, often as stock options: the right to buy shares later at a price fixed today. These usually come from an option pool, a block of shares set aside for staff and advisors, often created or enlarged when the company raises money. In US-style venture-backed startups, pools of around 10% to 20% of the company are common, though that's an observation, not a target.
Vesting with a cliff. Equity is usually earned over time. A widely used pattern, especially in the US, is four years of vesting with a one-year cliff: nothing vests during the first year, a quarter vests on the first anniversary, and the rest vests monthly over the following three years. Someone who leaves after ten months gets nothing; someone who leaves after three years has earned three-quarters. This protects the team from someone leaving early with a large stake.
Why early employees get more. The first people to join take the most risk: the company is more likely to fail, salaries are often lower and little is proven. Each percentage point is also cheaper while the company is worth less. So early hires usually receive larger percentages than people who join later.
Be honest with candidates that equity may end up worth nothing, because most startups fail. Never promise what it will be worth, and don't use it as a reason to pay unfairly. Tax treatment differs a lot between countries. The US distinguishes between types of options and has the 83(b) election for some share grants, both US practices; the UK has a government-backed scheme called Enterprise Management Incentives; and startups in some countries, such as Germany, often use virtual share plans instead of real options.
Contractors or employees. A contractor typically delivers defined work, decides how and when to do it, uses their own tools and can work for others. An employee works under your direction on an ongoing basis, and you take on duties such as payroll taxes and employment rights. What counts is how the work actually happens, not what the contract calls it, and getting it wrong can lead to back taxes, penalties and claims. The tests differ by country, and sometimes by state or province, so read official guidance, such as the IRS page on contractors and employees in the US or GOV.UK's employment status guide, and get local advice.
Whoever you hire, make sure they sign an agreement assigning the work they create to the company. In many countries, a contractor owns what they make unless the contract says otherwise.
Lead the people you hire
Hold regular one-on-ones
A one-on-one is a private, recurring conversation with each person who reports to you, often 30 minutes every week or two. It's their meeting more than yours, so let them raise topics first. Useful questions include "What's getting in your way?", "What should we change?" and "Is there anything I do that makes your job harder?" Keep a shared note of what you agree. Moving a one-on-one is fine; repeatedly cancelling tells people they don't matter.
Give feedback that's clear and kind
Feedback works best soon after the event, in private, and about specific behavior rather than character. "You were late to three customer calls this week" is something a person can act on; "you're unreliable" isn't. A simple structure helps:
- Ask permission. Check that now is a good moment.
- Describe what happened, specifically and without judgment.
- Explain its effect on customers, the team or the work.
- Ask for their view, since you may be missing context.
- Agree a next step together.
"Have you got ten minutes to talk about yesterday's call with the clinic? When the manager asked about pricing, you offered a discount before we'd agreed one. That means we've made a promise we might not keep, and she's expecting an email today. How did it look from your side?" Then, after listening: "Next time, could you say you'll confirm by the end of the day and message me? I'll write up our discount rules this week so you can decide on the spot."
Give praise the same way, specifically, and ask for feedback on yourself.
Write down how you work
A short "how we work" document saves you repeating yourself. Cover working hours and time zones, which channel to use for what, how quickly people should reply, how decisions are made and recorded, how to ask for help and how time off works. Turn recurring tasks, such as issuing a refund, into short checklists, and update the document whenever the same question comes up twice.
Stay sane
Exhausted founders make worse decisions. Protect your sleep and at least one full day off a week. Find a few other founders you can talk to honestly; people at the same stage often understand best. Notice your own warning signs, such as irritability or dreading work, and get professional support if you need it. Your team will copy your habits, so model the pace you want them to keep, and hand over decisions, not just tasks, as people show they can make them.
Do the work
Open the first hire plan builder.
- Name the role in plain words, then write two to four outcomes this person will own within six months. Make each one specific enough to check.
- Split skills into must-haves, three to five you can test, and nice-to-haves you could teach.
- Write where you'll look, including at least one place outside your own network.
- Describe your assessment steps, including the work sample and whether you'll pay for it.
- Outline your compensation approach: a pay range and, in general terms, whether and how you'll offer equity, noting what a lawyer or accountant will check.
- Plan the first 30 days week by week, and decide how often you'll hold one-on-ones and how you'll give feedback.
You're done when a co-founder, mentor or advisor could read the plan and understand what this person will achieve, how you'll choose them fairly, what you'll offer and how you'll support them once they start.
Your document for this module
First hire plan. A short plan for your first hire: what the role must achieve, how you'll find and choose someone fairly, what you'll offer and how you'll support them once they start. Share it with a co-founder, mentor or advisor before you post the job.