Going from a handful of people to a team of twenty is one of the most significant transitions a small business makes. The business model might be the same, the product or service might not change, but almost everything about how you run the place needs to evolve.
The end of everyone knowing everything
When you have five people, everyone broadly knows what everyone else is doing. Decisions get made in quick conversations. Information flows naturally. There's no need for formal processes because the team is small enough that informal ones work.
At twenty people, this breaks down completely. Decisions made without documentation get lost. Information reaches some people and not others. Assumptions that were shared without discussion cause confusion. What felt like unnecessary overhead at five people becomes necessary infrastructure at twenty.
Research on small business scaling consistently identifies the shift from informal to formal processes as the hardest cultural adjustment. Founders often resist it because it feels like adding bureaucracy. But without it, growth stalls or quality drops.
Hiring and the shift in management
At five people, the founder often manages everyone directly. At twenty, that's not possible. You need at least one layer of team leads or managers between the founder and most of the team, and those people need to actually manage, not just do.
This transition is harder than it sounds. Promoting a good individual contributor to a management role doesn't automatically make them a good manager. They need support, a clear brief about what the role is, and time to develop into it.
Systems that worked at five will not work at twenty
Your invoicing process that worked when one person handled everything will struggle when three people are creating invoices. Your project management approach that relied on everyone knowing the status of everything needs documentation. Your sales process that was all in the founder's head needs to be written down.
The answer is process documentation, which sounds dull but is just writing down how things work so that anyone can do them the same way. It's the difference between relying on Sarah knowing how to do this and here is how we do this.
Tools need to scale with the team
What works as a small team's software stack often doesn't work at twenty. Shared inboxes get chaotic. Project tools that were adequate for three people become confusing with eight. Spreadsheet-based systems for tracking clients or finances break under the volume.
This is a good time to consolidate your tools if you haven't already. WeekOne is built to handle the needs of a growing team in one platform, with CRM, projects, invoicing, and support connected, and user permissions that make sense at different team sizes.
Finance gets more complicated
At five people, a founder often has a fairly direct view of all the money. At twenty, the numbers are bigger, the expenses are more diverse, and the risk of things going wrong is higher.
You probably need a proper bookkeeper if you don't have one already, and potentially a part-time finance manager. Your cash flow forecasting needs to be more rigorous. Your payroll is more complex. Pretending that what worked at five will still work at twenty is a common mistake that creates real problems.
Culture does not maintain itself
At five, company culture is largely the founder's personality. At twenty, you need to be intentional about it. What does your business stand for? How do you want people to treat each other and treat clients? What behaviours do you reward and what do you not tolerate?
These things need to be said out loud, demonstrated consistently by whoever leads the business, and built into how you hire. Culture at twenty is a decision, not just an emergence.
It is harder than it looks, and that is normal
Most founders who've made this transition say the same thing: the 10 to 20-employee phase was harder than going from 1 to 10. The businesses that get through this phase well are the ones that accepted early that things needed to be built properly, not just improvised.