For requisitions and renewals under a value threshold, the agent would build the request from the last award, invite qualified suppliers, normalise the bids to landed cost and negotiate inside a playbook the category manager owns.
Wednesday 23 September 2026, 10:20. A requisition for 400 moulded housings for plant 1210, valued at $18,400, lands in the queue. Juno classifies it as tail spend under the $25,000 policy, finds the last award and builds the request from it, and invites Corvid Plastics and two qualified alternates through the supplier portal.
By Friday three bids are in, normalised to landed cost with freight and payment terms. Juno negotiates inside the playbook band and drafts an award to Corvid Plastics at 4.1% under the last price, with the reason and the two rejected bids beside it. D. Okafor, buyer, reads the three lines and approves the award.
Juno creates the purchase order in SAP S/4HANA, updates the info record and keeps the acknowledgement and the supplier’s acceptance from the portal. His time on the item: the minutes it took to read the draft. The week is the showcase estate; the roles it uses are designed and yet to be built.
Sourcing has the best named results in procurement. Walmart’s negotiation agent reached agreement with 68% of the suppliers it approached, gained about 3% on average and extended payment terms by 35 days (Pactum, client page, undated) 49; about 80% of Walmart’s suppliers had been unengaged for want of buyer bandwidth (Supply Chain Management Review, 5 May 2026) 50. Zycus cites 72% faster requisition-to-award and a 15% tail-spend reduction at Tata Play, a vendor claim (Zycus, 4 February 2026) 47.
McKinsey reports a chemicals company gaining 20 to 30% staff efficiency and 1 to 3% of value from autonomous tender preparation, and a telco cutting analysis time by up to 90% and saving 10 to 15% on software negotiations (McKinsey, 5 February 2026) 11.
Every suite has an agent. Oracle’s Autonomous Sourcing agent identifies eligible requisitions, prepares events and invites suppliers by policy (Oracle, 10 February 2026) 23; SAP’s Bid Analysis Agent and Tender Analysis Agent are generally available (SAP, 22 October 2025 and 14 April 2026) 16 15; Coupa’s Sourcing Event Creation Agent builds events 20 to 40% faster (Coupa, 18 August 2026) 32; GEP, Ivalua and Zycus ship the same 44 46 47. Gartner’s Source-to-Pay quadrant report names autonomous negotiation and assisted event creation as market capabilities (Gartner, 21 January 2026) 1.
The pain is time. About 28% of procurement staff time goes on transactional sourcing such as running bids (Gartner, in Supply Chain Management Review, 18 February 2026) 4; only a third of companies use e-sourcing tools at all (McKinsey, 27 October 2025) 10; APQC’s median from requisition to release is 2.0 days for catalogue items, against one to four weeks for a sourced tail item (APQC, n=1,250) 60. Gartner also notes the gap between the talk and the deployments (Gartner, 5 May 2026) 2.
A requisition below the sourcing threshold arrives with a free-text description. The buyer checks contract coverage; where the contract list is empty, the three-bids rule applies. The buyer e-mails three suppliers, waits three to ten days, chases, keys the quotes into a spreadsheet and normalises units, currency, freight and payment terms by hand.
Negotiation happens by phone or e-mail with the preferred supplier. The award is documented, the purchase order is created in SAP or Oracle, the info record or price list is updated, and the supplier acknowledges. Four people touch one tail item: the buyer, the requester, the supplier and the category manager for the exceptions.
Elapsed: one to four weeks for a sourced tail item, against a median of 2.0 days from requisition to purchase order release for catalogue items (APQC, n=1,250). Most tail suppliers are left unapproached for want of buyer time, which is what Walmart found before its agent: about 80% of its suppliers (Supply Chain Management Review, 5 May 2026).
One to four weeks for a sourced tail item, by hand, against a 2.0-day APQC median from requisition to release for catalogue items (n=1,250). Most tail suppliers are left unapproached for want of buyer time.
The same six stages as the PO cancellation agent in chapter 5, applied to a requisition under the threshold. Everything below is a design: what would be registered and mapped, the questions a buyer would ask, the terms the team would teach, the actions the agent would take inside the playbook, and what the feedback would improve.
The Wednesday-to-Friday run of the scene, step by step. Showcase estate; a designed run of roles yet to be built.
The market runs the event and the negotiation inside rules and drafts the award for a person: Zycus routes the award recommendation for approval (Zycus, 4 February 2026), and vendors start with the lowest-value spend and raise the level as trust builds (Supply Chain Management Review, 5 May 2026). The blueprint reads the same way: event build and award at A2, bid collection at A3, the playbook at A1 as the category manager’s decision, and strategic supplier negotiation at A0, where the work stays with people.
| Element | Setting | Set by | Changes |
|---|---|---|---|
| Objective | Compete every requisition under the threshold with an empty contract list, and award inside the playbook | The category manager | New version |
| Data scope | Requisitions, events, bids, contracts, price lists, info records and the approved supplier list in SAP S/4HANA, Oracle Fusion and the portal | A. Novak, data lead | New version |
| Rules | The playbook, version 1: target 5% under the last price, walk-away at the last price, two rounds, payment terms 30 to 60 days, the forbidden clauses listed | The category manager with the Planner Agent | New version, simulated first |
| Trigger | A requisition approved under $25,000 with an empty contract list · a contract expiry 90 days out · a quarterly campaign | The category manager | At once |
| Actions permitted | Build an event · invite from the approved list · normalise bids · negotiate inside the band · draft the award · create the order once approved | The category manager, owner | New version |
| Limits | Value threshold $25,000 · three suppliers invited at least · a payment-term change under 15 days · events per day 20 | The category manager and J. Harrison | New version |
| Escalation | A bid outside the band or a supplier counter, to D. Okafor · a payment-term change above the limit, to J. Harrison · a specification question, to the requester | The category manager, owner | At once |
| Level | A2 Supervised at the award, with D. Okafor as the named approver · A3 for the event and the bids · A0 for strategic suppliers | J. Ridley, director | Up on evidence, down in one step |
| Feedback | Every approve, edit and reject on an award is recorded with the bids and the playbook version | Always on | Fixed |
Every row is a setting or a versioned rule; the level and the limits are the ones a manager signs.
Lima’s agent blueprint is a design of 960 agent roles across five end-to-end chains. It is the map of what Juno can be configured to do, and the first agents are built from it one at a time, the way the PO cancellation agent was.
Additional capability in Procure-to-Pay lists the rest of the map for this chain.
| Measure |
|---|
| savings against last price (3% Walmart, 15% Tata Play) |
| RFQ-to-award days (72% faster, Zycus) |
| share of tail spend competed (80% unengaged baseline) |
| supplier acceptance rate (68%) |
| buyer hours per event |
| payment-term days gained (+35) |
| awards edited by the buyer per 100 |
Baseline the share of tail spend competed first, because it is the number the agent changes most and the easiest to count: take one quarter of purchase orders under the threshold and mark the ones that had three bids behind them. Savings against last price then has a denominator, and the buyer’s edits per 100 awards tell you when the playbook is ready for a wider threshold.
It invites suppliers from the approved list only, the playbook’s forbidden clauses are checks in its planning table, and the award waits for D. Okafor. The supplier risk use case adds the screening hold before an order is placed.
People do. The blueprint keeps strategic supplier negotiation at A0: the work stays with people; the blueprint lists the step so the map stays complete. The agent prepares the facts for that meeting and takes the tail.
The draft carries the reason in the words of the playbook, the two rejected bids with their landed cost, and the rounds of the negotiation. The same record goes on the audit trail with his approval.
The award becomes a purchase order. Then a customer pushes out, the plan changes, and 38 open lines stand above the need. Who cancels them, and how fast?
Purchase order change, cancellation and confirmation chasing: the one agent that runs, on the Monday chapter 1 opened on.
Bring two systems and one decision your planners make every week. In the first week we register the data, confirm the mapping with your team, answer your questions in ChatLima and run the first agent at the level you choose.