C
The Procurement Codex
The lifecycle, as a system · Free & open
⚙️

Fully autonomous project. The Procurement Codex is built, verified, and published end-to-end without manual authoring. Its core logic — the spine, the layer model, and the platform comparison rubric — is rebuilt and improved on every iteration for continuous method validation. Content is generated programmatically and refined each cycle: treat it as a directional learning aid, verify against primary sources, and send corrections — accuracy and fairness compound with each pass.

Episode 05 · Capturing the value

Negotiation

Evaluation named the supplier. Negotiation is where you actually capture the value — and where a well-run process either banks real savings and fair risk terms, or leaves money and protection on the table. It is the discipline of knowing your walk-away, modelling what the thing should cost, and trading across price, terms, risk and service to land the best total deal — not just a lower number.

Below: the plain concept → how every platform runs events and negotiations (fair A vs B vs C) → then we stack process mining, should-cost intelligence, expressive bidding, autonomous AI, orchestration and people on top until you see why standalone is never enough.

L0 · The Concept

What it is

The value-capture step: with a preferred supplier identified, you negotiate price, terms, risk allocation and service levels to land the best total deal. It spans competitive levers (e-auctions, expressive bidding) and collaborative value creation — anchored on a should-cost target and a clear BATNA.

Why it exists

Because a chosen supplier is not yet a good deal. Structured negotiation converts leverage and preparation into captured value — savings, better payment and risk terms, stronger SLAs — instead of splitting the difference on price and hoping.

What good looks like

BATNA known · should-cost modelled · negotiate total value not price alone · concession plan set in advance · risk and terms traded deliberately · outcome documented · savings tracked through to the contract and PO · relationship intact for delivery.

L1 · Platform-Native — A vs B vs C

Same rubric for every vendor, 1–5. We state explicitly what each is best and worst at. Toggle platforms to compare.

Platform Best at Watch-out

Scores are directional teaching aids based on typical deployments, not vendor benchmarks. Your mileage varies by configuration, module licensing, data quality, and integration maturity.

L2 · Best Practice

Design principles
  • Know your BATNA — your best alternative to a negotiated agreement is your real leverage; enter knowing your walk-away point.
  • Anchor on should-cost — build a cost model of what the item or service should cost, so the target is fact-based, not the supplier's opening number.
  • Negotiate total value, not price — payment terms, warranty, SLAs, risk allocation, volume flex and TCO all carry value; trade across them.
  • Plan concessions in advance — decide what you will give, in what order, and what you must get in return; never concede reactively.
  • Protect the relationship — you have to run the contract with this supplier; capture value without poisoning delivery.
KPIs & failure modes
  • KPIs — negotiated savings vs first offer, savings vs should-cost, cycle time, % savings realised in contract/PO, terms improvement, event participation.
  • Price-only tunnel vision — squeezing unit price while ignoring payment terms, risk and SLAs leaves real value untouched.
  • No walk-away — negotiating without a BATNA means conceding under pressure with nothing to fall back on.
  • Anchoring to the supplier's number — letting the opening quote frame the range instead of an independent should-cost model.
  • Savings leakage — a great negotiated price that never makes it into the contract, catalogue or PO evaporates.
  • Relationship damage — winning the negotiation but losing the delivery through an adversarial, scorched-earth stance.

The Layer Peeler — watch standalone become a system

Stack layers onto a plain negotiation and watch the architecture — and the outcome metrics — change. This is the whole thesis of the Codex in one control.

Outcome at this stack level
Negotiation cycle
Value levers used
Savings vs first offer
Savings realised in contract

L7 · The Synergy Composite

A real best-of-breed negotiation architecture — no single vendor owns all of it. The value lives in the seams.

flowchart LR
AWARD[Award decision
from Ep04] --> NEG[L1 Negotiation / auction suite
Ariba / Jaggaer / Coupa] SC[L4 Should-cost intelligence
aPriori · Sievo cost models] -.target price.-> NEG OPT[L4 Expressive bidding / optimization
Keelvar · Coupa CSO] -.complex lots.-> NEG AUTON[L4 Autonomous AI negotiation
Pactum for the long tail] -.tail terms.-> NEG PM[L3 Process mining
Celonis / PM4Py] -.cycle lag and leakage.-> NEG NEG --> TERMS[Negotiated price plus terms] TERMS --> GATE{L6 Concession governance} GATE --> CLM[Ep06 · Contract Lifecycle]

Standalone, a negotiation suite runs a clean e-auction or RFQ and logs the outcome — but it does not tell you what the item should cost, it cannot solve a constrained multi-lot award, and it cannot negotiate thousands of long-tail renewals by itself. Should-cost intelligence (aPriori, Sievo) sets a fact-based target; expressive-bidding optimizers (Keelvar, Coupa CSO) solve complex lot splits; autonomous AI (Pactum) negotiates the long tail at scale; process mining exposes cycle lag and the savings that leak between handshake and PO. No one tool models cost, optimizes award and negotiates the tail — the leverage is in wiring them together.

The Stack Builder — compose your own

Pick one from each column. The Codex assembles the composite and calls out where the seams need engineering. Shown here for negotiation; the same engine powers every episode.

Cheat Sheet — Negotiation

The 5-second definition

With the supplier chosen, trade across price, terms, risk and service — anchored on should-cost and your BATNA — to capture the best total deal.

KPIs that matter

Savings vs first offer · savings vs should-cost · cycle time · % savings realised in contract/PO · terms improvement · event participation.

Scorecard in one line

Know your BATNA · anchor on should-cost · negotiate total value not price · plan concessions · protect the delivery relationship.

Platforms in one line

Ariba & Jaggaer on auction breadth · Coupa & Keelvar on expressive / optimization bidding · Ivalua on terms · GEP on guided AI · Pactum on autonomous long-tail.

The layers

L3 mining finds cycle lag & savings leakage · L4 AI models should-cost, optimizes complex lots, and negotiates the long tail · L5 routes savings into contract & PO · L6 governs concession authority.

The thesis

No single tool models cost, optimizes award and negotiates the tail. Value is in the seams.

Scenario Check

Question /