Every founder we spoke to remembered the conversation, not the contract. The first person you hire is the first time your company becomes an argument you are making to a stranger: this is real, this will work, come and spend a year of your life on it. When that argument is wrong, it is wrong in a way that takes months to admit and a quarter to undo.1
We looked at 1,200 founder workspaces on 0to1 where a first non-founder hire was recorded between 2023 and 2025, and matched the hiring decision against what the team said twelve months later. The single cleanest finding: 43% of founders regretted their first hire. That number is not interesting on its own. What is interesting is who did not.
The shape of the regret
Regret was rarely about competence. Only one in five of the regretted hires were described as "couldn’t do the work." The rest clustered around a different failure: the hire was made to escape a decision the founders had not yet made themselves — about what the company was, who it served, or what the next ninety days were for.
“A first hire cannot resolve a question the founders are still avoiding. It can only give that question a salary.”
Source — 0to1 Data Drop, n=1,200 workspaces, 2023–2025
It is not about speed
The obvious lesson — hire slower — is the wrong one. Founders who waited longest were not meaningfully happier; several of the most regretted hires came after eighteen months of deliberation, by founders who had talked themselves into believing the perfect candidate would resolve their ambivalence. Timing correlated with regret only through a third variable: whether the team had a written, falsifiable reason for the role.2
Put plainly: the founders who did not regret their first hire were not more patient. They were more specific.
The three habits
Three practices separated the 57% from the rest. None requires capital, a recruiter, or a brand. All three are decisions the founders make before a single candidate is contacted.
- 01They wrote the role as a bet, not a wishlist. One sentence: "We are hiring X so that Y happens by Z, and we will know we were wrong if W." Teams that could write W had half the regret rate.
- 02They hired against the next ninety days, not the next funding round. The job that survives is the one tied to a demand you can already see, not the org chart you hope to need.
- 03They let the first hire change the founders. The durable hires were given one real decision to own in week one — and the founders adjusted to the answer instead of overruling it.
“The question is not "can this person do the job." It is "do we yet know what the job is."”
A repeated finding across 1,200 teams
What to do on Monday
If you are within a quarter of your first hire, write the W sentence before you write the JD. If you cannot complete "we will know we were wrong if —," you are not ready to hire; you are ready to decide. That is cheaper, faster, and the thing the role was standing in for all along.3
The 57% did not have better instincts. They had a written bet they were willing to lose. So can you, this week, for the price of an honest afternoon.
Notes
- 1Workspaces self-reported the regret at the 12-month mark via the 0to1 reflection prompt; figures are anonymised and aggregated, never attributable to an individual team.
- 2A "falsifiable reason" was coded as present when the recorded role description contained an explicit failure condition. Inter-rater agreement on this coding was 0.81.
- 3See also the Founders’ Playbook, decision 6: "The first hire," for the long-form version of the W-sentence exercise.