How to Know When Your Small Business Is Ready to Hire

The question behind the question

Most founders ask 'can I afford to hire' when the more useful question is 'do I actually need to hire, and is now the right shape of need'. Affordability matters, but it is only one of several conditions that have to be true at the same time. A business can afford a salary and still make a bad hire because the work was temporary, the role was undefined, or nobody had time to manage the person once they arrived.

Readiness is not a feeling of being busy. Almost every small business owner feels overloaded most of the time, because the work expands to fill whatever hours are available and then some. The test is not whether you are tired. It is whether the underlying demand for output is stable enough, and the role clear enough, that a stranger could step into it and produce value within a defined ramp-up period.

This guide sets out five conditions worth checking before you write a job advert: demand, definition, money, management capacity and systems. Treat them as a checklist, not a mood. If two or more are missing, hiring now is likely to cost you more in cleanup than it saves in relief.

Test one: is the demand recurring or a spike

In Kayley's experience, the most common reason a first hire does not work out is that the business hired against a temporary surge rather than an ongoing baseline. A big project lands, a founder says 'we need another pair of hands', someone is hired, the project finishes, and six months later there is a salary being paid against work that has quietly shrunk back to what the founder could do alone.

To test this properly, look back over the last two to three quarters, not the last fortnight. Has the volume of the work you want to hand off stayed roughly level, or trended upward, across that period? Is there a specific, named reason to expect it to continue at that level for at least the next twelve months, such as a signed contract, a repeatable sales pattern, or a structural change in how the business operates? If the honest answer is 'I think so' rather than 'yes, and here is the evidence', the demand test has not been passed yet.

• Chart the volume of the task or workload over the last two to three quarters, not just the last busy month.
• Separate one-off project work from work that repeats every week or month.
• Ask whether a client contract, seasonal pattern, or pipeline of confirmed work supports the next 12 months.
• Check whether the demand is growing because the business is growing, or because you have taken on too much personally.
• If demand is genuinely a spike, consider a freelancer or fixed-term contractor before a permanent hire.

Test two: can you describe the role in one page

If you cannot write a clear, one-page description of what this person will do in their first month, first quarter and first six months, the role is not yet defined enough to hire against. Vague roles produce vague hires: people who arrive keen and capable but with no clear way to judge whether they are doing well, which leads to drift, frustration on both sides, and often a resignation or dismissal within the first year.

Writing the role down also forces you to be honest about what you actually want off your plate. Founders often say they want to hire 'someone to help with admin' when what they mean is three quite different jobs: bookkeeping, customer email, and diary management. Naming those separately usually reveals that only one of them is a full role today, and that the other two might be better handled by a freelancer, a tool, or simply stopped.

1. List every task you currently do that you want this person to take on, however small.
2. Group the tasks into a coherent role — one that a single person could reasonably specialise in.
3. Write what success looks like at 30, 90 and 180 days in plain, observable terms.
4. Note which decisions the person can make alone and which need your sign-off.
5. Check the role still exists on paper if you removed every task that only feels urgent this month.

Test three: the real cost, not the headline salary

The salary you advertise is not the cost of the hire. Employer National Insurance, statutory pension contributions, equipment, software licences, recruitment costs and a ramp-up period during which the new person is not yet fully productive all add to the real first-year figure. Many founders budget against the advertised salary alone and then find the true cost of employment is meaningfully higher, which puts pressure on cash flow just when the business can least absorb it.

Alongside the cost, work out where the money to pay it will come from. There is an important difference between affording a hire out of cash you already hold or can reliably forecast, and affording a hire on the assumption that the new person will generate enough new revenue to pay for themselves. The first is a plan. The second is a hope, and hopes do not clear payroll on the last Friday of the month.

Current rates for employer National Insurance, the secondary threshold and pension minimums change from tax year to tax year, so always confirm the figures currently in force on GOV.UK before you model a specific number. What does not change is the principle: budget for total first-year cost with a reserve, not the advertised salary alone.

If the hire only works assuming everything goes right, it is not yet affordable.

Test four: do you have the management capacity

A new employee, however experienced, needs a defined amount of your time in their first few months: to explain how the business works, to answer questions, to review early work, and to correct course before habits set in. If your own calendar is already full, adding a person to manage does not create more hours in the day. It creates a person who is undermanaged, which is one of the most common and least discussed causes of early departures.

Be specific about how many hours a week you can genuinely set aside for onboarding and ongoing check-ins during the first three months, and whether that time already exists in your week or has to be found by dropping something else. If the honest answer is that you are already working evenings and weekends just to keep up, hiring will add a management burden on top of an already unsustainable load, and the new person will absorb the strain of that in the form of unclear direction and slow feedback.

• Block real calendar time for onboarding before the person starts, not after.
• Decide who answers day-to-day questions if it is not always going to be you.
• Plan a short weekly check-in for at least the first ten weeks.
• Identify what you will stop doing to free up the management time this requires.

Test five: can the work be handed over at all

Some tasks live entirely in a founder's head: which supplier to use for what, how a particular client likes to be spoken to, the order steps happen in, what 'good' looks like for a piece of work. If none of that is written down anywhere, a new hire cannot be expected to reproduce it, however capable they are. They will either guess, ask you constantly, or quietly do it their own way, none of which is a good outcome.

You do not need a polished operations manual before you hire, but you do need the basics: how the core recurring tasks are done, where things are stored, and who to ask when something is unclear. Building even a rough version of this before day one dramatically shortens the time it takes a new person to become useful, and reduces the number of times you have to stop what you are doing to answer the same question twice.

What it looks like when you hire too early

The pattern is familiar to anyone who has run a small team for a few years. A busy period creates pressure, a hire is made quickly to relieve it, the role was never fully defined so the person is given a shifting mix of tasks, the founder has no spare time to manage them properly because the same pressure that caused the hire is still present, and within four to nine months either the person leaves, is let go, or simply becomes another source of unmanaged workload rather than relief from it.

The financial damage compounds the operational damage. Recruitment costs, onboarding time, notice periods and the cost of doing it again all land on top of the original spend, often at a point when cash is already tighter than it was when the hiring decision was first made. This is why it is worth being deliberately slow and specific at the point of deciding, even when the pressure to act quickly feels intense.

What to do instead if you are not ready yet

Not being ready to hire does not mean doing nothing. It usually means one of a smaller number of moves: bringing in a freelancer or contractor for the specific piece of work that is currently overwhelming you, automating or simplifying a recurring task rather than paying a person to do it manually, delegating an existing task to someone already in the business who has spare capacity, or simply saying no to the piece of new work that is creating the pressure in the first place.

Each of these buys you time to build the conditions above properly: to confirm the demand is recurring, to write the role down, to build a cash reserve, and to document the basics of how the work is done. When you do eventually hire, you will be hiring into a role that has already been proven to exist, rather than guessing.

A short pre-hire checklist

Before you write a job advert, it is worth running through a short, honest checklist rather than relying on gut feel. None of these questions require a perfect answer, but each should have a specific, evidenced answer rather than an assumption.

1. Has this workload held steady or grown for at least two to three quarters?
2. Can you write the role in one page with 30/90/180-day expectations?
3. Have you modelled the full first-year cost, not just the salary?
4. Do you have a cash reserve or reliable forecast to cover it, separate from hoped-for new revenue?
5. Have you blocked real time in your calendar for onboarding?
6. Is the core of the work documented somewhere other than your head?