Hiring before the playbook exists
Most executive search is built for clarity. The client knows the role, the profile, the comparable companies, and the success metrics. The search firm runs a defined process against a defined brief, produces a shortlist of people who have done the job before, and the client picks one. For most of the economy, that model works perfectly well.
It breaks for category-defining companies, and it breaks at exactly the moment the stakes are highest.
A company creating a new market does not have benchmarks to hire against. There is no roster of people who have done this exact job, because the job did not exist until now. The role itself is often still forming, and will keep changing through the first year as the company learns what it actually needs. The talent pool is small, global, and not looking. And the cost of getting the hire wrong is high and slow to reverse, because an early leader shapes culture, sets the bar for everyone who follows, and makes decisions that are expensive to unwind later.
This is the work we are built for, and it requires a genuinely different way of thinking about search. The stakes are not abstract. When CB Insights analysed why startups fail, not having the right team ranked among the top three causes, cited in 23 percent of post-mortems, behind only no market need at 42 percent and running out of cash at 29 percent. The early leadership team is not a supporting detail. It is one of the few things most likely to decide whether the company survives.
Judge trajectory, not history
When there is no precedent to hire against, a resume tells you less than usual. The right question is not "has this person done this exact job before," because nobody has. The right question is "can this person operate in ambiguity, learn faster than the problem changes, and build systems that have never existed." That is a judgment about trajectory and temperament, not a checklist of past titles.
In practice this means weighting a few things heavily. Conviction, because category-defining work requires holding a direction through long periods of doubt, when the market is unconvinced and the data is thin. Learning velocity, because the problem will outrun anyone who is not compounding quickly, and the gap between a fast learner and a merely competent one widens every month in a fast-moving company. And judgment under incomplete information, because these leaders constantly make consequential calls without the data they would like to have, and the quality of those calls compounds.
None of these show up cleanly on a CV. All of them can be assessed, but only through the right conversations and the right references. You learn about conviction by asking someone to walk you through a time they held a hard line and what it cost them. You learn about learning velocity by tracing how quickly they have moved across domains and how deeply they went each time. You learn about judgment by examining the decisions they made with the information they had, not with the benefit of hindsight.
Define the role by working the problem
Because the role is still forming, the most valuable work often happens before sourcing begins. The temptation is to write a job description and go to market. The better path is to sit with the founding team and define what the role actually needs to be for this specific company at this specific stage, which is rarely what the generic title implies. A chief technology officer at a six-person company building something new is a different animal from a chief technology officer at a thousand-person company running something proven, even though the title is identical.
We have closed our hardest searches precisely because we invested in this upfront, working with founders to define what a leadership title meant for one specific platform before naming a single candidate. This is slower at the start and faster overall, because a sharp definition is what makes a rare profile findable. A vague brief produces a long shortlist of plausible people, none of whom quite fit, and weeks of interviews that end in a reset. A precise brief produces a short list of people who genuinely could do the job, and a faster, more confident decision.
Assess the team, not only the individual
Early leadership hires are rarely independent. The first handful of leaders have to work as a unit, and a brilliant individual who does not fit the emerging team can do more harm than a slightly less brilliant one who raises the whole group. When a company is building several leadership roles at once, the right approach calibrates candidates against each other as well as against their individual briefs, so the team coheres rather than merely assembling a set of strong resumes who cannot operate together.
Hire while it is still moving
The instinct under uncertainty is to wait for clarity before hiring. Category-defining companies cannot afford to, because the clarity arrives only after the right leaders are in place to create it. Waiting for the role to settle is waiting for an outcome that the hire itself is supposed to produce. The skill is hiring into a role that is still in motion, with a candidate who is genuinely comfortable that the job will change under them, and a process that calibrates against where the company is going rather than where it is today.
Most firms need the brief to be settled before they can help. The companies that need us most are the ones whose brief will not settle until the hire is made. That is not a gap in the process. It is the work, and doing it well is the difference between a leadership team that creates a category and one that arrives just in time to compete in a market someone else defined.