Scope of work sales

Scope of work sales is the part of a deal where buyer and seller agree exactly what will be delivered, for how much and by when, while the price is still open. It happens before anyone signs, and it is where delivery risk begins.

The signed document is a different thing. A statement of work (SOW) locks scope, deliverables, timeline and acceptance once both sides commit. Scope of work sales is the negotiation that produces that text.

One is pre-signature, the other is the signature — confusing the two is how teams end up arguing in month three about work nobody priced.

Key takeaways

• Scope of work sales happens while the deal is open; the signed SOW closes it.
• Describe required results, not the hours or the method used to reach them.
• Price and scope move together, so never fix one before the other is written.
• Put exclusions in writing, because an unwritten exclusion is read as an inclusion.

How it works

Scoping a live deal runs in five moves: capture the requirement, draft the deliverables, test them against a price shape, agree exclusions and acceptance, then convert the agreed text into a signed document.

Capture comes first and is usually rushed. The requirement a buyer writes down is rarely the requirement they actually have, so good scoping calls spend longer on the outcome being bought than on the shopping list.

Requirements usually arrive as a document rather than a conversation. A request for proposal template sets the questions, and the quality of your scope is capped by the quality of those questions.

Public buyers have had the cleanest rules on this for decades. Under the Federal Acquisition Regulation, requirements should be stated as functions, performance or essential physical characteristics rather than as a design dictated up front.

The performance rule is sharper still. Federal performance work statements must describe work by required results rather than hours provided, and must let performance be assessed against measurable standards.

Price shape is a scoping decision, not a finance one — choosing milestone based pricing forces the deliverables into discrete, checkable chunks before anyone signs.

The alternative pushes risk the other way. A fixed price contract outsourcing arrangement puts estimating risk on the provider, which only works when the scope text is specific enough to defend.

All of this is traded, not declared. Your contract negotiation strategy decides which clauses you concede and which you hold, and scope is usually the one worth holding to the end.

Write acceptance criteria as testable statements. “Ninety-five percent of tickets routed within thirty seconds, measured monthly” survives a dispute. “High quality routing” does not.

Scope and price get argued together or not at all. A buyer shown the price before the exclusions anchors on the number, then reads every exclusion as a late deduction from a deal they thought was closed.

Examples

Scoping looks different depending on whether the work is a build, a service or a public tender. Four shapes cover most commercial situations, and each one fixes a different variable first.

A software build is scoped by feature list and milestone. Both sides agree a numbered deliverable set, then attach payment to each accepted item rather than to elapsed time. Later change requests are priced against that same list.

An offshore support ramp is scoped by volume and standard. Seats, hours of coverage, languages and response targets are written down before pricing, because every one of them moves the headcount number. Shrink any one of them later and the price moves too.

A government services tender is scoped by outcome. The buyer publishes objectives and constraints, and bidders propose the performance work statement that will deliver against them. The scope arrives from the seller’s side, which is unusual.

A content pipeline is scoped by throughput and revision count. Two rounds of edits per piece is a scope line — unlimited revisions is a billing dispute waiting to happen.

Related terms

• statement of work (SOW): the signed document the sales scoping conversation is trying to produce.
• statement of work outsourcing: how that document is written when delivery sits with an external provider.
• contract negotiation strategy: the wider plan for trading clauses, of which scope is one.
• milestone based pricing: ties payment to accepted deliverables rather than to elapsed time.
• annual contract value: the yearly figure the agreed scope and price produce for the seller.

FAQ

What is scope of work sales?

It is the pre-signature work of agreeing exactly what will be delivered, for how much and by when. That agreed text later becomes the signed statement of work. Nothing in it binds either side until signature.

How is a scope of work different from a SOW?

The scope of work is what both sides agree the work is while the deal is still open. The SOW is the signed contract that locks it in place. The wording in both can be identical; the legal status is not.

Who should write the scope?

Whoever will deliver it, reviewed by whoever sold it. A scope written only by sales usually underprices the work — one written only by delivery usually loses the deal.

What belongs in the exclusions section?

Anything a reasonable buyer might assume is included and is not: data migration, training, out of hours cover, extra revision rounds. If a buyer would be surprised to be billed for it, write it down.

How do you stop scope creep before signature?

Write a change route into the scope itself, so later additions have a priced path instead of an argument.

Shortlist vetted providers in the Outsource Accelerator directory before you scope your first deal with one.