01In plain terms

What this rung really is

Level 10 is the top of the ladder, and it flips the whole relationship. You stop sitting at the keyboard running one agent at a time. Instead you run a fleet — many agents, each owning a job — and you direct it the way an owner directs a team: you say what you want, and it goes to work. By now every rung below is doing the work; your job is to point it.

The proof of this rung is that you can command from anywhere, on your phone, in one line. You send the intent — not the keystrokes — and the fleet executes while you're away from the desk; then it rolls its own health up into a single briefing you read in a minute. The last move is the biggest: you teach the climb, so the way you work becomes how the whole agency runs.

02The move

Command the fleet — one line of intent

The move at the top of the ladder is command: send the outcome you want, from your phone, and the fleet executes on the rails you built — you direct, you don't operate.

How it all connects
Your full setuprungs 1–9 behind itYOUR FLEET — MANY AGENTS, EACH A JOBsend intentdone /needs youYou, on your phoneone line of intentYour fleetruns it, unattendedAgent 1owns a jobAgent 2owns a jobAgent 3owns a jobOne briefingrolled up for youYou command the whole fleet from your phone

This rung sits on everything you wired in rungs 1–9. You add a fleet you command remotely on top — you don't start over.

03Set it up, step by step

Do this rung, for real

Everything you need is here — no tabs to chase. First, the jargon this rung throws at you, in plain words. Then the steps, with the exact things to paste or say.

A real way an agency owner would actually command the fleet

It's Saturday. You're not at your desk. A client's rankings slipped overnight, three other clients are due for their monthly content, and a new prospect wants an audit by Monday. From your phone you send one line: handle it. The fleet picks it up — one agent diagnoses the ranking drop, others draft and queue the monthly content per each client's brief, another builds the prospect audit — all on the rails you set on the rungs below. Sunday morning, one briefing on your phone tells you what ran, what shipped, and the single thing that needs your call. You ran an agency's worth of work without opening a laptop. That's L10: you command, you don't operate.

What is

Intent, not keystrokes

Telling the fleet the OUTCOME you want in plain words — 'handle the slipped client, ship this month's content' — and letting it decide the steps. You stopped typing commands a long way down the ladder; here you stop typing the plan too.

Why it matters here — It's the only way one person scales past one agent. When you brief outcomes, the fleet can run ten jobs at once without you sequencing any of them — your leverage stops being your typing speed and becomes your judgment about what's worth doing.

What is

Commanding from your phone

The fleet runs on an always-on machine you set up on the rungs below; your phone is just the trigger surface. You send the intent from anywhere and read the result anywhere — the desk is optional, not required.

Why it matters here — This is what makes it real freedom instead of a fancier desk job. The work no longer needs you in the chair — it needs you to decide. You can be away from the keyboard and the agency still moves.

01

Send the fleet an intent from your phone

From your phone, send the always-on fleet a single line that names the outcome, not the steps — the way you'd brief a trusted lead, not a junior. The rails you built on the rungs below decide who picks up what.

Say it out loud

“The Hartley account's rankings dropped overnight — diagnose it. And ship this month's content for all three retainer clients off their briefs. Flag me only if something needs a call.”

02

Let it run unattended, on your rails

Walk away. Multiple agents take the jobs in parallel and execute against the gates, specs, and memory you set lower on the ladder — so 'unattended' means on-rails, not unsupervised-and-hoping. You're not watching; the rails are.

03

Read one briefing, make the one call

When you come back, you don't dig through logs — the fleet rolls its own run up into a single briefing: what ran, what shipped, what's blocked. You read it in a minute and make the one or two judgment calls only you can make. That loop — command, run, brief, decide — is the operating model you then teach the rest of your team.

04What good looks like

How you know it's working

Before

Before L10: you're still the bottleneck. Even with great agents, work waits on you to be at the desk, to kick off each run, to check each result. Scale means more hours from you.

After — a good L1 setup looks like
  • You triggered real client work from your phone, away from the desk — the fleet picked it up and ran.
  • Several jobs ran in parallel, unattended, and stayed on the rails you set — not babysat.
  • You read one rolled-up briefing instead of watching runs or digging through logs.
  • The way you work is now teachable — the climb itself, not just the output, is how your agency operates.

Make it stick. Pick one recurring multi-client job you currently start by hand each week — and next time, trigger it from your phone as an intent and let the fleet run it. When the briefing comes back clean, you've moved from operating the work to commanding it.

05The skills that get you here

Our skills for this rung

Linked items are founding-circle skills — clone the repo and run ./install.sh from the skills folder. Unlinked items are practices you build by doing.

06Your checkpoint

Commander-level: an unattended fleet you direct remotely. Share the telemetry.

Clear this and you've genuinely cleared the rung — not read about it. Keep the proof; it's how you place yourself on the ladder.