Our people
3,400 colleagues across 24 offices, and a partnership model where the person who sold the work stays on it.
Global managing partner
London · AI strategy, operating model
Leads McAi's global practice on AI operating models. Twenty years advising boards on technology-driven change; previously led enterprise data at a European universal bank.
Senior partner, financial services
Stockholm · Risk, governance, credit
Works with banks and insurers on model risk, underwriting economics, and the evidence infrastructure that makes supervisory speed defensible.
Senior partner, operations
Singapore · Supply chain, planning, manufacturing
Rebuilds planning and operations for industrial and consumer clients. Specialises in turning monthly cycles into continuous, agent-assisted replanning.
Partner, energy & retail
Madrid · Data products, demand, grid
Leads decision-led data programmes across energy and retail. Her work on flexibility markets and assortment models is used by operators in six countries.
Partner, healthcare & public sector
Berlin · Clinical operations, responsible AI
Advises provider systems and public bodies on operational AI with a clinical or citizen-facing consequence. Chairs McAi's responsible-AI review board.
Partner, advanced industries
Chicago · Industrial AI, plant operations
Spent nine years on plant floors before consulting. Leads the firm's work on yield, reliability, and operator-in-the-loop systems.
Partner, people & organisation
Johannesburg · Workforce, reskilling, change
Designs workforce transitions for organisations absorbing AI into their operating model. Publishes the firm's work on capability building at scale.
Partner, technology & software
Tokyo · Engineering productivity, products
Works with software and platform companies on AI-native product strategy and on applying AI to their own engineering and support economics.
Partner, cybersecurity & resilience
Dubai · Security operations, AI estate
Leads security and resilience work, including the emerging discipline of protecting model endpoints, pipelines, and agent permissions.
How we behave
We tell clients what the evidence shows, including when it contradicts the programme they have already funded. Our baselines are written down before the work starts.
A use case is real when it runs in production, has a named owner, and moves a number someone is accountable for. Everything else is a pilot and is resourced as one.
We design systems in which accountability is held by a person who can disagree with the model easily, and we say clearly which decisions we would never delegate.
We stay until the capability is running without us. That usually means teaching, documenting, and handing over decision rights rather than defending them.
Join us
Consultants, engineers, designers, and researchers who would rather measure than assert.