Alex PooleSystems

Your business runs on what is in people's heads.

That does not scale, and it does not survive them leaving.

We architect the operating system underneath the business. One source of truth. Rules that hold when nobody is watching. Work that runs as a loop instead of a scramble. Then AI on top of all of it.

Score your operation

What you actually have right now.

Most businesses do not have a system. They have people who remember.

The quote that only Dave knows how to price. The client history in a WhatsApp thread. The onboarding that happens differently every time because it lives in a head, not a file. The deal that went quiet and nobody noticed for six weeks.

None of that is a discipline problem. It is a structural one. The business grew. The way it runs did not.

Read Rules Run

Everything we build runs on one framework.

  • READ

    For every fact the business depends on, there is exactly one place that owns the answer, it is current, and the system says so rather than guessing.

  • RULES

    Every claim the business makes about how it behaves is written down, in one place, and enforced by the system instead of by memory.

  • RUN

    The work itself. Fed by READ and RULES, feeding straight back into both, so the source of truth gets better every time somebody uses it.

Underneath the three sit four non-negotiables. Declare. Own. Record. Review. Every rule we write is one of those four, seen from closer up. There is no fifth.

Read the framework

What we build.

Six systems. Every one of them reports into the same source of truth.

One source of truth

The documents the business runs on, in one place, added to constantly, so it is the same answer everywhere.

Rules that hold without you

Standards, SOPs and decisions on the record, enforced by the system, not by who happens to be in the room.

Nothing falls through

Every project, deal and task has an owner, a live status and one next action.

Customers tracked end to end

First contact to renewal. Nothing dropped after the close.

Business operations on autopilot

Billing, invoicing, cash flow, forecasting, the routine admin.

Material by machine

Decks, SOPs, training and marketing produced by an engine, not rebuilt by hand.

How an engagement runs.

  1. 01

    Diagnose

    Score the operation. Find where it leaks and in what order it should be fixed.

  2. 02

    Architect

    Design the system. One source of truth, the rules that govern it, and where AI does the work.

  3. 03

    Build and embed

    Build it, migrate the knowledge out of heads, and get your team actually using it.

  4. 04

    Run and govern

    Keep it current, so standards do not decay the moment attention moves.

Take one stage or take the whole arc.

This is for you if

  • You have outgrown the spreadsheets and the off-the-shelf apps.
  • Your systems do not talk to each other, and one clear picture means somebody stitching it by hand.
  • The big ERP and the big-name consultancy both felt too heavy, too slow and too generic for how you actually run.
  • You want AI working across everything, but there is nothing clean for it to stand on yet.

This is not for you if

  • You are still looking for product-market fit.
  • You want a chatbot, not a system.
  • You want a deck to file away, not architecture that ships.
  • Every decision needs a committee. Owner-led means you can just decide.

7 questions. About 2 minutes.

You will see where you sit and the two systems leaking most, before we ever speak.

Score your operation