45% of UK SMEs plan to grow headcount this year, and more than a quarter expect to cut it because of AI. Both numbers are answers to the same underlying question: does a hire add capability the business doesn't have, or does it just move work off someone's desk? Only one of those compounds. The other gets automated, deprioritised or cut the moment budgets tighten, because it was never building anything in the first place.
The tell is in how you'd describe the role
If a hire is described as a list of tasks, invoices processed, inboxes cleared, diaries managed, it's competing with a tool, a process fix or an AI feature, and over time it loses that fight. If it's described as an outcome someone owns, a pipeline that gets built, a function that runs without daily check-ins, a market that gets covered without you carrying it, it's not competing with software. It's building capability the business didn't have before. That distinction is what separates a freelancer picking up tasks from a fully embedded team member owning a result.
Why this matters more when budgets are tight
When cost pressure hits, task-based hires get cut first, because the tasks either stop mattering or get absorbed elsewhere. 43% of employers dealing with a skills shortage have already hired fewer staff over the past year, and task-based roles are the first to go in that squeeze. Outcome-owning hires are harder to cut, because removing them removes a function, not a convenience. That's the real argument for building around a team-building framework from the start rather than a task list: it decides which hires survive the next tight quarter before you've even made them.
What to check before your next hire
Can you describe this role's success without listing tasks?
If AI or a tool got better tomorrow, would this role still matter?
Is this hire meant to free up your time, or meant to grow something the business doesn't currently have the capacity to grow?
A hire that only buys back an afternoon a week is a nice-to-have. A hire that owns something the business needs to grow is capacity. Know which one you're making before you write the job spec, because that's where this decision actually gets made, not in the interview.
FAQ
What's the difference between hiring for tasks and hiring for growth?
A task-based hire is defined by a list of things done for you. A growth hire is defined by an outcome they own, something that gets built, run or covered, regardless of how it gets done.
Why are task-based roles more exposed to AI and automation?
Because the value of the role is the task itself, and tasks are exactly what automation targets first. Over a quarter of UK SMEs already expect AI to reduce headcount this year.
Does this mean support roles aren't worth hiring for?
No, support functions can absolutely be outcome-owning roles. The difference is whether the person owns a result, a function that runs, a process that improves, rather than just clearing a queue.
How do I know if I'm hiring reactively instead of strategically?
If the role only exists because something's currently overflowing, and the job spec is a list of what needs doing right now, that's a reactive hire. A strategic hire is defined by what the business needs to be able to do in a year.
Is it wrong to want a hire that frees up my time?
Not at all, but it shouldn't be the whole justification. The hires that hold up under pressure are the ones freeing up time by building something, not just clearing a backlog.
Sources
• The Access Group / Open University Business Barometer 2026
The No Compromise Newsletter
Straight-talking hiring insight, once a month.
