Reading

Work it out yourself first,
then decide whether to hire anyoneThe things we end up explaining on every call

These are the parts of a diagnostic conversation that repeat every time. They're written down so you don't have to pay to hear them — and if reading them convinces you not to do this, that's the most useful outcome they have.
Book a diagnosticSee what we've built

Long reads

2

Diagrams

6

Email required

No

A likely conclusion

Don't do this yet

Everything here

Three pieces, three different questions

Ordered by how often each comes up. The first is the most asked.
Long read

Role map

“How much of this job can a machine actually take?”

Support, content and SEO, visual assets, sales development and back office, each split line by line into what goes and what stays. Four tests draw the line: does it have one correct answer, is a mistake reversible, does someone have to sign for it, and is the volume large enough.

  • Five roles, side by side
  • The four things left with people
  • Why “so cut two people” is a broken inference
Read it →
Long read

Five common mistakes

“Where did it go wrong for everyone else?”

Five ideas that sound entirely reasonable and stop projects from finishing — cutting staff, doing it all at once, expecting the AI to sort out a messy process, running unattended, and buying a tool. Plus the four preconditions to check before starting.

  • Five ideas that kill projects
  • Three moments where they die
  • When to stop rather than start
Read it →
Six pictures

Diagrams

“What does “AI automation” actually refer to?”

Six diagrams, one question each: what a workflow looks like, the five places it breaks, the three ways data can flow, where human checkpoints belong, how a knowledge base avoids inventing answers, and the four delivery stages. Align the vocabulary first and the call doesn't start with definitions.

  • The six actions in a workflow
  • The five places projects break
  • Self-hosted vs public SaaS, drawn
Read it →

Pick by where you are

Not sure which to start with

The same material, but which piece to read first depends on the seat you're sitting in.

We haven't decided whether to do this at all

Seeing what goes wrong is more useful than seeing what's possible

Read it →

Our team thinks they're being replaced

Getting the framing right matters more than getting the system in

Read it →

I have to explain this to a board or a CTO

Six pictures land faster than a proposal document

Read it →

If you'd rather see what has actually been built than read about method, the case studies are here →

Next

None of this can tell you about your own process

These pages can tell you which kinds of work suit automation. They can't tell you whether this specific thing in your company is worth doing — that depends on how your process actually runs today. The diagnostic fee is credited in full against the project.
Book a diagnosticStart with one module