working draft — includes my actual working agreement

Scaling solo:
your second brain.

The ceiling on a solo business is your own hours — and the way through it isn’t working more, it’s an executive or virtual assistant with real authority. This is how I work with mine: the trust levels, the shared platform, the mistake protocol, and the actual working agreement we use, free to steal.

Almost all of the pre-work in a service business happens over email. That means it doesn’t have to happen through you.

Authority, visibility,
and one rule.

You are the bottleneck — that’s a diagnosis, not an insult

A solo operator caps out at their own waking hours, and most of what fills those hours isn’t the craft — it’s coordination that happens entirely over email and screens. Which means it can be done by someone else, anywhere. Your first hire isn’t a worker. It’s a second brain.

Trust is built in levels, not leaps

The framework that makes delegation safe: Green — act autonomously (low risk, reversible, routine, easy to correct). Yellow — use judgment and inform me ("Here is what’s happening. I recommend X because Y. Unless you disagree, I’ll proceed."). Red — show me before it goes out (sensitive relationships, money, reputation, anything hard to reverse). You don’t hand over trust; you widen the Green zone month by month.

One platform you both can see

Everything — tasks, notes, decisions, drafts — flows to a single shared platform with visibility for both of you. Access levels start narrow (calendar, tasks, email drafts) and widen as trust compounds. Nothing important lives in someone’s head or a private DM thread; if it isn’t on the platform, it didn’t happen.

The one rule that carries the whole system

I prefer an imperfect early flag over a polished late surprise. Mistakes get surfaced fast, stated plainly — what happened, the impact, what’s already contained, the recommended next step — and it applies in BOTH directions. Your assistant is explicitly allowed to say "I think these two instructions conflict" and "you may be the blocker on this." That’s not overstepping; that’s the job.

High-octane mode needs a filter

Founders think out loud. A single message might contain an assignment, a commitment, an idea, a worry, and background context — and treating it all as tasks buries everyone. Teach your assistant (and their AI tools) to sort each message into: Act, Approval, Confirm, Watch, Context, and Ideas. Excitement is not priority. An idea is not an assignment. Mentioning a person is not permission to contact them.

The rhythm keeps it human

Minimum operating cadence: a brief daily update (bullets, only what’s useful), a protected weekly check-in (decisions, blockers, priorities — and your assistant has explicit permission to put it back on the calendar when you cancel), and a monthly conversation about the ROLE, not the tasks: workload, autonomy, tools, and yes — compensation review as scope grows. Raising it is not disloyal; it’s the system working.

Steal my
working agreement.

Not a template I made for this page — the real document my assistant and I work from: decision and approval levels, the mistake protocol, high-octane message triage, our touchpoint rhythm, and the instructions she shares with her AI tools. Replace the names and it’s yours.

Read the Full Agreement

From bottleneck
to second brain.

trust compounds monthly — start narrower than feels impressive

Set up the visibility

Before the first task is ever delegated.

  • Pick ONE shared platform where tasks, notes, and decisions live — and route everything into it
  • Define starting access: calendar + tasks + drafting first; money and sensitive accounts come later, earned
  • Write your Green list — ten routine things they act on without ever asking
  • Write your Red list — the things you always see first (money, reputation, sensitive relationships, hard-to-reverse)
  • Post the flag rule where you’ll both see it daily: imperfect early flag beats polished late surprise

Delegate for real

Week one.

  • List every task you personally did last week that happened entirely via email or a screen
  • Hand three Green items over completely this week — including the authority to finish them
  • Write the working agreement down and share it — decision levels, mistake protocol, communication style (steal mine below)
  • Set the daily-brief format: what moved, what needs you, what’s blocked — bullets, not reports
  • Resist re-doing their work; correct the system, not the task

Grow the trust

Every month after.

  • Protect the weekly check-in — and honor their permission to re-book it when you cancel
  • Move at least one Yellow item to Green each month — the zone should visibly widen
  • Hold the monthly role conversation: energy, clarity, sustainability, tools — not just tasks
  • Put the scope-and-compensation review on the calendar so it happens by design, not by awkwardness
  • Ask what would help them succeed — access, tools, training, context — before it becomes a problem

Or skip the
expensive drafts.

Every box above is doable solo — I’m not gatekeeping, the whole guide is free on purpose. But solo means you pay full tuition on each lesson: the wrong first hire, the package priced from fear, the move made a year too late. Fail-fast keeps the tuition survivable; it never makes it free.

A mentor doesn’t do the work for you. They’ve already eaten those mistakes, so you get to skip the drafts that only teach you what not to do. The guide hands you the map; someone who’s done it hands you their reps.

That’s the oldest shortcut there is — ask someone who’s been down the road before. Me, or anyone in your corner who has. (No one on your bench yet? Guide No. 6 is about building it.)

the checklist is free. the reps behind it weren’t.

Ask someone who’s done it

Ready to stop being
your own bottleneck?

This guide is free because teach-first is the whole philosophy. If you want help designing the delegation — what to hand off first, how to write your own agreement — the first conversation costs nothing.