Everything Runs Through Me

By the end, this is true:

✅ You named the work only you should do

✅ You named the work someone else should own

✅ You transferred ownership of at least one recurring responsibility, fully

✅ You stopped being the approval step for everything

✅ Something important moved forward without you touching it

⏱ About 1.5 hours to build. 30 days to prove it runs.

The one metric that matters (next 30 days): the number of recurring responsibilities you fully own that you no longer do. Not tasks delegated for a day. Ownership transferred for good.

You didn't start a business to end up here.

You started it to be free. And somewhere along the way it flipped, and now you're the most trapped person you know. The phone doesn't stop. You took a vacation last year and spent it on your laptop in the hotel bathroom so nobody would see. You wake up at 2am remembering the thing only you can handle. Every plate in the air is one you're personally spinning, and the second you stop, they fall.

And here's the part you don't say out loud. You're a little resentful. You built this thing so you'd own your time, and instead it owns you. You can't get sick. You can't fully unplug. You can't even take a Tuesday off without the whole thing quietly backing up behind you. You're the founder, and you have the one job you can never leave.

Underneath the resentment is the guilt, because you know it's your own doing. Nobody's making you hold all of it. You keep telling yourself you'll delegate when things slow down, and things never slow down, and the truth is you wouldn't let go even if they did.

And under all of it is something quieter. You've become the person everything runs through. People need you. You're indispensable. And somewhere in there, being needed started to feel like who you are. You don't entirely know who you'd be if the business didn't need you for everything.

Almost every founder hits this exact wall, and almost none of them get out, because everyone treats it like a time problem. It's not a time problem. You don't need to get more efficient at holding everything. You need to stop holding it. That's a different thing, and it's harder, and it's what this playbook is actually for.

You can put it down. Not all at once, and not perfectly. But you can stop being the thing everything waits on. Let's get you out.

We do this in a specific order. You'll sort the work by hand first, decide what's really yours and what never should have been, before we build anything, because you can't hand off cleanly what you haven't honestly sorted.

You already know you're the bottleneck. That's why you're here. The question is why you stay one, because you're smart enough to see the problem and you still haven't fixed it.

Here's the honest answer. It's not that there's no one to hand things to. It's that handing things off feels worse than just doing them. You hand something over, they do it differently, it's not quite right, you fix it, and you conclude it's faster to do it yourself. So you take it back. And now you've trained yourself and everyone around you that everything comes back to you. You didn't fail to delegate because you couldn't. You took it back because letting go felt worse than the work.

So the business grows only as fast as you can personally touch everything, which means it stops growing the day you run out of hours. You become the ceiling. Not the market, not the team, you.

This playbook is about transferring ownership, not dumping tasks. Dumping a task means they do the thing and bring it back to you. Transferring ownership means they own the outcome and you stop touching it. That difference is the whole game.

And before we start, the single most important thing to make peace with: you will never find someone who replaces you at 100%. Not your work ethic, not how much you care, not how you do it. Never. The people who'd give you 100% are out building their own thing, that's exactly why they're not working for you. So stop looking for that person. They don't exist. What you're looking for is someone who gives you 80%. Find people at 80% and you've got winners. Because 80% they fully own beats 100% that stays chained to you forever. Hold onto that, it's the thing that makes everything else in here possible.

Five plays, each removes a reason work keeps bouncing back to you. Do them in order. Build each one before you move on.

⏱ 5 minutes

