Making compliance disappear into the workflow — then moving eight legal entities without a single disruption.

The original brief for suitability was a separate compliance portal — advisors would build a recommendation, then visit another system to check it passed. It looked reasonable on a slide. In discovery, advisors described it as "another system I'll check eventually," which is a polite way of saying it would be ignored until an audit forced the issue.

Underneath that was a harder problem: front-office advisors wanted a frictionless tool, and compliance wanted a hard gate before any recommendation went out. Those two things read as mutually exclusive right up until you separate when the check happens from whether it interrupts the advisor.

• Reframed the constraint. The rule wasn't "compliance must interrupt the flow" — it was "compliance must happen before the recommendation is made." That distinction is what unlocked an inline architecture: the suitability check runs in the background as the advisor builds the recommendation, and surfaces the result at the exact moment they need it, not after.
• Built the scoring engine into the advisor's own screen — real-time suitability across Structured Products, Mutual Funds, ETFs, Private Equity, and Hedge Funds, tuned for UHNW, HNW, Corporate, and Trust client profiles across 8 legal entities.
• Delivered the Front Office / Middle Office target operating model, resolving a long-standing architectural gap in real-time cross-border product integration and client onboarding.
• Queried and validated the underlying compliance and suitability datasets directly with SQL to support requirements analysis, UAT, and production data issue triage — staying close enough to the data to catch problems before advisors did.
• Led the Brexit legal-entity migration (UK to Luxembourg): ran joint acceptance-criteria sessions with UK compliance and Luxembourg entity leadership before a line of code was written, then sequenced a two-week parallel-run window where both entity structures were live simultaneously so issues surfaced with zero client impact.

Both problems — suitability and the Brexit migration — resolve to the same instinct: find the one word in the brief that's doing too much work, and take it apart. "Compliance check" was doing two jobs at once (timing and interruption) until they were separated. "Migration deadline" sounded like a single cutover until it was separated into non-negotiables (day-one controls, KYC, suitability) and everything that could safely land after go-live.

The same discipline carried into Brexit: lock what genuinely cannot move (KYC, suitability, day-one controls), and give everything else room to land after go-live under a parallel-run safety net. It's a slower-sounding plan in the kickoff meeting. It's the only one that survives a live regulatory deadline.

Both stakeholder groups signed off on suitability — advisors because it didn't slow them down, compliance because the control never moved. The Brexit migration hit its regulatory deadline with every control validated pre-go-live, on a programme where "we were mid-migration" was never going to be an answer a regulator accepted.