Capacity vs Outcome - Choosing the Right Work Delivery Channel 

Different Ways to Get Work Done 

Organisations today have many ways to get work done. Permanent employees, contingent labour and outcome-based services suppliers all play a role. However, a common challenge for organisations is choosing the work delivery channel and model best suited to their requirements. 

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. 

Capacity vs Outcome 

Contingent workforce models are built with a primary focus on managing labour capacity and capability. They enable organisations to engage individuals, such as contractors, temps or freelancers, supplied by staffing agencies to perform tasks under internal direction, typically on a time and materials basis. The organisation defines the work, manages delivery and retains accountability for the outcome. 

Services procurement models operate differently, with a focus on delivering defined outcomes. Work is delivered by a supplier under a Statement of Work (SOW) contract, with agreed scope, milestones and deliverables. In this model, risk and responsibility for delivery sit with the supplier, not the buyer. 

Labour-based models manage work around people and time, while services models are built around scope, milestones and outcomes. These different starting points lead to fundamentally different approaches to governing delivery. 

Matching Work to the Model 

The distinction between capacity and outcome directly informs how organisations should structure work. 

It is about aligning the organisational requirement to the appropriate delivery model, whether that means managing and directing individuals to execute tasks, or engaging a supplier under an SOW to deliver a defined outcome. 

Making that decision upfront is critical, as it determines how the work is scoped, governed and delivered. 

The Role of Technology 

The two technology categories reflect these underlying differences. Vendor Management Systems (VMS) are designed to manage contingent labour capacity and capability on a time and materials basis, while Services Procurement Systems (SPS) govern the full lifecycle of supplier-delivered outcomes. Each aligns to a specific work delivery channel, with its own users, supplier types, structures, governance and success measurements. 

Where workforce-oriented systems are used for services, the platform often enters the process after the SOW has been created and key procurement decisions have already been made. As a result, supplier selection, scope definition and commercial negotiation typically sit outside the system, meaning it administers delivery rather than governing the full procurement lifecycle. 

Structuring Work Effectively 

Understanding this distinction is not about one approach being better than the other, but about recognising that they are fundamentally different. Both models are essential, but they are designed for different types of work and different delivery channels. 

Choosing the right work delivery channel ensures those differences are reflected in how engagements are structured, governed and ultimately delivered.  

For organisations looking to make that decision more consistently, there are tools available to support the process, with some MSP providers offering triage capabilities to help determine the most appropriate delivery model.  

Previous
Previous

Solving Services Procurement One Step at a Time

Next
Next

Laying the Groundwork for Scalable Services Procurement