I have made the first ten hires at a company twice, and I have watched fifty other founders make their first ten hires up close. The mistakes are not novel. The same five patterns keep showing up, and the same three sequencing calls keep getting made backwards. This playbook is the one I wish I had at hire one.
I am writing this in the first person because the other playbooks in this set are method-voice (Picked Team, the engineering and research leads). This one is a founder writing for founders. The arguments are mine; the mistakes named in section 08 are largely mine; the conviction calls are not committee positions.
The first ten hires are different from the next ten in three ways. First, you have no infrastructure. There is no recruiter, no HR business partner, no people-ops function, no onboarding template, no internal wiki to point a new hire at. You have a doc, a slack, and a calendar. Second, the variance is gigantic. A great hire two changes the trajectory of the company; a bad hire two costs you the next six months. The wrong-hire cost dominates everything else in your P and L. Third, every hire is a culture-defining act. The first eight engineers will form the culture; the manager you hire at twelve will inherit it but not create it. Get the first eight right.
Four things. Sequencing (who first, who second, who third, in section 02). Archetype-fit (the generalist, the specialist, the manager, the executive, in sections 04 through 07). Mistakes (the five I have made or watched up close, in section 08). And the founder-specific operating mechanics: comp, interview compression, the 30-day review at the earliest stage (sections 09 through 11).
I have used Picked at every Neuroworx hire since we hit hire four. The mechanics of the funnel are in the other playbooks; this one is about the calls only the founder can make.
Who do you hire first? At pre-PMF, three reasonable answers compete. Each is correct for a different company shape. Picking the wrong one for your shape will cost you a year.
Two questions to ask before you commit to a pattern.
One: is the product the constraint, or is the distribution the constraint? If the product is the constraint (you cannot demo to a single buyer because the demo is broken), tech-first. If the distribution is the constraint (you can demo all day but cannot get a meeting), sales-first.
Two: are you, the founder, currently the constraint on three workstreams or one? If three, ops-first might be right. If one, ops-first is a luxury and a delay.
For a typical post-pre-seed B2B SaaS, the sequence that worked best in the cohorts I have observed:
This trajectory assumes a B2B SaaS shape. Adapt for consumer (move designer earlier; defer sales), for marketplaces (move two operators in earlier; defer everything else), for deep-tech (move research scientists in at hire 1 and 2; defer everything else).
Before you write a job description for hire 1, you have to answer a single question. What does this person take off my plate? The answer is what the rubric scores on; the answer is what the role brief describes; the answer is what makes the candidate able to tell whether the role is for them.
A bad answer to this question is "they do general engineering" or "they help with the work". A good answer is "they own the product end-to-end from PRD to ship to support, while I run customer discovery and fundraising". A great answer is "they own the API platform and the integrations roadmap; I own everything else".
A test I run with every founder before they make hire 1. List the three things you do today that are on the critical path of the company. Now ask: which one of these three would this hire own from day one? If the answer is "none of them", do not hire yet. Hire 1 has to be on the critical path; otherwise the hire makes you faster on the wrong thing.
When the answer is "all of them", you are not ready to hire one person; you need to do another six months of work before hiring is the right move. The most common version of "all of them" is "we need someone who can do design, engineering, sales, and customer support". You will not find that person, and if you find them they will leave inside the year.
The temptation at hire 1 is to write a JD that lists every gap you have ever felt. Cut it. Pick the one critical-path workstream you are willing to hand over. Hire for that. The rest stays with you until hire 3 or 4.
At hires 1 through 3, the right archetype is almost always a generalist. Not because specialists are weaker, but because at hire 1 to 3 you do not yet know which specialism to bet on; the company shape is too undefined.
It does not mean "good at many things to a low level". It means "good at one thing to a high level and willing to do many other things to a workable level". The generalist engineer at hire 1 is a senior engineer who can ship a full-stack feature on Monday, talk to a customer on Tuesday, fix a deployment on Wednesday, and write the launch announcement on Thursday. The depth on Monday is what makes them senior; the flexibility on Tuesday through Thursday is what makes them a fit at this stage.
A first-hire generalist who refuses to talk to customers, or who refuses to write the launch announcement, is the wrong fit. Not because the work is theirs forever; because at the earliest stage there is no-one else, and the role only works if the person sees the whole thing.
Notice what is not on the list. Technical depth on any specific stack. Years of experience. Industry credentials. None of these predicts hire-1-fit better than the four behaviours above.
Hires 1 through 3 are paid in a mix of cash (below market) and equity (above what hires 5 onward will see). Typical bands: cash at 60 to 80 percent of mid-market senior; equity in the 0.5 to 2 percent range with four-year vesting, one-year cliff. Vesting acceleration on termination-without-cause is a fair ask and you should accept it.
A useful framing for the comp conversation: "We cannot pay market cash. We can offer real ownership in something we are betting on. If the cash matters more than the ownership for you, we are not the right fit right now." The conversation closes faster when you say this out loud.
Around hire 4 to 6, the shape of the company is clearer and the case for a specialist gets stronger. This is where the first specialised engineer, the first sales hire, or the first designer typically lands. The trick is timing: too early and you have a specialist with no specialism to own; too late and the generalists are burned out covering a gap that needs depth.
Three signals, any one is enough.
Hire a specialist when one workstream needs depth. Hire another generalist when no single workstream is yet clearly the constraint. About 70 percent of post-pre-seed companies in my observed cohort would have been better off making hire 4 a generalist instead of a specialist. The temptation to hire a specialist early is real and usually wrong.
Founders manage everyone until they cannot. Founder-management breaks down somewhere between team-size 8 and team-size 12; the symptom is that the founder cannot hold all the one-on-ones, cannot run all the reviews, and starts to drop work that used to feel managed. This is when the first manager hire becomes necessary.
Three concrete signs, any one is enough.
When two of the three signs are firing, hire a manager. When one is firing, wait one more month and see if it resolves; sometimes it does.
A manager with no team to manage will manage the founder, and the founder is not the manager's job. I have watched two companies hire a head-of-engineering at team-size 4 and lose them within nine months because there was nothing to manage and the manager was bored. Wait until there is a real team to manage.
The first executive is the hire where the founder-CEO transition begins in earnest. The first CTO, the first VP of sales, the first head of product. At this point you are hiring someone who is going to run a function that you, the founder, can no longer hold in your head end-to-end.
A common mistake at this stage is hiring a "head of" or "VP of" when a senior individual contributor would have been the right hire. The right question is: does this function have a team yet? If yes (3 or more people doing the work), a head-of is right. If no (you are about to hire person 2 in the function), a senior-IC is right.
I have watched a Series A company hire a VP of Marketing at team-size 12 with no marketers reporting in. The VP did not have a team to lead, did not enjoy the IC work, and left in six months. The right hire was a senior marketer who could build the team over twelve months and grow into the VP title.
Picked handles the screening, assessment, and behavioural interview the same way it does for any role. What is different at the executive level is the on-site and the references. The on-site is longer (a full day, not a half-day), the references go three deep (manager, peer, direct report), and the founder spends 90 minutes one-on-one with the candidate, not 30.
The hiring manager at an executive hire is, by definition, the founder. There is no "head of" above them to share the call. The decision is yours; the references are yours to read; the offer is yours to make.
Every executive hire is the founder shedding a piece of work they used to own. The shed has to be real. The most common executive-hire failure pattern is the founder hiring a "head of product", then continuing to make the product decisions themselves, and the head of product leaves frustrated within a year. If you are not willing to shed the work, do not make the hire.
Five patterns that show up over and over in early-stage hiring. Three are mine. Two I have watched up close. Naming them is the first move toward not repeating them.
The friend interview is the worst interview in start-up hiring. You meet for coffee, you both feel good, you skip the structured interview, you make an offer, you hire them. Six months later it is not working, and now you have to fire your cofounder's friend. I have seen this exact sequence five times. I have done it once.
The fix is simple: every hire goes through the same funnel. Friend, cofounder's friend, ex-colleague, all of them. The structured interview is the gate, not a formality. Skip it once and the next time the company has to fire someone, the firing is harder than it had to be.
Hiring someone less experienced than the role calls for, with the argument that "they will grow into it", is sometimes the right call. Hiring them without an explicit 30-60-90 plan that names which gaps will close and how is almost always wrong. The hire will struggle; you will not know whether to coach or replace; the months will pass; the work will not get done.
The fix: when hiring for potential, write the 30-60-90 plan before the offer letter goes out. Share it with the candidate. They either commit to it or they do not; if they do not, you do not hire them.
Covered in section 07. The most expensive version of this mistake is hiring a VP-of-sales before there is a sales motion to run. The VP-of-sales spends six months building a motion from scratch (which they have never done) and either burns out or you part ways. Most VPs of sales have run a motion, not built one. Hire a founding AE first.
A candidate who loves your product, has used it, has opinions on the roadmap, and is excited to join is a strong candidate. A candidate who has all that and is below the rubric on the competencies is still a wrong hire. Enthusiasm is a tiebreaker between two qualified candidates, not a substitute for the rubric.
The fix: do the rubric first. Enthusiasm is the last thing you weigh, not the first.
You know by month three. You hope by month four. You convince yourself by month five that it might still work. You finally have the conversation in month seven, by which point the hire has cost you four months of compounded delay and the rest of the team has been quietly disappointed for two of them.
The fix: when the 30-day review (section 11) is honest about a gap, address it then. Coach with a deadline; share the deadline with the hire; do not let the deadline pass without the conversation. The fact that the conversation is hard is the reason it has to happen on time, not the reason to delay it.
Compensation at hire 1 to 10 is mostly equity, partly cash, and entirely defensible only when you can post the numbers and they hold up to a conversation.
These ranges assume a Series-A-likely company with one prior priced round, no large secondary, and a hiring market that is competitive but not frothy. Adjust upward if the founders gave up less to investors; adjust downward if the equity is highly diluted.
Cash for hires 1 to 6 typically sits at 60 to 80 percent of mid-market senior cash for the role. For hire 1, sometimes lower; for hires 5 and 6 sometimes higher if the candidate has a non-trivial alternative offer.
Hires 7 to 10 (the managers and executives) need closer-to-market cash. The pool of candidates is smaller; the option to take a senior IC role at a larger company is real; below-market cash is a faster path to no than to yes.
Over-pay in cash when the candidate is risk-averse, has a family obligation, or is mid-career with cash dependencies. Over-pay in equity when the candidate is mission-aligned, has a track record of taking equity-heavy compensation, and is making a long-horizon bet.
The wrong move is to under-pay in both. A candidate offered below-market cash and below-market equity is reading a signal: this company does not value this role. The hire will accept reluctantly, look around inside six months, and leave by month eighteen.
At the earliest stage, the founder is the recruiter, the interviewer, the reference checker, and the offer-writer. There is no infrastructure to delegate to. The Picked-side of the funnel runs in the background; the founder-side is compressed into something that has to fit alongside running the company.
You post the role; Picked runs triage, the AI screen, the assessment, the behavioural interview. Three vetted finalists arrive in your inbox on Friday morning. You read three cards in ten to fifteen minutes. The first ten Picked screens are free; you can run the entire founder-stage hiring cycle without paying for vetting at all.
What you cannot delegate: writing the brief (you have to know what to look for), running the on-site, making the call, making the offer. These remain founder-time.
A typical Picked-recommended on-site has five blocks across a half-day. At the earliest stage, the team is too small for five separate blocks. Adapt to three:
If the team is one or two people, the "meet the team" round becomes a longer 1-on-1 between the candidate and the cofounder (or the sole prior employee). This conversation does not produce a structured score; it produces a yes-or-no on whether the second person in the company wants to work with this hire every day. Take that yes-or-no seriously.
A "no" from the only other person in the company is a non-starter, even if your founder-side judgement is strongly positive. The cost of a bad fit at team-size two is everything.
A 30-day review at hire 1 is different from a 30-day review at hire 50. At hire 1, there is no HR structure, no template, no peer-review process. There is the founder, the new hire, an hour, and the rubric. That is the whole review.
Five questions, in order. Each one is a 5-to-10-minute conversation.
The fourth question is the load-bearing one. The candidate scores themselves on the rubric; you score them; you compare. When the scores match, the hire is on track. When they diverge by more than one point on a competency, you have a coaching conversation in front of you; either the candidate is over-confident or you are under-recognising. Talk it through.
Two patterns to watch for.
One: under-investing in the review because the company is tiny. The founder is busy; the new hire is shipping; the review feels like overhead. It is not. Skip the 30-day review at hire 1 and you are reading the wrong signals at month four when the gap is bigger and the conversation is harder.
Two: over-investing in the review by trying to run it like a corporate performance cycle. The new hire does not need a 360. The team is two people; the 360 is one peer. The review is a conversation, not a process.
The whole playbook in one page. Print this section; pin it above your desk; come back to it every time you are about to make the next hire.
Founder of Neuroworx. Eight years building psychometrics into hiring. Writes about the unit economics, the candidate side of the funnel, and what shipping with Claude looks like in practice.