You know the situation. The cloud migration has slipped three months. The data platform needs engineers you don’t have. The board wants an AI roadmap by next quarter. At some point, someone says “we need more people”, and almost straight away someone else asks: contract or perm?
It’s one of the biggest calls in technology workforce planning, and it’s usually made in about five minutes. The budget line decides it, or habit does, or whatever feels quickest. Get it wrong and you won’t notice on day one. You’ll notice six months later, when your new permanent hire is sitting in a role that has quietly run out of work. Or when an IT contractor has become the only person who knows how your core systems talk to each other.
The decision isn’t getting any easier. In a June 2026 Robert Half survey of 500 UK hiring managers, 47% said they planned to grow permanent technology headcount before the end of the year. Another 25% were expanding contract and project-based hiring. Most organisations are using both routes, and they’re often chasing the same people.
So how do you make the call?
Start with the work, not the job title
Before you write a job spec, try this. Write down what needs to be true in twelve months that isn’t true today.
Maybe it’s workloads moved to the cloud and the old data centre switched off. Maybe it’s a data platform the business trusts enough to make decisions on. It could be an acquired company’s systems folded into yours, or a team that can run its own AI models without calling for outside help.
That answer will tell you more than any job title. If the work has a clear finish line, like a migration, a platform build or a post-deal integration, it usually points towards contract or project support. If the work never really ends, like running the data platform or leading your security function, it points towards a permanent hire.
Lots of roles sit somewhere in between. An ERP integration might need a specialist contractor to lead design and cutover, then a permanent owner once things settle. Spot that early and you can plan the handover instead of scrambling for one.
Think about who keeps the knowledge
Every hire builds up knowledge. The question is where it goes when they leave.
Say you bring in a contractor to design a data pipeline that your team will be running for the next five years. The day rate is only part of the cost. You also need the documentation, the time spent working alongside your people, and a proper handover. None of that is a problem if you plan for it from the start. It becomes a problem when nobody owns it and the contract just keeps getting extended.
Here’s a simple test. If this person left tomorrow, who would pick up their work, and how long would it take them? If the honest answer is “no one” and “months”, you either need a permanent hire or a clear plan to build that skill in-house.
Be honest about how fast you need someone
Contractors are usually quicker to bring in. Permanent hiring involves more sign-offs and longer notice periods. In the hottest skill areas, you’re also up against a lot of competition. APSCo and CV-Library’s Q3 2026 Technology Sector Overview, which looked at Q2 2026 job postings, found that AI engineer postings were up 74.4% year on year for permanent roles and 96.3% for temporary ones. Cyber security is just as stretched. The government’s Cyber security skills in the UK labour market 2026 report found that 57% of businesses had a basic technical cyber security skills gap, up from 49% the year before.
But speed only helps if the work is ready to start. Too often a specialist arrives before the decisions they need have been made. The architecture isn’t agreed, the environments aren’t set up, data access hasn’t been approved, and stakeholders are still debating the plan. Paying a specialist to wait is one of the most expensive ways to lose time.
If you need someone fast, map out their first four weeks before they walk in.
Compare the full cost, not day rate against salary
Putting a day rate next to a salary is the most common shortcut, and it can mislead you either way.
A permanent hire costs a lot more than their salary. There’s employer National Insurance, pension, benefits, kit, management time, training and the cost of hiring them in the first place. A contractor’s rate looks higher on paper. But there’s no long-term commitment, and you only pay for the time you need. The fairer comparison is total cost against the outcome you wrote down at the start.
Don’t leave IR35 until the end
If a contractor works through their own limited company, the UK’s off-payroll working rules, better known as IR35, decide whether they should be taxed like an employee for that piece of work.
Who decides depends on who you are. Public sector organisations, and private or voluntary sector organisations that don’t count as small, have to make that call themselves. They then give the contractor a status determination statement explaining why. If the contractor falls inside the rules, whoever pays them, often an agency, deducts Income Tax and National Insurance before paying them. For small private sector businesses, the contractor’s own company makes the assessment instead.
What matters for hiring managers is that the job title doesn’t decide it. How the work is actually set up and run does, and it’s judged contract by contract. If you manage a contractor day to day like an employee, with no clear deliverable, they’re more likely to fall inside the rules. HMRC’s CEST tool is a good starting point, but complicated cases need proper tax advice. Either way, think about it when you’re planning the role, not in a rush when the offer is going out.
You don’t have to pick one or the other
Some of the best set-ups mix the two:
- Lead and shadow: a specialist contractor runs a cloud migration or AI pilot, with a permanent team member alongside them who takes over at the end.
- Interim to permanent: an interim leader steadies a data or security function, then helps shape and hire the permanent role.
- Project-based delivery: a small team delivers a defined piece of work, like a systems integration, with handover built into the plan.
- Contract to hire: both sides get to see if it works before committing.
These all work best when everyone agrees the end point up front. Without that, a temporary fix has a habit of quietly becoming permanent.
Write a brief people actually want to read
Whichever route you go down, the brief makes a big difference. The best specialists often aren’t looking for a new role. What gets their attention is a brief that tells them what problem they’d be solving, why it matters, who they’d be working with and what good looks like.
Twenty technologies followed by “excellent communication skills” won’t do that. “Move 40 applications to Azure and leave the internal team confident running them” will. Writing a line like that also makes you answer every question in this article.
It’s a bigger decision than it looks
Contract or permanent is rarely just a staffing question. It says a lot about how clearly the work has been thought through, how you want to build your team, and who will own the result once the pressure is off. That’s why the best hiring decisions start with how the work will get delivered, not with a job description.
That’s the space we work in at Synnovate. We help organisations across AI, data, cloud, cyber security, M&A and digital transformation with specialist talent, delivery teams and project-based consultancy. So we look at both sides: what a programme needs to succeed, and the right mix of people to get it there. Sometimes that’s a permanent hire. Sometimes it’s a specialist contractor, or a project team that delivers and hands over. Often it’s a bit of each.
If you’re trying to work out the right approach for a role or a programme, we’d be happy to talk it through. Connect with us at synnovate.co.uk.
How we combine specialist talent, delivery teams and project-based consultancy to fit the work in front of you.