What This Template Is For
Annual planning in a SaaS company is the process of translating company strategy into a sequenced set of product investments for the next 12 months. Done well, it produces clarity on what you are building, why, and in what order. Done poorly, it produces a wish list that falls apart by Q2.
This template walks you through the full annual planning cycle: reviewing the prior year, aligning on strategic themes, setting OKRs, sequencing the roadmap, allocating capacity, and establishing the review cadence. It is designed for PMs, product leaders, and founders running annual planning for a SaaS product team of 5-100 engineers.
The Product Strategy Handbook covers how strategic themes connect to execution. For a refresher on setting measurable objectives, see the OKR glossary entry. If you need to prioritize across competing initiatives, the RICE Calculator helps quantify impact and effort.
How to Use This Template
- Start with a retrospective. Review the prior year's goals, outcomes, and key learnings before planning forward.
- Align on 3-5 strategic themes. These should come from company strategy, not bottom-up feature requests. Each theme represents a bet the company is making.
- Set OKRs per theme. Each theme gets 1-2 Objectives with 2-4 Key Results. Key Results must be measurable and time-bound.
- Map initiatives to themes. Every initiative on the roadmap should ladder up to a theme. If it does not, question whether it belongs.
- Allocate capacity. Assign engineering weeks to each theme based on strategic priority, not equal distribution.
- Sequence by quarter. Place initiatives into Q1-Q4 based on dependencies, seasonal factors, and capacity constraints.
- Establish the review cadence. Annual plans are not static. Define monthly and quarterly review checkpoints.
The Template
1. Planning Metadata
| Field | Details |
|---|---|
| Company | [Company name] |
| Planning period | [e.g., FY2027: Jan 1 - Dec 31] |
| Planning lead | [Name, title] |
| Participants | [Names of cross-functional leads involved] |
| Date completed | [Date] |
| Review cadence | [e.g., Monthly metrics review, quarterly roadmap review] |
2. Prior Year Retrospective
Summarize the prior year before planning the next one.
| Area | Target | Actual | Key Learning |
|---|---|---|---|
| Revenue | [e.g., $5M ARR] | [e.g., $4.2M ARR] | [What drove the gap or overperformance?] |
| User growth | [e.g., 10K MAU] | [e.g., 12K MAU] | [What worked? What did not?] |
| Retention | [e.g., 95% annual retention] | [e.g., 91%] | [Where did churn concentrate?] |
| Product velocity | [e.g., 12 major features] | [e.g., 9 shipped] | [What slowed the team down?] |
| Strategic bet 1 | [Description] | [Outcome] | [Would you make this bet again?] |
| Strategic bet 2 | [Description] | [Outcome] | [Would you make this bet again?] |
Top 3 lessons from last year.
- [Lesson 1]
- [Lesson 2]
- [Lesson 3]
3. Strategic Context
| Input | Summary |
|---|---|
| Company vision | [Where is the company headed in 3-5 years?] |
| Board priorities | [What has the board or investors emphasized?] |
| Market shifts | [What changed in the competitive field this year?] |
| Customer signals | [Top themes from NPS, churn interviews, sales calls] |
| Technical debt | [Critical infrastructure or reliability investments needed] |
4. Strategic Themes (3-5 Themes)
Each theme is a strategic bet for the year. Themes should be mutually exclusive and collectively cover 80%+ of planned investment.
Theme 1: [Name]
| Field | Details |
|---|---|
| Description | [1-2 sentences on what this theme means and why it matters] |
| Business case | [Revenue impact, retention impact, or strategic positioning] |
| Capacity allocation | [% of total engineering capacity, e.g., 30%] |
| Success metric | [Primary metric and target] |
| Owner | [Product lead responsible] |
Objective 1: [Outcome-oriented objective]
| Key Result | Baseline | Target | Tracking Method |
|---|---|---|---|
| [KR 1.1] | [Current value] | [Target value] | [How you will measure] |
| [KR 1.2] | [Current value] | [Target value] | [How you will measure] |
| [KR 1.3] | [Current value] | [Target value] | [How you will measure] |
Theme 2: [Name]
| Field | Details |
|---|---|
| Description | [1-2 sentences] |
| Business case | [Revenue/retention/positioning impact] |
| Capacity allocation | [% of total engineering capacity] |
| Success metric | [Primary metric and target] |
| Owner | [Product lead responsible] |
Objective 2: [Outcome-oriented objective]
| Key Result | Baseline | Target | Tracking Method |
|---|---|---|---|
| [KR 2.1] | [Current value] | [Target value] | [How you will measure] |
| [KR 2.2] | [Current value] | [Target value] | [How you will measure] |
Theme 3: [Name]
| Field | Details |
|---|---|
| Description | [1-2 sentences] |
| Business case | [Revenue/retention/positioning impact] |
| Capacity allocation | [% of total engineering capacity] |
| Success metric | [Primary metric and target] |
| Owner | [Product lead responsible] |
Objective 3: [Outcome-oriented objective]
| Key Result | Baseline | Target | Tracking Method |
|---|---|---|---|
| [KR 3.1] | [Current value] | [Target value] | [How you will measure] |
| [KR 3.2] | [Current value] | [Target value] | [How you will measure] |
5. Capacity Plan
| Team / Squad | Total Eng Weeks (Year) | Theme 1 | Theme 2 | Theme 3 | Tech Debt / Reliability | Buffer |
|---|---|---|---|---|---|---|
| [Team A] | [e.g., 200] | [80] | [40] | [40] | [20] | [20] |
| [Team B] | [e.g., 150] | [30] | [60] | [30] | [15] | [15] |
| [Team C] | [e.g., 100] | [20] | [20] | [40] | [10] | [10] |
| Total | [450] | [130] | [120] | [110] | [45] | [45] |
Capacity notes.
- Buffer should be 8-12% of total capacity for unplanned work
- Tech debt allocation should be 10-15% minimum for SaaS companies with 3+ years of codebase
- Do not allocate 100% of any team to a single theme
6. Quarterly Roadmap Sequence
| Initiative | Theme | Owner | Q1 | Q2 | Q3 | Q4 | Eng Weeks | Dependencies |
|---|---|---|---|---|---|---|---|---|
| [Initiative 1] | [Theme 1] | [PM] | Build | Ship | - | - | [20] | [None] |
| [Initiative 2] | [Theme 2] | [PM] | Discovery | Build | Ship | - | [30] | [Initiative 1] |
| [Initiative 3] | [Theme 1] | [PM] | - | Discovery | Build | Ship | [25] | [API migration] |
| [Initiative 4] | [Theme 3] | [PM] | Build | Ship | Iterate | - | [15] | [None] |
| [Initiative 5] | [Theme 2] | [PM] | - | - | Discovery | Build | [20] | [Initiative 2] |
| [Tech debt: DB migration] | Reliability | [Eng] | Prep | Execute | - | - | [12] | [None] |
7. Cross-Functional Dependencies
| Dependency | Owner | Needed By | Status | Risk Level |
|---|---|---|---|---|
| [Marketing launch plan for Initiative 1] | [Marketing lead] | [Q1 Week 8] | [Not started] | [Medium] |
| [Sales enablement for Feature X] | [Sales ops] | [Q2 Week 4] | [Not started] | [Low] |
| [API partner integration] | [Partnerships] | [Q3 Week 1] | [In discussion] | [High] |
| [Infrastructure upgrade] | [Platform eng] | [Q1 Week 6] | [In progress] | [Low] |
8. Risk Register
| Risk | Likelihood | Impact | Mitigation | Owner |
|---|---|---|---|---|
| [Key engineer departure] | [Medium] | [High] | [Cross-train, document, hire backfill pipeline] | [Eng manager] |
| [Competitor launches similar feature] | [High] | [Medium] | [Accelerate Initiative 2 timeline] | [PM lead] |
| [Q2 revenue miss triggers scope cut] | [Medium] | [High] | [Pre-identify which initiatives to defer] | [VP Product] |
9. Review Cadence
| Frequency | Meeting | Attendees | Purpose |
|---|---|---|---|
| Weekly | Squad standups | Squad members | Execution progress, blockers |
| Monthly | Metrics review | Product + Eng leads | Are KRs on track? Adjust tactics |
| Quarterly | Roadmap review | Leadership team | Re-prioritize based on results and market changes |
| Mid-year | Strategy check-in | Exec team + board | Confirm or adjust strategic themes |
Filled Example: CloudMetrics (B2B Analytics SaaS)
Prior Year Summary
Revenue: $3.8M ARR (target $4.5M). Missed due to slow enterprise pipeline. User growth exceeded target (15K MAU vs. 12K target) driven by self-serve signups. Net retention at 108%, below the 115% target. Two of three strategic bets paid off (self-serve onboarding, API platform). One did not (enterprise marketplace).
FY2027 Strategic Themes
Theme 1: Activation (35% capacity). Self-serve users sign up but only 22% reach the "aha moment" in week 1. Goal: increase activation to 40%.
Theme 2: Enterprise expansion (30% capacity). Existing mid-market accounts have expansion potential. Goal: increase net revenue retention from 108% to 120%.
Theme 3: AI-assisted insights (25% capacity). Customers ask "what does this data mean?" more than "show me a chart." Goal: launch AI insights feature, 30% WAU adoption by Q4.
Buffer + tech debt: 10% capacity.
Q1-Q2 Sequencing
Q1: Activation experiments (onboarding wizard, template library, guided setup). Enterprise: discovery interviews with 20 accounts. AI: prototype and internal testing.
Q2: Ship best activation variant. Enterprise: launch expansion playbook and first upsell features. AI: beta with 50 accounts.
Key Takeaways
- Start with a retrospective of the prior year before planning forward
- Align on 3-5 strategic themes that represent meaningful bets, not feature categories
- Every initiative must ladder up to a theme. Orphaned initiatives signal misalignment
- Allocate capacity by theme, not equally across teams. Strategy means choosing
- Build in 10% buffer for unplanned work. No plan survives the year without adjustment
- Establish monthly and quarterly review cadences. Plans are living documents
About This Template
Created by: Tim Adair
Last Updated: 3/5/2026
Version: 1.0.0
License: Free for personal and commercial use