Skip to content
The Journal
Field Notes · Vol. 03

The Founder Who Became Everyone's Bottleneck (and How He Escaped It)

One great VA freed his week. Three months later he was the bottleneck again — for two people this time. Here's how he built a remote team that runs itself.

Stephen Sundae Luna 7 min read
The Founder Who Became Everyone's Bottleneck (and How He Escaped It)

From the field

Picture a founder — let's call him Daniel, who runs a small e-commerce brand. Hiring his first virtual assistant was the best decision he'd made in a year. Suddenly he had his mornings back. Then the brand grew, the work piled up again, and Daniel did the obvious thing: he hired a second VA. Which is when everything got weirdly worse. Two great people, both capable, both idle half the day — because every task still had to route through Daniel to get unstuck. He'd built a two-person team and made himself the bottleneck for both of them. His story is worth telling, because the mistake he made is the exact one that traps most owners right at the edge of real leverage.

The wall

Why hiring more people made things slower

For the first few weeks, Daniel's second hire felt like a downgrade. Messages piled up in his DMs: 'Which supplier do I use for this?' 'Can you approve this before I send it?' 'What did you want me to prioritize today?' He was now answering the same kinds of questions twice, and the two VAs occasionally did the same task without realizing it, or each assumed the other had it. The relief he felt with one person had curdled into a new, more exhausting kind of busy.

Here's what Daniel eventually understood: a single VA can run on you as the operating system. You hold the context, you make the calls, they execute. That works beautifully with one person. Add a second and that model quietly breaks, because now the shared context lives nowhere except your head — and your head can only answer one question at a time. He hadn't outgrown his people. He'd outgrown running the team out of his own memory.

The fix

The day he stopped being the hub

The turning point was almost boring. Daniel spent one afternoon doing three unglamorous things, and within two weeks the DMs mostly stopped. He drew clear lanes — his first VA owned customer support and orders, the second owned marketing and content — so no task lived in the gap between them. He moved the shared context out of his head and into a simple wiki of SOPs, so 'which supplier?' had an answer nobody had to ask him for.

And he made one of the two people the coordinator instead of routing everything through himself. That last move was the real unlock. His first VA — who knew the business cold — became the day-to-day point person, fielding the small questions and assigning the work. Daniel went from answering twenty messages a day to reviewing one weekly summary. The team didn't get smaller. His role in it did.

The pattern

The order that actually works

Daniel's path is the one we see work again and again, and it has a shape worth stealing. You don't build a remote team by cloning yourself; you build it by adding capability in the order that removes the most friction, then handing off coordination before you become the ceiling.

Tip

Generalist first, specialist second

Your first hire clears the broad daily load; your second should own the specific gap — bookkeeping, social, support — that your generalist can't go deep on.

Tip

Promote a point person early

The moment you hit two or three people, name a coordinator — often your first VA — so questions route to them, not you.

Tip

Let SOPs be the shared brain

Every process you write down is a question that never lands in your inbox again. This is the same SOP habit that makes onboarding a second hire fast instead of painful.

Build the engine, don't be the engine

Daniel's brand runs on a small remote team now, and he spends his weeks on the two things only he can do — product and growth — instead of triaging his own people's questions. That's the whole shift: from doing the work, to being the bottleneck for the work, to finally building an engine that runs without you in the middle of it. If you're stuck at that second stage right now, it's the best possible problem to have — and it's fixable. Book a free discovery call and we'll help you build the team the right way.

Ready to grow?

Are You Ready to Grow Your Business?

Find out how our services can help your business become more productive.