- Product squads (Outcomes): Own the KPI, prioritize agents by ROI, run experiments
- AI platform (Capability): Tools, memory, orchestration, evaluation harness
- Safety function (Policy): Guardrails, red-team, audit trail, model risk
- CoE / Chief AI Officer (Governance): Portfolio, funding model, cross-BU standards
Why AI programs stall after the pilot
The pattern repeats across every enterprise we assess. Twenty to forty pilots run, three or four demonstrate real value, and none reach production at scale. The blocking constraints are almost never model quality. They are: no owner accountable for the business metric, data that cannot be retrieved with the right permissions, no path for an AI system to write into a system of record, and no evaluation harness — so nobody can prove the thing is safe to scale. Consulting that does not attack those four constraints is producing slides, not transformation.
What AI transformation consulting should actually deliver
Six deliverables, in order: a readiness diagnostic grounded in your data and estate, a prioritised workload portfolio with modelled economics, a target operating model naming who owns what, a reference architecture that survives vendor change, a governance and evaluation framework, and at least one workload in production during the engagement. If the statement of work ends at the roadmap, you have bought a research report at consulting prices.
Engagement models and how to price them
Three shapes work. A fixed-scope readiness and roadmap sprint (four to six weeks) when leadership needs an evidence-based plan. A build-and-transfer engagement (one to two quarters) where the advisor ships the first workloads and hands the operating model to your team. A managed AI operations model for enterprises without a standing platform team. Avoid open-ended time and materials advisory with no production deliverable — it is the single most common source of AI spend with no attributable outcome.
Choosing an advisor: five questions that separate them
Ask to see an evaluation harness they built and run in CI. Ask which system of record their last engagement wrote to, and who approved the entitlement. Ask for a workload where they recommended against building. Ask how inference cost was modelled at peak, not pilot, volume. Ask which of their people will still be on the account in month nine. Firms that answer all five concretely are delivery organisations; firms that pivot to a maturity model are not.
The 12-month transformation sequence
Quarter one: readiness diagnostic, data and permission remediation on one domain, one workload in production. Quarter two: operating model stood up, governance and evaluation in CI, second and third workloads shipped. Quarter three: platform consolidation and cost controls as inference volume grows. Quarter four: portfolio review, decommission the losers, and move the CoE from build to enablement. Each quarter ends with a measured business number, not a maturity score.
Cost of ownership nobody models at the start
Beyond licences and consulting fees: inference at production volume, the evaluation and QA harness, integration maintenance as source systems change, model and prompt version management, and the standing run team. In our experience run cost overtakes build cost in year two. Programs that never modelled it end up quietly rationing usage — which is how a successful pilot becomes a shelved capability.
Measuring transformation honestly
Track four families: business outcome per workload (cost, cycle time, revenue, risk), adoption depth (share of eligible transactions actually handled), quality and safety (evaluation pass rate, incident count), and unit economics (fully loaded cost per successful task). Maturity scores are useful for internal narrative and useless as a decision instrument. Fund the next wave on the first three.
- AI programs stall on ownership, data permissions, write access and evaluation — not model quality
- A credible engagement puts at least one workload in production, not just a roadmap
- Five questions separate delivery firms from advisory theatre — start with the evaluation harness
- Run cost overtakes build cost in year two; model inference at peak volume from day one
Questions leaders ask us
- What is AI transformation consulting?
- AI transformation consulting is advisory and delivery work that takes an enterprise from scattered AI pilots to production workloads with a named owner, a governance framework, a target operating model and measurable business outcomes. Credible engagements ship at least one workload into production, not just a roadmap.
- How much does AI transformation consulting cost?
- Fixed-scope readiness and roadmap sprints typically run four to six weeks; build-and-transfer engagements run one to two quarters. The larger cost to model is ownership: inference at production volume, evaluation tooling, integration maintenance and the standing run team, which usually overtake build cost in year two.
- How do we choose an AI consulting partner?
- Ask to see an evaluation harness they run in CI, which system of record their last engagement wrote to, a workload they recommended against, how they modelled inference at peak volume, and which named people stay on the account in month nine.
- Why do most enterprise AI pilots never scale?
- Four repeatable constraints: no owner accountable for the business metric, data that cannot be retrieved with correct permissions, no write path into a system of record, and no evaluation harness to prove the workload is safe to scale.
- How long does an AI transformation take?
- A realistic first year is: readiness and one production workload in quarter one, operating model and governance plus two more workloads in quarter two, platform and cost consolidation in quarter three, and portfolio rationalisation in quarter four.