The method

Four steps, then it runs without me.

The same sequence whether you buy one department or five. Nothing gets built before the structure is agreed in writing.

1

Intake

You describe the work that repeats, the way you would explain it to a new hire. I ask what must never go out without your approval, and which AI tools you already pay for. Ten to fifteen minutes.

2

Design

Departments, roles, handoffs and review points, mapped before anything is built. You see the map and sign off on it. This is what the free consult is on its own.

3

Build

Agents, team leads and gates, configured on the tools you already use: Claude Code, ChatGPT, OpenAI Codex CLI. No new subscription to me.

4

Handover

A plain-language guide so your team can run it, change it and keep it going without me.

YOUMarketingteam leadOperationsteam leadITteam leadProductteam leadAPPROVAL GATEback to you
The chain of command

Four checks before anything reaches you

Each layer exists because the layer below it can be wrong. The point is that being wrong is caught inside the structure rather than by you, afterwards.

Agents do the work

Each one has a defined job, not a general instruction to be helpful. A narrow job is a job you can check.

A team lead reviews it

Every department has one. It reads its own agents' output and passes up only what holds up.

An auditor stops what is not ready

The last check before anything leaves the department, for quality rather than permission.

You decide at the gate

Three triggers, listed below. Your yes is the only thing that releases them.

The three triggers

What always waits for your yes

You set these boundaries before I build, and the gate is built into the structure rather than left to anyone's memory.

Waits for you

Spends money

A renewal, a subscription, an ad buy, a job board fee. The agent prepares it, prices it, and stops. You see the amount before anything is charged.

Waits for you

Reaches a customer

An email to your list, a reply to a review, a message to a client. It gets written and reviewed inside the organization, then waits at the gate.

Waits for you

Cannot be undone

Deleting accounts, granting access, cancelling a service. Anything with no second chance is asked, not assumed.

Approvals arrive in your portal with the reason attached: what was proposed, who raised it, and what it costs. You approve, or you reject with a note that goes back into the organization.
Deliverables

What you get, every engagement

Four artifacts. The same four, whether you start with a consult or a full build. They are files, and they are yours. Nothing here is licensed back to me.

A map of your process

Who does what, in what order, and where the work gets checked.

Setup files

Configured for Claude Code, ChatGPT or OpenAI Codex CLI. Not another subscription to buy.

A failure plan

What happens when something breaks, and who picks it back up.

A plain-language guide

Written for the person who runs it, not for a developer.

Tell me the process that's eating your week.

I'll map it out before you commit to anything.

Get in touch