The Vendor Dependency Spiral
£1.25 billion in contracts. Declining leverage with each one.
DHCW manages a vendor portfolio valued at approximately £1.25 billion. Each outsourced capability deepens dependence on the vendor; internal capacity to validate vendor claims atrophies; the next strategic decision is made with less independent technical judgement than the last. Specific contracts (a £20M Kainos framework the Chair admitted he had not looked at; a £226M Microsoft Enterprise Agreement passed in one sentence with no questions) show the pattern at board level.
When a complex programme arises, the path of least resistance is to outsource it. But outsourcing does not build internal capability. Without internal capability, you cannot evaluate vendor performance or negotiate from strength.
What is the Vendor Dependency Spiral at DHCW?
The vendor controls timeline and cost. When the next programme arises, you outsource again – because you still lack the capability you never built. The portfolio grows. The leverage shrinks.
Each outsourced programme reduces the internal skill pool available to assess the next contract, which makes the next contract more likely to be outsourced on worse terms.
How It Manifests at DHCW
DHCW runs a £1.25 billion contract book and barely reads what it signs. Approving a £20M Kainos framework, the chair said the quiet part live: “I should have looked. I don’t know how these appear on our website as contracts.” The £226M Microsoft agreement — the largest single thing it buys — was handled at a ~13-minute extraordinary board where the chair stated the real decision was happening elsewhere: “We’re not going to formally approve it here today. We’re going to do that outside of this meeting.” The contract’s value was never stated in that forum at all — only a “£34.2M cost avoidance,” a discount measured against an option DHCW itself called impossible. And the chair named the pattern: “we do go through this conversation every few years.”
The terms are kept dark and the competition is theatre. The supplier on a £47M radiology deal (Philips) surfaced only at a one-item extraordinary board, never in the annual report or the published procurement register. A £10M workforce framework drew two tenders per lot and not a single bid from a small or medium supplier — and the same handful of names (Kainos, TPXimpact, Trustmarque) recur across frameworks. Internal audit logged the consequence as recurrence: a “third strike” of procurement non-compliance, including retrospective call-offs to Kainos (£390,000) and TPXimpact (£271,000).
The cause is simple. An organisation that cannot build can only buy, and DHCW has bought so long that consultants no longer supplement its workforce — they stand in for one that does not function. None of it is forced: Denmark and Estonia built modern health infrastructure on smaller budgets by backing their own people and running real competitions. The dependency is a product of incompetence.
What would a healthy alternative look like?
Every outsourced programme includes a mandatory knowledge transfer plan and internal capability build. Contract values are published. Vendor performance is assessed independently. Sole-bidder contracts trigger automatic governance review. Internal technical teams retain enough capability to evaluate vendor claims and negotiate from strength.
How does the blueprint break the Vendor Dependency Spiral?
The spiral only unwinds when the default choice flips from “outsource” to “build”. Flip the Model rebuilds internal technical capability as the primary delivery mechanism, with vendors used for bounded specialist work on published terms. As in-house competence rises, the organisation regains the ability to evaluate vendor claims — which is the precondition for every other procurement and contract reform.