Small, provable steps.

No enterprise programme. No twelve-month roadmap. We find one place you are losing time, build the AI system that wins it back, and only then talk about the next one.

The four steps

Good fit, probably not.

Probably a good fit

  • Repetitive knowledge work that someone does every week.
  • People moving information between systems by hand.
  • Processes that need judgement, not just triggers.
  • Expensive employees doing cheap work.

Probably not

  • You want a chatbot on the website.
  • The process happens twice a year.
  • Nobody can explain how the process currently works.
  • You want a strategy deck or an opinion rather than a working system.
  • You want someone to advise while your team keeps building it.

Four ways to get this done.

  • An agency that scopes but never builds

    You get a deck and a diagram. Nothing runs.

  • A freelancer who ships a demo and disappears

    The demo works until it meets your real data and your real edge cases.

  • Buying another SaaS tool

    Another subscription, still not integrated, still needing a person to glue it together.

  • Hiring an in-house engineer

    The right long-term answer, and the slowest, most expensive way to start.

  • Us

    We implement the working system in your stack and your accounts, prove it with evals, and hand it over with the code.

Where we lose: after handover you still need someone to run and extend the system. We are not a fit if you want advice rather than a build.

Is this a $500 thing or a $50,000 thing?

Coaching is priced by the session. Team work starts with one process. You can co-build it with us by the hour, have us deliver it as a fixed project, or start with a one-day workshop. Expand only if the economics work.

Sessions and coaching

One-to-one, priced by the session. Start with the free twenty minutes.

Start here

Free

First session

Free

first 20 minutes

Talk through the job you're stuck on. No card, no obligation.

  • 20 minutes, one-to-one
  • One concrete next step
  • No card required

Best for: Anyone deciding whether this is for them.

One-off

30-minute unstick

$89

30 minutes

One problem, solved on the call, with notes you keep.

  • Focused 30 minutes
  • Written follow-up notes
  • No subscription

Best for: A single blocker that doesn't need a project.

One-off

60-minute working session

$150

60 minutes

Work a real job end to end and leave with methods that are yours.

  • A full hour on your material
  • Templates and methods you keep
  • Written recap after

Best for: Getting genuinely better at one workflow.

One-off

Three-session pack

$390

three 60-minute sessions

A habit, not a one-off. Roughly 13% below three single sessions.

  • Three working sessions
  • A plan you set once and follow
  • Written recap after each

Best for: Changing how you work, not just unblocking once.

Team implementation

Work built with or for a team, starting from one process.

Done with you

Co-build by the hour

$250 / hour

per hour, or 4h $1,000 / 10h $2,500 / 20h $5,000

We work in your tools alongside your team. Best when someone can carry it forward.

  • Live working sessions on your real workflow
  • Your team learns the system as it is built
  • Hour packs: 4 hours $1,000, 10 hours $2,500, 20 hours $5,000

Best for: Teams with technical capacity who want to learn by doing.

Fixed-scope project

Done for you

$2,500 – $12,000

typical first project

We take one workflow end to end: understand it, build the system, prove the time saved, and hand it over.

  • One workflow, measured before and after
  • Fixed price agreed before we build
  • Handover and documentation your team keeps

Best for: Teams who want the result, not a project to manage.

Flat price

One-day team workshop

$3,500

one day

A single day with your team on your own material. Everyone leaves with methods they can use the next morning.

  • One day, one flat fee
  • Your documents and workflows, not slides
  • A written pre-workshop assessment

Best for: Teams who need to build the habit before they build the system.

No pitch, no scoping marathon.

Describe the repetitive job and I reply with a same-day fixed quote. If it isn't a fit, I say so and point you somewhere better.

  • Prices are fixed once scoped. The number on the quote is the number on the invoice.
  • You start with one process. Nothing expands unless the measurement says it should.
  • Prefer writing to talking? That is the default here, not an escape hatch.

Straight answers.

What does a first project cost?
A fixed-scope first project is $2,500 – $12,000, quoted once after we understand the workflow. If you would rather build it with us, co-building is $250 / hour with hour packs. Every number is on the pricing block above.
How long before something is actually running?
Usually one to three weeks from kickoff to a system running on your real work, depending on how many systems it touches. You see something working early, not at the end of a long engagement.
Which models do you use?
Whichever fits each step. We orchestrate between models rather than betting everything on one vendor, and we run them in your accounts so you are not locked in. If a cheaper model passes the evals, we use the cheaper model.
Why do evals matter?
Because a system that looks right in a demo and fails on your real edge cases is worse than no system. We build a test set from your own examples and nothing reaches production until it passes.
What happens when the model gets it wrong?
Risky steps stop for a person: the system proposes and a human approves. Everything is logged, exceptions are surfaced rather than buried, and wrong answers become new test cases so the same mistake is caught next time.
Who owns the accounts and the code?
You do. Systems are deployed in your infrastructure and your accounts. Handover includes the integration, the evaluations, and the documentation, so nothing depends on us being on retainer.
How is our data handled?
Your data stays in your accounts. Retrieval runs over your own documents with your permissions respected, and we do not use your data to train models. What leaves the building is what the workflow needs, and nothing else.
What does handover mean, concretely?
The code and configuration running in your environment, the evaluation set you can re-run after any change, a short runbook for what to watch, and a session with your team so the system outlives the project.

Start with one process.

Tell us where the time goes. We'll come back with where to look first, and what it would cost.