The owner-approval bottleneck: when every yes waits for you
The owner-approval bottleneck is when replies, proposals, discounts and exceptions wait for the owner's yes, so the business moves at the pace of one person's day. The fix is written rules that send routine approvals to a named person, bring the owner only the exceptions with a draft and context, and give every wait an expiry and a fallback.
A lead's reply sits drafted until you've read it. The proposal waits for your sign-off, the discount waits for your yes, and so does the client who asked for one extra round of changes. Most of the time your team already knows the answer, and they still ask, because asking is safer than guessing wrong. So a week you spend deep in client work is a week the rest of the business spends waiting for you.
Why every yes ends up with you
Early on, approving everything yourself was the right call. You knew every client and every price, and the rules for what was fine lived in your head. The only way anyone else could apply those rules was to ask you, so they did, and the habit stays long after the business has outgrown it.
So every yes joins one queue, and you're the only one serving it. More leads, more proposals and more clients all add to the line, while the person clearing it has the same hours as before, most of them already spoken for by client work. Once the queue grows faster than you can clear it, the wait stops tracking how hard the decisions are and starts tracking how busy you are.
Rules change who decides. Without written rules, every decision looks like it might be an exception, so every decision goes up to you. Once the rules are on paper, most of the queue turns out to be the same handful of calls made the same way each time, and those can go to someone else.
What waiting on you costs
Every yes that waits costs time somewhere else. A lead who asked a question cools while the reply sits drafted. A proposal that waits for your sign-off gives the buyer a few more days to talk to someone else. And your team learns that deciding is your job, so they stop trying, and the queue gets longer.
The bigger cost is your own week. Evenings go to clearing approvals, and the work only you can do, like pricing, hiring and the clients who need you, gets whatever time is left.
A wait with no end can also lose the thing it was meant to protect. In a test of lead to reply, a system I built, on 2026-09-17, the approval wait expired after a full day with no tap on the approval card, and the lead was dropped with no record and no alert. I filed it as a defect, and it's why every wait in the shape I'd build has an expiry and a fallback.
How much of your week goes to moving work between people depends on your own volume. The coordination cost calculator takes your counts and the time each one takes, and shows what that adds up to across a year.
What the system looks like
I'd start with the rules, written down: what needs the owner at all, what a named person can approve, and where the line sits between the two. Routine approvals go to that person, someone who can stand behind the answer. You see only the exceptions, and each one arrives with a draft and the context you'd otherwise go looking for: what was asked, what was said before and what the rule says. Every wait gets an expiry and a fallback, so a request nobody answers moves to a backup person and raises an alert instead of sitting there.
- Work that needs a yes
- Rules decide what needs the owner at all
- Routine approvals go to a named person
- Owner sees the exceptions with a draft and the contextHUMAN
- Every wait has an expiry and a fallback
In an agency, consultancy or studio, the usual approvals tend to split along these lines.
| Kind of decision | Who approves by default | What goes to the owner | What I'd set to happen when nobody answers |
|---|---|---|---|
| A drafted reply to a new lead | Someone you name at the business, you or someone on your team, from their phone | A lead asking about a price, a start date or work you don't usually take on | The draft moves to a backup person and an alert goes out, and the lead stays on record until someone answers it |
| A proposal | A named person checks the draft against your template | Scope and price, on every proposal | A reminder reaches you with the draft and the date you promised the buyer |
| A discount or a change to your standard terms | The account lead, within a limit you wrote down | Anything past that limit | The request stays on your standard terms, and the account lead tells the client when they'll hear back |
| A client asking for extra work or a rush date | The account lead, using your written rules on what's included | Anything that changes scope, price or a date you've already promised | It moves to a backup person with the context, and the client hears when they'll get an answer |
| Finished work before it goes to a client | A named reviewer on the project | The first piece on a new account, or work for a client you've flagged | It moves to a second reviewer, and the due date stays in front of both of them |
What stays with you
The rules move the routine off your desk, and the decisions that shape the business stay on it.
- The rules themselves. You write them, you set the line between routine and exception, and you move it when the same exception keeps coming back.
- Who approves. You name the people, and who backs each of them up.
- Price, scope and any date the business hasn't promised before.
- Exceptions, which reach you with a draft and the context so you can answer from wherever you are.
Replies to leads keep a person in front of them either way. Every reply the AI drafts for a lead waits for someone at the business to approve it from their phone, and you choose who that is: you or someone on your team.
Questions
How do I stop being the bottleneck in my own business?
Write down the rules you already apply in your head, starting with the approvals you give most often. Most of them come out the same way every time, and those can go to a named person. Keep the exceptions for yourself, and give every wait an expiry so a request can't sit with nobody on it.
What should a business owner still approve personally?
Anything that sets a price, changes scope or promises a date the business hasn't promised before, plus anything your written rules don't cover. Those are the calls that are hard to take back. Routine replies, discounts within a limit and day-to-day client requests can go to someone you trust.
Who should approve things if it isn't me?
Someone who can stand behind the answer: they know the client, the work and your rules well enough to defend the call if anyone questions it. Name them, write down what they can approve, and name a backup for the days they're out.
What happens if nobody approves in time?
With no expiry, the request waits, and the lead or client waits with it. In the shape I'd build, every wait has an expiry and a fallback: when the time runs out, the request moves to a backup person and raises an alert, and it stays on record until someone deals with it.
Should I hire an operations manager to take approvals off my plate?
A person helps when the decisions need judgment. The written rules come first either way, because a new hire without them will ask you the same questions you're answering now. The comparison of hiring a coordinator with installing a system sets out what each one costs.
Related
- Human-in-the-loop approvalWhat human-in-the-loop approval means in an automation, which steps should wait for a person, and how an approval card makes sure an email sends once.
- The client-approval queue: finished work waiting on a client's yesFinished work sits with a client for days and nobody owns the chase. Send each piece with one clear question and a due date, and draft the reminder.
- The proposal bottleneck: why proposal turnaround is slowProposals wait for one person's free afternoon. Capture the inputs as the call ends, draft in your template, and keep scope and price with the owner.
- The lead-response bottleneck: how fast to answer a new leadHow fast to answer a new lead, why a slow reply hands the decision to someone else, and a system that drafts from your rules for a person to approve.
- Website form leads, scored and answered with a reply I approveA system I built: each website form lead is checked, added to HubSpot once and scored. Gmail sends the drafted reply when I approve it in Telegram.
- Should I hire an operations coordinator or install a system?What an operations coordinator costs a year, set against installing a system: where each one fails, and which to pick first when your agency is growing.
- What does coordination cost your business each year?Turn your leads, proposals and active projects into the hours your people spend coordinating each month, and what that time costs you in a year.