Three engagement shapes.

Engagements usually start with one of three triggers: a leader departs on short notice, a new unit needs standing up, or a team needs a steady hand through a difficult phase. The seat is occupied with full authority from the first week.

Onboarding is short — the seat is ready for decisions, not still searching for background. Decisions run on a weekly cadence with the executive. A successor is identified early, coached through the mandate, and handed the keys formally.

The goal is to leave the house lighter than it was — and someone else holding the keys.

Typical roles

• Director of Operations
• Head of Operations / Head of Supply Chain
• Programme or project leadership
• Product Management roles

The target operating model, the merged organisation, the quality system, the supply chain, the AI transformation itself — what needs to change is already clear. What's thin is the capacity, or the distance from the problem to run it honestly.

Scope is fixed at kick-off, outcomes signed off, decisions on a weekly cadence. The work happens inside the team, not alongside it. Documentation is written with the people who will run it after handover.

Target operating models only work when the people who run them wrote the documentation.

Typical scope

• Target operating model design
• AI transformation — operating model, workflows, governance
• Post-merger process harmonisation
• Quality management systems (ISO 9001 / EN 9100 / 14001 / 45001)
• Supply-chain setup in regulated environments
• Competitive vendor selection and onboarding
• Nearshoring and service-centre build-outs

Active across the full arc — with AI (daily operator use in teams), through AI (automation, tooling, cleaned data foundations), and for AI (workflow redesign, governance, making the organisation AI-ready from the inside). Most mandates combine two or three of these; pure ones are rare.

One principle runs through all of them: on your machines, with your data, with someone who owns the output at the end. Nothing lives on a vendor's server unless you put it there deliberately.

Most AI pilots don't reach the P&L because nobody owns the output.

Typical formats

• Workshop track · 5–8 hours per tier — Foundation, Builder, and Strategist formats, from first setup to governance.
• Embedded AI work · inside a Lead or Build mandate — The AI layer of an operations or transformation engagement.
• Automation builds · per engagement — Specific workflows, shipped clean into the business.
• Data foundations · per engagement — Clean-up, pipelines, knowledge graphs where they pay off.

Read the underlying perspective — why most AI adoption doesn't show up in the P&L