Professional orchestrating a holographic workflow diagram
How we work

Twelve weeks from questionnaire to a running system.

No mystery, no magic words: a five-phase process that starts with your real workflows and ends with an AI operating system your team actually uses. Here is exactly what happens and when.

Prefer to watch?

The twelve-week process, explained.

James walks the five phases from first questionnaire to a running system. Or keep scrolling to read each one.

01

The five phases

P1Discover

Weeks 1 to 2. A structured digital questionnaire maps your company and each department in scope, followed by paid discovery workshops on your real workflows and files. We leave knowing exactly where the hours go and which arm to build first. Discovery fees are credited in full against a signed program.

P2Design

Weeks 2 to 4. We design your operational brain: which large language model runs where, what knowledge it holds, what stays on your infrastructure with local models, who may access what, and which workflows get automated first. You approve an architecture, not a mystery.

P3Build

Weeks 4 to 8. The system goes up: the brain connected to your files and systems, the first automations running, the marketing engine configured if it is in scope. Everything is tested on your real work before anyone is asked to rely on it.

P4Train

Weeks 8 to 10. A foundation session for everyone, deep dives per department on their own workload, and a leaders' session on governance and spend control. People adopt what solved their Tuesday problem, so that is exactly what we train on.

P5Operate

Ongoing. An Octopus operator stays at your side: tuning workflows, encoding new skills, publishing the marketing cadence, and reporting what the system earned you, until intelligence stops being a project and becomes just how the company works.

0weeks from questionnaire to a running system
0phases: Discover, Design, Build, Train, Operate
0operational brain your whole company works from
The technology, plainly

What we mean by an operational brain.

The engine is a large language model, the same class of technology behind ChatGPT and Claude, but connected to your business instead of the open internet: your documents, your ERP, your project history, your way of writing. It answers from your truth, drafts in your voice, and works inside your walls. Sensitive data can run on local models that never leave your infrastructure.

“Model plus memory plus your systems plus governance. That is the operational brain, and it is the first arm of every engagement.”

See the process on your own workflows.

The first phase is a questionnaire and a workshop. You will know within two weeks exactly what your system looks like.

Start your discovery