Founders who stay the bottleneck usually aren't short on good intentions or good people. They're short on a system for letting go. My view: a handoff without a written standard, clear authority and a release date is a loan, and you'll call it back the first bad week.
Knowing you're the bottleneck is step one. This is about what comes after.
The problem: delegation as a single conversation
Here's the pattern I see constantly. The founder finally decides to hand something off. They pick a strong person, have a good conversation, and say "this is yours now."
Two weeks later, something goes sideways. A client complains, a number slips, a decision gets made differently than the founder would have made it. The founder steps back in "just this once." Then again. Within a month the new owner has stopped making decisions, because they've learned the founder is going to remake them anyway.
The founder concludes that person wasn't ready. Usually the handoff wasn't ready.
Five kinds of dependency
Before you build handoffs, get specific about what kind of dependency you're dealing with. They transfer differently.
- Decision: Things that need your yes. Pricing exceptions, hires, spend.
- Operational: Work you personally do. Reviewing proposals, running a meeting.
- Relationship: People who only want to talk to you. Key customers, partners, investors.
- Knowledge: Things only you know. How a deal was structured, why a process exists.
- Leadership: People who look to you, not their manager, for direction.
Relationship and knowledge dependencies take the longest. Picture your largest customer, the one whose CEO still texts you directly. That relationship doesn't transfer because you sent a nice intro email. It transfers when the customer has watched the new owner deliver, more than once, with you in the background.
Once you've listed your dependencies, map each one on two questions: how much does it matter to the business, and how ready is someone to take it? Start where impact is high and readiness is already decent. That's your first handoff.
The five-part handoff
For every handoff, write down five things.
- Owner. One name. Not a team, not "ops."
- Standard. What good enough looks like, in results someone could observe. Not "the way I'd do it."
- Authority. What they can decide without you. Put a number on it where you can.
- Control. How you'll know it's working without hovering. A weekly number, a short review, an exception report.
- Release date. The day your involvement ends.
The release date is the one founders resist. Without it, "I'll stay close for a while" turns into permanent co-ownership. A date turns a feeling into a commitment.
Here are the exact words: "As of [date], this is yours. Here's what good looks like. You can decide anything up to [amount] without me. We'll look at [the number] together every Friday for 4 weeks. After that, I'm out unless you pull me in."
Crawl before we walk
A handoff isn't a switch. I use four stages:
- Watch. They sit with you while you do it.
- Together. You do it side by side, and you say your judgment calls out loud. Why this price, why this answer, why you pushed back.
- Supervised. They do it; you watch and only speak at the end.
- Released. The date arrives and you step out.
Stage 2 is where most of the transfer actually happens. Founders carry their judgment in their heads. Saying it out loud is how it gets into someone else's.
Expect friction, and sort it
A strong person will do it differently than you. That's the point of hiring strong people. When it happens, sort the decision into one of two buckets before you react.
Actually wrong: It breaks the standard you wrote down or crosses a line that matters. Step in, explain, fix the standard if it was unclear.
Just different: It meets the standard, just not your way. Leave it alone.
Most founder re-entries happen in the second bucket.
Count the re-entries
Now track one number weekly: how many times you walked back into something you handed off. Log each one and the reason.
The log does two things. It shows you your pattern (most founders re-enter the same 1 or 2 areas). And it keeps you honest, because "I was just helping" looks different when it's the fourth entry that week.
Over 30, 60 and 90 days, that number should fall. If it doesn't, look at which of the five parts is missing. It's usually the standard or the authority.
What to do this week
Pick one dependency. Not ten. Write the five parts on a single page, set a release date 60 to 90 days out, and have the conversation using the words above. Then start the re-entry log on Monday.
Founder's Trap OS
The Founder's Trap OS is a free tool that runs this whole process. It helps you score your dependencies across the five types, map them by impact and readiness, define the owner, standard, authority, control and release date for each, and build a 30/60/90-day plan. Then it tracks your weekly progress and re-entries so you can see your independence actually grow.
Open the Founder's Trap OS →Get the next lesson in your inbox
Short, practical lessons like this one for founders running $1M–$20M companies, plus every new free tool before anyone else.
If this is the call in front of you, let's talk it through.
A focused 30-minute conversation. No pitch. Just a direct discussion about the decision and whether I can help.
Book a call with Danny →
Danny Feldman is a 3× founder and the advisor behind Feldman Advisory. He founded and scaled Stellar to $100M in annual revenue across 15 states, raised $55M+ as a founder, and used AI to double revenue before exiting to private equity. Earlier, he recruited and trained 55,000+ sales reps at Cutco and grew a division from 1 to 58 locations. Operator to operator, he now helps founders of $1M–$20M companies get out of the middle of the business, build the leadership team, and raise capital. Book a 30-minute call →