Scaling your startup: when to hire your first executive
There's no universal headcount or revenue number at which a startup "should" make its first executive hire. We get asked about timing constantly, and the honest answer is that it depends less on size than on which specific gaps are starting to cost the business money or momentum.
Quick answer: hire your first executive when a specific function has grown complex enough that founder-level attention on everything else is suffering — not on a fixed timeline, and not before you can describe exactly what that person would own in their first 90 days.
The two failure modes
Hire too early, and you've spent scarce runway on a senior salary for a function that doesn't yet have enough complexity to justify full-time executive attention — often leaving that person under-utilised and frustrated enough to leave within a year. Hire too late, and the gap has already started costing you: deals slipping, quality dropping, or the founder quietly burning out trying to hold a function together that's outgrown what one person can manage alongside everything else.
Five questions that actually tell you
- Could someone spend 100% of their time on this productively? If the role would only fill two or three days a week of real work today, it isn't ready to be a full-time hire yet — map out what they'd actually do on a Tuesday six months from now.
- Can you describe their first 90 days in specific terms? Not a job description — the actual decisions, projects and relationships they'd own from day one. If you can't name three concrete things they'd be doing in week two, the role isn't fully formed yet.
- Are decisions in this area currently slow or inconsistent because no one owns them end-to-end? That's a stronger signal than headcount or revenue — count how many decisions in this function sat unresolved for more than a week last month.
- Would a wrong hire here be expensive to unwind? If yes, you want more certainty about the role's shape before committing to a permanent search — which is exactly what fractional support gives you: real information about the role before you commit to it permanently.
- Has this already cost you something concrete? A missed deadline, a dropped deal, a quality issue — not a feeling that "we should probably have someone on this," but an actual instance you can point to from the last quarter.
Three or more "yes" answers is a strong signal the function is genuinely ready for dedicated ownership. Fewer than that, and the gap is probably better covered a different way for now — see the fractional option below.
The test isn't "are we big enough" — it's "is this function complex enough that it needs a dedicated owner, full stop."
The fractional middle ground
Between "founder does it all" and "full-time executive hire" there's a useful middle step a lot of founders skip: fractional or embedded senior support that gives you the judgement and experience of an executive without the full-time cost or the risk of a premature permanent hire. It also gives you real information — what the role actually needs, at what capacity, which decisions genuinely need daily attention versus weekly — before you commit to hiring it permanently, which directly answers question two above.
What good looks like once you do hire
When the timing is right, the first 90 days usually look like this: week one is spent mapping the actual state of the function (not the plan, the reality); weeks two to six involve fixing the most visible gap while building trust with the team; and by week twelve, the founder should notice specific decisions no longer reaching their desk at all. If that last part isn't happening by month three, the role wasn't scoped correctly — which is exactly the risk a trial period of fractional support is designed to catch before a permanent hire.
Next step
If you're weighing a first executive hire and aren't sure whether the function is ready for one, it's worth working through the five questions above with someone outside the decision. We help founders figure out exactly that.