Updated 29 September 2026 · by Amy Wilkinson

Approach

Understand. Build. Hand over.

Three stages, written down before anything is built. Every engagement ends with a system your team runs, not a retainer you renew.

01 · Weeks 1 to 2

Understand

The diagnosis. We sit with your team, map how growth runs today and decide which work should run as a system.

  • Where pipeline, content and follow-up leak today
  • Which tools stay, which go, and what connects them
  • A written scope, an order of build, and the price of the first one
02 · Weeks 3 to 8

Build

The first system is built inside your workspace, on your positioning, your voice and your approval rules.

  • Prepared work starts landing in week one of the build, as drafts
  • Your team approves; every send has a named person behind it
  • Results feed back, so the system gets better at your business
03 · Ongoing, if you want it

Hand over

You own the system, the data and the playbook. We stay on only for what your team asks us to.

  • Full documentation and a runbook your team can operate
  • Next systems scoped from what the first one learned
  • No retainer needed to keep it running

Principles

The rules every build follows.

Prepare, never sendPrepare, approve and send are separate permissions. The system holds the first; your team holds the other two.
One memoryEvery system reads the same record of who you are talking to, what went out and what is on the calendar.
Your toolsNothing to migrate. If it does not fit the stack your team already opens every morning, we do not build it.
ReceiptsEverything that goes out is logged with who approved it. You can audit a quarter in an afternoon.
Owned by youCode, prompts, data and playbooks are yours from day one. The engagement can end; the system does not.

The six systems

Each one has its own page.

Questions

Questions about how we work.

How long does an engagement take?
Two weeks for the diagnosis, four to six weeks for the first system, then as long or short as you like. Many teams stop after the first handover and come back for the next system later.
What do you need from my team?
Access to the tools the system will run in, a few hours with the founder in the first two weeks, and one named person who approves what goes out.
What happens when the engagement ends?
Nothing stops. The system runs in your accounts, with a runbook your team can operate. A retainer is optional, for tuning and new work, not for keeping the lights on.

Related

Start here

Let's build what runs without you.

Twenty minutes on how growth runs in your company today. If a build is not the answer, we will tell you what is.

See pricing