You closed the Series B in March. Ninety people now, and a board that has graduated from "tell us the story" to "show us the plan." So you did what worked at Series A. You booked a weekend, wrote the strategy yourself, turned it into a thirty-slide deck, and presented it at the all-hands to real applause. By June, three of the six priorities have quietly changed and nobody has updated the deck. The plan is already a historical document.
Series A planning is founder planning. It works because one person holds the whole company in her head and can re-plan in real time by walking across the floor. Series B breaks that, and it breaks it quickly. The operating model that carried you this far starts failing somewhere between hire 40 and hire 80, and your planning process is the first place the cracks show.
The founder weekend stops scaling around 80
The weekend plan works at Series A because it encodes context that lives in one head, and at forty people most of the company can absorb that context by osmosis. At ninety, the people executing the plan were not in the room and do not share the founder's mental model. So the deck becomes an artifact people nod at in the all-hands and then interpret four different ways at their desks.
The plan did not get worse. The company got too big for the way it was made. What has to change is the ownership of planning itself. Direction still comes from the CEO. The plan gets built by the exec team, with each leader owning the goals and strategic initiatives in their area and one accountable name on each.
Plan an operating model, not a deck
The deliverable of Series A planning is a deck. The deliverable of Series B planning is an operating model, and the deck is downstream of it.
An operating model answers the questions a deck skips. Who owns which goal. How a mid-quarter trade-off gets decided and by whom. What cadence the company reviews progress on. How capacity gets allocated when two leaders want the same engineer. Write those rules down once and most of the year's small decisions answer themselves. Leave them unwritten and every decision escalates to the CEO, which is the exact bottleneck a Series B is supposed to remove.
Connect the plan to the work or it dies in the deck
Here is the failure that eats most Series B plans. The plan lists initiatives. The work happens in Jira, Asana, HubSpot, and Planner. The two never touch again after the offsite.
Progress gets self-reported in a monthly slide, and self-reported progress drifts toward green regardless of reality. By the time a red status is honest enough to alarm anyone, the quarter is gone. Strategy execution at this stage means wiring the plan to the systems where work actually happens, so progress and risk are derived from real activity instead of a status a manager typed the night before. When the plan and the work are connected, a stalled initiative shows up in week two rather than at the QBR.
Replan every quarter
Annual planning assumes the year is predictable. A company that just doubled its headcount is not predictable. The org chart and the competitive picture both move every quarter, and a plan locked in January is describing a company that no longer exists by April.
So replan on a quarterly cadence. Not a full rewrite. A structured review of which initiatives still map to a live goal and where capacity needs to move. Keep the annual plan for direction and use the quarters for allocation. The companies that scale cleanly through Series B treat the plan as a living system they adjust, and the ones that struggle treat it as a document they defend.
A plan wired to the work this way is most of what Vindaris does, holding goals of any framework next to the real execution meant to move them.
FAQ
How often should a Series B company replan? Review quarterly and set direction annually. The annual plan fixes the destination and the big bets. The quarterly review reallocates capacity and cuts initiatives that no longer map to a goal. Monthly replanning is usually too frequent to be strategic and turns into another status meeting.
Who should own strategic planning after a Series B? The CEO owns direction, but a Chief of Staff or a head of strategy should own the process. That split matters, because a CEO running the mechanics of planning is a CEO not running the company. The exec team owns the goals inside the plan, one accountable owner each.
Do we need to adopt OKRs at Series B? Only if the framework earns its keep. OKR, KPI, EOS Rocks, OGSM: the specific syntax matters far less than whether each goal has a single owner and a live connection to the work meant to move it. A company can run beautiful OKRs and still have a plan that dies in a deck.