Count open questions, not open roles

A pre-seed founder booked a call last week with a hiring plan. Three roles in the next sixty days — a head of growth, a second engineer, and a part-time operations person. I asked her one question: how many things about the business has she figured out? She paused, then said 'most of it'. So I asked her to name the top five questions she still hadn't answered. She got to three.

That's the ratio I now ask every founder to track. Not headcount. Not burn. The question-to-role ratio.

What Startup Genome actually found

The 2011 Startup Genome Report looked at 3,200 startups and found 74% failed from premature scaling — hiring, spending, or marketing ahead of validation. They also found the companies that scaled properly grew roughly 20× faster than the ones that scaled early. None of the premature-scalers crossed 100,000 users.

That data is fifteen years old and the rule still holds. The money arrives before the clarity — which is the trap of a successful pre-seed round. You have cash, you have a team that's bigger than one, you feel like a company. So you start hiring the roles a company has.

The open-question test

Before you write the job description, write the question. Five prompts I use with founders:

• Who exactly is your first customer — not the ICP, the person? What's their job title, company size, and what do they hire your product to do?
• What's the one price they'll pay without a discount?
• Why did your last three customers buy, and why did the three before that not?
• What happens on day 7 after a customer signs up — do they come back, and why?
• If you had to cut half your product surface, which half would you keep?

If you can't answer three of those five with a straight face, you don't have a hiring problem. You have a question problem. A head of growth hired into an unanswered first-customer question costs six months and a relationship; a third engineer hired into an unanswered product-cut question builds the wrong thing twice as fast.

When it's actually time

Hiring unlocks — sorry, opens — when the answer to a question is clear and the bottleneck is throughput, not clarity. If you already know exactly what needs building, who it's for, what they'll pay, and why it hasn't shipped faster is a hands problem, then yes — hire. If any of those is fuzzy, the hire buys you noise.

Every hire is a confession of a bet you've already made. Before you confess, make sure you actually bet.