Statement of Work — SOW — seems to be cropping up more and more in recruitment conversations.
It's hardly new. Consulting, technology and professional services businesses have worked this way for years, but it's becoming increasingly relevant as customers rethink how they access skills, manage projects and buy external expertise.
At its simplest, an SOW sets out what needs to be delivered rather than simply who needs to be hired.
Typically, there's a defined piece of work, agreed scope, deliverables, milestones and an understanding of what success looks like. The supplier isn't simply providing people; it's taking responsibility for getting something done.
And that's where it gets interesting for recruitment.
From people to problems
Recruitment has traditionally worked around a simple proposition: you need somebody, we'll find them.
SOW starts somewhere else:
What are you actually trying to achieve?
A customer might say they need four software contractors when what they actually need is a platform migrated by December. They might ask for three data specialists when the real requirement is a new reporting infrastructure.
It's a subtle but important shift.
Instead of saying “we'll find the people who can do it,” the proposition becomes “we'll get it done.”
That requires much more from the recruitment business. You need to understand the problem, scope the work, assemble the capability, manage delivery and be accountable for the result.
Suddenly, you're getting much closer to consultancy and professional services than traditional recruitment.
And then there's IR35
SOW has inevitably become tangled up with IR35, but it isn't an IR35 magic trick.
Calling something a Statement of Work doesn't automatically turn labour supply into an outsourced service. HMRC looks at the reality of the arrangement: who is responsible for the work, how it's delivered and whether the supplier is genuinely providing a contracted-out service.
If you're effectively supplying four contractors who are managed by the customer and billing for their time, putting SOW on the paperwork doesn't necessarily change what you're doing.
Done properly, this is a genuinely different commercial model.
Where could this go?
This is the bit I find particularly interesting.
The recruitment company of the future may not define itself simply by permanent or contract recruitment. It might place someone permanently one day, provide an embedded team the next, run an RPO somewhere else and take responsibility for delivering an entire project for another customer.
Perhaps we're moving from selling talent to selling capability.
And AI could accelerate that. If finding and matching people becomes easier, simply having access to candidates becomes less valuable as a differentiator. Understanding the customer's problem, knowing how to assemble the right expertise and being prepared to stand behind the outcome become more valuable.
Recruitment businesses are potentially well placed for that. They understand talent, have deep networks and, at their best, possess enormous knowledge of the markets they serve.
But there's a big step between finding people who can solve a customer's problem...
and becoming the business responsible for solving it.
That, for me, is where SOW starts to get really interesting.
