Every operator who has lived through Series B describes the moment the same way: we could feel it before we could name it. The product is working. The market is real. The Series B is in the bank and the headcount plan is signed. And then, somewhere between hire 40 and hire 80, things start taking longer than they should. Decisions that used to take an afternoon take three weeks. Teams that used to just figure it out now need a meeting to align. The CEO starts to feel like she is managing the org chart instead of driving the company.
That is not the product breaking. That is the operating model breaking. And almost nobody sees it coming because the symptoms look like personnel issues.
What the operating model was at 30 people
At 30 people, the operating model was the founding team. Strategy lived in the CEO's head. Priorities were communicated at the weekly all-hands. Anyone with a question walked over to whoever had the answer. Work happened everywhere — Notion, Slack, Jira, a shared Drive — and nobody minded, because everyone knew everyone.
That is not dysfunction. That is a 30-person company running correctly. Oral tradition is a perfectly good operating system when everyone can be in the same room. The trouble is that it does not scale, and most founding teams do not notice it stopped working until two quarters after it stopped working.
The 50-person threshold
Fifty people is approximately where oral tradition fails as an operating model. At 50, there are teams that have never had a full conversation with each other. Work streams duplicate quietly. Decisions get made at the team level that should have been made at the exec level — and decisions get escalated to the exec level that should have been settled by the team in twenty minutes.
The founding team almost always tries to solve this with more meetings. Weekly syncs become daily standups. The all-hands becomes biweekly. The CEO's calendar fills with alignment conversations that should have been prevented by a system. You cannot replace a system with a meeting. You can only buy a few weeks of the appearance of coherence.
The three things that break at the same time
When the operating model hits its limit, it does not break in one place. It breaks in three, and the breaks reinforce each other.
The first is goal-to-work disconnection. At 30 people, the connection between what the company is trying to achieve and what is being worked on is maintained by proximity. Everyone knows what matters because they heard it at the all-hands last week. At 80, proximity fails. Teams work on things that were priority three months ago. Strategic bets do not have the capacity they were promised. Nobody knows, because nobody has a system that shows it.
The second is ownership ambiguity. At 30 people, accountability is maintained by ego and visibility. If you do not deliver, everyone notices. At 80, there is enough structure to hide. A goal belongs to "the product team." A KPI belongs to "revenue and ops, jointly." Nobody actually drives it. The quarterly review becomes a tour of things that were important and did not happen, narrated in the passive voice.
The third is bandwidth invisibility. At 30, everyone knows who is working on what. At 80, nobody does. The new initiative gets approved. The engineer it depends on is already at 110% across three other things. Nobody knows until the initiative stalls — and by then the cost is sunk.
What the operating model needs to become
The fix is not more process. More process at this stage usually makes things worse because it adds ceremony without changing the underlying architecture. The fix is a different architecture entirely.
The operating model that works at 80 to 150 people has three properties. Single-owner goals. Every goal — OKR, KPI, OGSM, EOS Rock, whatever syntax you prefer — has exactly one person accountable for it. Contributors are separate. The owner has authority to decide, escalate and change course. The goal can be green or red without a committee meeting to determine the colour.
Traceable work. Every work item links to the goal it is supposed to move. Not in a quarterly mapping exercise — natively, at the moment the work is created. Leadership can see, at any point in the quarter, which goals have active work behind them and which are running on hope.
Honest capacity accounting. The system shows where bandwidth is allocated. New initiatives require explicitly naming what capacity they take from existing bets. The CEO approves a fourth priority only when she has also seen that it requires taking the lead engineer off priority two. The trade-off is not implicit. It is in the artefact.
The Vindaris view
Most Series B companies try to solve the operating-model problem with goal frameworks. They run OKR workshops. They cascade. They check in. None of it works, because the problem is not goal clarity. The problem is that goal clarity, without a structural connection to the work meant to prove it, is just a cleaner version of the same ambiguity. You end up with a beautiful slide deck and the same execution gap.
The operating model that works at Series B is not a goal tool with a roadmap attached. It is a system where goals of any syntax and the work meant to prove them live in one place — and where leadership can see, without reconstruction, whether the strategy is being executed. The break at 50 is structural. The fix has to be too.