Managing Director
Chief Executive
Sets the firm's direction and remains personally accountable for the largest programmes. Spends a fixed share of each week on client engagements rather than internally.
- Strategy
- Key accounts
- Governance
Leadership
A leadership team that still delivers — every person here carries client engagements alongside their firm-wide responsibility.
18 yrs
Average experience
9
Leadership team
6
Practice areas
100%
Client-facing
Leadership team
If your engagement runs into trouble, one of these people will be in the room.
Chief Executive
Sets the firm's direction and remains personally accountable for the largest programmes. Spends a fixed share of each week on client engagements rather than internally.
Technology & Architecture
Owns the firm's technical direction and the standard every engagement is held to. Chairs the architecture review board and the technology radar.
Programme Delivery
Accountable for every engagement landing on time and to the agreed quality bar, including the ones that go wrong. Runs the post-mortem process.
Cloud & Platform Practice
Leads migration, landing zone, and platform engineering work across AWS, Azure, and GCP, including the FinOps practice.
Cyber Security Practice
Runs assessment, architecture, and detection engineering. Sets the standard that every engagement's security gate is measured against.
Data & AI Practice
Leads data platform and applied AI work, with a particular focus on the governance that determines whether models reach production at all.
People & Capability
Responsible for hiring, capability development, and the internal engineering progression framework.
Finance & Commercial
Owns commercial structure and pricing, including the fixed-price model and the way scope changes are handled contractually.
Sector Practice
Coordinates the sector specialists across financial services, healthcare, manufacturing, and public sector engagements.
How we lead
These are the things clients tell us make the difference, so they are the things we protect.
Everyone on this page carries client work. A leadership team that has stopped delivering loses the ability to judge what is actually achievable.
Problems are escalated the week they appear, not the month before a deadline. Sponsors hear it from us before they hear it from their own team.
If we are not the right team, or the timeline is not achievable, we say so and lose the work. That is what makes our estimates worth anything.
Architecture and commercial decisions come with recorded reasoning, so the choice can be revisited later by people who were not in the room.
Accountability
Published with response times, because an escalation path you only discover during a problem is not an escalation path.
| Role | Accountable for | You will meet them | Escalation reaches them in |
|---|---|---|---|
| Engagement leadYour main contact | Scope, delivery and the commercial relationship | From the first call, and throughout | Same day |
| Practice lead | Technical standards and staffing for the practice | At architecture review and at each phase gate | One business day |
| Principal engineer | Architecture decisions that outlive the engagement | During design, and whenever a decision is contested | One business day |
| Delivery director | Cross-practice programmes and delivery risk | On programmes spanning more than one practice | Two business days |
| Managing partner | The relationship, and anything the above cannot resolve | At contract, and at any point you ask | Two business days |
Engagement lead
Your main contactPractice lead
Principal engineer
Delivery director
Managing partner
How we lead
Continuity
The most common complaint about consultancies is that the senior people in the pitch are never seen again. Our engagement leads stay on the engagement, and if one has to change we tell you why before it happens rather than in a status report.
Escalation
Escalation is only meaningful if it reaches someone who can change the plan. Ours is published with response times, and it ends at a partner rather than at an account manager who has to ask.
Candour
Bad news does not improve with age. Leadership here is measured partly on whether problems surface while they are still cheap to fix, which requires that nobody is punished for raising one.
Questions
Mostly the pitch-team question, which is a fair one to lead with.
Yes. The engagement lead named in the proposal is the engagement lead on delivery, and the principal who reviews your architecture during scoping is the one who reviews it during the build. If someone genuinely has to change — illness, someone leaving — we tell you before it happens and introduce their replacement properly.
Raise it with the engagement lead first, and if that does not resolve it the path above is published with response times and ends at a partner. We would much rather have an uncomfortable conversation in month two than a contract dispute in month nine, and nobody here treats a client raising a problem as a relationship difficulty.
Nine people across thirty-seven engineers, which is deliberately top-heavy for a firm this size. It is the mechanism that makes the continuity commitment above affordable — senior people deliver here rather than only selling, and that only works if there are enough of them.
Ask for whoever leads the practice relevant to your problem. You will get them, not an account manager.