AI Executive Office — CXO Assistant Platform  ·  View 05 of 30  ·  2 · People and journeys

Journey — Implementation Lead, Onboarding a Tenant

The journey that decides whether this is a product or a bespoke build repeated: six weeks, no forked code.

Editable source SVG draw.io All views
Implementation lead M+ delivery Goal — A new ministry live in six weeks with no product code forked Trigger — Contract signed; the sovereignty tier is set Done when — The CXO's first brief is right on day one 1 · Provision day 1–3 2 · Connect week 1–2 3 · Map to canon week 2–4 ◆ moment of truth 4 · Configure week 4–5 5 · Prove week 6 ◆ moment of truth What they do Picks isolation tier Runs the tenant pipeline Registers 6 sources Maps fields to canon Reconciles to the board pack Loads an industry pack Sets approval limits Runs the scenario suite Touchpoint Tenant console Source registry Mapping workbench Config studio Evaluation report Behind the glass Bicep + landing zone Data Factory connectors Canonical model + graph Versioned config artifacts Golden-question harness How it feels In control Working Sinking Where it hurts Which tier did they buy? No read API on the old ERP Their cost centre is not ours Every tenant wants a tweak Right answer, wrong wording What answers it Tier is a deployment parameter CDC and file drop both allowed Mapping is config, not a fork Config schema is versioned Eval gate blocks go-live Journey — Implementation Lead, Onboarding a Tenant v 1.0 · owner Data & AI Global Practice · date 2026-09

The trough, and what answers it

  • Mapping the customer's ERP to the canonical model is where every multi-tenant AI product either becomes a platform or becomes twelve consulting projects
  • The answer is that mapping is configuration in a versioned repository, schema-checked in the pipeline, never a code change (views 10, 13, 22)
  • "Right answer, wrong wording" at Prove is real and is why the go-live gate is a golden-question suite the customer writes, not an internal accuracy score

Decisions

  • Isolation tier is a deployment parameter chosen at provisioning, not an architecture rewrite (view 10)
  • An industry pack — government, banking, energy, conglomerate — ships KPIs, agent prompts, thresholds and terminology. It is the commercial asset that makes tenant twelve cheaper than tenant two
  • Tenants that cannot expose an API get a scheduled file drop. Refusing that would exclude most public-sector estates

Numbers

  • Target: 6 weeks to first correct brief; 3 of those weeks are mapping and reconciliation
  • Tenant twelve should cost under 40% of tenant two. If it does not, the packs are not doing their job