A statement of work buys an outcome instead of hours: defined deliverables, milestones and acceptance criteria, with the supplier carrying the risk of reaching them. Managing it means keeping that structure real. We do that across 11 countries, where a statement of work that is really staff augmentation in disguise stops being a procurement problem and becomes a legal one.
Of managed workforce spend now runs through statements of work, against 18% in 2017. The fastest-moving line in external spend, and the least governed.
Of it is misclassified staff augmentation, on one provider's estimate. Priced as consulting, delivered as hours.
The Belgian law a disguised statement of work runs into. English-language SOW guidance rarely mentions it.
Scope and deliverable definition
Including what is explicitly out of scope.
Milestones and acceptance criteria
Agreed before the work starts, not after.
Supplier selection for outcomes
Different criteria from selecting for hours.
Change order discipline
Where scope creep gets priced, not absorbed.
Spend visibility
Statements of work in the same view as staffing.
Structure testing
Whether it survives a labour inspection.
Milestone-based payment
Because time and materials undoes the point.
Risk that moves
The point of buying an outcome is that the supplier carries the risk of delivering it. Written loosely and paid by the hour, that risk quietly stays with you while you pay a premium for having supposedly transferred it.
Spend you can actually see
Statements of work signed inside business units land in procurement or consulting ledgers rather than in your workforce reporting. Bringing them into one view usually surprises the person who signed off the budget.
Scope that survives contact
Deliverables, milestones and acceptance criteria written before anyone starts, with a change process for what comes after. Most disputes we see are scope arguments held after the fact.
Legally sound
The structure tested against the rules that apply where the work happens, not only against your procurement policy. In Belgium and France those rules reach the client, not only the supplier, which is the part that gets missed.
Governed SOW | Unmanaged SOW | By the hour | Consulting | |
|---|---|---|---|---|
| What you buy | A defined outcome | Nominally an outcome | Capacity, honestly labelled | An outcome, plus our team |
| Delivery risk | Supplier, and it holds up | Stated as supplier, actually yours | Yours, openly | Sparagus, fully |
| Payment basis | On milestones, on acceptance | Monthly, on time spent | On hours worked | On the engagement |
| Visibility | In one workforce view | In a procurement ledger | Good, if programme-managed | One engagement, one owner |
| Fits when | Recurring project spend across suppliers | Never, and it is the most common | You direct the work day to day | You want the problem taken away |
Send us three statements of work and how those teams are actually directed.
Spend discovery
Finding the statements of work already signed, across ledgers they were never reported in.
Classification review
Which engagements are genuine outcome purchases and which are hours wearing a different contract.
Structure and templates
Scope, milestone and acceptance templates that hold, plus the change order route and the approval thresholds.
Govern and review
New statements of work screened at intake, milestones checked against acceptance rather than against invoices, and renewals treated as decisions. Reviewed quarterly, because a clean structure drifts back one small renewal at a time.
Of managed workforce spend now runs through statements of work, against 18% in 2017. The fastest-moving line in external spend, and the least governed.
Of it is misclassified staff augmentation, on one provider's estimate. Priced as consulting, delivered as hours.
The Belgian law a disguised statement of work runs into. English-language SOW guidance rarely mentions it.
Software and application
Development work bought as a project, delivered as a team sitting in yours.
Data and business intelligence
Genuinely project-shaped work, which makes it the best candidate for a real outcome contract.
Cloud, DevOps and SRE
Migrations start as projects and end as run work nobody re-contracted.
Testing and validation
Easy to define, easy to accept, and often the cleanest statement of work on the estate.
Engineering studies
Deliverables are documents, so acceptance criteria can be written properly.
Business process work
Bought by the function rather than by procurement, so it rarely reaches reporting.
Financial services
External technology work now carries its own regulatory question on top of the labour one.
Life sciences and pharma
The sector with the highest share of managed spend running through statements of work.
Energy and utilities
Site work bought as a project, then supervised by the client, which is exactly the trap.
Send us three statements of work and a description of how those teams are actually directed. You get a written view of which ones hold, which ones do not, and what it is costing you.
Driving business success with expert solutions.
