When to Hire and When to Hold

When to Hire and When to Hold: The Capacity Decision Australian Founders Get Wrong | The Founder's Desk
The Founder's Desk
Decision Advisory · Australia

When to Hire and When to Hold: The Capacity Decision Australian Founders Get Wrong

Hiring too early burns cash. Hiring too late costs clients. Most founders make this call on instinct, under pressure, at the worst possible moment to be thinking clearly.

1 in 3
Australian SMEs cite capacity as their primary growth constraint
$40k+
Estimated cost of a mis-timed hire once salary, onboarding and lost focus are counted
6 mo
Typical lag before a wrong hire becomes undeniable and a decision gets made

The pressure that produces the wrong call

The moment most founders decide to hire is the moment they are most stretched. The inbox is full, a client is unhappy, something fell through a crack. The decision feels obvious: bring someone in. But a decision made at peak stress, with no structured thinking behind it, is rarely the right one.

The real question is “what is the actual constraint, and does adding a person fix it?”

Most founders hire for output when the bottleneck is coordination. The new person adds work to the system without removing the thing that was breaking it.

Two mistakes, opposite directions

Founders either hire reactively when pain forces the decision or they hold indefinitely, absorbing a cost in quality and founder energy that never shows up cleanly on a P&L. Both are expensive. The difference is which one is invisible until it is too late.

Reading the signals correctly
Signals that support hiring now
Revenue is consistent and the constraint is clearly time, not demand
Quality is slipping on work you can no longer personally oversee
You are turning away work you could otherwise take
The role is specific, scoped, and the success criteria are clear
Signals that say hold for now
Revenue is inconsistent and a new salary would pressure cashflow
You cannot describe what the person would do in their first 30 days
The real problem is process, not headcount
You are hiring to relieve stress rather than remove a specific bottleneck

The question underneath the decision

Before committing to a hire, answer one question precisely: if this person were in the role tomorrow, which specific constraint would be removed, and how would you know within 60 days that it had worked?

If that question produces a clear answer, the hire is probably right. If it produces a list of things you hope will improve, it is not yet a decision — it is a wish.

Capacity decision map
REVENUE STABILITY CONSTRAINT CLARITY LOW HIGH HIGH LOW Plan the hire Constraint is clear. Shore up cashflow first, then move. Hire now Conditions are right. Move quickly on a scoped role. Hold and stabilise Neither condition supports a hire. Fix the foundation. Fix process first Revenue is stable but the problem is not headcount.
The principle that holds

Hire for the bottleneck that is breaking quality, not for the pressure you are feeling. Those are often different things. The pressure is real. The source of it may not be what it appears.

If you are not sure which quadrant you are in, that is itself useful information. It means the decision needs structured thinking before it needs a job ad.


The Founder's Desk

Facing a capacity decision right now?

A fit conversation is 20 minutes and free. We will establish whether a Decision Sprint is the right next step and what it would look like for your situation.

Book a fit conversation →
Free Resource

Not sure which decision needs attention first?

The Clarity Kickstart is a free self-paced tool that helps you frame the decision before anything else.

Get the Clarity Kickstart →
Next
Next

Prioritisation: A critical business capability