Stopping
the bleed
Our decisioning stack was quietly burning [a six-figure monthly run-rate]. I got [the CXO] to approve [the spend/runway] to stabilise it, stopped the bleed, then led the migration to a purpose-built decisioning platform so rule changes stopped being engineering projects.
The situation
A cost centre no one had stopped
[What "bleeding money" actually was — wasted spend, vendor lock-in, eng time sunk into rule changes? Rough run-rate is fine; a range is fine.]
[Why it had gone unaddressed — whose budget it sat in, why it was hard to see.]
The bet
Stabilise first, then re-platform
Two moves, in order. Stabilise to buy time — stop the immediate loss without a risky big-bang rewrite. Then re-platform onto decisioning the risk team can change without engineering, turning a runaway cost centre into a controllable system.
How I led
Winning the mandate, then spending it well
The outcome
From runaway cost to controllable system
[Quantify it: run-rate stopped, rule-change speed before/after, decision volume on the new platform, timeframe. Ranges/qualitative are fine.]
The lasting change: decisioning went from a line no one could explain to an operating system the business actually controls.
"Risk platforms are an operating system for decision-making across a company."