Expected reading time: 10 minutes
In our previous article on the vendor selection RFP, we showed how structure protects value before a vendor relationship begins. Once you award the contract, the expectations you set in the RFP need somewhere to live. For most IT services, that place is the Statement of Work (SOW), where commercial promises become delivery commitments. Yet many organizations still sign SOWs that buy days rather than results. This article explains why an outcome-based SOW gives you more control and why this deserves the same attention as the RFP received.
Staff Augmentation Keeps Us in Control
Staff augmentation feels safe on two fronts. First, organizations believe they control what contractors do: the days worked, the tasks picked up and the pace of delivery. Second, they believe they control what those days cost, because both sides agree the day rate upfront. Moreover, prices compare easily, finance approves budgets quickly, and a team can scale up in a week instead of negotiating scope for a month. On a spreadsheet, the arrangement therefore looks like control on both fronts.
Reality: You Bought Days. Nobody Bought the Result.
In our experience, most organizations control neither. A day rate fixes the price of a single day. However, it says nothing about how many days the work will take, or whether the right work fills them. In other words, a day rate prices capacity and cost. Neither tells you what those days actually produce.
Under this model, the organization buys capacity and keeps the responsibility for turning time into results. The vendor delivers the days as contracted. Whether those days add up to a working solution becomes an internal question, answered through steering meetings, status calls and extension requests. A rate card is a pricing instrument, not a governance mechanism. It governs nothing until someone owns the result.
Why the Rate Card Keeps Winning
Urgency plays a part. When a project needs skills next month, the fastest route to a signature is a rate card and a short order form. Whoever has time drafts the SOW, often by copying the last one. Often , procurement joins late, after the team has already chosen its preferred consultants. Incentives add to the pull. Project teams earn recognition for launching and delivering, and rarely for contract quality. Budgets fund capacity in units everyone recognizes: people and days.
The deeper reason sits in the effort involved. Defining an outcome forces a team to say what “done” looks like, who accepts it and which dependencies belong to the client. A day rate lets an organization postpone that conversation. Yet the conversation never disappears. Instead, it moves into the project, where changing scope has less leverage and often more cost.
The incentive works both ways. Under time and materials (T&M), vendors have no obligation to commit to deliverables, and a timesheet is all they need to justify. As a result, that absence of commitment on the vendor’s side removes any pressure on the organizations to define an outcome up front, so both parties settle into the same comfortable ambiguity.
The Total Nobody Approved
The cost of that ambiguity rarely arrives as one decision. Instead, it accumulates through many small ones: a two-week extension here, an extra consultant there, a change request for an interface nobody mentioned at kickoff. It also shows up at team scale. For example, a pilot that starts with two contractors can become a full delivery team within a quarter. The team adds one role at a time, and each addition looks reasonable on its own.
Consider an illustrative twelve-month engagement. The original SOW covers €400,000 of work. Over the year, the team approves six extensions and nine change requests, each worth between €15,000 and €60,000. Every invoice matches an approval. Yet the total reaches roughly €720,000, about 80% above the figure anyone agreed to at the start. Meanwhile, the engagement now rests on specific people and open end dates instead of a deliverable with an end.
Each approval was visible on its own. The running total was not. Nobody decides to overrun the budget. The budget gets spent, one sensible approval at a time. Behind it all sits one shared gap. The vendor delivers the agreed days, the organization needs a working solution, and the contract never connects the two.
What Mature Buyers Ask Before Signing
Mature buyers start with one question: are we buying capacity or a result? Capacity, such as backfilling a role under internal management, suits a day rate well. By contrast, anything with an end state, such as a migration, an implementation or an integration, suits an outcome-based SOW. That SOW names the business outcome, breaks it into deliverables, attaches acceptance criteria to each and ties payment to milestones. Analysts see the same shift: Gartner’s 2026 research on outcome-based pricing notes that SPVM leaders are under growing pressure to tie IT services contracts to business outcomes.
The rate card still has a role. It becomes the pricing reference for changes, so every commercial discussion starts from a number agreed upfront. In short, the rate card supports the commercial model rather than becoming it. The effect shows quickly. Vendors know what done means, because a good outcome-based SOW only exists after a genuine joint analysis of the work. Organizations know what they will receive. As a result, conversations move from hours worked to progress achieved.
Still, an outcome-based SOW does not fit every engagement. When scope is genuinely unknown, as in discovery work or early product exploration, a fixed outcome pushes the vendor to price in a large risk premium. In those cases, mature buyers run a short time-and-materials discovery phase first. They then turn its findings into an outcome-based SOW for delivery.
Three Steps Toward an Outcome-Based SOW
Moving from days to outcomes does not require a new procurement function. Instead, three governance actions close most of the gap:
- Classify before you contract. Decide whether each engagement buys capacity or a result, and choose the commercial model to match.
- Track the running total. Monitor the combined value of extensions and change requests against the original SOW. Then set a threshold, for example 15%, that triggers a fresh approval of the whole engagement.
- Make acceptance a defined event. For each deliverable, state the acceptance criteria, the reviewer, the review window and the evidence required.
Finally, release payment on acceptance rather than on elapsed time.
The Leadout Perspective : Turning Days into Results
At Leadout, we see the outcome-based SOW as the bridge between what the RFP promised and what the vendor delivers. Within Sourcing, Procurement and Vendor Management (SPVM), we help organizations standardize how they write, accept and report on SOWs. In practice, that starts with one template built on eight sections: business outcome, deliverables, acceptance criteria, assumptions, client dependencies, milestones and payment, change control, and exit. Because every section links back to the result, a consistent structure exposes gaps at first read. Acceptance then becomes a defined event.
Leadout helps organizations review each deliverable within an agreed window against stated evidence, and payment follows acceptance. This is not a standalone step. The same discipline that shapes the SOW out of the RFP carries the vendor’s accountability through delivery, so the obligation to deliver results runs back-to-back from the RFP through to final payment.
Why put outcomes at the center? Because an outcome gives both sides the same finish line. The organization knows what it will receive and when. The vendor knows what done looks like and can shape its team and approach around it.
Reaching that finish line, however, takes joint work upfront. The organization brings the business need, the vendor brings delivery expertise, and together they agree on done before a day of work starts.
That conversation costs time. Yet it pays back twice: first in a shared understanding that carries the engagement through change, and then in delivery that reflects what the business actually needed.
Our values shape the approach the same way. Integrity keeps assumptions visible. Pragmatism keeps day rates where capacity is the goal.
A holistic view connects each stage from sourcing and contracting through delivery and vendor management so commercial intent does not get lost once the contract is signed.
Key Takeaways
- Ask first: are you buying capacity or a result?
- A day rate prices the input. An outcome-based SOW ties commercial accountability to results.
- Accumulated individual demands and change requests add up, so track their combined value against the original SOW.
- Keep the rate card as a reference for capacity and controlled changes, not as a substitute for defining the outcome.
- Time invested in defining the outcome pays back in the quality of what gets delivered. Defining outcomes takes real effort, and that effort is not wasted time.
The goal is not to stop buying days. It is to start expecting outcome delivery.
Curious how this applies to your organization? Let’s talk. Schedule a call with us.
Nick@leadoutsolutions.com Kris@leadoutsolutions.com
Share this message: