Case Study

Case Study: How I Got Out of My Agency's Delivery Queue

How I cut my week at W3whiz from 60-70 hours to 10-20 while the agency grew from 30 to 37 accounts, by writing the standard down before handing anything off.

Asif Dilshad
Nov 2, 2026 · 4 min read

Two years ago I worked 60–70 hours a week on my agency and spent under 10% of it on how the agency ran. Today I spend 10–20 hours a week on W3whiz, 60% of it on the operation, and the agency has grown from 30 to 37 accounts with the same seven people.

The change wasn't delegation. Nothing could be handed off until the standard I carried in my head was written down.

Before: busy everywhere, working on nothing

Two years ago, almost none of my week, under 10%, went to how the agency actually ran. The rest was split between doing SEO work on accounts, checking work, and fighting fires.

I wasn't one of the two senior reviewers. I sat above them, which sounds like the right place to run an operation from. In practice it meant I was the escalation point. Late deliverables, partner complaints and anything the seniors couldn't settle came to me. Between those, I went back to what I knew best: optimizing websites myself.

Operations work only happened when something broke. Then the fix was whatever got that deliverable out the door, not a change to how deliverables got made.

Three signals that arrived together

I was working 60–70 hours a week, and the agency had stopped growing. Then a partner offered us five accounts and I said no, because I couldn't say whether we had room.

Any one of those I could have explained away. Long hours are normal for a founder. Growth stalls. Saying no to one partner is a judgment call. Together they said the same thing: my hours weren't buying growth. They were holding up an operation that couldn't run without me, and still couldn't take on more.

What I stopped doing, and who took it over

I handed off four jobs. None of the handoffs worked until the standard was written down, because before that, "how Asif would do it" lived only in my head.

What I stopped doingWho does it nowWhat made the handoff possible
Hands-on SEO on routine accountsJuniorsThe written definition of done for each deliverable
Last-minute quality checksChecks built into the templatesWork that fails a check can't reach review
Routine partner communicationThe two seniorsTheir review load dropped to about a third, which freed the time
Being the escalation pointMy co-founderThe exception log: most issues now have a rule, so fewer escalate

My week now: 10–20 hours, mostly on the operation

I now spend 10–20 hours a week on W3whiz, down from 60–70. My time on the operation didn't shrink. Everything around it did.

My time on W3whizBeforeNow
Hours per week60–7010–20
Share on the operation (systems, rules, exception log)Under 10%About 60%
Hours on the operationUnder 6–7About 6–12
Hours on accounts54–63 (doing, checking, firefighting)About 4–8 (only accounts that aren't working)

The operation work is small and steady. Each month there are five or six recurring exceptions to turn into rules, a template to tighten, a handoff to remove. The rest of my week goes to consulting for other agencies, helping them fix the same problem.

What it changed for the agency

The agency grew again once I stopped being part of every deliverable. With a quarter of my old hours, W3whiz serves more accounts, delivers faster, and has room to grow.

  • Accounts: 30 to 37, with the same seven people and no senior hire.
  • Turnaround: 11 days to 3–4, and it has held there.
  • Capacity: room for five more accounts, a number I can now state.
  • New juniors: productive in under three weeks, down from six or more.

The full story of how the delivery side was fixed is in We Said No to Good Revenue. The numbers and the method are in the case study 30 to 37 Accounts With the Same Seven People.

The hard part was me

The systems took about a quarter to build. Letting go took longer.

  • Work done differently. Deliverables came back good, just not how I'd have done them. I had to learn that "meets the standard" and "how Asif would do it" are different, and only the first one belongs in the spec.
  • Staying out of partner conversations. The seniors were ready before I was. Every time I jumped in, I taught partners to come to me again.
  • A quality dip at first. For a few months, the team treated the checklist as the ceiling, not the floor. Work was technically complete and strategically flat. The fix was saying it plainly: passing the checks is the minimum.
  • Feeling less needed. I came up optimizing websites. Being the expert was my identity. Running the operation instead of doing the work felt like a demotion until the results showed it wasn't.

If you're stuck in your own queue

You're probably where I was if most of these are true:

  • Under 10% of your week goes to how the agency runs
  • Escalations and partner questions default to you
  • You still do hands-on work on accounts that don't need you
  • You can't say how many more clients you could take on
  • You're working more hours, and growth has stalled

Don't start by delegating. Start by writing down what "done" means, because you can't hand off a standard that only exists in your head. The quickest way to find it is three weeks of logging every change your reviewers request.

If you want help working out what to hand off first, book 20 minutes.

Keep reading

Work out what to hand off first

Bring your week and your last ten escalations. We will find which job to hand off first and what has to be written down before you can.

Book 20 Minutes