Stop debating permanent vs contractor hiring. Start forecasting.
Updated: Sep 22
Every consultancy hits this moment: work has landed, delivery needs bodies, and someone asks the question that feels like the decision.
Permanent, or contractor hiring?
This isn’t the question. This is a symptom, and treating it differently is exactly how you end up back in the reactive resourcing cycle.
Permanent hiring can feel safer. Contractors feel flexible. So the debate becomes a tug of war between cost-certainty and flexibility, usually settled by whoever's most anxious in the room that week and delivery wanting a body now, finance wanting the lower long term cost and talent trying to hold the line on culture and capability.
Nobody's wrong. But everyone's answering the wrong question.
What the real question is
Before permanent-vs-contractor hiring even comes up, there's a question that should already be answered:
What stage is this business at, and how volatile is the pipeline behind this specific role?
That's a maturity question, not a staffing question and it changes the entire calculation. For example…
Volatile pipeline, unproven demand = contractor, every time. You're not ready to carry the overhead of a permanent hire against work that might not repeat.
Stable, repeatable demand = permanent, and the sooner the better. Contractors are expensive long-term insurance against a risk you've already priced out.
Somewhere in between = this is where most consultancies actually live, and where most get it wrong. ‘Somewhere in between’ doesn't feel like a clean answer, so people default to whichever option feels less uncomfortable right now.
Why this gets skipped
Because it requires someone to sit across business development, delivery, and finance and actually forecast - not guess, not hope, but actually forecast - how likely this demand is to repeat. That's uncomfortable work. It means business development has to be honest about pipeline confidence, delivery has to be honest about capacity assumptions, and someone has to own turning that into an actual staffing decision rather than a reactive one.
Most consultancies don't have that someone. So the permanent vs contractor question gets asked in isolation, decided by knee-jerk reactions, and revisited in a panic six months later when it turns out to have been the wrong call either way.
What good looks like
A resourcing decision that starts with the maturity question, not the contract-type question allows for more stability and clarity.
Forecast honestly first. Is this demand a one-off, a trend, or unknown? Don't skip to solutions before you've answered this.
Match commitment to confidence. Low forecast confidence, low commitment. High forecast confidence, then it’s time to invest properly in your resourcing and talent pipeline.
Revisit regularly, not in a crisis or at the end of the quarter. The maturity of a role's demand changes over time. What was volatile a year ago might be stable now. Build in a regular check-in, not just a reactive one when contracts are ending or landing. Reduce the risk of panic. Build a business that can withstand change.
So, what actually changes?
You stop making hiring decisions in isolation, and you start building a resourcing / talent function that can forecast and inform business planning. Permanent vs contractor hiring stops being a debate and starts being an output. The next time your leadership team asks this question, you already know the answer because you know the demand and you have someone who understands the market. This clarity lets you scale without panic.
Where I come in
This is exactly the kind of decision making I help growth stage businesses with. If you're weighing up your next hire and it feels more like a guess than a decision, that's exactly the conversation we should have.
Comments