Why Growing Agencies Break at 20 Employees

At five people, a service business runs on memory. Everyone knows everyone's clients, everyone's open items, everyone's exceptions. There's no workflow to break because there's barely a workflow at all, just a small group of people who talk constantly and remember everything.

At twenty, that stops being true, usually before anyone notices. The founder can no longer hold every client relationship in their head. A new hire doesn't have three years of tribal context. The handoff that used to happen by someone glancing over (sales telling delivery a new client just signed) now depends on someone remembering to send a Slack message, and eventually, someone forgets.

The first symptom is almost never framed as an operations problem. It shows up as a client complaint, a missed deadline, a new hire who takes two months to become useful when the founder expected two weeks. Leadership responds the way growing teams almost always do: hire a coordinator to hold the seams together by hand, or buy a tool that promises to automate a process nobody has actually mapped.

Both responses treat the symptom. Neither touches the cause, which is that a workflow built for five people was never redesigned for twenty. The fix isn't more people watching the gaps, and it isn't more software automating an undocumented process. It's mapping the workflow as it actually runs today, at this size, and rebuilding the one part that's costing the most.

This is the size where Brancr does its first work with most clients, and it's not a coincidence. Twenty employees is roughly where Operational Debt stops being an inconvenience and starts being a growth ceiling.