The Series B problem is predictable. It's so predictable that every operator who's lived through it describes it the same way: "We could feel it before we could name it."

The product is working. The market is real. The funding is in. The headcount plan is approved. 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's managing the org chart instead of driving the company.

That's the operating model breaking. Not the product.

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 in the weekly all-hands. Anyone with a question could walk over to whoever had the answer. Work happened everywhere — Notion, Slack, Jira, a shared Google Drive folder — and nobody cared, because everyone knew everyone.

That's not dysfunction. That's a 30-person company running correctly. The informal communication layer works when everyone can be in the room. When they can't, it breaks.

The 50-person threshold

Fifty people is approximately where oral tradition stops working as an operating model.

At 50 people, there are teams that have never had a full conversation with each other. There are work streams that duplicate each other. There are decisions being made at the team level that should have been made at the exec level — and decisions being escalated to the exec level that should have been made at the team level.

The founding team tries to solve this with more meetings. Weekly syncs become daily standups. The all-hands becomes more frequent. 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 time.

The three things that break simultaneously

When the operating model hits its limit, it doesn't break in one place. It breaks in three:

1. Goal-to-work disconnection. At 30 people, the connection between what the company is trying to achieve and what's being worked on is maintained by proximity. Everyone knows what matters because they heard it at the all-hands last week. At 80 people, proximity fails. Teams work on things that were priority three months ago. Strategic bets don't have the capacity they were promised. Nobody knows, because nobody has a system that shows it.

2. Ownership ambiguity. At 30 people, accountability is maintained by ego and visibility. If you don't deliver, everyone knows. At 80 people, there's enough structure to hide. A goal belongs to "the product team." A KPI belongs to "revenue and ops, jointly." Nobody drives it. The quarterly review becomes a tour of things that were important and didn't happen.

3. Bandwidth invisibility. At 30 people, everyone knows who's working on what. At 80 people, 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.

What the operating model needs to become

The fix isn't more process. It's different architecture.

The operating model that works at 80–150 people has three properties:

Single-owner goals. Every goal — OKR, KPI, OGSM, EOS Rock, whatever syntax — 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 it.

Traceable work. Every work item links to the goal it's supposed to move. Not in a quarterly mapping exercise — natively, at the moment it's 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's also seen that it requires taking the lead engineer off priority two.

The Vindaris position

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 isn't goal clarity. The problem is that goal clarity, without a structural connection to the work that proves it, is just a cleaner version of the same ambiguity.

The operating model that works at Series B isn't a goal tool with a roadmap attached. It's 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.