Hiring your first employee is one of the most consequential decisions a founder makes. It changes the shape of the company, the cost structure, the pace of work, and — often overlooked — how you spend your own time. Get it right and you unlock 2-3x your capacity. Get it wrong and you spend 6 months managing someone who's costing you money, blocking your progress, and impossible to fire without pain.
Most founders make one of three predictable mistakes on this hire: hiring too early (before there's a clear job), too senior (paying for capability they don't need yet), or too generic (a "generalist" who ends up doing nothing specific well). Each of those errors costs $50k-$150k in the year you make it, plus opportunity cost.
Here's the honest decision framework — what to actually think about before pulling the trigger.
First: are you actually ready to hire?
Before comparing candidates, be honest about whether you should be hiring at all.
Three signs you're ready:
1. You have a specific, repeatable task you personally do more than 10 hours a week that someone else could do at 80% quality. Not "I need help." A specific task. If you can't name the task in one sentence, you're not ready.
2. You have revenue (or committed funding) to pay salary + overhead for at least 12 months without depending on the hire producing revenue. Hiring someone whose success determines your survival is unfair to both of you.
3. You've genuinely tried the alternatives first. AI tools (see how non-technical founders should use AI), contractors, VAs, part-time freelancers. If those don't scale, hiring makes sense. If you haven't tried them, do that first.
Three signs you're NOT ready (don't hire yet):
1. You want to hire because it feels like the "next step" a real business would take. That's ego, not strategy. Hiring should solve a specific bottleneck, not validate your identity as a "real CEO."
2. The task the hire would do isn't clearly defined. If your job description is "help me with... stuff," you're going to end up with someone who doesn't know what to do and can't be held accountable.
3. You'd need them to be revenue-positive in 6 months to keep the lights on. That's not a hire; that's a Hail Mary. Different dynamic entirely.
The 4 categories of first hires (and which is right for you)
Most first hires fall into one of four categories. Each has a specific "when it's right" moment.
Category 1: Operational hire (executive assistant, virtual assistant, ops person)
What they do: everything routine that eats your time — email, calendar, invoicing, basic bookkeeping, customer support triage, scheduling, travel.
When it's right: you're spending 15+ hours a week on tasks that don't require you specifically. Common when the business is generating $10k+/month and you're the bottleneck on delivery.
What it costs:
- Full-time in US: $50k-$70k/year for a good EA or ops assistant
- Remote/international: $18k-$36k/year
- Part-time (10-20 hrs/week): $12k-$30k/year
Best hire order: usually the first or second hire for a solo founder. High ROI, easy to onboard, easy to measure success.
Why founders skip this and shouldn't: feels less impressive than hiring an engineer or designer. But every hour they save you is an hour on your highest-value work. Often the highest ROI hire in the first year.
Category 2: Senior technical hire (engineer, senior developer, tech lead)
What they do: build the product, own the codebase, ideally free you from being the sole technical person.
When it's right: you have a working product with real customers, and the roadmap requires more code than you can ship alone. If you don't have both of those, don't hire an engineer yet.
What it costs:
- US mid-level: $90k-$130k/year
- US senior: $130k-$200k+/year
- Remote/international senior: $50k-$100k/year
- Total loaded cost (salary + benefits + equipment + tools): add 25-35% to salary
Warning: most first engineering hires FAIL because the founder didn't set up the engineering practices they need to succeed. If you don't have a codebase they can work in, tests they can run, and a clear next 3 months of work, you're setting them up to fail.
Consider before hiring: fractional CTO (10-20 hours/month, $150-$300/hour) or senior contractor for 3 months. Cheaper way to test whether you need full-time engineering leadership.
The freelancer vs agency vs in-house decision tree covers when to bring engineering fully in-house vs stay contract-based.
Category 3: Sales/growth hire (SDR, account executive, growth marketer)
What they do: drive revenue growth beyond what you can personally do.
When it's right: you have proven that YOU can sell your product (10-20 closed deals with your own hands), you know exactly what your sales process is, and you have enough pipeline that you can't keep up alone.
What it costs:
- SDR (outbound cold outreach): $50k-$75k base + commission, US
- Account executive (closer): $70k-$130k base + commission
- Growth marketer: $80k-$130k
Warning most founders miss: you cannot delegate what you don't understand. If you haven't personally closed 10+ deals, you cannot hire someone to do it — you don't yet know what "closing" looks like in your business. First learn to sell, then hire.
Consider before hiring: a fractional VP of Sales (10-15 hours/week, $200-$400/hour) to build the process with you. Test if outsourced sales works for your product before committing to a full salary.
Category 4: Second product person (designer, product manager, engineer #2)
What they do: own a specific product area you don't need to touch anymore.
When it's right: you have a product with real users, a clear roadmap, and enough capacity that one more product person meaningfully accelerates you.
What it costs: similar to senior technical hire (Category 2).
Warning: the second product person is often HARDER than the first, because now you have to think about how they and the first person collaborate. Don't hire the second product person until the first is thoroughly successful.
The 5 questions before you make the hire
Once you've decided you're ready and picked the category, answer these:
1. Can you write the specific job in one paragraph?
The paragraph should include: what they'll do daily/weekly, what success looks like in 90 days, what they're empowered to decide on their own, and what they need your approval for.
If you can't write this, you don't know what you're hiring for.
2. Can they be productive without you managing them daily?
If your answer to "who trains them?" is "I do, over the first 2 months" — you're going to lose a lot of your time. If it's "our SOPs and their previous experience carry them through" — you're set up for success. The PRD template post on this site applies here too — clear documentation is what lets a new hire be productive fast.
3. What's your firing plan?
Not because you plan to fire them — because everyone hopes it goes well but sometimes it doesn't. Know upfront: what does the 90-day probation look like? What signals in month 2 would tell you it's not working? What's the escape hatch if it goes badly?
Founders who don't think about this end up trapped with a bad hire because "firing them would be so hard."
4. What's the true cost, not just the salary?
For a US full-time employee at $80k base, the true cost is closer to $110k when you add:
- Payroll taxes (~7-8%): $6,000
- Health insurance (partial contribution): $5,000-$10,000
- 401k match (if you offer): $2,000-$4,000
- Equipment (laptop, software, home office setup): $3,000-$5,000
- Tools (email, CRM, project management, etc.): $500-$2,000/year
- Recruiter cost (if you used one): $8,000-$20,000
Budget the loaded cost, not the sticker price.
5. How does this hire change YOUR week?
The whole point of hiring is to change what you spend time on. If you can't articulate what YOU'LL do differently after they start, the hire is unlikely to be transformative.
Bad answer: "I'll have more time for high-level strategy." Good answer: "I'll go from spending 15 hours a week on customer support to 2 hours. Those 13 hours will go to talking to more prospects, which should double our sales pipeline."
Where to find first hires
Best places (in order):
1. Your network's warm intros. Ask 20 people you trust "who's the best [role] you've worked with recently?" Warm intros produce 5-10x higher-quality hires than cold applications.
2. Industry-specific communities. Slack groups, Discord servers, Twitter follows. Real people you've seen do good work publicly are much better hires than resume-only candidates.
3. Wellfound (formerly AngelList Talent). Best marketplace for startup roles specifically. Free basic tier works.
4. Toptal, Turing, A.Team (for contractors). Higher rates but pre-vetted, faster time to productive.
5. LinkedIn Jobs. Works but noisy. Expect 50-200 applications per role, most low-fit.
Places to be cautious:
- Fiverr / Upwork. Fine for very small contract work. Not great for full-time roles.
- Facebook groups. Depends heavily on the group. Some are gold; most are noise.
- Job boards for your specific role. Vary widely — do your research per platform.
The interview process (fast version)
You don't need a Google-style 8-round interview loop. For your first hire, a simple 3-step process works:
Step 1: 30-min screening call. Confirm they can do the job, their expectations match, and the personality fit is reasonable.
Step 2: Paid trial project (2-8 hours of work). Give them a REAL task from your business. Pay them for the time (not free work). Judge them on the output.
Step 3: Reference calls. Not "check references at the end" — CALL two people they've worked for and actually ask specific questions.
Do NOT: ask brain-teaser questions, do 5+ rounds of interviews, hire based on "gut feeling" without a paid trial, or hire someone who ghosts on communication during the interview process.
Do: run the 12 questions from the developer hiring post if you're hiring engineering — the framework works for most professional hires.
The 90-day plan
Once they start:
Week 1: onboard them like a person, not like a hire. Introduce them to customers, tools, key documents. Set expectations for the 90-day check-in explicitly.
Weeks 2-4: they should be shipping visible work. If they're still "learning" past week 3, something's wrong — either your onboarding is broken or the hire is wrong.
Month 2: they should be independently productive. Your involvement drops to weekly 1:1s and unblock-me conversations.
Month 3: 90-day check-in. Are they hitting the success criteria you wrote in the job description? If yes, congratulations. If no, be honest with yourself: is this fixable in the next 30 days, or are you rationalizing?
If it's not working: end it clean at the 90-day mark, not 6 months later. The longer you wait, the worse for both of you.
A specific example
I know a founder who bootstrapped a SaaS to $30k/month solo. She was drowning. Her instinct was to hire an engineer to help build more features. She almost did.
We ran the framework:
- Specific task: she couldn't articulate a specific engineering job — "help me build the roadmap faster" was too vague.
- True bottleneck: she was spending 20+ hours a week on customer support and 5 hours on invoicing/ops. Actual engineering was 15 hours/week and going fine.
- What she actually needed: an operational hire (Category 1), not an engineering hire.
She hired an experienced remote EA/ops person at $2500/month. Within 3 months:
- Support went from 20 hrs/week (her) to 4 hrs/week (her, only escalations)
- Invoicing/ops went from 5 hrs to 0 hrs
- She used the reclaimed ~20 hrs/week for sales conversations — pipeline grew 60%
- Total cost: $30k/year. Revenue impact: an extra ~$120k/year annualized.
An engineering hire would have cost her ~$150k/year, added zero revenue in year 1, and forced her to spend more time managing (not less).
The right hire depends on where the actual bottleneck is. Most founders assume it's product, but it's usually elsewhere.
What to do this week
If you're thinking about hiring:
- Track your time honestly for 5 days. Categorize every hour: sales, support, product, ops, admin, strategic thinking. See where the actual hours go.
- Write the ONE-paragraph job description for the hire you're considering. If you can't, you don't know what you're hiring for.
- Do the true-cost math (not just salary — include taxes, benefits, equipment, tools).
- Talk to 3 founders who made a similar hire in the last year. What went well, what didn't, what would they do differently?
If you're not ready to hire but need capacity:
- The AI workflows post covers what to try before hiring
- Consider a fractional or part-time version of the role first (fractional CTO, fractional CFO, part-time VA)
- Look at whether the work could be automated with existing tools
If you're in the process of interviewing:
- Use the paid-trial approach. The 2-8 hour paid trial is the single strongest signal of whether they can actually do the job.
- Actually call references. Ask specifics: "What would they need to grow into to be great at this role?" (Better than "were they good?" — reveals real information.)
Hiring is not a decision you undo lightly. Do the framework work upfront. The founders who hire well don't have better luck — they have better process.
---
If you're deciding whether to make your first hire and want an outside opinion on whether it's the right time and the right role, reach out via the contact page with a paragraph about your business stage and the specific problem you'd hire to solve. I'll spend 30 minutes on it and tell you honestly what I'd do.