Make sure you're in the right playbook. This one is about getting work off your plate, transferring ownership of things you currently do. It's not about hiring (that's a later playbook, and most founders think they need to hire when they actually need to delegate first) and it's not about building systems/documentation (that's also separate). If your problem is "I'm drowning and everything needs me," you're home.

Answer honestly:

• If you took two weeks fully off, no phone, would the business keep running or quietly stall?

• How many decisions a day wait on you that don't actually need you?

• When you've handed things off before, did they stay handed off, or did they bounce back to you?

• Be honest: do you keep work because no one else can do it, or because you don't trust it done any way but yours?

If the business runs through you and you can't step away without it stalling, this is your playbook.

✅ Before you move on: Post in the room, if you disappeared for two weeks, what's the first thing that would break? That thing is the most stuck to you. That's where we start.

Quick one before the plays, because some of you are reading "transfer ownership" and thinking, to who? It's just me.

Here's the reframe that unlocks it. Delegation isn't "hire someone." Delegation is "stop being the one who does it." Those aren't the same thing. A person is one place work can go. It's not the only one, and for a lot of you it's not even the first one.

You've already been delegating in this program. You just didn't call it that. Every Engine you built took work off your plate without a single hire. The Content Engine owns the blank page now, not you. The Outreach Engine writes the openers you used to stare at. The Sales Engine handles the follow-ups you used to drop. That's delegation. You transferred the doing to a system, and it doesn't call in sick, doesn't need managing, doesn't bounce it back to you. If you ran those playbooks, you already own tools doing work you used to do by hand. That's the first team you ever hired.

So for the founder with no people, the order is this.

First, delegate to the tools you've already built. Anything repeatable, content, follow-up, outreach, first-draft anything, hand it to a system. You've seen how. That alone claws back hours and it costs you nothing but the setup.

Second, delegate the next layer to contractors, not employees. You don't need to hire someone full-time to get work off your plate. A bookkeeper, a VA, an editor, a fractional whoever, for the specific recurring things a tool can't own. Same rule as the whole playbook: transfer the outcome, not the task. A contractor who owns your books is delegation. It doesn't require building an org.

Third, only then hire a person. And when you do, you'll do it right, because you'll already know exactly what ownership you're handing over, you defined it by offloading it to tools and contractors first. That's the correct order, and it's the reason the Hiring playbook comes after this one. Most founders hire too early, to a vague role, and end up managing a person instead of running a business. You won't, because you'll have delegated everything a system or a contractor could own before you ever put someone on payroll.

The whole point: you are never too small to delegate. You're only too small to hire. Those are different. Start with the tools you already have, add contractors for the rest, and let hiring be the last step, not the first. Every play that follows works whether "they" is a tool, a contractor, or an employee. The principles don't change. Only who's on the other end does.

⏱ 25 minutes

Why this matters. You can't hand off what you haven't sorted. Right now everything feels like it needs you, because you've never separated the work only you can do from the work you're just holding onto out of habit. Most of what's on your plate isn't founder work. It's work you never let go of. This play sorts it.

Do this now.

1. List what you actually do in a week. Brain-dump everything, the real list, including the small recurring stuff that eats your day.

2. Mark each one: is this work only I can do, or work I'm just keeping? "Only I can do" is a short list, the vision, the key relationships, the decisions that genuinely need the founder. Be ruthless, most founders mark far too much as "only me." If someone could be taught to do it in 90 days, it's not only-you work.

3. Circle the biggest time-eater in the "just keeping" pile. That's your first transfer. Not the scariest one, the one stealing the most hours.

Now you can see it. The list of what you're holding that you don't need to be.

Common mistakes.

• Marking everything "only I can do." That's the bottleneck talking. If it can be taught, it can be transferred.

• Starting with the scariest thing to hand off. Start with the biggest time-eater that's lowest risk. Build the muscle first.

• Confusing "I'm best at it" with "only I can do it." You're best at lots of things you still shouldn't be doing.

✅ Proof to move on: Post your "only me" list and the one recurring responsibility you're transferring first. Continue.

⏱ 25 minutes

Why this matters. Most delegation fails because the founder hands off a task, not an outcome, and stays on the hook. "Can you do this for me" keeps you the owner, they're just helping you with your job. Transferring ownership means they own the result, not the steps. That's the difference between something leaving your plate and something temporarily borrowed from your plate.

Do this now. For the responsibility you picked in Play 1:

1. Define the outcome, not the task. Not "send the invoices," but "you own billing, invoices go out by the 5th, follow-ups happen, we get paid, I don't think about it." Hand them the result they're responsible for.

2. Give them the context and the boundaries, then the authority. What does good look like, what's the budget or limit, when do they actually need to check with you (make this list short), and then, the part founders skip, tell them they own it. They decide, they run it, they don't ask permission for the normal stuff.

3. Set the check-in, then get out of the way. One recurring check-in to review the outcome, not the steps. Between check-ins, it's theirs.

Now you've handed off a result they own, not a chore they return to you.

⚡ You're writing this handoff by hand first, on purpose. You need to feel the difference between dumping a task and transferring an outcome before a tool does it for you. Once you've done one, we build the tool that turns "here's the messy thing I do" into a clean ownership handoff in minutes, so offloading the next responsibility takes ten minutes instead of an afternoon. We build it at the end.

Common mistakes.

• Handing off the task but keeping the outcome. Then it's still yours. Transfer the result.

• Dumping it with no context or authority, then being surprised it fails. Give them what they need and the power to act.

• Requiring approval for everything. That just makes you the bottleneck inside the delegation. Define what needs you (little) and let them own the rest.

✅ Proof to move on: Post your ownership handoff, the outcome, boundaries, and check-in for the thing you're transferring. Continue.

⏱ 15 minutes

Why this matters. This is the real unlock, the emotional center of the whole playbook. Everything before it is logistics. Everything after it is maintenance. This is where delegation actually happens. They will do it differently than you. Slower at first, in a different order, not exactly how you'd do it. And the instinct that kills every delegation is to step in and correct it back to your way. If "handed off" secretly means "does it exactly like me," you haven't delegated, you've installed a copy of yourself that needs constant correction. The fix: let them own the how, as long as the outcome's right.

Do this now.

1. Decide what actually matters: the outcome or the method. For almost everything, it's the outcome. If the invoices go out and you get paid, does it matter that they organized it differently than you would? Usually no. Separate "this is wrong" from "this isn't how I'd do it." Only the first one is a real problem.

2. Let the first few be imperfect. Their version will be rough early because they're learning, the same way you were once. If you swoop in and fix it, they never learn and it bounces back to you forever. Let them be a B+ and get better, instead of needing you to make it an A every time. Remember the 80% rule: you're not looking for someone who does it as well as you, that person doesn't exist, they're off building their own thing. You're looking for 80%. If they own the outcome and hit 80% of your standard, that's a win, not a problem to fix. The gap between their 80% and your 100% is the price of freedom, and it's the cheapest thing you'll ever buy.

3. Correct outcomes, not styles. When you check in, react to whether the result was right, not whether they did it your way. Coach the outcome. Leave the method alone unless the method is causing the bad outcome.

This is where you actually let go. Not when you hand it off, when you let them do it differently and don't take it back.

⚡ Same tool from Play 2. Defining what a good outcome looks like, clearly enough that you can judge against it instead of your gut, is exactly what the Handoff Builder does. We build it at the end.

Common mistakes.

• Correcting style instead of outcome. If the result's right, leave the method alone.

• Taking it back the first time it's imperfect. Imperfect and improving beats perfect and dependent on you.

• Calling it delegation when it's really supervision. If they need you for every step, you didn't transfer ownership.

✅ Proof to move on: Post the thing you let someone do their own way this week, and what happened. Continue.

⏱ 20 minutes

Why this matters. Play 3 told you to let them do it their way, to let them be at 80%, to stop correcting style. And your gut is already fighting back, because you've been burned. You handed something off once, it blew up, you took it back, and that's half the reason you hold everything now. So let's be honest about the part the delegation advice usually skips: sometimes they really do drop it. Not "did it differently." Actually failed. The outcome didn't happen.

The mistake isn't that they dropped it. The mistake is what most founders conclude when they do, "see, I can't delegate, I have to do it myself." That's the wrong lesson, and it's the one that keeps you buried for another five years. A dropped handoff isn't proof delegation doesn't work. It's information. Your job is to read it correctly, because there are three very different reasons work fails, and they have three completely different fixes. Confuse them and you either fire good people or keep bad ones.

Do this now. When something you handed off fails, run it through these three before you react.

1. Was it a bad handoff? Be honest first, because this is the most common one and it's on you. Did they actually know what the outcome was? Did they have the authority and the context to hit it, or did you hand them a task with no real ownership and no power to act? Most "they dropped it" is really "I never handed it off cleanly." If the handoff was vague, it's not their failure, it's yours, and the fix is to redo the handoff properly (Play 2), not to take the work back. Run it through your Handoff Builder and hand it again, clean this time.

2. Is it the right person, still learning? If the handoff was clean and they still missed, ask whether this is early reps. New ownership is rough at first, the same way you were rough once. A miss in week two isn't a verdict, it's a learning curve. The fix here is coaching, not reclaiming. You point at the outcome that got missed, you ask what they'd do differently, you let them run it again. If they're getting better each time, that's the right person mid-climb. Stay with it. Taking it back now trains them to hand everything to you, which is the exact thing you're escaping.

3. Is it the wrong person? Here's the one nobody says out loud: sometimes it's a clean handoff, real coaching, real time, and they still don't own it. They keep bringing it back. They don't improve. They wait to be told. If you've handed it cleanly, given it real time, coached the outcome, and it's still not landing, that's not a delegation problem, that's a personnel problem, and no amount of you trusting harder fixes it. The fix isn't taking the work back onto your plate. It's accepting you have the wrong person in that seat and moving toward the right one. Taking it back is you covering for a bad fit forever. Don't.

The trap to see clearly: founders take work back for all three, and taking it back is the wrong answer for all three. Bad handoff, redo the handoff. Right person learning, coach them. Wrong person, replace them. In none of those cases is "do it myself forever" the fix. That's just the bottleneck reinstalling itself and calling it caution.

Common mistakes.

• Concluding "I can't delegate" from one dropped ball. One failure is data, not a verdict. Read it, don't retreat.

• Blaming the person when the handoff was vague. Check your own handoff first. Usually the gap is there.

• Coaching a wrong-fit person forever because firing feels worse than carrying the work. Carrying it forever is more expensive than the hard conversation. You're just paying in a currency you don't notice, your own time.

• Taking it back "just this once." That once becomes permanent. The work is yours again and you taught everyone it always comes back to you.

✅ Proof to move on: Post one thing that got dropped or done wrong, which of the three it actually was, and what you're doing about it (re-handoff, coach, or replace), not taking it back.

⏱ 20 minutes

Why this matters. Even after you hand things off, you can stay the bottleneck by being the approval step for everything. Every decision routes back through you for a yes. That's a slower, sneakier version of doing it all yourself, the work moves, but it all freezes waiting on your sign-off. The fix: stop being the default approver. Push decision-making authority down so things move without you.

Do this now.

1. Find your approval chokepoints. What decisions wait on your yes? List them. Most of them don't need you, you're just the habit.

2. Set decision rules instead of decisions. Replace "ask me every time" with a rule they can run themselves. "Anything under $500, just do it." "Refunds under X, your call." "Standard requests, handle them, only flag the weird ones." Now the decision happens without you, because you decided once instead of every time.

3. Make "don't ask me, decide it" the default. Tell your people: for anything inside the rules, I don't want to be asked, I want you to decide. Asking me is the slow path now. This feels backwards and it's the whole point.

Now work doesn't pile up at your desk waiting for a yes. It moves.

Common mistakes.

• Keeping approval power because it feels safer. It feels safer and it makes you the bottleneck. Set the rule and let go.

• Vague rules that still require judgment calls back to you. Make them clear enough to run without you.

• Punishing people for using the authority you gave them. If you gave them the call and they made a reasonable one, back them, or they'll just start asking again.

✅ Proof to move on: Post one approval you turned into a rule, so it no longer waits on you. Continue.

⏱ 15 minutes

Why this matters. Transferred work creeps back. A busy week, a dropped ball, and you quietly take it back "just for now," and now it's yours again. This play makes the handoff permanent by building the habit that keeps you out of it, so you don't slide back into being the bottleneck the first time things get hard.

Do this now.

1. Make the rule: it doesn't come back to me. When something handed off goes wrong, the fix is to coach the owner, not to take it back. Taking it back is the easy choice that re-installs you as the bottleneck. Resist it. Fix the ownership, don't reclaim the work. And when you feel the urge to take it back because "they're just not doing it like I would", that's the 80% talking. Of course they're not doing it like you. Nobody will. 80% they own beats 100% you're chained to. Coach them up, don't take it back.

2. Run one recurring "what can come off my plate next" review. Monthly, look at your week, find the next thing that's crept on or never left, and transfer it. Delegation isn't a one-time event, it's an ongoing habit of staying out of the work.

3. Track the one number: recurring responsibilities you fully own that you no longer do. Watch it grow. If it's stuck, you've stopped transferring or you're taking things back. That number is whether you're actually getting out of the way.

Now letting go is a habit, not a one-time act of courage. You keep getting freer instead of sliding back.

Common mistakes.

• Taking work back the first time it wobbles. Coach the owner instead. Taking it back undoes everything.

• Treating delegation as done after one handoff. It's a habit. Keep transferring.

• Tracking how busy you are instead of how much you've transferred. Busy is the old scoreboard. Transferred ownership is the new one.

✅ Proof to move on: Post your count of responsibilities you've fully transferred, and your recurring "what's next" review on the calendar. Then you've built the machine.

Now build the tool that makes offloading fast.

You just did the hard version by hand. You took something in your head and turned it into a clean handoff, the outcome, the boundaries, the check-in. It probably took you a while, because turning "the messy thing I do" into something another person can own is real work.

Here's the problem. You've got a whole list of things to offload from Play 1, and if each one takes an afternoon, you'll do two and quit. The offloading itself becomes a bottleneck. So we build the tool that does the turning-into-a-handoff part for you, so getting the next thing off your plate takes ten minutes instead of an afternoon, and "I'll delegate it later" stops being an excuse.

You build it once. You own it. Ten minutes. Claude or ChatGPT, paid tier.

Step 1 — Make the container. In Claude, a new Project. In ChatGPT, a new custom GPT. Either works.

Step 2 — Give it its instructions. Paste this in:

You are my Handoff Builder. Your job is to help me get work off my plate for good by turning a messy description of something I do into a clean ownership handoff someone else can fully own.

I'm going to describe something I currently do, probably in a messy, incomplete way, the way it lives in my head. Your job is to turn it into a handoff built around ownership of an outcome, not a list of tasks.

For whatever I describe, produce:

1. The outcome. One clear sentence describing the result this person now owns, written as an outcome they're responsible for, not a task they perform. "You own billing, invoices out by the 5th, follow-ups happen, we get paid, I don't think about it," not "send the invoices."

2. What good looks like. A short, concrete description of a successful result, so they can judge their own work against a standard instead of guessing.

3. The boundaries and authority. What they can decide on their own, any limits (budget, scope), and the short list of things that actually need to come to me. Bias toward giving them authority. Keep the "check with me" list as small as honestly possible.

4. The check-in. One recurring check-in focused on reviewing the outcome, not the steps.

Rules: Push me toward transferring outcomes, not dumping tasks. If what I describe is really me trying to keep control while pretending to delegate, call it out. If I've made the "check with me" list too long, tell me, that's me staying the bottleneck. Ask me for any detail you need. Keep it tight and usable, something I could hand a person today.

Step 3 — Feed it context (optional but better). Drop in your "only me" list from Play 1 and the handoff you wrote by hand in Play 2. Now it knows your business and it has a model of a good handoff to match. In Claude, add them as files. In ChatGPT, upload to the knowledge.

Step 4 — Test it. Take the next thing on your offload list. Describe it messily, out loud, the way you'd explain it to a friend. Watch it come back as a clean handoff. If the outcome's right and the "check with me" list is short, you're done. Hand it to a person this week.

That's your Handoff Builder. From here on, every time you want something off your plate, you describe it once and it hands you back the ownership doc. The thing that used to feel like too much work to delegate now takes ten minutes. Which means you'll actually do it, again and again, until the business stops running through you.

You built the delegation habit. Now you prove it runs.

For 30 days, transfer ownership, let people do it their way, turn approvals into rules, and refuse to take work back. Post your wins to the Proof Wall, things you handed off, decisions that happened without you, the first time something important moved while you weren't looking.

The outcome was never "delegate a few tasks." It's that work stops routing through you, so the business can grow past your personal capacity. Either you transferred ownership or you didn't. The freedom is the byproduct.

Honest part.

You understand everything in here. You know you should delegate. You've known for years. And you still hold on, you still take it back, you're still the bottleneck. So it's not knowledge. It's something underneath.

You're protecting your sense of being needed.

Letting go means finding out the business can run without you touching everything. And some quiet part of you doesn't want to find that out. Being the person everything runs through feels like mattering. It feels like being indispensable. If you hand it all off and the place runs fine without you, what does that say about how essential you actually are? So you stay in the middle of everything and call it being responsible, being thorough, having high standards. Underneath, you're protecting the identity of being the one who's needed.

And there's a loneliness in it you've probably never said to anyone. Being the only one who can do it all means you're carrying it alone. Nobody else fully understands the weight, nobody can take it from you, and over the years that aloneness stopped feeling like a burden and started feeling like who you are. The one who carries it. The one it all depends on. Letting go doesn't just mean giving up tasks. It means giving up that identity, and that's why it's so much harder than it looks on paper. You're not afraid they'll do it wrong. You're afraid of who you are if you're not the one holding everything.

Here's the thing you've got backwards. A business that needs you for everything isn't a sign of how important you are. It's a cage you built. The founders who matter most aren't the ones doing the most, they're the ones who built something that runs without them and freed themselves to work on what only they can do. Being needed for everything isn't power. It's the thing keeping you small. And the version of you on the other side of letting go, the one who isn't buried, who has room to think, who actually likes the business again, that person was always who you were trying to become. You just have to put this down to meet him.

So the question: what are you protecting by staying the person everything runs through, the business, or the feeling of being indispensable?

Answer it honestly in the room. Then hand off the next thing and don't take it back, even when it wobbles. The handoff process was never really the bottleneck. It was how we got you to face letting go.

If you built the habit and ran it for 30 days, you started getting out of your own way. You built your first Scale Machine, the business is no longer capped at what you can personally touch. Most founders never do this. They stay the bottleneck forever and call it dedication.

Now notice what surfaces next:

• "I've delegated everything I can to the people I have, and I'm still short-handed." → Now hiring makes sense, because now you know exactly what ownership you're hiring for. That's the next playbook (in development).

• "Things I hand off keep breaking because there's no system, it's all in people's heads." → That's a systems and documentation bottleneck. Scale Engine.

• "My team owns their work but they're not stepping up as leaders." → That's a leadership bottleneck.

You don't graduate. You cleared the first bottleneck that was capping your growth, you. Now the Scale Engine opens up: hiring for defined ownership, building systems, and leading a team that runs without you.

Your move: Post in the room, now that things can run without you touching them, what's the next thing stopping you from scaling? Name it. That's the start of the next one.