The model was never the hard part
AI across large, federated organisations: multi-unit rollout, entitlement-aware retrieval, system integration and cost attribution finance can use.
Rollout
A pilot proves the model works; the rollout proves the operating model does. Different source systems, entitlements, regulators and languages. We design for the second unit while building the first, and make divergence a decision with a visible cost.
Identity
Retrieval enforces the source system's permissions per user and per document at query time, including the ones that changed this morning. Not a filter applied after the fact.
Scale
500+
enterprise clients served across 22 countries at 99.9% platform uptime
Adoption
An assistant in a portal nobody visits goes unused. We put it inside the CRM, the ticket queue and the chat client instead.
Operating model
Central owns the gateway, guardrails, evaluation and logging — expensive to duplicate, dangerous to vary. Units own use cases and outcomes. The failure is choosing neither.
Cost
Usage instrumented by unit, use case and user, cheap tasks routed to cheaper models, and attribution finance can charge against. Consolidation usually funds the platform work.
Shared platform
Identity
Business systems
Content
Platform
Governance
3–5 weeks
What AI is already running and what it costs, where the identity constraints sit, and a recommended operating model.
Estate audit with total spend, rationalisation plan, target operating model
12–24 weeks
The shared platform stood up, with two business units delivered on it and the landing pattern documented for the next.
Shared platform, reference integrations, two delivered units, landing pattern
Ongoing
Rollout across units and countries, operation under an SLA, and enablement with a quarterly cost and portfolio review.
SLA operation, adoption programme, quarterly review, security review support
A boundary rather than a choice. Central should own what is expensive to duplicate and dangerous to vary: gateway, guardrails, evaluation, logging and cost control. Units should own use cases, prompts and outcomes. A central team that also owns use cases becomes a bottleneck, and units route around it.
Audit before you police. Shadow tooling tells you about unmet demand and about how slow the sanctioned route is. We inventory what runs, what it costs and what data it touches, then offer a path that is genuinely faster than the expense card. Consolidation usually funds the platform work outright.
When the process is not agreed. If two divisions define the same customer or ticket differently, an assistant will surface the disagreement to staff and customers at speed. The same applies where entitlements are not modelled well enough to say who may see which document: without that there is no safe retrieval design.
Regulator, budget, deadline, legacy core, a board that has been burned once already. Tell us what you are working around.
