When Should I Make My First Hire?

Founders often frame the first-hire decision around workload. That is only part of the question.

A better test is whether the business has a recurring problem that another person can own.

Business.gov.uk identifies several practical signals: work is consistently exceeding the founder's capacity, demand cannot be met alone, there is enough surplus revenue to cover employment costs, or a valuable contract cannot be delivered without additional help. It also recommends logging the work before hiring so the founder can see which tasks are genuinely recurring and which are temporary spikes.

That distinction matters. A founder who is busy for two weeks does not necessarily need an employee. A founder who has spent six months doing the same high-value work that someone else could own may have a much clearer hiring case.

Before writing a job description, document what is actually happening.

For several weeks, record:

• recurring tasks
• time spent
• bottlenecks
• work that requires specialist skill
• work that only the founder can currently do
• work that could be improved with software or a process
• work that is being delayed because there is no capacity

This creates a more useful question than "Who should I hire?"

It becomes: "What outcome do I need another person to own?"

If the answer is still vague, keep diagnosing.

If the answer is specific, recurring and measurable, the role is beginning to take shape.

A useful first role usually does one of three things:

1. removes a recurring operational bottleneck
2. creates capacity for revenue-producing work
3. adds a capability the founder cannot reasonably build or perform alone

The third category needs care. A missing skill does not automatically justify a full-time employee. Business.gov.uk notes that short-term or irregular demand may be better handled with contractors, freelancers or other flexible help.

The decision is therefore not simply employee versus no employee.

It is:

What is the smallest reliable capacity commitment that solves the problem?

Sometimes that is a full-time hire. Sometimes it is part-time help. Sometimes it is a contractor. Sometimes it is a better process.

Salary is not the same as employment cost.

Before hiring, model the complete commitment for your jurisdiction: compensation, employer-side taxes or contributions, benefits, equipment, software, recruiting costs, onboarding time and the management capacity required from the founder.

The SBA's guidance similarly emphasizes establishing payroll, understanding employer responsibilities and distinguishing employees from contractors before making the hire.

Then test the decision against cash flow.

Ask:

• What happens if revenue is flat for six months?
• What happens if a major customer pays late?
• What happens if the hire takes longer than expected to become productive?
• What existing expense will you reduce, if any?
• What measurable capacity or output should the hire create?

A first hire should not depend on the best-case month continuing forever.

Hiring can increase burn before the underlying business is working.

YC's Michael Seibel has argued that founders often hire and increase spending before they have established strong product-market fit. His description of stronger fit centers on growing usage, paying customers and a founding team struggling to keep up with genuine demand, rather than simply having funding or a larger team.

That does not mean every company should wait for textbook product-market fit before hiring.

It means the reason for the hire should be visible in customer demand or a clearly necessary business capability, rather than the belief that adding people will create traction by itself.

A weak first-hire brief says:

"Need a proactive, fast-moving self-starter."

A stronger brief says:

"We need someone to own customer onboarding from signed contract to successful activation. The current process has five recurring handoffs. Your first 90 days are to document the workflow, reduce avoidable delays, and establish a repeatable reporting rhythm."

The second version gives a candidate something real to evaluate.

It also gives the founder a way to evaluate the hire later.

A useful role definition contains:

• the problem
• the owner
• the decisions they control
• the constraints
• the first 30, 60 and 90-day outcomes
• the measures that indicate progress
• the decisions that still require founder approval

If the workload is irregular, a contractor or freelancer may be more appropriate. If the bottleneck is repetitive administration, a process or software change may solve it. If the founder is spending time on low-value work, delegation may be possible without creating a new permanent role.

Business.gov.uk explicitly recommends considering process improvements, software, contractors and outsourcing when demand is uncertain or the role is not yet clear.

The point is not to avoid hiring.

It is to make the commitment match the problem.

Before making the offer, answer these questions in writing:

If most answers are green, the hiring question has become concrete enough to act on.

If several are warnings, the next move may be better diagnosis rather than recruitment.

A first employee does not simply add capacity. It changes the founder's work.

The founder now has to explain context, make decisions explicit, give feedback, manage payroll or providers, and build a role that another person can succeed in.

That is why the decision should be treated as an operating-system change, not just a recruitment event.

The best first hire is not the person who makes the founder feel less busy for a month.

It is the person who takes durable ownership of a problem the business genuinely needs solved.

Related reading: \2 · \2

Harvard Business Review — The Right Way to Handle Decision Rights. Decision ownership works better when the decision itself is clearly defined first. Harvard Business Review — Recruiting for Cultural Fit. Culture can shape hiring, but useful fit criteria should translate into observable behavior.

Evidence boundary: These sources support the underlying principles and context; they do not prove that one universal tactic works for every founder, market or company. SOE separates source evidence from editorial synthesis.