Consulting and AI SystemsOne doctrine, two linesEngagements are scoped and proposal-led
A long vaulted stone service tunnel, identical bays receding into darkness with a single run of iron conduit along the vault

AI Systems

A strategy needs something to run it.

Build and run the presence and growth infrastructure that executes the strategy. You are paying for production capacity — and for the discipline about where that capacity is allowed to make decisions, which is nowhere.

A dressed stone channel that ends abruptly at a squared kerb, the ground beyond it left rough

The rule that governs it

AI automates production, not decision-making or execution that requires judgment.

Research, content execution, qualification, booking and routing are production: high volume, rule-governed, and finishing at a defined completion state rather than a judgment call. That is the layer where a machine genuinely substitutes for headcount, and it is the only layer where we let it.

Everything that requires judgment — what a client actually needs, what to do about it, what to say when the answer is no — stays with people. Not as a value statement. It is the part that produces the result.

Where the line falls

The same boundary this line is built around, drawn. Everything to the left of the rule finishes at a defined completion state; everything to the right is a judgment call, and is given to a person on purpose rather than by exception.

  1. 01

    Production

    Research, content execution, lead qualification, appointment-booking and CRM routing — the work this line actually automates, at volume.

    Automated

  2. 02

    The transition

    A ready opportunity moves to appropriately-scaled sales resourcing rather than to the most senior person available.

    Scaled to the sale

  3. 03

    Value realisation

    The expansion conversation, taken by the most capable people and never delegated to the production layer.

    Most senior people

  4. 04

    Co-seats

    Each human role paired with an AI partner scoped to that seat, built during onboarding as a deliverable.

    Paired, one to one

How it is bought

Not licensed separately
Delivered inside an engagementAI Systems is built and run as part of a Foundry or Watch engagement rather than sold on its own.
Built to your pod
Co-seatsEvery pod role built during onboarding is paired with an AI partner scoped to that seat, not a shared department serving everyone generically.
Handed over legibly
Yours to runWhat was built, why, and how it is operated is written down. A system nobody but us can run is a dependency, not an asset.

Ask what would actually get built.

The diagnosis decides it. Signal first, then a written proposal with the scope on it.

Sent straight to the two people who answer it. No autoresponder sequence, no call centre.

Ask Bastion

Ask Bastion