Analyse the question before you finalise the solution
When a founder asks us 'should I hire someone for this role?', we always reframe it.
The question isn't whether you need more capacity. You probably do. The question is what kind of capacity do you need, and how confident are you that the demand creating the pressure is structural rather and not temporary.
- Permanent hires solve structural problems
- Contractors solve temporary ones
- Freelancers solve specific ones
Each is the right answer in different circumstances. Founders get into trouble when they reach for permanent every time, because permanent is the most expensive and least reversible option you have.
When is the right time for a permanent hire?
Three things should be true before you put the job spec out for a permanent hire.
Trigger one: sustained utilisation above 75% for three months.
One busy month makes a tired team but doesn't make a strong case for hiring. If utilisation is oscillating between months, then it’s a planning problem, not a capacity problem and hiring won't fix it.
Wait until the pressure has been tangible for a full quarter.
Trigger two: pipeline visibility on retained revenue, not project income.
A retainer client renewing for another twelve months is a fairly long term commitment. A fixed term project is a one-off. The first justifies a permanent hire but the second not always.
If you end up making ap permanent hire for a short term commitment, you’ll end up putting pressure on your growth team to secure the next big project.
Trigger three: a specific skill gap that recurs across multiple accounts.
If you keep needing a senior strategist for client work and you've outsourced it three times in the last six months, a permanent hire makes sense.
But if you needed a motion designer once for a one-off campaign, a permanent hire is not the right choice.
Test whether the gap shows up in your business often enough to justify carrying the overhead between uses.
When all three triggers fire at the same time, it’s the time to make a permanent hire.
When is a contractor the right answer?
Contractors have a very specific use case.
- A six-month project with a defined end date
- Parental cover
- You're building out a capability you want to test before committing
- You're working through a peak that will pass
On an average a contractor costs 20-30% more per hour than a permanent hire, but for agencies running through revenue cycles, contractors are often the cheapest option on a true cost basis, even at higher day rates.
The premium you pay buys you flexibility, and flexibility is what most agencies actually need.
Most agencies we work with use contractors below their actual capacity to absorb them. The instinct is to treat contractors as a last resort but they should be a first option for any work with a definable end date.
Tip: It’s important to note the IR35 layer, it’s where many founders make mistakes. If you're engaging a contractor through a personal service company, you need to determine whether the engagement is inside or outside IR35. Inside means PAYE applies. Outside means the contractor pays their own taxes. Get this wrong and HMRC will come for penalties. The test for outside IR35 is to determine if the contractor operates as a business. Do they have multiple clients? their own equipment? the right to send a substitute? And real control over how the work gets done. If you're treating someone like an employee in everything but name, they're an employee.
When is a freelancer the right answer?
Freelancers solve specific problems. A logo, a landing page, a piece of copy. Freelancers should be the go to choice for work that has a clear scope, a clear deliverable, and a clear end.
The agencies that use freelancers well have built a roster of two or three trusted people in each specialisation.
Freelancers vs Contractors?
If you’re confused about choosing between a freelancer or a contractor for your project, remember that the use case isn't about duration, it's about specificity.
You can use the same freelancer for six months and they're still a freelancer if every engagement is project-shaped. You can use a contractor for one month and they're still a contractor if they're operating as part of your delivery team.
The distinction in the management overhead is also substantially different. Freelancers manage themselves. You brief, they deliver, you pay. But contractors slot into your team and need to be managed alongside permanent staff. It is easy to confuse the two and either end up over-managing freelancers or under-managing contractors.
The fourth option: wait
This is the one nobody likes because waiting feels passive. But if the triggers for a permanent hire aren't fully there, and a contractor doesn't quite fit, the right answer is sometimes to wait.
Wait and watch the pressure for another month and see whether the pipeline materialises. The cost of waiting is short-term pressure on the team. But the cost of hiring too early is structural overhead, in which case the maths favours waiting more often than founders think.
The only exception is when waiting will cost you a client. If a key account is at risk because you can't deliver, don’t bother waiting, hiring is the best option.
The framework in practice
Here's how the decision should run.
- Start with utilisation. If it's been above 75% for three months, keep going. If it hasn't, stop. You have a planning problem, not a capacity problem.
- Then check the revenue picture. Is the pressure coming from recurring revenue or project income? Recurring revenue justifies permanent capacity. Project income doesn't, regardless of how large the project is.
- Then identify the gap. Is it a skill that recurs across multiple accounts, or a one-off? Recurring gaps justify a permanent hire. One-off needs justify a contractor or freelancer.
If all three line up for a permanent hire then go for it. If utilisation is high but the revenue is project-based, hire a contractor. If the need is specific and short, use a freelancer. If the picture is unclear, wait another month before deciding.
The agencies that follow this framework end up with leaner permanent headcount, more flexible cost bases, and better margins. The data backs this up healthy agencies run overheads at around 20% of fee income. The cohort average is 27%. That eight-point gap almost always sits in non-billable permanent headcount the billable team has to carry.
The Unusual take
Hiring well is one of the highest-leverage decisions a founder makes. Most founders make it under pressure, on instinct but usually without a framework. The ones who build the framework first save themselves years of structural overhead they didn't need to carry.
The agencies in our collective that hire well do two things differently. They wait longer before committing to a permanent hire and they use contractors and freelancers far more aggressively than their instincts suggest.
If you're staring at a hiring decision right now and not sure how to think about it, that's the kind of work we can help you with.
Book a call with us and we'll walk through where the pressure is actually coming from, and what the right answer looks like for your specific situation.


.jpg)

.jpg)