How we work

Start with one workflow. Not an AI transformation.

One workflow, built properly, tested against reality, measured from your own records, and expanded only if it earns its place. You are buying the result, not the architecture.

Show us where it breaks See the process

Most engagements start with the workflow that annoys you most.

Autonomy is earned

  1. Recommends

    It tells your team what it would do. A person does it.

  2. Drafts

    It writes the quote or the reply. A person reads it and sends.

  3. Sends

    It acts inside the rules on its own, and logs every time it did.

A workflow moves up when the rung below it has been right often enough that you stopped checking. That call is yours.

The process

Eight steps, in the order they actually happen.

  1. Before anything is built
  2. Show us what happens now Not your tech stack. The actual sequence: who picks it up, what they look up, where it has to end up.
  3. Define the outcome A sent quote, a booked job, an updated record. If we can’t name the result in one sentence, we don’t build it.
  4. Map the rules and systems Your prices, your exceptions, and the software that has to stay the source of truth.
  5. Building it
  6. Build the smallest useful version One workflow, live, doing real work. Not a platform.
  7. Review before autonomy It recommends before it drafts, drafts before it sends. This is the ladder at the top of this page, and where a workflow sits on it is your call.
  8. Test reality Missing data, wrong details, duplicates, interruptions, strange requests, API failures, timeouts, permissions.
  9. After it is running
  10. Measure Against the outcome we named in step two, from your own records. If it can’t be measured, we say so.
  11. Expand only if it earns its place The next workflow gets built when the first one has paid for itself in time or money.

Scoped small on purpose. The first build is deliberately narrow. That is what makes step six honest: you can test every edge of one workflow, you cannot test every edge of ten.

For selected workflows, we may start with a tightly scoped pilot before either side commits to a larger build.

See what we’ve shipped →
Step one, in full

“One workflow” is a specific thing, so here is one.

Everyone says start small. Small is only meaningful if someone writes down where it ends. A scope we would actually agree to fits on one page and spends most of that page on what is not included.

Workflow

Quote requests arriving by email at one address

Outcome

A priced quote sent, or a drafted one waiting for a person

In scope

  • Requests to that one address.
  • Jobs your rate card already covers.
  • Writing the quote into your job system and sending it from your address.
  • A daily count of what it priced and what it stopped on.

Not in scope, for now

  • Phone calls.
  • Anything that needs a site visit before it can be priced.
  • Discounts, payment terms and variations.
  • Your second inbox.

Finished when

  • Twenty real requests have been through it.
  • Every stop it made was one you agreed with.
  • You have stopped checking the ones it priced.

An illustration of the shape, not a scope we have signed. A real one names your software, your rate card and your numbers, and the middle list is the one that takes the longest to agree.

You are buying the result, not the architecture.

Nobody hires us to own an AI stack. The workflow that answers, quotes, books and writes back is the product. What it is built on is our problem.

Why reliability is the hard part →

Which one annoys you most?

Show us the workflow that annoys you most. We’ll tell you where we’d start.

  • Maybe you already know which workflow you’d start with.
  • Maybe you have three and no way to rank them.

Either is fine. Show us what happens today and we’ll tell you what the smallest useful first version looks like, what it would need from you, and what we’d leave alone for now.

Would rather talk it through than type it out? Book a 30-minute call.

About the process

Four questions. Owen picks up the rest on the call.

Add a bit more (optional)

Owen reads every submission. You’ll usually hear back within one working day.