Somewhere around 30 employees, a lot of companies hit an invisible wall. It's not a wall anyone put there deliberately — it's just the point where the informal systems that worked fine at a smaller size start creaking under real strain. Decisions that used to happen in a hallway conversation now need an actual process. The founder or CEO who used to know every project in flight can no longer hold it all in their head. And the tools — technical and organizational — that got the company to 30 people often aren't the tools that will get it to 40, 50, or 100.
The Trap of "It's Always Worked This Way"
The instinct during a growth phase is usually to protect what's working, and that instinct is often right — culture, values, and the things that made early hires want to join shouldn't get thrown out just because the org chart is getting bigger. But there's a difference between protecting what actually matters and clinging to informal processes purely out of familiarity. A lot of companies conflate the two, and end up defending genuinely broken systems because changing them feels like a betrayal of "how we do things here."
The clearest signal that a company has hit this wall is usually operational, not cultural: things that used to just happen — a new hire getting fully set up on day one, a client issue getting resolved without three people needing to get involved, a system update rolling out without breaking something else — start requiring visible effort and coordination that they didn't used to require. That's not a sign the team is failing. It's a sign the informal scaffolding that used to handle this invisibly has run out of runway.
What Actually Needs to Change (and What Doesn't)
The mistake a lot of growing companies make is treating every operational problem as a hiring problem — "we just need more people" — when a meaningful share of the friction is actually a systems and infrastructure gap that more headcount won't fix on its own. Adding people to an under-built system usually just distributes the same friction across more people, rather than eliminating it.
A more useful question at this stage is: which of our current systems were built for a company half our size, and which ones can genuinely scale with us? IT infrastructure is one of the most common areas where this gap shows up first, because it's invisible until it isn't — file permissions that were never cleanly organized, an onboarding process that depended on one person remembering all the steps, security practices that were "good enough" when there were fewer people and less sensitive data flowing through the company.
Investing Ahead of the Growth Curve, Not Behind It
The companies that navigate this transition well tend to share one trait: they invest in operational infrastructure slightly ahead of the growth curve, not purely in reaction to it. That's a harder discipline than it sounds, because spending money on systems before the pain is acute enough to force the issue always feels premature — until the pain arrives all at once and the fix becomes an emergency instead of a planned upgrade.
This applies directly to how a growing company handles its technology function. A company scaling from 30 to 40 employees that's still relying on the same ad hoc IT setup — one internal generalist, or a reactive outside vendor — that worked at 15 people is setting itself up for exactly the kind of breakage this piece is describing. Bringing in a genuine managed IT partner at this stage, rather than waiting until something breaks badly enough to force the decision, is one of the more common (and more effective) moves growing companies make. The right partner scales its own service delivery alongside a client's headcount, rather than treating every client the same regardless of size or trajectory.
Protecting Culture While Changing Everything Else
The paradox of this stage is that protecting what made the company special often requires changing almost everything operational about how it runs. That's not a contradiction — it's the actual work of scaling. The values, the relationships, the sense of shared mission: those are worth fighting to preserve. The informal processes that happened to work when the company was smaller: those were never the point, and letting go of them in favor of systems that can actually scale is usually what allows the things that do matter to survive the transition intact.
