Annual SaaS Planning Template for PMs

Start 6-8 weeks before the fiscal year begins. The first 2 weeks are for gathering inputs (retro, market analysis, customer data). Weeks 3-4 are for theme alignment and OKR drafting. Weeks 5-6 are for initiative mapping and capacity allocation. Weeks 7-8 are for cross-functional review and finalization. Rushing the process leads to plans that do not survive contact with reality. The [Product Strategy Handbook](/strategy-guide) covers the full planning lifecycle.

If a request does not fit a theme, it should go to a "not now" list rather than being forced into an existing theme. If more than 20% of high-priority requests fall outside your themes, the themes may be wrong. Re-examine them. The [RICE framework](/frameworks/rice-framework) helps evaluate individual requests on their merits when theme alignment is unclear.

Yes. The themes, OKRs, and quarterly roadmap should be visible to everyone. Hiding the plan breeds misalignment. Details like capacity allocations and risk registers can stay within the product and engineering leadership team.

Strategic themes should rarely change (0-1 theme shifts per year). OKR targets may adjust at quarterly reviews based on new data. Initiative sequencing changes frequently as you learn what works. If you are re-planning every quarter from scratch, your themes were not strategic enough. If nothing changes all year, you are not learning from execution.

Three to five. Fewer than three means you are under-investing in diversification. More than five means you are spreading too thin to make meaningful progress on any theme. For a team of 20-30 engineers, three themes is typical. For 50+ engineers, four or five is manageable. ---