Data model
The golden-source schema your data lands on — completeness, revenue integrity and provenance built in from day one, not bolted on after go-live.
Every acquisition lands somewhere. If that somewhere is whichever CRM the last deal happened to use, the group never becomes one business — it stays a shelf of firms with a shared logo. The architecture decision gets made by default, one deal at a time, by whoever is closest to the integration.
A target operating model with the client and adviser experience sitting on top of the core rather than inside it — so when the core changes, only the integration layer is reworked. Advisers keep the same screens; clients see nothing. One data model and one golden source that every acquisition maps to once.
Designed AI-native, meaning the operation can be measured and automated later without being rebuilt — but the decision in front of you is an architecture decision, not an AI one.
The golden-source schema your data lands on — completeness, revenue integrity and provenance built in from day one, not bolted on after go-live.
The evidence trail and control points any automation will need to run against, whoever builds it — so there is something to check against later.
The sequenced route from current state to target state that Move will execute — scoped, scored and priced before a single record moves.
Who holds the architecture after we leave — documented so it’s your asset, not a dependency on us or any other vendor.
You get the target architecture, an honest gap against what you run today, and a landing playbook your next three deals can follow.
Then this is the map they’ve been asking for, built from the estate as it actually is rather than as documented.
Good. This is the work that tells you what to select against.