Choosing help
Consultant or in-house hire: which do you actually need?
I've been the consultant, built in-house teams, and handed work to permanent hires I helped recruit. The right answer depends on whether your need is a project or a permanent stream of work, and buyers get that call wrong in both directions.
The short answer
Bring in a consultant when the need is finite or specialist: a diagnosis, a research programme, a service redesign, an accessibility deadline, a decision your team can't settle from the inside. You get senior experience in days, pay only while the work runs, and nothing sits on the payroll afterwards.
Open a permanent role when the work is continuous and the knowledge should compound in-house: a product that needs research every sprint, a service that needs a designer embedded for years. If you can't describe twelve months of concrete work for the role, you don't need the role yet.
Independent consultant vs permanent hire, dimension by dimension
| Independent consultant | In-house hire | |
|---|---|---|
| Total cost | A fixed price per engagement, or a day rate, paid only while the work runs. No payroll, pension or overheads. | Salary is the floor: employer NI, pension, recruiter fees, equipment, training and management time all sit on top, paid every month, busy or not. |
| Time to useful work | Days. One conversation, one agreement, first findings typically inside the first week. | Months to recruit a senior specialist, then more months of onboarding before full productivity. |
| Breadth of experience | Patterns from 21 years across banking, government, healthcare and retail. Your problem is rarely new to me. | Deepens in your product and organisation over time, but starts with one CV's worth of contexts. |
| Permanence | Ends when the work ends. Continuity has to be deliberately handed over. The honest limitation. | Stays, and knowledge compounds. The whole point, if there's a permanent stream of work to compound on. |
| Cost of a wrong call | A scoped engagement that misses is a bounded cost that ends at the boundary. | A mis-hire is slow and expensive to unwind, and senior mis-hires take the longest to surface. |
| When it's right | Finite problems, specialist gaps, deadlines, and decisions that need an outside view. | Continuous workload, a team to build around, and knowledge you need to keep in the building. |
The real cost of a permanent role
A salary is the headline number, not the cost. Employer National Insurance, pension contributions, recruiter fees, equipment, licences and a share of management time all stack on top, and the meter runs whether the role is fully loaded that month or not. None of that makes hiring wrong; it makes comparing a salary to an engagement price the wrong sum.
The bigger hidden cost is time. A senior researcher, service designer or accessibility specialist takes months to find and more months to become effective. If the reason you're looking is a deadline, whether a rebuild, a procurement or a compliance date, the role will still be an open requisition when the deadline lands.
When in-house is genuinely the right call
Some work should never be outsourced for long. A product that needs research feeding every sprint, a design system serving several teams, a service under continuous redesign, that's a permanent stream of work, and knowledge of your users and your organisation compounds in a way no outsider can match. Hire for it.
The honest test is workload, not ambition. If you can describe a year of concrete work for the role, open it. If what you can actually describe is a project, however large, scope it as an engagement, and let the case for a permanent role be one of its findings.
The fractional middle ground
There's a third option many buyers don't know exists: fractional leadership. A day or two a week of senior direction: research and design strategy, mentoring the team you already have, a seat in the leadership conversations, without a full-time salary for a role that doesn't yet have full-time work.
It also pairs well with a plan to hire. I hold the senior layer while you recruit into it, help you define and assess the role, then hand over deliberately rather than leaving a gap.
The same decision, whatever the discipline
Whether the role you're weighing is a researcher, a service designer, an accessibility lead or a product strategist, the consultant-versus-hire logic runs the same way. Start where your problem lives.
Try the middle ground before committing to either
The fractional engagement gives you senior product and UX leadership by the day: strategy, mentoring, critique and hands-on research, without the payroll commitment. Everything finite is covered by a scoped, fixed-price engagement.
Still deciding?
Frequently asked questions
Isn't a consultant far more expensive than hiring?
Per day, yes. Per outcome, usually not. An engagement runs for weeks and then stops costing you anything, while a permanent role costs salary plus employment overheads every month regardless of workload. If there's a genuine year-round stream of work, the hire wins that sum. If the need is a project, a deadline or a decision, the engagement is almost always the cheaper way to buy senior judgement.
Can a consultant help us make the permanent hire?
Yes, and it's one of the more useful things I do. I can define what the role actually needs, which is often different from the first draft of the job description, sit in on interviews and portfolio reviews, and keep the work moving while you recruit. Then the handover is to a person, not a vacuum.
Doesn't the knowledge walk out the door when the engagement ends?
Only if the engagement is run badly. I work alongside your team rather than in a black box: they observe research sessions, join workshops, and see the reasoning as it forms, not just the report at the end. The deliverables (findings, maps, roadmaps, recordings) stay with you, and they're written to be acted on without me in the room.
LET'S WORK TOGETHER
Ready to improve your product?
UX, research and product leadership for teams tackling complex digital services.
Previous feedback
I had a fantastic experience working with Andy. One of his most impressive achievements during our time at NHS HEE was masterminding a deeply complex information architecture for a new platform that brought together a large number of legacy websites.
Will Parkhouse
Senior Content Designer