Approach

Engagements designed to end

Every consulting relationship is, over a long enough period, building either toward your independence or toward your dependence. The mode is rarely stated out loud. It is almost always visible in how the engagement is structured.

Why "senior-led" is no longer the point

For decades the boutique pitch was simple: at a large firm you meet the partner at the pitch and never again, and the work is done by consultants two years out of business school. At a small firm, the people who sell the work do the work.

That distinction is disappearing. McKinsey, BCG and Bain have frozen entry-level consultant salaries for a third consecutive year and cut graduate intake sharply. PwC's global chair has said publicly that the industry needs a different set of people — fewer juniors writing decks, more senior practitioners. The pyramid is flattening across the whole industry, which means senior-led delivery is becoming the floor rather than a differentiator.

So the useful question for a buyer has changed. Not will senior people do my work, but at the end of this, do I own anything?

Dependency, and how to spot it

A dependency-shaped engagement produces artefacts only the firm can interpret. The deliverable is a deck rather than a system. The understanding of your context lives in the consultants' heads, so when your team tries to operationalise the recommendations, the missing layer turns out to be the firm itself. This is rarely cynical. It is simply what the business model rewards.

Three signals worth checking in any proposal, ours included:

  • Does a proprietary platform sit underneath the architecture as a load-bearing component? If the system stops working when the contract does, you bought a subscription, not a capability.
  • Is the methodology taught or held? If your team cannot re-run the prioritisation exercise on a new idea next quarter without calling the firm, the methodology was never transferred.
  • Is there an explicit handoff phase with a named internal owner? This is the phase most engagements silently skip, and the one that determines whether the work survives.

The four phases

PHASE 01 PHASE 02 PHASE 03 PHASE 04 Diagnose Architect Build Hand off Two weeks, fixed fee Design before a line is written Your people in the room throughout Named owners, defined off-ramp WHAT YOU KEEP Opportunity map Scoring logic Costed roadmap Architecture docs Decision criteria Governance controls Running system Evaluation harness Deployment pipeline Trained owners Maintenance runbook Exit checklist OWNERSHIP Us You transfer is continuous, not a single handover event
Each phase leaves an artefact in your stack — readable, editable and extensible without us. Ownership shifts across the whole engagement rather than arriving as a document dump at the end, which is what makes the engagement able to close.

Diagnose

A structured assessment producing a written mandate and a prioritised opportunity map. The scoring logic is documented so your team can apply it to future ideas independently. More on the readiness assessment →

Architect

Design of the operating model and technical architecture — decision criteria, data flows, governance controls, and the configuration that will run the system. These live in your stack from the first day, not ours.

Build

Implementation with your people involved throughout rather than briefed at the end. The system runs on your accounts, configured with your context. We are teaching at least as much as we are building. More on architecture and build →

Hand off

Named internal owners trained, documentation reviewed with the people who will maintain it, and a defined off-ramp. The engagement ends when ownership has transferred rather than when the budget is exhausted.

An engagement that has no ending designed into it is not a project. It is a retainer with a project's paperwork.

Indicative 2026 market pricing for comparable AI consulting scope.
Firm typeDiagnostic & roadmapFull build, ownership transferredDelivery model
Boutique $25k–$75k $150k–$400k Senior practitioners deliver directly; small scopes
Mid-tier consultancy $80k–$150k $200k–$600k Mixed seniority, heavier implementation weighting
Big 4 / global strategy $150k–$400k $500k–$1M+ Leverage model; built for Fortune 500 procurement

The difference is largely headcount the engagement is structured to carry, not quality. Where a large firm is genuinely the right answer, we say so.

What we'll tell you honestly

There are situations where a boutique firm is the wrong choice, and we would rather name them at the first conversation than three weeks into a contract:

  • Multi-country programmes with heavy regulatory exposure requiring in-country legal coverage and an enterprise compliance bench — the bench itself is the deliverable, and a small firm cannot provide it.
  • Work genuinely requiring hundreds of consultants in parallel, such as large-scale infrastructure migrations or multi-ERP consolidations.
  • Procurement built around large-vendor counterparties with insurance and bonding thresholds sized for firms ten times larger, where the administrative friction exceeds the value of the engagement.
  • Straightforward tool deployment in a stable environment — if the answer is a standard rollout with a known playbook, a certified vendor partner is the better and cheaper route.

For everything else — bounded transformations at mid-market scale, where judgement matters more than headcount — the structure works in your favour.

Start here

If we're not the right fit, we'll say so.

Tell us the problem and the size of the organisation. A short conversation is usually enough to know.