When should annual planning start?

6 weeks before the fiscal year starts. For calendar-year companies, that means starting in mid-November. Waiting until January means Q1 is spent planning, not executing.

Should we plan annually or quarterly?

Both. Annual plan sets strategic direction and headcount/budget envelope. Quarterly plans refine execution against the annual plan. Startups that plan only quarterly lose strategic coherence; startups that plan only annually become rigid in a changing environment.

CEO owns the strategy and integration. Function leaders own their functional plans and delivery. The plan is a written document with a version number, not a slide deck — decks get ignored, documents get referenced.

Startup Annual Planning: The 6-Week Process (2026)

Annual planning at most startups produces a deck no one reads. Here's a 6-week process that produces a plan the team actually executes against.

Annual Planning: The 6-Week Process That Actually Aligns a Startup

Annual planning is where most startups burn 200+ person-hours to produce a plan that's ignored by Q2. The failure mode is usually the same: too much top-down goal-setting, not enough bottom-up capacity check, no explicit trade-offs. A 6-week process with defined artifacts fixes this — the goal is alignment, not a deck.

Week 1-2: strategic direction

CEO + leadership team define: 3-year vision (refreshed), 12-month strategic priorities (3-5 max), and explicit non-goals (what we're saying no to). Output: 2-page strategy memo. Circulate to full team for input, not approval — leadership owns the direction.

Week 3-4: function-level plans

Each function (Eng, Product, GTM, Ops) drafts their annual plan: goals, roadmap, headcount, budget. Bottom-up, not top-down. Format: quarterly milestones with owners. Include capacity honesty — what you can't do given current or planned headcount. Present to leadership team for challenge and integration.

Week 5: integration and trade-offs

Leadership team reconciles function plans against strategy and cash. Explicit trade-off session: which initiatives get funded, which get deprioritized, where the sequencing needs to shift. Output: integrated company plan with quarterly milestones, headcount plan, budget by function.

Week 6: rollout

All-hands presentation of the plan: strategy, priorities, non-goals, quarterly milestones. Written company plan document circulated. Each function does a team-level cascade in the following two weeks. Q1 kickoff meeting sets execution rhythm — weekly team check-ins, monthly cross-functional reviews, quarterly plan updates.

What to avoid

Top-down quotas with no capacity check ('we're going to 3x ARR' when the pipeline model shows 1.8x max). Departments planning in isolation and colliding at handoffs. No non-goals (a plan that says yes to everything is a plan that ships nothing). Board pressure driving unrealistic goals that break the plan before it starts.

Frequently asked questions

When should annual planning start?: 6 weeks before the fiscal year starts. For calendar-year companies, that means starting in mid-November. Waiting until January means Q1 is spent planning, not executing.
Should we plan annually or quarterly?: Both. Annual plan sets strategic direction and headcount/budget envelope. Quarterly plans refine execution against the annual plan. Startups that plan only quarterly lose strategic coherence; startups that plan only annually become rigid in a changing environment.
Who owns the plan?: CEO owns the strategy and integration. Function leaders own their functional plans and delivery. The plan is a written document with a version number, not a slide deck — decks get ignored, documents get referenced.