You've shipped the MVP. You've got a few paying customers. The roadmap is starting to outrun your nights and weekends. So you start thinking about hiring your first real employee.
This is one of the most consequential moves a first-time founder makes. Pick wrong and you'll burn six months of runway training somebody who never quite fits. Pick right and you'll double your output and protect your sanity. Hire #1 is solvable if you treat it like a strategic decision, not a vibes call. This guide walks through when to hire, what to hire, how to pay, how much equity to grant, and how to run the process so you don't blow it.
When should you make your first startup hire?
You should make your first startup hire when there's a specific bottleneck that's costing you more than the hire will cost. The wrong trigger is "I'm tired and want help." The right trigger is "I keep delaying X because I'm doing Y, and X is the highest-impact thing in my business right now."
For most software startups, that bottleneck shows up around $5K to $15K in monthly recurring revenue, or roughly 30 to 50 paying customers. Before that you don't have the cash flow to absorb a hire without slashing your runway in half. After that you're usually drowning.
Calculate it directly. Fully loaded cost of a first hire in the US ranges from $90K to $180K per year once you include payroll taxes, basic benefits, and equipment. That's $7,500 to $15,000 a month against your burn. If your runway drops below 9 months after the hire, raise first or wait. If you'd rather pay yourself nothing than keep doing the thing you'd be hiring for, you waited too long.
What role should your first employee fill?
Your first employee should free up the thing only you can do. For a technical founder that usually means hiring a generalist on the go-to-market side. For a non-technical founder it's almost always an engineer. The pattern: if you spend 60% of your time on something a junior version of you could handle, that's the hire.
Three archetypes work for hire #1 at a pre-Series A startup.
A founding engineer who can ship features without spec'ing them. Pay range is $130K to $180K base with 1% to 2% equity at a pre-seed company. Stripe's first non-founder hire (Greg Brockman) wrote integrations and product simultaneously. Linear's early team did the same.
A founding GTM hire who runs sales, content, and customer success at the same time. Pay range is $100K to $160K base with 0.5% to 1.5% equity. They demo, write the blog, run onboarding calls, and stitch HubSpot to Stripe themselves. Notion's Akshay Kothari operated as this hire for a long time.
A founding operator who closes 80% of the operational gaps so you can keep selling and building. Think recruiting, vendor management, finance ops, customer support. Pay range $90K to $140K with 0.25% to 1% equity. Lattice and Brex both hired this role early.
If you find yourself listing three "would be nice to have" roles, the answer is usually a generalist instead of a specialist. Specialists make sense once you have something to specialize in.
Should you hire an employee or a contractor for your first role?
You should hire a contractor first if the role is shorter than 4 months, scoped tightly, or you're not sure you trust your roadmap yet. You should hire an employee if you want commitment, equity alignment, and a person who'll defend the company when it's hard. Contractors are faster to start and easier to end. Employees are more invested but cost more emotionally and financially to remove.
A useful sequence is "contract to hire." Hire someone on a 3-month contract through a platform like Deel, Toptal, or A.Team. Pay them a market rate. Treat the contract like a tryout where both sides find out if it works. Conversion rates from strong contract starts to full-time are commonly cited in the 40 to 60% range at early-stage companies.
A few rules of thumb that save founders pain.
Don't pay contractors in equity only. The IRS, state labor boards, and the contractor's lawyer will all eventually have something to say about that arrangement.
Don't classify a contractor as a 1099 if they work full-time for you, set their own hours, or take direction every day. That's an employee. Misclassification penalties in California can run $5,000 to $25,000 per violation. Run the IRS 20-factor test before you commit.
Use Gusto, Rippling, or Justworks for US payroll. Use Deel or Remote.com for international hires. Don't try to run payroll yourself. The $40 to $80 a month a PEO charges is the cheapest insurance you'll buy.
How do you find startup-ready candidates without a recruiter?
You find startup-ready candidates by recruiting from your existing network and from communities where startup-curious people already hang out. Recruiters cost 20 to 25% of first-year base salary, which means a $140K hire costs an extra $28K to $35K up front. At hire #1, that's runway you don't have. Most founders close their best first hire from a warm source.
Where to actually look.
Your past coworkers. The single highest-conversion source for early hires. Make a list of 20 people you've worked with who you've thought "I'd hire them tomorrow" about. Email them this week. Not all 20 will be available. Three to five will be open to a conversation, and one or two of those will be a real fit.
Your customers and users. Founders forget this one. The people who already love your product and have relevant skills are the highest-trust hires you'll ever make. PostHog, Linear, and Notion have all hired heavily from their user base.
Public communities. For engineers: GitHub, contributors to open source projects in your stack, the Recurse Center alumni list, and r/SideProject. For GTM: r/sales, RevGenius, Modern Sales Pros, and the founding GTM Slack channels run by Pavilion. For operators: On Deck cohorts, Lenny's Newsletter community, and the COO Alliance.
Job boards that actually work for early-stage roles. Hacker News "Who's Hiring," Wellfound (formerly AngelList Talent), Y Combinator Work at a Startup, and Lever's startup job board. Skip Indeed and ZipRecruiter for hire #1. The signal-to-noise ratio is poor at this stage.
When you publish the role, write it like a founder writing to a peer, not a corporate JD. Tell them what your first 90 days will actually look like, the three problems they'll own, the cap table truth, and the equity offer. The best candidates filter on honesty.
What should you pay your first employee?
You should pay your first employee 70 to 90% of their market base salary in cash, with the gap made up in meaningful equity. Below 70% you'll lose to a competing offer. Above 90% defeats the point of startup equity. The exact number depends on your runway and stage.
Real ranges for first hires in US startups, drawn from the 2025 Carta and Pave compensation reports.
Founding engineer (full stack, 4 to 8 years of experience): $130K to $180K base. Market rate at a Series B company is $200K to $230K. Your discount: 20 to 35%.
Founding GTM lead (account exec or growth marketer with 5+ years of experience): $100K to $160K base plus a clear variable component if revenue-tied. Market: $140K to $200K. Discount: 20 to 30%.
Founding operator (chief of staff, ops lead, BizOps hybrid): $90K to $140K base. Market: $120K to $170K. Discount: 15 to 30%.
Founding designer (product designer with 4+ years): $120K to $160K base. Market: $150K to $210K. Discount: 15 to 30%.
The cleanest framing: pay them slightly below what they'd get at a Series B company, and grant them equity that could be worth 5x to 20x more if the company works. Founders who try to underpay at hire #1 spend the next year backfilling and re-hiring. The cost of a bad first hire (search time, lost work, severance, morale tax) is conservatively 6 to 12 months of their salary. Pay close to market.
If you can't afford close-to-market, that's a signal you should raise first, not hire first.
How much equity should your first hire get?
Your first employee at a pre-seed startup should get between 0.5% and 2% in stock options, depending on seniority, role criticality, and how much cash you're paying them. Cash and equity are interchangeable to the company, not to the candidate. Lower cash, higher equity. Higher cash, lower equity.
Carta's 2025 compensation report puts the median first non-founder hire at 1% with a 4-year vest and 1-year cliff. Index Ventures' Option Plan tool, the most-used founder reference for this question, suggests these bands for a US software startup pre-Series A:
Employee 1 (founding engineer or GTM): 0.75% to 2%
Employee 2 to 3: 0.5% to 1.5%
Employees 4 to 10: 0.25% to 1%
Employees 11 to 20: 0.1% to 0.5%
A few mechanics every first-time founder gets wrong.
Use ISOs, not NSOs, if your hire is a US employee. Tax treatment is better and the candidate cares.
Set a 4-year vest with a 1-year cliff as standard. If you don't include the cliff, you can't part ways with a bad hire after 3 months without giving them 3 months of equity. The cliff exists for both sides.
Get a 409A valuation done before you grant options. Carta, Pulley, or LTSE Equity will run one for $500 to $2,000. Without it, your strike price isn't defensible and your hire will eventually have a tax problem.
Talk to your hire about the difference between options and shares, the strike price, the dilution they'll see at the next round, and what an exercise window looks like if they leave. Founders who avoid this conversation get the equity grant wrong. The transparent ones convert offers at 75%+ rates.
How do you run the interview process when you've never hired before?
You run the interview process by replacing the panel-interview ritual with a paid trial and a small number of high-signal conversations. Most founders waste hire #1 on a 6-round process modeled on companies 100x their size. You don't need that. You need three things: signal that they can do the work, signal that they want the work, and signal that you can work with them.
A process that's worked across hundreds of early-stage hires:
A 30-minute intro call. You explain the company and the role. They explain their story. Both sides leave with one question: "do I want a second conversation?"
A scoped paid trial. 6 to 16 hours of real work, paid at their market hourly rate. For an engineer, ship a small feature against the production codebase. For a GTM hire, write a cold email sequence, run a discovery call, or draft an outbound list. For an operator, take a real internal problem and write a one-page plan. This is the single most predictive step you'll run. Skip it at your peril.
A reference call with 2 to 3 people they've actually worked with, not "I knew them in college." Ask the same five questions to every reference: "What did they own?" "What did they struggle with?" "Would you hire them again?" "Who else should I talk to?" "Anything I should worry about?" The "who else should I talk to" question consistently surfaces references the candidate didn't list.
A working session on a real problem with the founder. 90 minutes. Whiteboard or shared doc. You're testing how they think, push back, and ask questions when they have incomplete information. This replaces 4 rounds of behavioral interviews and catches culture mismatches that traditional interviews miss.
If you're stuck on whether to make an offer, the answer is no. Hire #1 is a high-stakes decision and ambivalence is data.
How do you onboard your first employee so they actually stick?
You onboard your first employee by treating week one as a structured plan, not a free-form ramp. The number-one reason early hires leave in the first 90 days isn't the work. It's that they show up Monday and the founder hasn't decided what they should do. Write the plan before they sign.
A 30-60-90 day plan for hire #1 that's worked at companies like Notion, Linear, and PostHog in their early days:
Days 1 to 7. Shadow you on every customer call, sales conversation, and product decision. Get full access to every system. Document one thing they're surprised by. Ship one tiny thing (a doc, a bug fix, a customer email).
Days 8 to 30. Take over a discrete responsibility. For an engineer, own one feature end to end. For a GTM hire, own one stage of the funnel. Daily 15-minute standups. Weekly 60-minute one-on-ones where you talk about how it's going, not status.
Days 31 to 60. They're now the owner of the area you hired them for. You stop touching it day to day. They report on outcomes in your weekly meeting. Bring them to a board update or investor call so they understand the bigger picture.
Days 61 to 90. They're hiring or scoping the next person in their function. They're proposing changes to how you operate, not just executing. If by day 90 they're still asking you what to do every morning, that's a signal. Have the direct conversation.
Two more onboarding moves that compound. First, give them write access to your strategic planning workspace. Whether you're keeping plans in Notion, Linear, Foundra, or a shared doc, your first hire needs to see the financial model, the GTM plan, and the roadmap. Founders who hide the plan from hire #1 create a two-tier company that doesn't scale. Second, run a "no surprises" weekly. 15 minutes where you and the hire each name one thing you're worried about. It surfaces trust issues, frustration, and bad fits before they become resignations.
Key takeaways
Hire when the bottleneck is bigger than the cost. The right trigger is a specific, recurring blocker, not generalized exhaustion. For most software startups that means 9+ months of runway and $5K to $15K in MRR.
Hire the role that frees up the thing only you can do. Generalists beat specialists at hire #1. Founding engineers, founding GTM, and founding operators are the three archetypes that work.
Pay close to market in cash, make up the gap with meaningful equity. Pre-seed first hires typically land at 0.5% to 2% equity, 4-year vest, 1-year cliff, with cash at 70 to 90% of market base.
Skip the panel interview. Run a paid trial, two reference calls, and a working session on a real problem. The paid trial is the single most predictive signal you'll get.
Onboard with a 30-60-90 day plan you write before they sign. Day 90 should look like full ownership of the area you hired them for. Founders who skip the plan lose their first hire to a competitor within 12 months.
Frequently asked questions
Can I pay my first employee in equity only?
No, not in the US, and not anywhere that has employment law worth respecting. Full-time employees are entitled to minimum wage and, depending on state, overtime. Equity-only "employees" are almost always misclassified contractors at best, and unpaid laborers in the eyes of the IRS at worst. If cash is the blocker, hire a contractor part time or raise first.
How long should my first hire's trial period be?
A paid trial of 6 to 16 hours of real work is enough to get a strong signal on output. A contract-to-hire arrangement of 60 to 90 days is enough to test working style. Anything longer than 90 days starts to feel like a worse version of full-time employment for the candidate, and the strongest people will walk.
Should I hire a senior person or someone earlier in their career?
Hire the most senior person you can afford who's willing to take a 20 to 30% cash haircut. Senior hires bring pattern recognition you don't have. Junior hires bring more hours and more upside for you, but they need management you can't yet provide. The exception is if you've managed people before and want a force multiplier you can mold.
What if my first hire doesn't work out?
Have the conversation by day 60. If it's not working by then, it usually doesn't get better. Be direct, document the issues, and offer a severance package of 2 to 4 weeks plus 30 days of equity vesting acceleration if it's not a fit. Treating the exit well protects your reputation, which matters more than the cash you save by being stingy.
Do I need to set up benefits for one employee?
You need worker's comp, payroll tax registration in your state, and at minimum health insurance contribution in most states (California, Massachusetts, and a few others require it explicitly). Gusto and Rippling will set this up in an afternoon for $50 to $100 a month. Skip 401(k), dental, vision, and life insurance until hire #3 or 4.
Where do I find templates for offer letters and equity grants?
The Y Combinator post-money SAFE library and the Cooley Go template library both include offer letters, equity grants, and at-will employment templates that are free and lawyer-approved. Index Ventures' Option Plan tool covers equity grant sizing. For a strategic-planning view of how this hire fits into the bigger company plan, the founder community at foundra.ai/key-reads/ has a number of deep dives on roadmap, runway, and team building.
Top comments (0)