Solo Founder Hiring: How to Make Your First Hire When There Is No Co-Founder

Solo founders do not get a second opinion on hiring. No co-founder to gut-check a candidate. No partner to split reference calls with. No one to say "I got a weird feeling in that interview, did you?"

You are the entire hiring committee. That is the reality.

It is also the reason solo founders make hiring mistakes that co-founded teams catch early. The mistakes are not about bad judgment. They are about decision fatigue. When you are selling, building, fundraising, and hiring alone, your brain hits a limit. At some point, every candidate looks fine because saying no means another week of being the bottleneck.

This post is a framework for solo founders who are hiring without a safety net. It covers what to hire for first, how to evaluate alone, and the one mistake that sinks more solo-founder hires than anything else.

Hire for the Function You Are Worst At

Most solo founders hire a generalist first. Someone who can "help with everything." It feels right. You are drowning in everything, so you want someone who can swim everywhere.

This is the most expensive hiring mistake solo founders make.

Here is why: at two people, generalism means you are both mediocre at 10 things instead of excellent at five each. The founder is mediocre at the thing they hired for, and the new hire is mediocre at the thing the founder was already doing badly. Nobody is excellent at anything.

Instead, rank every function in your business by how badly you perform at it. Not by how much time it takes. By how poor your output is. The function at the bottom of that list is your first hire.

If you are a product-minded founder who can sell but cannot write a clean line of code, hire an engineer. If you are technical but allergic to outreach, hire someone who sells. The goal is not to offload busywork. The goal is to plug the hole where your work product is genuinely bad.

One solo founder I worked with spent 18 months doing his own bookkeeping. He hated it. He was bad at it. He filed taxes late twice. He finally hired a part-time accountant at $600 a month. His first reaction: "I should have done this on day one. I was losing more money being bad at this than I paid her."

That is the test. If paying someone to do something badly is more expensive than paying someone to do it well, you needed the hire six months ago.

Write the Scorecard Before You Write the Job Description

Co-founders have an advantage solo founders do not: they argue about what good looks like. That argument, as frustrating as it feels in the moment, forces clarity. Two people cannot share a hire until they agree on what they are hiring for.

Solo founders skip this step. They write a job description, post it, and start interviewing. The problem is that a job description describes activities. A scorecard describes outcomes.

Before you write a single word of the job post, write down the five things this person must accomplish in their first six months to make you say "that was a great hire." These are not responsibilities. They are results.

Bad scorecard item: "Manage our social media accounts." Good scorecard item: "Grow qualified inbound leads from social channels from 3 per month to 15 per month."

Bad: "Handle customer support tickets." Good: "Reduce average time-to-resolution from 48 hours to 8 hours while maintaining 95 percent satisfaction."

When you interview alone, the scorecard is the only thing keeping you honest. After each interview, score the candidate on each outcome on a scale of 1 to 4. Do not write "seemed smart" or "good energy." Force yourself to assign numbers. A candidate who gets all 2s and 3s is not a hire. You are just tired of interviewing.

The Four-Attitude Minimum

Culture fit is harder for solo founders to evaluate because there is no existing culture to compare against. At a 50-person company, you can ask "would this person fit with the team?" At a one-person company, the question is "would this person fit with me?"

That question is too vague to answer reliably. You need structure.

Pick four attitudes you are unwilling to compromise on. Not values on a wall. Attitudes that show up in behavior. Examples from solo founders who got this right:

"Comfort with incomplete information." At a two-person company, there is no onboarding doc, no process manual, no person to ask. The right hire figures it out or asks fast. The wrong hire waits to be told.

"Ownership of mistakes." In every interview, ask the candidate to describe a project that went wrong. Listen for whether they say "we" or "I" when describing the failure. Solo founders cannot afford hires who blame circumstances.

"Low ego about work." The first hire at a solo-founder company will do unglamorous things. Customer support. Data entry. Chasing down a late invoice. If the candidate talks about what they are "above" doing, they will not survive month two.

"Direct communication." No co-founder means no triangulation. If something is broken, the hire needs to tell you directly. Candidates who manage up with vague positivity will leave you guessing until the resignation letter arrives.

Score each candidate on these four attitudes after every interview. If the candidate is a 4 on outcomes but a 2 on attitudes, do not hire them. Attitude problems at a 2-person company are terminal. There is no team to absorb them.

The Redundancy Test

Here is a question most solo founders never ask themselves: "If I got hit by a bus tomorrow, could this person run the company for 30 days?"

The answer does not need to be yes. But it needs to be closer to yes than no. Early hires at solo-founder companies inherit more responsibility than their title suggests. They become the de facto number two whether you intend it or not, because there is nobody else.

During the interview, give the candidate a real problem you are dealing with right now. A customer who is about to churn. A product decision you are stuck on. A vendor who missed a deadline. Ask them what they would do.

You are not looking for the right answer. You are looking for whether they can think through an ambiguous problem without you in the room. That is the skill that separates a solo founder's best hire from their most expensive mistake.

Reference Checks: Ask the Question Nobody Asks

Solo founders do reference checks alone too. Most ask "were they good to work with?" That question produces polite answers and teaches you nothing.

Ask this instead: "On a scale of 1 to 10, how likely are you to hire this person again if you had an open role tomorrow?"

Anything below an 8 is a no. Anything below a 9 deserves a follow-up: "What would it take to make it a 10?"

Then ask: "What is the one thing I should know about managing this person that they would not tell me themselves?"

The best reference checks feel awkward. If the reference sounds comfortable, they are not telling you the whole story.

---

Solo founders do not get a hiring safety net. That sounds like a disadvantage, and in some ways it is. But it also forces discipline that co-founded teams often skip. No arguing about what good looks like. No splitting the difference on a candidate because the other co-founder sees something you do not. No hiring by committee.

You make the decision. You own the outcome. The framework above makes sure the decision is not a guess.