Your agency has grown. You now employ account directors, department leads and maybe a general manager. The organization chart looks like a proper company.
Then look at your calendar. You're still approving proposals, resolving client scope disputes, signing off routine hiring decisions and answering questions that could have been settled two layers down.
Congratulations. You've bought yourself a more expensive version of the same job.
I say that with affection because founder dependency is easy to create and difficult to notice. Owners often believe they're protecting quality. Sometimes they are. But every time a capable employee has to wait for the founder's permission, the agency learns a little less about making decisions without them.
I have written about my own experience going too far in the other direction: in 2011, after spending years concentrating on building Anvil rather than delivering services, my team told me I'd lost touch with the work. That's a reminder that stepping back entirely isn't the solution. This article is about a different problem: giving people meaningful authority while keeping the founder informed.
Job titles aren't decision rights
A new hire can be called head of client services, director of operations or managing partner. None of those titles explains what they can decide.
Can the account director authorize extra work? Up to what amount? Can a practice lead reject an unrealistic deadline? Who decides whether to replace a client team member? When does the owner get involved in a commercial dispute?
If those boundaries aren't clear, people act rationally: they ask permission. A founder then becomes the de facto operating system of the business.
The issue is not that your team lacks initiative. You may have designed a company in which initiative is punished whenever someone makes a choice you would have made differently.
Map the last twenty interruptions
Before hiring another senior manager, try a small experiment. For one week, write down the meaningful decisions that land on your desk unexpectedly. Don't record every notification or minor question. Focus on decisions that stop someone else from progressing.
For each, note the requester, the decision, why it needed you and whether you reversed or approved what the team already recommended.
At the end of the week, put them into four categories:
Only the owner can decide. Significant financial risk, strategic direction, ownership matters, unusually sensitive people decisions. It may be entirely right for these to stay with you.
A senior leader should decide. Cross-functional conflicts, agreed commercial exceptions, hiring within a budget, major client escalations.
The responsible team should decide. Routine technical choices, ordinary project adjustments and previously agreed processes.
This shouldn't be a decision at all. If the same question comes up every week, a standard, template or clearer client agreement may solve it.
The last category is often overlooked. Don't empower people to ask the founder a recurring question faster. Remove the question.
Hand over authority with boundaries, not with a slogan
"I trust you to own this" sounds encouraging. It is not an operating instruction.
A stronger handover explains the desired outcome, the limits and when someone should escalate. For example: an account director may resolve a defined class of scope disputes within an agreed commercial limit, provided they document the decision and inform finance. Anything outside the limit needs a different conversation.
The actual thresholds will depend on the agency's size and risk appetite. Don't borrow somebody else's dollar amount from a business book. Decide what your organization can reasonably manage.
Then resist the temptation to overrule a reasonable decision merely because you would have done it differently. If employees expect every answer to be re-litigated, they will continue to route everything through you.
The counterintuitive part: you still need to know what's happening
Delegation should not create a vacuum. This is where my Seattle lesson still matters. I don't recommend that agency owners disappear into strategy meetings and lose touch with their service.
Instead, ask your team for a short exception-based review: which decisions fell outside the normal process, what was learned, and whether the boundaries need to change. Be curious about the reasoning. Save your intervention for the moments where your experience truly changes the answer.
You're trying to build judgment in the organization, not simply reduce your inbox.
An owner who delegates decisions but punishes errors will get endless escalation. An owner who never checks what happened won't build trust either. The balance is transparency, coaching and proportionate accountability.
A thirty-day test
Week one: record the decision queue. Week two: choose three recurring decisions that should move down a level and agree on boundaries. Week three: let the responsible leaders make those calls, recording outcomes without constant intervention. Week four: review what worked, where people needed support and which boundary should change.
This is a proposed experiment, not a promise that thirty days can transform a business. Some choices involve legal, financial or people risks that need deeper safeguards. Start with the reversible, routine work.
The objective is not to make the founder redundant overnight. It's to make the agency less fragile and the people in it more capable.
What kind of agency do you actually want?
If your long-term goal is to remain a hands-on owner, that's a perfectly legitimate choice. If you want to scale, take more time away, bring in partners or eventually sell, dependency becomes more consequential. A buyer or successor will care whether the team can operate without the founder explaining every decision.
Being indispensable feels flattering until you realize it's also a constraint.
The question I would leave you with is this: if you took a genuine two-week break, what would the team be unable to decide—and how many of those decisions truly require you?
If that question exposes a bottleneck, you can start with the founder-dependency advisory page or bring one concrete decision to a conversation. We can work from the actual operating problem, not a leadership cliché.
Is one of these decisions on your desk?
Bring a real situation to an independent founder-advisory conversation.
EXPLORE FOUNDER DEPENDENCY ADVISORY ↗