What This Template Is For
Annual planning is where product strategy becomes resource allocation. Without a structured planning process, annual plans devolve into wish lists. Every team lobbies for headcount, every stakeholder submits their pet project, and the final plan is a politically negotiated compromise instead of a strategic document. This template provides a repeatable framework for turning company strategy into product themes, themes into bets, bets into quarterly milestones, and milestones into resource commitments.
The template works for product orgs of 5-50 people. It assumes you have a company-level strategy (even if informal) and at least one quarter of historical data. The output is a one-page annual plan that the entire company can reference, plus a detailed backing document with quarterly breakdowns and resource allocations.
For the strategic thinking that precedes annual planning, the Product Strategy Handbook covers vision, positioning, and competitive strategy. If you need a prioritization framework for ranking bets, the RICE Calculator provides quantitative scoring. The Quarterly Product Roadmap template gives you the format for breaking the annual plan into executable quarters. For aligning stakeholders on the plan, the Stakeholder Management Handbook covers communication strategies.
How to Use This Template
- Start 6-8 weeks before your fiscal year begins. Annual planning done in 2 weeks is rushed and produces weak plans.
- Begin with the Strategy Input section. Gather company objectives, market context, and customer data before generating ideas.
- Define 3-5 Strategic Themes. These are the high-level bets for the year. Everything in the plan should map to a theme.
- For each theme, define specific Bets with expected outcomes, resource requirements, and quarterly milestones.
- Allocate resources across themes. This is the hardest step. Use the Resource Allocation section to make trade-offs explicit.
- Get executive sign-off on the plan before Q1 starts. Share the one-page summary broadly. Keep the detailed plan accessible to the product org.
- Review the plan quarterly and adjust. The annual plan is a starting point, not a contract.
The Template
Strategy Inputs
Gather these inputs before the planning session.
| Input | Source | Summary |
|---|---|---|
| Company mission | CEO / Board | [One sentence] |
| Annual company objectives | Leadership team | [3-5 company-level goals] |
| Revenue targets | Finance | [ARR target, growth rate, key segments] |
| Market context | Product / Strategy | [Competitive moves, market trends, regulatory changes] |
| Customer feedback themes | CS / Product | [Top 5 pain points from customers] |
| Technical debt assessment | Engineering | [Critical debt items, estimated cost to address] |
| Previous year retrospective | Product | [What worked, what did not, lessons learned] |
Strategic Themes
Define 3-5 themes that will drive the year's product investment. Each theme should be a statement of strategic intent, not a feature list.
| # | Theme | Strategic Rationale | Success Metric | Target | Investment Level |
|---|---|---|---|---|---|
| 1 | [Theme name] | [Why this matters for the business] | [Primary metric] | [Target value] | [% of eng capacity] |
| 2 | [Theme name] | [Why this matters for the business] | [Primary metric] | [Target value] | [% of eng capacity] |
| 3 | [Theme name] | [Why this matters for the business] | [Primary metric] | [Target value] | [% of eng capacity] |
| 4 | [Theme name] | [Why this matters for the business] | [Primary metric] | [Target value] | [% of eng capacity] |
| 5 | [Infrastructure / Debt] | [Maintain velocity and reliability] | [Uptime, deploy frequency] | [Target value] | [15-25% of eng capacity] |
Theme selection checklist.
- ☐ Each theme maps to at least one company-level objective
- ☐ No more than 5 themes (focus requires saying no)
- ☐ At least one theme addresses customer retention, not just acquisition
- ☐ Infrastructure/debt gets a dedicated allocation (15-25% minimum)
- ☐ Each theme has a measurable success metric, not just a deliverable
Bets per Theme
For each theme, define 2-4 specific bets. A bet is a hypothesis: "If we build X, we expect Y outcome."
Theme 1: [Theme Name]
| Bet | Hypothesis | Expected Outcome | Confidence | Size (T-shirt) | Quarter |
|---|---|---|---|---|---|
| [Bet 1.1] | If we [action], then [outcome] because [reasoning] | [Metric: X to Y] | [High/Med/Low] | [S/M/L/XL] | [Q1/Q2/Q3/Q4] |
| [Bet 1.2] | If we [action], then [outcome] because [reasoning] | [Metric: X to Y] | [High/Med/Low] | [S/M/L/XL] | [Q1/Q2/Q3/Q4] |
| [Bet 1.3] | If we [action], then [outcome] because [reasoning] | [Metric: X to Y] | [High/Med/Low] | [S/M/L/XL] | [Q1/Q2/Q3/Q4] |
Repeat for each theme.
Resource Allocation
| Team / Pod | Headcount | Theme 1 (%) | Theme 2 (%) | Theme 3 (%) | Theme 4 (%) | Infra/Debt (%) | Total |
|---|---|---|---|---|---|---|---|
| [Team A] | [X] | [%] | [%] | [%] | [%] | [%] | 100% |
| [Team B] | [X] | [%] | [%] | [%] | [%] | [%] | 100% |
| [Team C] | [X] | [%] | [%] | [%] | [%] | [%] | 100% |
| Total | [X] | [%] | [%] | [%] | [%] | [%] | 100% |
Hiring plan.
| Role | Team | Theme | Start Date | Status |
|---|---|---|---|---|
| [Senior PM] | [Team A] | [Theme 1] | [Q1] | [Open / Approved / Filled] |
| [Staff Engineer] | [Team B] | [Theme 3] | [Q2] | [Open / Approved / Filled] |
| [Product Designer] | [Team C] | [Theme 2] | [Q1] | [Open / Approved / Filled] |
Quarterly Milestones
Break the annual plan into quarterly checkpoints.
Q1: Foundation
- ☐ [Milestone 1.1]: [Specific deliverable or outcome]
- ☐ [Milestone 1.2]: [Specific deliverable or outcome]
- ☐ [Milestone 1.3]: [Specific deliverable or outcome]
Q2: Acceleration
- ☐ [Milestone 2.1]: [Specific deliverable or outcome]
- ☐ [Milestone 2.2]: [Specific deliverable or outcome]
- ☐ [Milestone 2.3]: [Specific deliverable or outcome]
Q3: Execution
- ☐ [Milestone 3.1]: [Specific deliverable or outcome]
- ☐ [Milestone 3.2]: [Specific deliverable or outcome]
- ☐ [Milestone 3.3]: [Specific deliverable or outcome]
Q4: Optimization and Planning
- ☐ [Milestone 4.1]: [Specific deliverable or outcome]
- ☐ [Milestone 4.2]: [Specific deliverable or outcome]
- ☐ Annual plan retrospective completed
- ☐ Next year's planning process kicked off
Risks and Mitigations
| Risk | Likelihood | Impact | Mitigation | Owner |
|---|---|---|---|---|
| [Key hire does not close in Q1] | [High/Med/Low] | [Which theme is affected] | [Contingency: redistribute work, extend timeline] | [Name] |
| [Competitor launches similar feature] | [High/Med/Low] | [Which theme is affected] | [Contingency: differentiate on X, accelerate Y] | [Name] |
| [Technical debt blocks Theme 3] | [High/Med/Low] | [Which theme is affected] | [Contingency: increase infra allocation by X%] | [Name] |
One-Page Summary
This is the version you share with the entire company.
| Field | Details |
|---|---|
| Vision for the year | [One sentence: what the product will become by year-end] |
| Theme 1 | [Name]: [One sentence summary] |
| Theme 2 | [Name]: [One sentence summary] |
| Theme 3 | [Name]: [One sentence summary] |
| Theme 4 | [Name]: [One sentence summary] |
| Infra | [X% of capacity dedicated to reliability and debt] |
| Primary success metric | [The single metric that indicates the year was successful] |
| Hiring plan | [X new hires planned across product, engineering, and design] |
Filled Example: CloudMetrics FY2026 Plan
Strategy Inputs (Filled)
| Input | Summary |
|---|---|
| Company mission | Make product analytics accessible to every SaaS team |
| Annual company objectives | Reach $25M ARR, expand enterprise (>50% of new ARR), launch AI product line |
| Revenue targets | $25M ARR (from $18.2M), 37% growth |
| Market context | Amplitude and Mixpanel cutting prices. AI analytics emerging as a category. |
| Customer feedback | Top pain: alerting is unreliable. #2: dashboards are slow. #3: no AI insights. |
| Technical debt | Query engine needs rewrite (est. 2 engineers, 2 quarters). Alerting infra is fragile. |
Strategic Themes (Filled)
| # | Theme | Success Metric | Target | Investment |
|---|---|---|---|---|
| 1 | Enterprise Ready | Enterprise NRR | 120%+ | 30% |
| 2 | AI-Powered Insights | AI feature adoption | 25% of active users | 25% |
| 3 | Core Performance | Dashboard load time (p95) | < 2 seconds | 20% |
| 4 | Self-Serve Growth | Activation rate (day-7) | 40% (from 28%) | 10% |
| 5 | Infrastructure | Uptime, deploy frequency | 99.95%, 20 deploys/week | 15% |
Q1 Milestones (Filled)
- ☑ Launch SSO and RBAC for Enterprise theme
- ☑ Ship AI anomaly detection beta (10 customers)
- ☐ Reduce p95 dashboard load from 4.2s to 3.0s
- ☐ Hire 2 engineers for AI team
Common Mistakes to Avoid
- Planning bottom-up instead of top-down. Starting with feature requests and working up to themes produces a plan that is a patchwork of tactical asks. Start with strategy, then derive bets, then scope features.
- Allocating 100% of capacity to new features. Teams need 15-25% of capacity for infrastructure, debt, and unplanned work. Plans that assume 100% feature capacity will slip every quarter.
- Treating the plan as a contract. The annual plan is a strategic direction, not a commitment to ship specific features by specific dates. Review quarterly and adjust based on what you learn.
- Too many themes. Five themes is the upper limit. Companies that run 8-10 themes in parallel make incremental progress on everything and transformative progress on nothing.
Key Takeaways
- Annual planning is resource allocation, not feature listing
- Start with company strategy and derive 3-5 product themes
- Each theme needs measurable success criteria, not just deliverables
- Reserve 15-25% of engineering capacity for infrastructure and debt
- Review quarterly and adjust. The plan is a compass, not a map
About This Template
Created by: Tim Adair
Last Updated: 3/4/2026
Version: 1.0.0
License: Free for personal and commercial use