MBAI, homeBook a first session
Menu

For your team

The same work, for a team that has to move together

Workshops, manager enablement and rollout, business architecture, and selective implementation. Scoped engagements, a written estimate before anything starts, and nothing you cannot run yourselves afterward.

For your team

When the whole team needs it

Scoped work, a written estimate before anything starts, and nothing you cannot run yourselves afterward.

  • Workshops

    Who it is forTeams who need a common starting point, fast.

    You leave with
    Role-specific use cases people can apply the same week, and a shared standard for safe use that everyone in the room agreed to.
    What happens, format, and scope
    What happens
    Sessions structured around your operation, not generic AI training. We use your documents, your processes, and your real questions. Leadership sessions cover strategy, risk, and what to say no to. Workforce sessions teach people to use these tools well and to recognize a bad output before it reaches a customer.
    Format
    Half or full day. Fixed rate.
    Scope
    One engagement, priced before we start.
    Ask about a workshop
  • Manager enablement and rollout

    Who it is forOrganizations where the tools are already bought and nobody uses them.

    You leave with
    A capability map, a rollout sequence, an ownership model, the controls, and a measurement plan you can run without us.
    What happens, format, and scope
    What happens
    Program planning with the people who actually have to reinforce it. We work out who owns what, what good use looks like in each role, what is off limits, and how anyone would know whether it worked.
    Format
    Scoped engagement. Written estimate first.
    Scope
    Sized to your org after a discovery conversation.
    Start a conversation
  • Business architecture

    Who it is forAnyone about to automate something they have not mapped.

    You leave with
    A workable system diagram, the places where the work is genuinely stuck, and a build, buy, test, or wait recommendation for each one.
    What happens, format, and scope
    What happens
    We map the roles, decisions, handoffs, data, systems, controls, and measures as they actually are, not as the process document says. Most of the value shows up here, before any tool is chosen.
    Format
    Scoped engagement. Written estimate first.
    Scope
    Ends in a document and a decision, not a subscription.
    Start a conversation
  • Selective implementation

    Who it is forTeams who already know which piece is worth building.

    You leave with
    Something your team uses, trusts, and owns, plus the documentation to run it after we are gone.
    What happens, format, and scope
    What happens
    We build the one thing the coaching or the architecture work justified. On infrastructure you control, with your data, using whichever tool fits, including an off-the-shelf product if that is the honest answer.
    Format
    Custom. Written estimate before any work begins.
    Scope
    Deliberately narrow. We would rather build one useful thing than six half-finished ones.
    Start a conversation

How an engagement runs

Transparent from the first conversation

Pricing is not a guessing game. Here is exactly how we scope, estimate, and deliver, before you commit to anything.

  1. Discovery

    We define the problem, look at the data you actually have, confirm who owns what, and agree a schedule. A mutual NDA lets us talk freely about your operations.

  2. Written scope

    That conversation becomes a defined scope, a timeline, and a written estimate tied to the outcome we expect it to produce. You see the number and the reasoning behind it before anything starts.

  3. Delivery

    Work proceeds against named milestones on a regular cadence, usually weekly, so you always know what is done and what is next.

  4. Check-ins

    After delivery we come back on an agreed schedule to see whether it is still being used, still correct, and still worth running. If it is not, we will tell you to turn it off.

What we recommend

Buy, build, test, or wait

Most of what a team needs already exists and can be bought. Some of it has to be built. Some of it should be tested cheaply first, and some of it is not ready. Telling you which is which is the work.

  • Buy

    When
    A product already does this well, the market is mature, and your version of the problem is not unusual.
    Why
    Why
    Cheaper and better supported than anything we would write, and you are not dependent on us to keep it running.
  • Build

    When
    The work depends on your own data, your own rules, or a process nobody sells software for.
    Why
    Why
    You end up owning the asset and the knowledge, and you are not renting the part of your operation that makes you different.
  • Test

    When
    The value is plausible but unproven, or two approaches both look reasonable.
    Why
    Why
    A small, time-boxed test answers in weeks what an argument will not settle in months, and it is far cheaper than committing to the wrong one.
  • Wait

    When
    The tooling is moving fast, the data is not ready, or nobody internally owns the outcome yet.
    Why
    Why
    Waiting deliberately, with a date and a trigger to revisit, is a decision. Drifting is not. We will say wait when wait is the answer.

Work with us

Tell us what your week looks like. We will tell you honestly whether an hour with us is worth your time.

Book a first session