What it is
A Statement of Work (SOW) is a contract that defines the scope, deliverables, milestones, timeline and price for a discrete piece of work, agreed and paid against the outcome rather than the hours or the headcount involved. It typically sits underneath a Master Service Agreement, referencing the MSA's liability, data-handling and payment terms rather than re-negotiating them, though a single-client engagement can run on a standalone SOW without a full MSA in place.
That is what separates a SOW from a job order. A job order requests a specific role, filled on a day rate, a time-and-materials basis or a placement fee tied to the hire. A SOW prices a defined piece of work itself, a hiring project, a market-mapping exercise, an embedded RPO engagement, with payment released against milestones and acceptance criteria rather than time worked. The same mandate can sometimes be structured either way, and which one a client chooses changes the commercial deal completely.
A SOW prices the outcome. Scope it loosely and the outcome belongs to the client, the risk stays yours.
Why it matters
A SOW shifts real risk onto the party delivering it. Commit to a fixed price against a vaguely scoped deliverable and any slippage, a widened brief, a missed milestone, a client who keeps adding requirements, comes straight out of margin. A tightly scoped SOW with clear acceptance criteria protects the agency. A loose one is a race to the bottom dressed up as a contract.
SOW-based engagements are also growing for reasons beyond convenience. In the UK, a genuinely outcome-based SOW, priced against deliverables rather than a worker's time, is one of the clearer routes to an outside-IR35 determination, which is pushing more enterprise clients to route contingent work through SOWs rather than day-rate job orders. Agencies that can scope and deliver against a SOW win bigger, stickier engagements than a desk that only ever fills one role at a time.
How boilr handles it
boilr does not draft or negotiate a SOW, that stays a conversation between the consultant, the client and legal, but it keeps the commercial reality visible before a scope gets agreed. Account status shows whether a SOW is being proposed against an account that already has an executed MSA in place, or whether that groundwork still needs doing first, and the scope, deliverables, milestones and payment triggers live in the Company Brain once a SOW is signed.
boilr also watches for the signals that tend to precede a SOW opportunity opening, a new project announcement, an RPO or MSP programme being re-tendered, a headcount expansion that looks too large for one-off job orders, and drafts a task the moment one fires on an account that fits your ICP. Milestone dates and renewal windows stay visible to the whole desk, not locked in the inbox of whoever negotiated the original scope.
