- Before
- Could not read each SOW against the MSA, the rate card and the playbook, so read the first page and hoped.
- Now
- Opens each SOW with the agents' notes beside each clause and a fix ready for each; asks and instructs them in plain words, and decides each change with a reason code.
A $480,000 transformation SOW through review, from supplier draft to signed PO
A consultancy sends the company a $480,000 fixed-fee SOW for digital transformation support in the Distribution division, against the budget owner's request and a $500,000 budget line. Here is how a services procurement buyer works it through with the agents, screen by screen, in the working solution.
A worked example on sample data. Names, IDs and figures on the screens and in this section come from the demo.
- 01Thursday morning
The agents have already said what needs the buyer
Services procurement buyerThe buyer's Today screen: 12 SOWs in review worth $5.32M, 4 waiting for the buyer, 7 high-severity notes open, each with a proposed fix, and $708,900 protected this quarter. Beside the list, the agents talk to the buyer. The routing agent has ranked the morning; overnight, the checker agent re-checked a change order from a design studio and found 8 of its 20 assets already in the signed scope.
Routing agent: “Morning. 4 SOWs wait for you; the first is due today. The consultancy's is the biggest: 3 high notes on $480,000.”
- 02The biggest SOW first
The SOW as a document, with the agents' notes in the margin
Services procurement buyerThe SOW opens as the supplier wrote it, clause by clause. Next to each problem clause sits a note: scope too vague, key people not named, rate above the rate card. The top bar shows $480,000 against a $500,000 budget, fixed fee with 40% on signature, 16 weeks, and 46 checks run: 37 passed, 3 high, 4 medium, 2 low open. The intake agent has already linked the master services agreement, its rate card Exhibit C and the budget owner's request.
Checker agent: “I re-computed all 9 findings from the sources without seeing the other agents' working: 9 of 9 agree.”
- 03§2.1 Scope
One sentence of scope becomes three deliverables from the brief
Scope agentThe only deliverable is to “support the digital transformation” of the division. It fails all five parts of the deliverable test: a measurable output, an owner, a date, an acceptance test, what is out of scope. The scope agent rewrites it from the budget owner's own request: D1 a current-state assessment of the six distribution centers by week 4, D2 a roadmap of at least 12 prioritized initiatives with business cases by week 9, D3 a slotting pilot at one distribution center measured against the D1 baseline by week 16.
In the company's own signed SOWs, a deliverable like this had change orders on 61% against 18%, a change-order risk of about $67,000. The scope agent does not invent scope the request does not support.
- 04§4.1 Rates
A Principal at $295 an hour; the card says $260
Rate agentThe rate agent re-adds the price build-up and matches each role to the rate card. The Principal is billed at $295 an hour; Exhibit C, row 3, caps the role at $260, and clause C.4 says no SOW may exceed the card without written agreement. 320 hours × $35 = $11,200 over. One click on the source opens the rate card with the passage the agent relied on highlighted.
“The highlighted passage is what the agents relied on. Opened from the record; it cannot be edited here.”
- 05The buyer asks
“Why is 40% upfront a problem?”
Buyer and payment agentThe buyer asks in plain words. The payment agent answers with its sources: $192,000 would leave on signature, before anything is delivered; the playbook allows 10% mobilization and the rest on written acceptance, and calls anything above 20% a walk-away. It opens the note on §5.2: a new schedule of 10%, 25%, 30% and 35% tied to D1 to D3, adding up to $468,800, with each step of how it checked, a confidence of 98% and the checker's agreement.
$145,120 of cash moved behind delivery. The payment agent does not move a payment the budget owner has not seen.
- 06The buyer instructs
“Make the pilot 6 weeks”
Buyer and scope agentThe buyer tells the agents what to change. The scope agent redrafts D3 as a 6-week pilot at the distribution center, measured on the last 4 weeks of warehouse data and still finishing by week 16, and marks it as a proposal on §2.1. Nothing in the SOW changes until the buyer accepts it.
Scope agent: “Done, as a proposal: D3 is now a 6-week pilot … Nothing changes in the SOW until you accept it on §2.1.”
- 07Nine decisions
Seven accepted, and the two legal notes sent to counsel
Services procurement buyerEach note is accept, edit or reject with a reason code: “Matches our playbook”, “Matches the rate card”, “Rate exception requested”. The buyer accepts scope, rate, payments, the expense cap of $37,504 (8% of fees under the travel policy), a 10-business-day acceptance window, named key people and 30 days' notice. The IP clause and the missing data-protection terms go to counsel: legal wording is counsel's decision. The SOW now shows each change tracked, and its value falls to $468,800.
Legal notes are never accepted in bulk: they go to counsel.
- 08The supplier replies
Eight accepted, one counter on IP, inside the fallback
Terms agentThe buyer sends the redlines with a cover note the routing agent drafted. The consultancy's partner accepts eight changes but wants to keep the firm's own diagnostic toolkit. The terms agent reads the counter clause by clause and maps it to the playbook's IP positions: the company owns the deliverables, the supplier keeps its background IP with a perpetual, royalty-free license. That is the fallback position, so it is acceptable, with counsel's approval.
Terms agent: “No walk-away position is touched.” Approving legal wording stays with counsel.
- 09One page, then the signature
Counsel approves the wording; the budget owner signs
Counsel and budget ownerThe routing agent builds one page for approvers (what we get, when, what we pay, what changed from the supplier's first version and why) and routes it by the delegation of authority: $468,800 sits in the $100,000 to $500,000 band, so counsel approves the legal wording first and the budget owner approves on the buyer's recommendation. Counsel approves with a reason code. The budget owner chooses the reason code “Within the budget line; deliverables measurable”, types a name and signs. The routing agent sends the SOW to the supplier for e-signature and creates the purchase order.
The agents read, check, propose and route. Each acceptance, approval and signature is a person's, with a reason code.
- 10After signature
The signed scope keeps working
Scope agent and routing agentChange orders are tested against what was already bought: the design studio's change order asks $18,600 for 20 social assets, but 8 of them are the carousel cards already in §2.3 of its signed SOW. The agents propose $11,160 for the 12 new ones, and because the SOW would grow more than 25%, the budget owner and the category manager approve again. On Delivery, another supplier's $64,500 invoice is held: milestone 2 has no recorded acceptance.
The routing agent releases no invoice without a recorded acceptance.