Statement of Work Staffing That Says Who Pays the Overrun
Project teams under a SOW with a real acceptance test, pricing picked on purpose, and IP that transfers.
Statement of work staffing means a staffing firm delivers a defined result instead of billing hours you direct. The SOW sets scope, the acceptance test, pricing, who owns the work and who pays when the job runs long.
Last updated: September 30, 2026
- This page
- How a SOW engagement gets written. Scope, acceptance, five pricing structures and who carries the overrun under each one, and the IP clauses a SOW needs.
- Covered elsewhere
- How the team itself gets assembled and managed is on our project staffing page. Gainshare contracts get a full treatment in outcome-based delivery, and the copyright law behind IP transfer is in who owns contractor work.
SOWs tend to show up in one of two shapes. Forty pages of boilerplate with the actual deliverable buried on page 31. Or a single page that says “development services, as directed,” which isn’t a statement of work at all. It’s a timesheet with a signature block.
Statement of work staffing sits between buying hours and hiring a consultancy. KORE1 recruits the people, and the SOW makes us answerable for a result instead of a headcount, which changes what has to be written down before anyone starts and who takes the loss when the estimate turns out wrong. Rather point the work yourself? Then our contract staffing model is the simpler purchase.
What a Statement of Work Staffing Contract Pins Down
Seven things. Leave one out and you’ve scheduled an argument. You just don’t know the date yet.
- Scope, and what’s outside itThe exclusions list does more work than the scope paragraph. “Integrate with the ERP” invites a fight. “Integrate NetSuite sales orders, not purchase orders or returns” doesn’t.
- DeliverablesThings someone can hold up and inspect. A deployed service, a migrated dataset with a row count, a runbook. Never “support.” Nobody can inspect support.
- AcceptanceWho tests, against what, and how long they get. It decides when money moves, so it has its own section below.
- Change controlA written path for pricing a new request before anyone builds it. Skip it. Scope grows anyway, one hallway conversation at a time, and six months later nobody can point to the week the job doubled, who agreed to it, or what it was supposed to cost.
- Pricing and the payment triggerOne of the five structures compared below. Then the trigger, which matters just as much. Does money move on a calendar date, on hours logged, or on an accepted deliverable?
- Named peopleNames, not roles. Who’s on the job, how much notice you get before anyone rotates off, and your right to interview and approve a replacement before they touch your code or your data.
- Who runs the dayWho decides what gets worked on each morning? If it’s your manager and there’s nothing to accept at the end, you’ve bought staff augmentation with a SOW cover sheet, and our contingent program governance checklist explains why procurement cares about the label. Suspect some of your current SOWs already look like that? You can audit the SOW spend you already have.
Where the Overrun Lands Under Five Pricing Structures
Same work on every row. A scope of 1,000 hours at an illustrative $150 blended rate, or $150,000. Then it runs 20% long. Or it comes in 10% short.
You payVendor absorbsPriced in, paid either wayPaid only if the metric is met
Time and materialsEvery hour billed at the rate.
If it runs 20% overYou pay $180,000
If it comes in 10% underYou pay $135,000
T&M with a not-to-exceedHourly, capped at $165,000.
If it runs 20% overYou pay $165,000. Vendor absorbs $15,000, unless a change order lifts the cap.
If it comes in 10% underYou pay $135,000
Fixed feeOne price, $165,000, set before work starts.
If it runs 20% overYou pay $165,000. Vendor absorbs $15,000.
If it comes in 10% underYou pay $165,000, including $30,000 of reserve the work never used.
MilestoneThe same $165,000, released in four $41,250 payments as each deliverable passes acceptance.
If it runs 20% overYou pay $165,000. Vendor absorbs $15,000.
If it comes in 10% underYou pay $165,000, and no payment moves before its acceptance test.
Fee at riskA $132,000 fixed base plus $33,000 paid only if the agreed metric is met.
If it runs 20% overYou pay $132,000 to $165,000. Vendor absorbs $15,000.
If it comes in 10% underYou pay $132,000 to $165,000, depending on the metric.
Time and materials swings $45,000 between the two outcomes. The fixed rows don’t move. That’s the whole trade.
FAR 16.202-1 · fixed price
“This contract type places upon the contractor maximum risk and full responsibility for all costs and resulting profit or loss.”
FAR 16.601 · time and materials
Allowed only when the extent or duration of the work can’t be estimated with confidence, and only with “a ceiling price that the contractor exceeds at its own risk.”
Commercial buyers aren’t bound by the federal rules. The logic travels anyway. What you’re really choosing is how well you can describe the finish line today.
Can you write the acceptance test now? Then a fixed fee or milestones usually win, and you’re paying a known reserve to push the overrun onto us, which is a perfectly reasonable thing to buy when the scope is solid and a late invoice would hurt more than a slightly higher one. Can’t write it yet? Pay for hours, cap them, and refuse a fixed-fee reserve on scope nobody can see, because with a loose scope that reserve climbs toward the 30 percent our outcome-based delivery piece describes.
Acceptance Criteria Decide When You Pay
Four of those five rows turn on one question. Did the deliverable pass? Write the test first. Then the price.
- A criterion somebody else could check. “Checkout loads in under two seconds on the 50 busiest product pages” can be tested. “Performs well” can’t.
- A review window, often five or ten business days, and what happens when it closes with no answer. Silence has to mean something.
- What a rejection has to cite. Tie it to a numbered criterion or it’s really a change request, and it goes through change control like any other.
- How many retest rounds the price covers. One is typical. Beyond that, talk.
Government buyers call the result-first version a performance work statement. FAR 37.602 tells agencies to describe the work “in terms of the required results rather than either ‘how’ the work is to be accomplished or the number of hours.” Same advice here. Describe the result and let the team own the how.
IP Assignment Under a SOW Is Three Clauses, Not One
More hands touch the code on a staffing SOW than on an employee’s work, and ownership has to pass through every one of them.
- Foreground IP
- Everything made for you under the SOW. It should transfer as it’s created. Not on final payment, because then a billing dispute turns into an ownership dispute.
- Background IP
- The vendor’s existing tools and libraries. You won’t own those, so the SOW should list them and grant a permanent license to whatever ends up inside your deliverable.
- Flow-down
- Anybody the vendor brings in, subcontractors included, signs the same assignment. Otherwise the chain stops one hop short of you. Every hop needs paper.
The copyright law underneath is its own subject, including why a “work made for hire” line on its own doesn’t cover software (the Copyright Office’s Circular 30 lists the nine categories that qualify, and code isn’t one), and our guide to who owns the work a contractor writes walks through it. Engineering work adds patents and inventions to the list, which our page on IP agreements for contract engineers covers.
One more item for the closeout list. Name every open-source package shipped in the deliverable, with its license, using the identifiers on the SPDX license list. An afternoon at closeout. Much longer in the middle of an acquisition.
92%
twelve-month retention across KORE1 hires
17 days
from open req to a KORE1 IT hire, on average
2005
KORE1 opens its Irvine doors
30+
U.S. metros KORE1 recruiters cover
Figures from Why KORE1.
Pick the Engagement Before the Pricing
A SOW is paperwork wrapped around an engagement. Choose the engagement first. Pricing mostly follows. A standing team billed by the month is a different purchase again, closer to a managed capacity model.
You direct
Contract seats by the hour
Individual contractors on our W-2, taking daily direction from your team and billed for time worked.
Contract staffingWe deliver
A scoped project team
A team KORE1 assembles with its own lead, working to milestones and the acceptance test in the SOW.
Project staffingTech builds
IT projects with an end date
Software, data and network projects planned back from go-live, each seat staffed to its roll-off day.
IT project staffingPaid on results
Part of the fee on a metric
Some of the fee rides on a number you already track, for steady workstreams with a measured baseline.
Outcome-based delivery
Common Questions
Is a statement of work just staff augmentation with more paperwork?
Sometimes, and that’s the problem. A real SOW has a deliverable someone can accept or reject, and the vendor directs the work toward it, choosing the approach, the order of the work and which person on its team handles which piece. If your manager assigns tasks every day and the bill is hourly with nothing to accept, it’s staff augmentation and should be managed like it.
Which costs less, a fixed fee or time and materials?
Time and materials, when the work lands on or under the estimate. A fixed fee carries a reserve for overrun risk, and you pay it whether the overrun shows up or not. In our illustrative model that’s $165,000 fixed against $135,000 to $180,000 hourly. Neither one is wrong.
Who owns the code a SOW vendor writes for us?
You do, if the SOW assigns it. New work should transfer as it’s created, the vendor’s existing tools should come with a permanent license, and every subcontractor should sign the same terms. Leave those out and ownership can stay with whoever wrote it. Check before signing.
What happens when we change our minds halfway through?
That’s normal. The change control clause should price each new request as a written change order, with its cost and schedule impact, before anyone builds it. No surprises. Nobody finds out at invoice time that the job doubled.
How quickly can a SOW team start?
About 17 days for most IT seats, going by our average time-to-hire, and recruiting can run while the contract is still in review. The slower part is usually agreeing on the acceptance test and the pricing, because those are the two clauses where legal, procurement and the project owner all want a say. Start those drafts first.
Could a SOW team member join us permanently?
Yes, as long as the SOW says how. Write the conversion terms in at signing, meaning the fee, when it applies and any waiting period. Otherwise a good hire turns into a negotiation at the worst possible moment. Write it down early.
Does putting fee at risk work on a brand-new project?
Rarely. Tying fee to a result needs a baseline, and a new build hasn’t got one yet. It fits steady work like application support or regression testing, where the metric already exists and both sides know what a normal month looks like.
Send the Scope You Have, Even a Rough One
A paragraph and a target date are enough. Really. Someone on our recruiting team calls back with a team shape, a suggested pricing structure and the acceptance questions we’d want answered first.
Scope a Statement of Work →Or call 949-706-6990
