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 15 · Where the spine closes into a loop
Fourteen steps have produced an enormous amount of data about how an organisation actually buys. Spend intelligence is what decides whether that becomes a strategy or a filing cabinet — and it is the step that turns a linear process into a loop that gets better each time round.
Below: the plain concept → how every major platform handles it → best practice → process mining, AI, orchestration and ownership, stacked until standalone is never enough.
Spend intelligence is the ingestion, cleansing, classification and analysis of all procurement data — spend, contracts, suppliers, process events and savings — to answer what was bought, from whom, at what price, under what agreement, and what should change. Continuous improvement is the discipline of feeding those answers back into Ep02 category strategy and Ep03 sourcing rather than reporting them.
Because every earlier step optimises locally. Only a view across all of them can see that three business units buy the same part at three prices, that half of a category savings never reached the ledger, or that the approval step added last year costs more than the errors it prevents. Without this step, the spine runs forever without learning anything.
Spend is classified consistently and refreshed automatically, not rebuilt in a spreadsheet each quarter. Savings are tracked from negotiated through contracted to realised, with finance agreeing the definitions. Opportunities are surfaced continuously rather than discovered in an annual review. And the output has a named route back into category strategy, with owners and dates.
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, scope, and integration maturity.
Stack layers onto a quarterly spend spreadsheet and watch the architecture — and the outcome metrics — change. This is the whole thesis of the Codex in one control.
A real best-of-breed spend intelligence architecture is never one product — and at the end of the spine, it is the layer that makes every earlier one improvable. Here is the composite, and where the value actually lives — in the seams.
flowchart LR ERP[ERP spend and ledger
S4HANA / Oracle / D365] --> ING[L1 Ingestion and harmonisation] PO[Ep09 orders] --> ING INV[Ep11 invoices] --> ING CON[Ep06 contracts and prices] --> ING SUPP[Ep07 supplier master
parent-child hierarchy] -.entity resolution.-> ING ING --> CLASS[L4 AI classification
Sievo / suite-native / custom taxonomy] CLASS --> CUBE[L1 Spend cube
category, supplier, entity, time] PMIN[L3 Process mining
Celonis / Signavio] -.how the process behaves.-> INSIGHT RISK[Ep14 risk and ESG signals] -.exposure overlay.-> INSIGHT PERF[Ep13 supplier performance] -.delivery overlay.-> INSIGHT CUBE --> INSIGHT{L4 Opportunity engine
price variance, fragmentation, tail, leakage} INSIGHT --> SAV[L2 Savings tracking
negotiated to contracted to realised] SAV --> FIN[L6 Finance agreement
shared definitions and sign-off] INSIGHT --> LOOP[L5 Back to Ep02 category strategy
and Ep03 sourcing] LOOP --> SPINE[The spine runs again, better]
Standalone, a spend analytics tool produces a beautiful dashboard that changes nothing. Wired to the ledger for completeness, to Ep07 for entity resolution, to Ep06 for contracted price, to Ep13 and Ep14 for performance and exposure overlays, to process mining for how the process actually behaves, and to finance for savings definitions everyone accepts, it becomes the mechanism by which the whole spine improves. This is the closing argument of the Codex: fifteen steps, no single vendor, and all of the compounding value sitting in the seams between them.
Pick one from each column. The Codex assembles the composite and calls out where the seams need engineering. Shown here for spend intelligence and continuous improvement; the same engine powers every episode.
Pull every source of spend and process data together, classify it consistently, find where money and time are leaking, and route what you find back into category strategy with an owner.
Classification accuracy · refresh frequency · spend under management · savings realised versus negotiated · contract price leakage · opportunity conversion rate.
If your savings number and finance savings number differ, finance number is the one that exists.
Specialists win on classification accuracy and savings tracking; suites win on native data and closing the loop; process mining wins on the half of the story spend data cannot see.
L0 spend spreadsheet → L1 spend cube → L2 definitions and leakage discipline → L3 process mining → L4 AI classification and opportunity detection → L5 loop into sourcing → L6 shared accountability with finance → L7 composite.
Standalone is never enough. Intelligence becomes improvement only when data, definitions, process truth and a route back into strategy are wired together.