These were public bodies with established processes and resources, yet both still faced significant liabilities. For private organisations, the lesson goes beyond IR35. Third-party services are commissioned across multiple functions, suppliers and systems, while the decisions behind them can be spread across the business. When something goes wrong, having a process is not enough. You need to be able to show what was bought, why it was approved, how it was managed and what has changed since. 

By the time an outsourced services overrun becomes visible, the opportunity to prevent it has often already passed. 

Large supplier-delivered services engagements rarely exceed their budget because of a single decision. They drift over time as scope evolves, requirements change and delivery adapts. Individually, those changes often appear reasonable, but collectively, they can fundamentally alter the commercial profile of an engagement. By the time the full impact becomes apparent, the budget has already shifted, and the forecast has become increasingly difficult to recover. 

Most organisations can report, with a high degree of accuracy, what they spent on outsourced services last year. Far fewer can demonstrate, with the same confidence, what that investment actually delivered. 

It's a question that sounds deceptively simple: 

“For everything we spent on third-party services like consultancy, IT, engineering and business transformation, what did we actually get in return?” 

An outsourced supplier engagement comes to an end, the final invoice is paid, and the project is signed off. Yet months later, members of the supplier's delivery team may still have access to business systems, sensitive information or company facilities because that access was never formally removed. In many organisations, no one can say with confidence exactly how often this happens or how many former supplier personnel still retain access they no longer need. 

Ask most businesses how many individual contractors they have working for them right now, and they can usually get an answer in minutes. Ask what the business is getting in return for the millions it spends on third-party services, whether projects are on track and whether they are delivering the outcomes they were paid to achieve, and the answer is often far less certain. That gap is where services spend can become a black hole, where organisations know what they are spending but struggle to see whether that investment is translating into business outcomes.  

When an organisation buys goods, suppliers can generally be compared on specification, quality and price. Contingent labour follows a similar principle, where value is closely linked to the rate paid for an individual's time and materials. Services procurement operates differently. Two suppliers may submit proposals at almost identical prices yet deliver very different outcomes. The price captured within the Statement of Work (SOW) and ultimately reflected in the purchase order (PO), says little about the value the organisation will achieve. 

One of the biggest levers leaders have on cost, risk and speed is also one of the least understood at board level. 

Every executive team is judged on the same handful of things: protecting margin, controlling risk, and moving fast enough to stay ahead. One of the largest levers on all three sits in a part of the business that rarely reaches the boardroom is how an organisation buys, governs and manages the services it depends on. 

Many organisations view services procurement as an extension of contingent workforce management. It's an understandable assumption as both involve engaging external suppliers, bringing in specialist expertise, and managing non-employee spend, so it feels natural to reach for the same systems and the same playbook for each. 

However, while the two disciplines may appear similar on the surface, they are solving fundamentally different problems for different work delivery channels. Treating one as a version of the other is where many processes run into difficulty. 

A Statement of Work (SOW) is often misunderstood as simply a contract document used to engage external services. In reality, an SOW is the contractual framework through which services procurement engagements are defined, managed and measured typically sitting beneath a Master Services Agreement (MSA) that governs the broader commercial relationship.  

Services procurement and contingent workforce management are often discussed together because both involve external resources. However, they operate under fundamentally different models, with different stakeholders, governance structures, and objectives.

In services procurement, organisations are not buying capacity in the same way they do in contingent workforce programmes. They are buying outcomes, defined pieces of work delivered by external suppliers. That shift changes how risk is introduced, distributed, and managed. 

In many organisations, services procurement doesn’t begin with a process, it begins with a need. 

A team identifies a problem, starts shaping a solution, and often has an idea of which suppliers to engage. By the time a Statement of Work (SOW) contract is created, key decisions like scope, delivery approach, and supplier choice, have often already been made. 

Both stages contribute to value, but in different ways. Upstream determines what is being delivered, while downstream determines how that service delivery unfolds. If either is missing, the link between definition and delivery becomes less clear. 

Whilst contingent workforce and services procurement may appear similar both involving external parties and sitting within the broader external spend ecosystem, they solve fundamentally different problems for different work delivery channels. 

Services procurement and contingent workforce management are both central to how organisations engage external resources but, they govern fundamentally different types of work channels. 

Most organisations don’t realise they have a services procurement problem until costs escalate, projects overrun, or leadership asks for data that simply isn’t available. Because services are intangible and delivered via outcomes, gaps in governance don’t always surface immediately. They show up gradually through inconsistent scoping, limited performance visibility, misclassification, fragmented approvals, or spend that’s difficult to consolidate or justify against value.

Services are one of the fastest growing areas of organisational spend, yet the basic language around how they are bought and managed is often misunderstood. One of the most common points of confusion is the difference between services procurement and a Statement of Work (SOW). They’re closely related, but they aren’t the same, and treating them as interchangeable can create misunderstanding, unnecessary risk and lost value.

Across most organisations, procurement has undergone major digital transformation. Systems for managing physical goods are streamlined and digitised. Workforce solutions that manage people and time are advanced, data-driven and globally scalable.

But the same progress hasn’t been made for services procurement.

When people across organisations think about procurement, their attention tends to focus on goods, which are tangible items with clear prices, definitions, metrics, and delivery dates. But there’s another class of spend flying under the radar that’s just as big but much less visible, with billions spent every year, which is services procurement. 

Services procurement has been one of the biggest, misunderstood areas of organisational spend. It accounts for almost half of global organisational expenditure, yet for years has sat in a grey area, vital to business outcomes, but lacking ownership, structure, and visibility.