Architectural writing on Source-to-Pay transformation, operating model design, capability building, and the change you didn't plan for. Not opinion. Not vendor commentary. Practitioner-grade analysis.
Four perspectives on why S2P transformations stall — and what changes when capability is architected, not assumed. Read in any order; the argument compounds.
A business case that survives contact with reality without revision wasn't a business case. It was a sales document. On how programmes substitute activity for outcome — and what changes when the case stays live.
A training plan asks what to deliver. A capability strategy asks what must remain after the programme leaves the building. The four-layer architecture most programmes never put in place.
A platform doesn't impose an operating model — it exposes the absence of one. On the architectural decision most S2P programmes never make explicit, and the friction that follows.
Above the waterline: platform, process, timeline. Below it: roles, behaviours, politics, assumptions. Most transformations plan only what is visible. The series opens with the discipline most programmes skip.
Architectural notes on specific decisions, failure modes, and inflection points in the S2P landscape — each one a self-contained read.
The real shift isn't job elimination — it's job migration. What the age of agentic AI actually demands of procurement and supply chain leaders.
A contemporary commercial agreement is a network of 500+ conditional relationships. This is the point at which human reasoning collapses — and where embedded intelligence changes everything.
Most S2P transformations are measured by the wrong things. True adoption is a behavioural outcome — starting long before go-live and ending long after the implementation partner has left.
Why transformation programmes fall into the Data Trap — measuring everything that's easy to count while ignoring what actually determines success.