AI consultancy

A straight answer on AI, then a plan you can act on

Most AI advice is a sales pitch in a lab coat. This is an assessment from someone who builds and runs these systems for a living: what is worth doing in your business, what is hype, and exactly what I would build first.

You get Dean, start to finish. Not an account manager, not a junior, not a team you never meet.

Book a consultationSee what we build

Half the AI projects we get asked to quote should not exist

I will tell you if yours is one of them. I make money building systems, so it would be easy to recommend one every time. I do not. Some problems are process problems, some are people problems, and some are best solved with a spreadsheet. The roadmap says what I would do with my own money, including the projects I would walk away from.

And yes, the advice costs money. That is exactly why it has to be straight: advice you pay for has to be worth more than it costs you, and vague does not clear that bar. You are paying for the calls I have already got wrong on my own projects, so you do not repeat them on yours.

Dean Cookson, founder

The engagement

Four stages, each with something in your hands

Every stage ends with an artefact you keep. Nothing depends on staying engaged with us.

  1. 01

    Understand

    Where the hours go, where leads come from, what your team still does by hand. Not a questionnaire. A proper conversation about the work.

    Output: a map of where time and money leak

  2. 02

    Assess

    What AI genuinely fixes in your business, and what it will not. I build and run these systems myself, so this is grounded in what survives production, not what demos well.

    Output: a straight list, worth doing vs hype

  3. 03

    Roadmap

    A prioritised plan: what to build first, why it pays back fastest, what it replaces and what it depends on. Plain English, ordered by payoff.

    Output: a roadmap your team can build from

  4. 04

    Build or hand over

    Two ways forward, both fine by me. I build the system for you, or your team takes the roadmap and runs with it. No lock-in either way.

    Output: a working system, or a fully briefed team

What you leave with

Three documents, not a deck

The engagement ends with things you can hold and act on. The examples below are illustrative; yours are written about your business.

document 1 of 3

The roadmap

01

Quote follow-up engine

build first
02

Invoice chasing

build second
03

Reporting digest

later

Ordered by payoff: what each build replaces, what it depends on, why it is in that order.

document 2 of 3

The build-or-buy list

Proposal drafting

build it

Accounting

keep your package

Email sending

keep what you have

Where an off-the-shelf tool does the job, the list says buy it. Bespoke is for the work nothing off the shelf can do.

document 3 of 3

The not-worth-it list

Website chatbot

skip

would not move a number you care about

Full CRM replacement

skip

a process problem, not a software one

Often the most valuable page: the projects that would burn budget without moving anything.

All three are yours, no lock-in. Build with us, build in-house, or sit on them until the timing is right. Nothing in them depends on staying engaged with us.

Before you book

The questions people ask on the first call

Who owns the IP in what you build?
You do. Code, prompts, data, documentation: all of it. If we stop working together, everything keeps working and it is all yours.
What stack do you build on?
Proven, hireable tools: Next.js, Supabase, Cloudflare, and whichever AI model fits the job best. Nothing exotic. Any competent developer can pick up what we leave behind.
What happens after launch?
Your choice. We run the system for you, with monitoring and improvements, or we hand it over fully documented and your team runs it. Both are normal, and plenty of clients do one then switch to the other.
How do you handle our data?
Systems are built in your own accounts wherever possible, so you hold the keys. Operosus is a UK registered company working under UK GDPR, and your data is never used to train anyone’s models.
What if AI is not the answer for us?
Then the roadmap says so and we stop there. Some problems are process problems, some are people problems, and some need a spreadsheet. You will not get a build recommendation just because building is what we sell.
Do we need technical people in-house?
No. The roadmap is written in plain English, ordered by payoff. If you build with us, you need nobody technical. If you want your team building their own tools, that is what the training is for.

More on engagement shapes, comms and billing: how we work

Get the assessment

Book a call. 30 minutes, no pitch deck. You get a view on what is worth building in your business, or an honest reason to build nothing.

Book a consultationJoin a free Cook-a-Long

Book a call. 30 minutes, no pitch deck.