The strategic plan a scaleup finishes in November describes a company that will not exist by March. By then you will have doubled a team and quietly sunset a product line that looked core in Q4. The plan was not wrong when it was written. It went obsolete on a schedule, and everyone kept presenting it anyway, because reopening it felt like admitting the offsite had been a waste.
Annual strategic planning was designed for companies whose operating environment moves slowly. A scaleup is the opposite case. Running an enterprise planning calendar inside a 200-person company that resets its revenue plan every year produces a specific and expensive failure.
Why the annual cycle breaks in a scaleup
The mechanics of annual planning assume the inputs hold for twelve months. Market size, headcount, the competitive set, the product roadmap - all fixed at planning time, all treated as stable enough to build a year on. In a slow business that assumption roughly holds. In a scaleup, half of those inputs change materially within two quarters.
We have covered the deeper reasons in why annual planning fails in its second year, and the short version is that plan and reality diverge faster than the calendar lets you correct. By the time the next offsite comes around, the organisation has spent months executing against assumptions everyone privately knows are stale. The plan turns into a document you defend rather than a tool you use.
The usual response makes it worse. Companies add rigour to the annual process, more pre-reads and more review gates, which lengthens the cycle and makes the output even more expensive to change. A heavier plan is a more brittle plan.
A lighter rolling process
The alternative keeps planning but changes its unit from a year to a rhythm.
Two things stay annual. A small set of durable strategic bets, the few moves that define where the company is going and genuinely should not shift every quarter. And the financial envelope that constrains everything else. Both are stable by nature and worth the offsite.
Everything below that plans on a quarterly rhythm. Each quarter you set the goals that serve the annual bets, assign a single owner to each, and commit the capacity to deliver them. The annual layer gives direction. The quarterly layer does the real planning, close enough to reality that the assumptions still hold when the work starts. This is the structure behind durable strategic initiatives: a bet that spans the year, decomposed into quarterly goals that can each be re-cut without reopening the whole strategy.
The lighter process also lowers the cost of being wrong. When a quarter's plan rests on a bad assumption, you correct it in the next cycle instead of carrying it for a year. Planning becomes a control loop rather than an annual verdict.
Connect the plan to the work, or it dies in the deck
Most strategic plans die the same way. They are written, presented, applauded, saved to a shared drive, and never opened again until the next planning cycle. Teams go back to their tools and their backlogs, and the plan and the work drift apart within weeks.
This is the gap between having a strategy and executing one, and it is almost never a planning-quality problem. The plan can be excellent and still die, because nothing connects the strategic bets in the deck to the epics and hires meant to deliver them. The plan lives in slides. The work lives in Jira and the CRM. No line runs between them.
Closing that gap is the whole premise of strategy execution as a discipline. In practice it means each quarterly goal links to the real work items delivering it, so progress on the plan is read from delivery rather than from a status slide. When a strategic bet falls behind, you see it in the work stalling, weeks before it would surface in a quarterly business review. The plan stays alive because it is wired to the thing that proves it.
Revisit quarterly, with a real agenda
A quarterly strategy review is not a status meeting with better slides. It answers four questions, in order. Which bets are on track based on the work behind them, not the self-reported colour? Which assumptions from last quarter turned out wrong? What has changed in the market or the business that the plan has not absorbed? And given all of that, what do we re-cut for next quarter?
The discipline is to treat the plan as revisable at each of these reviews and fixed between them. Constant re-litigation is as damaging as annual rigidity, because a team cannot execute against a target that moves every week. Quarterly is the cadence that balances stability against adaptation for most scaleups: long enough to execute, short enough to correct before a bad assumption compounds.
Vindaris was built to keep a plan connected to the work that delivers it, so quarterly reviews run on real progress instead of reconstructed status.
FAQ
How often should a scaleup actually revisit its strategy? Keep the durable bets and the financial envelope on an annual cycle, and put everything beneath them on a quarterly one. The bets set direction and should stay stable; the quarterly layer is where you plan against current reality and correct last quarter's wrong assumptions. Monthly tends to be too frequent to execute against, and annual is far too slow to catch the drift that sinks a fast-moving company.
Does a lighter process mean less strategic rigour? No. It moves the rigour to where it pays off. The annual offsite still does the hard thinking on the durable bets. The quarterly cycle applies rigour to the near-term plan, where the assumptions are actually knowable. A heavy annual plan spends real effort forecasting details that change before they matter, which is activity, not rigour.
What is the first thing to fix if our plan keeps dying in a deck? Link the plan to the work. Take your top strategic bets and connect each to the specific epics and campaigns meant to deliver them, so progress is visible from delivery rather than from a monthly status update. Until that line exists, every other planning improvement is cosmetic, because the plan and the execution still sit in separate systems that never talk.