Why this exists
Everything on this page is derived from the live book next door, not from a slide.
The cost sits in the touches, not the software
A drawdown case costs what its manual touches cost. On this book a standard case carries £360 of handling against £0 on a pre-provisioned one, at £42 a touch. Across 18,000 cases a year that difference is £6,485,684 — illustrative, and only as good as the cost-per-touch you put into Settings.
Pre-provisioning moves the work years earlier
Identity, destination account and bank validation are not hard. They are only expensive because they happen while a member is waiting for their money. Done at wake-up pack age 55, with a £1 taxable payment to bring back a live PAYE code, the request itself reduces to: check the code, draw liquidity, pay, settle behind. Average elapsed on this book: 5.6 days standard against 3.4 days pre-provisioned.
The RTI leg is not guaranteed
The code-return leg has no SLA. Where no code has come back the platform says so and taxes the payment on the month-one basis, showing the member the reclaim position rather than hiding it. 10 of 40 members on this book have a live code.
Observed facts, never scores
The platform records what happened — a field edited nine times, a call abandoned — with the innocent reading printed next to it and a named human deciding what follows. No inference is stored, no vulnerability score exists, and enabling one would need a separate lawful basis, a DPIA and a contest route.
What this build is
Phase 1: observes and orchestrates. It does not hold client money or move it outside the provider's own rails. Card, balance and deposit surfaces are a later-phase conversation and are not in this build.