Skip to content

How we implement AI: find it, build it, hand it over, keep improving it.

AI implementation here runs in four phases: diagnosis, implementation, handoff, then optional monthly improvement. Same sequence every time, whatever the modules turn out to be. The first three stages take roughly three months end to end, and payment is tied to delivery milestones, so nothing is paid upfront for work that has not happened.

The diagnosis is also the entry point on its own. You can buy stage one, get the bottleneck map and the roadmap, and stop there with something useful in hand. Nobody has to commit to a build before seeing the numbers.

Duration3 to 4 weeks

Diagnosis

We talk to your team, map the processes and find where time and money are leaking. Every bottleneck comes out quantified: hours lost, money attached, and what it costs to leave it alone.

DeliverableBottleneck map, AI roadmap prioritised by return, and the proposed architecture.

Duration6 to 8 weeks

Implementation

We build what the diagnosis prioritised and nothing beyond it. The foundation goes in first, then the two to four modules that kill the biggest bottlenecks, plus the integrations they need to actually act.

DeliverableFirst automations in production during the phase, not only at the end.

Duration2 to 4 weeks

Handoff

We train the team, document the system and stay for 30 days of tuning. The goal is the opposite of consultant dependency: the system running in-house with the people you already have.

DeliverableTrained team, operating documentation, and a stable system in the day to day.

DurationOngoing, optional

Keep improving

Handoff is not the end of the relationship unless you want it to be. The optional retainer keeps the system improving: tuning what is live, adding agents as new bottlenecks surface, and folding in new capability as the models change.

DeliverableMonthly optimisation and new modules on request, renewed monthly, never locked in.

What happens inside each phase

The phases have lengths, not a fixed weekly script, because what week two looks like depends on what the interviews turn up. This is the order the work happens in.

3 to 4 weeks

Diagnosis

  1. 01We interview the people who run the processes, not only the ones who describe them.
  2. 02We map how the work actually moves, step by step, including the parts nobody wrote down.
  3. 03We quantify each bottleneck: hours lost, money attached, and what it costs to leave it alone.
  4. 04We come back with the bottleneck map, the roadmap prioritised by return, and the proposed architecture.
6 to 8 weeks

Implementation

  1. 01The foundation goes in first: the company second brain, with permissions per team.
  2. 02Then the two to four modules the diagnosis prioritised, in the order of what they save.
  3. 03Then the integrations those modules need to act inside your operation rather than beside it.
  4. 04Each module reaches production as it is finished, so it meets real work before the phase ends.
2 to 4 weeks

Handoff

  1. 01Your team is trained on the running system, with your data and your approval rules.
  2. 02The system is documented for the people who operate it, not for engineers.
  3. 03We stay 30 days while it meets real volume, and fix what only surfaces under load.
Ongoing, optional

Keep improving

  1. 01We tune what is live as your operation changes around it.
  2. 02New agents get added when a new bottleneck surfaces, not on a schedule.
  3. 03New capability folds in as the models change, without rebuilding what already works.
  4. 04Renewed monthly. Stopping does not break anything you own.

What you have to provide

Four things. If any of them is not there, the diagnosis is the wrong thing to buy right now and we will say so.

Time from the people who do the work

Not a summary from a manager. The diagnosis runs on conversations with whoever actually touches the process, because that is where the difference between the manual and the reality lives.

Access to the systems the modules reach

A module that cannot get to your CRM, your inbox or your documents is a demo. Access is scoped to what the diagnosis put in the build, and nothing beyond it.

Someone who can decide at each milestone

There is a review at every milestone. It needs a person who can approve the next step in the room, otherwise the build waits.

A yes or no on anything risky

Nothing outbound or destructive happens without your written sign off. That gate is yours to work, and it stays yours after we leave.

How payment works

Four milestones, each one tied to something that has actually been delivered. The amounts are named in the proposal, not here.

Payment is tied to delivery. You never pay the whole thing upfront, and no phase begins before the one before it is settled.

  1. 01Signing and kickoff
  2. 02Diagnosis delivered and the build approved
  3. 03Foundation and first agents delivered
  4. 04Final delivery and handoff

The investment is presented as a proposal after the diagnosis conversation, anchored in what the diagnosis found. There is no on-the-spot quote, on purpose: pricing a build before understanding the operation is how a company ends up paying for the wrong thing.

Questions about the method

Why is there no on-the-spot quote?

The investment is presented as a proposal after the diagnosis conversation, anchored in what the diagnosis found. There is no on-the-spot quote, on purpose: pricing a build before understanding the operation is how a company ends up paying for the wrong thing.

What does my company have to provide for the diagnosis to work?

Four things. If any of them is not there, the diagnosis is the wrong thing to buy right now and we will say so. The main one is time from the people who do the work, not a summary from a manager, because that is where the gap between the manual and reality lives. The others are access to the systems the modules reach, plus the two listed on this page.

Do the phases follow a fixed weekly script?

No. The phases have lengths, not a fixed weekly script, because what week two looks like depends on what the interviews turn up. The order of the work is fixed, the calendar inside it is not.

Start with an AI diagnosis.

Thirty to forty five minutes. We find out whether there is a bottleneck worth removing, and I tell you honestly if I cannot help.

Book a diagnosis