TD · Multi-channel platform, regulatory change, sunset
Two Channels, Twelve Systems, 120 Seconds — Then Three Regulatory Changes on the Live Flow
1M+
Customers
120 s / <500 ms
Partner SLA / Decision P99
0
Cutover Incidents
Overview
A vendor delivered a skeleton decision engine. We configured it into live production for a million customers across two channels — a national e-commerce partner with a two-minute decision promise and the direct channels — redesigned the API architecture around it, absorbed three regulatory changes on the live flow, and retired the on-premise engine it replaced.
The Challenge
Applications reached the platform from two channels with different data formats and security models and flowed through twelve downstream systems in sequence. No single document mapped the partners, contracts and data flows. Regulation changed mid-flight: a provincial rule on requested credit limits, insurance consent and retention, and a distinction between proactive and reactive limit increases. The legacy engine had to keep running until cutover.
The Approach
Made a build-vs-buy decision: bought the engine and internalised the product work the vendor did not supply—strategies, access model and channel contracts. Wrote the API architecture document covering upstream partners, downstream contracts, security, data-type contracts and error handling. Enforced the provincial rule at the channel boundary; modelled insurance as an eligibility-gated flag with its own consent record and retention clock; treated proactive and reactive limit increases as two products, with optimistic UI prohibited. Held the 120-second SLA as non-negotiable and cut scope in two sprints to protect it. Introduced a Definition of Ready; defined tiered support and access governance before go-live; ran cutover as shadow comparison with criteria set before dates.
Key Outcomes
- Automated approval rate increased 22% after third-party behavioural signals were integrated.
- Held the 120-second partner SLA and sub-500ms decision API P99 for 1M+ customers.
- Delivered three regulatory changes on the live flow with zero compliance exceptions in post-launch audit.
- Decommissioned the legacy engine with zero cutover incidents; Definition of Ready reduced rework 30%.
The Result
Buying the engine saved time on the engine, not on the product. The contracts, the access model and the regulatory logic were the product — and if the PM does not write the operations requirements before launch, the first incident becomes the spec.