How an engagement actually runs

Most failed AI projects were built before anyone agreed what problem they were solving or how anyone would know it worked. These four stages exist to stop that, and we run them in order every time.

Discover

We sit with the people doing the work and follow a job from first contact to invoice. We are looking for where it stops moving: the second entry of the same address, the inquiry nobody owns, the quote that sits for three weeks.

Assess

We size each gap in terms you can check — hours, missed calls, unworked records — and rank them. Some will not be worth closing yet, and we will say which ones and why.

Implement

We build one agreed improvement, with a defined scope and a checking step where a person reviews what the system did. Then we train the people who will use it and leave written instructions behind.

Optimise

We compare what happened against the measures agreed in stage two. Actual results are reported separately from projections, always.

What we need from you

These are the things that decide whether an engagement goes well. None of them are large, but all of them are necessary.

One person who can decidesomeone who knows the business and can approve
Time with the people doing the workusually three conversations, 45 minutes each
A few real examplesactual jobs or inquiries, not hypotheticals
Access to the systems involvedwe explain exactly what is needed and why
Someone to answer interested customerswithin one business day, or the work is wasted
Your approval before anything goes outmessages, scripts and rules are yours to sign off

How we work

You own everything

Accounts, phone numbers, data and configurations are created in your name. If you stop working with us, nothing stops working and nothing has to be handed back.

Vendor and model agnostic

We are not resellers and take no commission from providers. The telephony, the model and the CRM are chosen on fit and cost, and can be changed later.

A person stays in the loop

Anything that touches a customer gets a checking step. Systems draft, qualify and route. People decide, especially when money or a promise is involved.

Scope is written down

What is included, what is not, and what triggers a new conversation about price. If the work turns out larger than the package, we tell you before building, not after.

Pricing is quoted per engagement. It depends on the systems involved, the size of your list, and how much integration work is genuinely needed. We give you a fixed figure and a payment schedule in writing before any work starts.

Start with one problem

Tell us about a single task that eats time every week, or one place where work goes missing. That is enough to begin.