Most Stage 5 founders meet senior hiring the same way. The team has grown to 10-19 FTEs. The sales motion or the product roadmap (sometimes both) is straining at the seams. The founder is the rate limiter on whichever one is breaking. The conversation about a senior hire — Head of Sales, Head of Product, sometimes both — starts. The hire happens. Six months later, the hire is gone, and the team is back to where it was, minus the salary and the disruption.
The instinct after a failed senior hire is usually to blame the candidate. Wrong fit, wrong stage, wrong industry. Sometimes that is the diagnosis. More often, the candidate was fine; the system that brought them in was thin.
Why senior hires fail at Stage 5
A Stage 5 business is large enough to need senior layers but small enough that the founder has personally hired everyone before. Junior and mid-level hires are within the founder's hiring muscle — the founder has seen 30 of those candidates, knows what good looks like, knows the tells of what doesn't. Senior hires are different. The founder has usually hired one or two senior people, and the sample size doesn't generate the pattern recognition the founder relies on for everyone else.
The standard Stage 5 senior-hire pattern: founder writes a generic JD, runs 4-6 candidates through unstructured interviews, picks the one with the strongest CV and the most charisma, and onboards them with a vague 'find your feet' month. Six months later the hire has either been quietly absorbed into a role smaller than the JD promised, or has left because the role wasn't what they signed up for.
The fix is structural. The hiring system has four pieces that compound into a hire that sticks. Skip any of them and the stick rate drops. Build all of them and the stick rate compounds with the rigour of the system.
The four pieces of a senior hire that sticks
1. Constraint diagnostic before the JD. Which senior hire moves the most leverage point? Head of Sales — if the sales-team build is the gap, if revenue is being capped by the founder being in every call, if comp restructure and pod leads are needed. Head of Product — if product 3+ is the gap, if the second product is launched but the third is stuck, if the product roadmap is constrained by the founder's calendar. The diagnostic forces the choice between the two before the JD gets written. Stage 5 buyers who try to hire both at once usually fail both, because the supporting structure for either one isn't there yet.
2. JD against the actual constraint. Not a generic template. The JD names the specific business constraint the role exists to solve. 'Head of Sales who will install pod-lead structure across a 6-rep team, restructure comp around the new product 2 mix, and step the founder out of daily sales management by Week 20 of their tenure.' Specific. Bound to outcomes. Different from the same JD a £100M company would post. Salary band benchmarked to the buyer's geography and stage, not to industry-average tables that mix Stage 5 with Stage 8.
3. Scoring rubric, interview script, reference protocol. The rubric defines what 'good' looks like for each interview stage — phone screen, structured interview, panel, working session. The script ensures every candidate gets the same questions in the same order so comparisons are real. The reference protocol structures backchannels — usually 4-6 references including at least two outside the candidate's listed referees, with structured questions that produce comparable answers. None of these are clever. All of them are the difference between hiring on charisma and hiring on evidence.
4. 30-60-90 plan written before the candidate starts. Day 1 the new hire walks into a documented set of priorities tied to specific business outcomes — not three months of figure-it-out. Day 1-30: assess existing team, audit pod structure (or product roadmap), present diagnostic at end of month 1. Day 31-60: ship one structural change (comp restructure or product roadmap rework), build trust with team. Day 61-90: take ownership of the rhythm — pod leads run daily standups under the new structure, or product roadmap moves to a documented quarterly cycle. The plan isn't a contract; it is a mutual agreement on the early path. Hire-stick rate compounds with the rigour of the plan.
Why honest disclosure of land time matters
Senior hires take 90-180 days from JD posted to start date. JD posting + sourcing usually 30-45 days. First-round interviews 14-21 days. Final rounds and offer 14-21 days. Notice period at the candidate's current employer 30-90 days. Real start date 90-180 days from the JD going live.
Stage 5 founders often plan as though the hire will be in seat by Week 24 of a 24-week engagement. They won't be. The hire typically starts in early Operate Phase — month 2-3 after engagement-end. The system that hires them ships in the engagement; the hire themselves lands after.
Disclosing this honestly upfront is the difference between a buyer who is comfortable with the timeline and a buyer who is disappointed at Week 24 because the hire isn't in seat. The disclosure is part of the system. The 30-60-90 plan, the JD, the rubric, the interview script — all of these get built in the Build Phase. The candidate gets sourced, interviewed, and offered in the Build Phase. The candidate starts in the Operate Phase. That is the timeline. Honest disclosure makes the timeline workable.
What this looks like working
The early signal is the JD. The first version is generic; the diagnostic-against-constraint draft is specific. The candidate pipeline that comes from the specific JD is smaller (because fewer people self-select in) but higher quality (because the people who self-select in are the ones who match the constraint). By Week 22 the buyer has 3-5 candidates interviewed against the rubric. The shortlist by Operate Phase month 2 is 2-3 candidates the buyer can choose between.
The late signal is the hire's first 90 days. The 30-60-90 plan gets executed against. Day 30 the new hire presents the diagnostic. Day 60 they ship the first structural change. Day 90 they own the rhythm. The founder steps out of the territory the new hire was hired to own. The hire doesn't leave at month 6 because the role was what they signed up for and the structure for them to operate in was already there.
Why founders resist this
The most common resistance is the founder believing they already know what the JD should be without doing the diagnostic. Sometimes that is true. More often, the founder's instinct is to write a JD that describes the symptoms ('we need someone to take sales off my plate') rather than the constraint ('we need someone to install pod-lead structure across a 6-rep team and restructure comp around the new product 2 mix'). The diagnostic forces the structural framing.
The second resistance is the discomfort of structured interviewing. Founders who have hired everyone via instinct find the rubric feels mechanical. The fix is to run rubric-scored interviews alongside the founder's instinct read for the first 3 candidates and compare the scores to the founder's gut. Usually the rubric and the gut agree; sometimes the rubric catches a candidate the gut would have hired who would not have stuck. After 3 candidates, the founder trusts the rubric. Before 3, they don't.
The third resistance is the worry that 90-180 day land time means the engagement underdelivered. The opposite is true. The engagement that ships the system in 24 weeks and produces a hire who lands in early Operate Phase has compressed the senior-hire process from typical 12-18 months down to 6-9 months. That is faster than market, not slower. The disclosure makes the speed visible; without it, the buyer sees only the calendar gap.
What this looks like in real businesses
A construction business we worked with needed a Head of Sales. The founder had been writing JDs from memory, none of them landing real candidates. The constraint diagnostic surfaced that the actual gap was pod-lead structure plus comp restructure, not 'someone to manage sales.' The new JD named those outcomes. The candidate pipeline went from 8 underqualified responses to 3 well-matched candidates. The hire started in early Operate Phase month 3. By month 6, pod leads were running daily standup, comp had been restructured, and the founder was in 20% of calls instead of 80%. The hire was still there at month 18, by which point revenue and profit had doubled.
A consulting firm needed a Head of Product, not a Head of Sales (the diagnostic flipped the founder's instinct, which had been to hire a Head of Sales). The actual constraint was that the second product had launched but the third was stuck, and the founder was the rate limiter on the roadmap. The Head of Product JD named that constraint. The hire took 4 months to source and 3 months notice period. They started in Operate Phase month 5. By Operate Phase month 12, the third product had launched, the roadmap was running on a quarterly cycle, and the founder had stepped out of weekly product reviews.
The bottom line
Senior hires fail at Stage 5 not because candidates are wrong but because the hiring system is thin. JD, scoring rubric, interview script, 30-60-90 plan, reference protocol — these are the four pieces that compound into a hire that sticks.
The constraint diagnostic comes first — Head of Sales or Head of Product, but only one at Stage 5. The JD names the specific constraint, not generic responsibilities. The rubric and script make every interview comparable. The 30-60-90 plan gives the new hire a real path from day 1.
90-180 day land time is honest disclosure, not a bug. The system ships in Build Phase; the hire lands in Operate Phase. The buyer who plans against that timeline gets a hire who sticks. The buyer who pretends the timeline is shorter gets a hire who joined the wrong role and left at month 6.
Frequently Asked Questions
How do we choose between Head of Sales and Head of Product at Stage 5?
Run the constraint diagnostic. Head of Sales if revenue is being capped by founder time in calls, sales-team scaling is the gap, comp restructure and pod leads are needed. Head of Product if product 3+ is the gap, the second product is launched but the third is stuck, the roadmap is constrained by founder calendar. Stage 5 buyers who try to hire both at once usually fail both because the supporting structure for either isn't there yet.
Why does the JD have to name a specific constraint?
Because generic JDs produce generic candidate pools. Candidates self-select against the language of the JD. A JD that lists 'manage sales team, drive revenue, build culture' attracts candidates who want a generic Head of Sales role. A JD that lists 'install pod-lead structure across 6-rep team, restructure comp around product 2 mix, step founder out of daily sales management by Week 20' attracts candidates who specifically want that work. The pipeline is smaller, the matches are stronger, the hire-stick rate is higher.
How does the scoring rubric work in practice?
Every interview stage has a rubric defining what 'good' looks like — typically 4-6 dimensions per stage, each scored 1-5. The script ensures every candidate gets the same core questions in the same order. After each interview, the interviewer scores against the rubric within 24 hours. Comparisons across candidates are real because every candidate was assessed on the same dimensions. The rubric catches charisma-driven hires that wouldn't stick and surfaces under-the-radar candidates who would.
Why is 90-180 day land time framed as honest disclosure rather than a problem?
Because that is the actual market timeline for senior roles. Pretending it's faster sets the buyer up for disappointment at Week 24 of the engagement. Naming it upfront makes the timeline workable — the buyer plans against the real calendar, the system ships in Build Phase, the hire lands in Operate Phase. The 6-9 months total is faster than the 12-18 months a Stage 5 founder would typically take running this without a system.
How does this fit into the wider Build the Product Stack engagement?
Senior Hire That Sticks is Workflow #13. It runs Weeks 17-24 plus Operate Phase. The constraint diagnostic happens Week 17. JD plus rubric plus 30-60-90 plan ship by Week 22. Candidate pipeline runs Weeks 18-24. First 3-5 candidates interviewed against the rubric by Week 24. Hire shortlist by Operate Phase month 2-3. Start date Operate Phase month 2-3. The system ships in the engagement; the hire lands after.