How it works

Start with one workflow. Prove it. Then scale.

Buyers of AI work are right to be wary of two things: a pilot that never becomes a system, and a system that only the consultant can run. The engagement is shaped to avoid both. It is a ladder, and you can step off at any rung with something useful in hand.

  1. 1

    AI readiness review

    We map your workflows and tell you which two or three are worth automating, and which are not.

    You get
    A written document you keep whether or not you hire us for the build.
    Shape
    Days, not months. Starts with a free 30-minute call.
  2. 2

    Proof of concept

    One workflow, built and running against your real systems, with a success measure agreed up front.

    You get
    A working agent on the one process, the measure, and an honest read on whether to go further.
    Shape
    Measured in weeks, scoped to one workflow.
  3. 3

    Implementation

    The full build: integrated with the tools you already run, monitored, documented.

    You get
    The system, its documentation, training for your people, and a post-launch support period.
    Shape
    Scoped per project after the proof of concept, not guessed before it.
  4. 4

    Handover or retainer

    Your choice, made after the build rather than assumed before it.

    You get
    Either way, a system your own team can run.
    Shape
    Handover is the default; a retainer is there if you want us on call.

What it costs

We do not publish price lists, because a proof of concept on a two-person office and one on a company with forty technicians are not the same job. What we do instead: the first call is free, the readiness review is a fixed fee agreed before it starts, and every later phase is quoted from the review, in writing, before any work begins. You will always know the number before you say yes.

Ongoing model usage is paid by you, directly to the provider, at the provider's own rates. We instrument it so you can see what each workflow costs to run. See AI cost management.

What you keep, whatever happens

  • The written readiness review, whether or not you hire us for the build.
  • Source code, configuration and documentation for anything we build, in your name.
  • Systems that run on infrastructure you control, with credentials on your side.
  • Training for your own people, and a post-launch support period after implementation.

The rules every agent follows

We treat an agent that can act as a production system, because it is one. Every agent we deploy has these four things.

  • Defined task boundaries

    An agent does the job it was built for and nothing adjacent. The boundary is written down before it runs.

  • An audit log

    Every action the agent took, with what it saw and what it decided, in a log you can read.

  • A human approval step

    Anything that touches money or customer records waits for a person to say yes.

  • A rollback path

    If it goes wrong, there is a known way back, tested before launch, not improvised after.

Not sure where to start?

The readiness review page has a self-assessment you can run now. It produces a written report, and it is the same questions we would ask on the first call.

Book a workflow review