AI-native development and the future of consulting

The traditional structure is familiar. A strategy firm defines the opportunity. A design partner shapes the experience. A systems integrator builds it. Each handover requires a document, each document loses fidelity, and each team inherits decisions it did not make and cannot easily revisit.

That structure was rational when building was slow and expensive. Specialisation and scale were how you managed risk. But the economics that justified it have changed, and the cost of the handovers is now visible in a way it was not before.

What clients notice first

The value of a recommendation drops the moment it becomes possible to see the working version instead.

Once a client has experienced a working application in week two of an engagement, a three-month analysis phase producing a target operating model is a harder sell. Not because analysis has no value — it does — but because it can now be tested rather than argued.

What the new model demands

• Smaller teams with wider range: people who can sit in an operations review in the morning and shape the application in the afternoon.
• Seniority throughout, not only at the proposal stage. Pyramids of junior capacity are a solution to a problem that has shrunk.
• Accountability for the outcome in production, not for the deliverable.
• Honesty about what is genuinely fast and what is not — integration, data quality and adoption have not been automated.

This is a narrower model. It suits work where the business problem is specific, the process is understood by someone in the room, and the measure of success is something running. It does not replace deep industry strategy work, and firms that pretend otherwise will disappoint clients.

What it does replace is the long middle: the months of translation between a decision and its implementation. That was always the least valuable part of the engagement. It is simply the first part that technology made optional.