Growth exposes everything.
Not all at once. It happens in a specific order, and if you've seen it enough times you start to recognize the sequence. The thing that breaks first is almost never the thing you were worried about.
Here's what I've watched fall apart, consistently, at the moment a startup starts to scale.
Onboarding. When you have five people, onboarding is a conversation. Someone sits with the new hire, walks them through the tools, introduces them to everyone. It works fine. Then you hire ten people in a quarter and suddenly nobody has time to do the thing that used to happen naturally, and new hires are starting without laptops, without access, without any real sense of what they're supposed to be doing in week one. The informal system didn't break because anyone was careless. It broke because it was never actually a system.
Compensation. Early on, offers get made fast. Someone needed to fill a role, there was a candidate, a number got put on the table. It made sense at the time. Do that enough times and by the time you hit thirty people you have a compensation structure held together by individual negotiation history and nobody can tell you with confidence whether your pay is equitable, competitive, or defensible. This one tends to surface at the worst possible moment, usually when someone compares notes.
Performance and feedback. Founders are often great at giving feedback one on one. That scales until it doesn't. When the team gets big enough that not everyone reports directly to a founder, feedback becomes inconsistent. Some managers do it well. Others avoid it entirely. People start to feel unmoored and the first sign is usually attrition you didn't see coming.
Approval and decision rights. Small teams make decisions fast because everyone is in the room. As you grow, it becomes less clear who can approve what. Vendors wait weeks for a signature. Hires stall because nobody is sure who owns the final call. Things that should take a day take a month, and the people closest to the work get frustrated and start going around the process entirely, which creates its own problems.
None of these are surprising in retrospect. They're all predictable. The issue is that most founding teams are focused on the product and the growth, and the operational infrastructure gets built reactively, after something breaks, rather than proactively, before it does.
The good news is that none of this requires a massive investment to fix. It requires someone who has seen the sequence before and knows what to build, in what order, before the cracks turn into crises.
That's most of what I do.
I work with seed and Series A startups as a fractional operations partner. saharnaim.com
