How an engagement runs, start to finish.

Six steps and one decision: what happens at each, who does the work, and how long it takes.

Discovery
30 minutes
Proposal
One scope, one number
Build
Roughly 8–12 weeks

Every step at a glance.

StepWhat happensWho does itHow long
DiscoveryWe learn how your business runs, explain a little of what AI can and can't do for a company like yours, and decide together whether we're a fit.Robert and you30 minutes
Explore & ScoreWe map how work moves through your business with the people who do it, find the gaps, and score two or three opportunities with you. Together we pick the one worth building.Robert, with the people who run the processOne or two sessions, ideally on site
Design & TailorWe show you ideas, and a demo if it helps you decide. We agree the scope that solves the core problem and what “working” will mean, written down.Robert and your teamA few weeks
ProposalWe walk you through the scope, the acceptance gates and the price, and answer every question before you decide.Robert, you, and whoever signsOne meeting
Build in steps you sign offWe build it step by step with the people who own the process. Each step is checked against the agreed gate and signed off by you before the next one starts.Us, with your teamRoughly 8–12 weeks
Yours, runningYou own the system, the data and the documentation, and your people are trained to run it. We stay on to tune it as the process changes.Your team, with us tuningOngoing

The build loop: nothing moves on until you've signed it off.

Build opens into this loop. The gate is agreed once, before anything is built. Each step is then checked against it and signed off by you before the next one starts, until the gate is met.

The build loopAgree the gate and the payback. Build the next step. If you haven't signed it off, the step is reworked. Once it is signed off, check the gate: if it isn't met yet, the next step is built. When it is met, it is live and yours.Agree the gateand the paybackBuild the next stepSigned off by you?Gate met?Live, and yoursnot yetyesmetnot yet:the next step
  1. Agree the gate and the payback

    Before anything is built, what “working” means is written down, with the payback the build is scoped against.

  2. Build the next step

    One piece of it, built with the people who own the process.

  3. You sign it off

    Not yet? It goes back and gets fixed. Nothing moves on until you've signed it off.

  4. Check the gate

    Not met yet, the next step gets built. Met, it's live and yours.

Often the first thing we build.

A read-only connection between Claude and the system that holds the most-asked answers: usually the ERP, often the CRM next. It runs in your own cloud, under each person's own login, and your team can start asking it questions in the first week of the build.

Questions people ask at this point.

All questions
How long does it take to get a working AI agent running?

The first call is 30 minutes. Exploring takes one or two working sessions with the people who run the process, ideally on site, and shaping the solution a few weeks after that. The proposal is one meeting. The build itself takes roughly 8 to 12 weeks, step by step, with each step signed off before the next one starts. When connecting Claude to your ERP is part of the build, it's often the first thing we do: the one we've measured went live within a week of the first working session, and the team started asking it questions straight away.

What does an engagement cost?

Everything before the proposal is free. Every build is scoped and priced in the proposal, against a payback we agree up front. Each step is checked against the agreed gate and signed off by you before the next one starts. We don't publish a price list, because each build is scoped to your process. You get the scope and the number in writing before anything is built.

Do we own what you build?

Yes. The system, the data, and the documentation are yours, and the people who own the process are trained to operate it. There is no license and no lock-in. We stay on afterward to monitor the agents, handle edge cases, and take the next process once value is proven — but that is a partnership around something you own outright, not a dependency you cannot leave.

It starts with a 30-minute call.

You'd be talking to Robert Dopart directly: the person accountable for the build, not a salesperson.