⚡ Promptolis Original · Business & Strategy
📅 Annual Planning Framework — Strategy + OKRs + Budget In 90 Days
The structured 90-day annual planning cycle — covering the strategic direction setting (October), OKR cascade (November), budget + resource allocation (December), and team-level rollout (January) that produces actionable plans rather than shelf-ware strategic documents.
Why this is epic
Most companies do 'annual planning' in a 2-week rush in December. Result: strategic direction unclear, OKRs are last-year+10%, budget misaligned with strategy. This Original produces the 90-day annual planning cycle: October strategic direction, November OKR cascade, December budget, January rollout.
Names the 4 common annual planning failures: rushed (all in December), disconnected (strategy + OKRs + budget separate), top-down-only (no team input), no rollout (plan in binder, teams unaware). Each has structural fix.
Produces complete annual planning sequence: October strategic offsite, November OKR cascade with each function, December budget alignment, January all-hands + team-level cascades, quarterly checkpoints through year. Based on Google OKR methodology + Bain annual planning research.
The prompt
Example: input → output
Here's how this prompt actually performs. Real input below, real output from Claude Opus 4.
<company-context>Series B SaaS, $30M ARR, 180 employees, 8 execs, 12 teams.</company-context> <planning-history>Mixed. Last 2 years: rushed December planning, OKRs not cascaded, budget disconnected from strategy. Team felt plan was imposed. 2026 needs to be better.</planning-history> <planning-calendar>Fiscal year = calendar year. Planning for 2026 starting October 2025. Board reviews mid-December.</planning-calendar> <org-structure>CEO + 7 VPs (Product, Engineering, Sales, Marketing, CS, People, Finance). Each VP has 2-4 team leads. About 12 discrete teams. Some cross-functional.</org-structure> <strategic-context>Growth deceleration year. Enterprise pivot being considered. Fundraise timing decision needed. Need better execution discipline.</strategic-context> <stakeholders>CEO drives. COS (Sarah) owns operational planning process. CFO owns budget. Each VP owns their function plan.</stakeholders> <prior-year-learnings>2025 plan: ambitious but not executed well. Strategy was clear but OKRs didn't cascade. Budget prioritized existing initiatives over new. Team alignment weak by Q2.</prior-year-learnings> <resource-constraints>Cash runway 18 months. Need to hit 2026 milestones to raise well. Team scale 220 cap.</resource-constraints>
Annual Planning: Series B SaaS, 2026 Planning, Fix Prior Year Weaknesses
An annual planning framework produces 90-day cycle transforming strategy into executed plans rather than shelf-ware documents. Based on Bain research + Google OKR methodology, planning processes succeed when 4 elements align: October strategic direction, November OKR cascade, December budget alignment, January rollout — each building on the previous. Your situation — prior-year planning rushed/disconnected, growth deceleration, enterprise pivot needed — is ideal for structural planning redesign. This framework produces 90-day calendar with specific milestones, OKR cascade methodology, budget-to-strategy alignment, and rollout approach designed to fix 2025 failures.
90-Day Planning Calendar
| Month | Primary Focus | Output |
|---|---|---|
| October | Strategic direction | Exec alignment on 2026 strategy |
| November | OKR cascade | Company + function + team OKRs set |
| December | Budget + resource allocation | Annual budget approved |
| January | Rollout + launch | All-hands + team-level OKR cascades |
| Q1-Q4 | Checkpoints | Quarterly reviews + adjustments |
October: Strategic Direction (Weeks 1-4)
Week 1 (Oct 1-7): Pre-Work
Each exec prepares:
- 2025 function review (what worked, what didn't)
- Key strategic challenges for 2026
- Initial priorities + resource asks
Analyst prepares:
- 2025 company metrics + variance to plan
- Competitive + market analysis
- Customer insights + satisfaction trends
Output: pre-read materials for exec offsite
Week 2 (Oct 8-14): Exec Strategic Offsite
2-3 day offsite. Strategic decisions made.
Day 1: Divergent
- Market + competitive review
- Customer insights review
- Company performance honest assessment
- Options generation (strategic directions)
Day 2: Convergent
- Strategic direction decisions
- 3-5 strategic priorities for 2026
- Decision on fundraise timing
- Enterprise pivot commitment (or not)
Day 3: Integration (half-day):
- Resource implications of decisions
- Cross-functional dependencies
- Stop-doing list
Output: 5-page 2026 strategic memo
Week 3 (Oct 15-21): Board + Leadership Preview
- Share strategic direction with board informally (not formal approval — input)
- Present to second-level leadership (12 team leads) for input
- Iterate based on feedback
- Finalize strategic direction
Week 4 (Oct 22-31): Strategy Finalization
- 2026 Strategic Memo finalized (10-15 pages, company-wide shareable)
- Communicate strategic direction to all-hands (30-min overview)
- Transition to OKR cascade phase
Month 1 Output: 2026 strategic direction locked + communicated.
November: OKR Cascade (Weeks 5-8)
Week 5 (Nov 1-7): Company OKRs
CEO + exec team sets company OKRs:
- 3-5 Objectives for 2026
- 3-4 Key Results per Objective
- Aligned with strategic direction from October
Example 2026 Company OKRs:
O1: Establish enterprise segment as primary growth engine
- KR1: Close 12 enterprise logos ($200K+ ACV) in 2026
- KR2: Enterprise segment revenue reaches 35% of total ARR
- KR3: Sales cycle for enterprise averages <120 days
O2: Build defensible AI-powered product moat
- KR1: Ship 3 AI-powered features with measurable customer value
- KR2: 40% of customers use AI features within 6 months of launch
- KR3: AI-feature-using customers show 2x expansion rate
O3: Achieve sustainable unit economics
- KR1: NRR back to 120%+ by Q4
- KR2: CAC payback <12 months
- KR3: Gross margin improves from 70% to 75%
O4: Scale team capabilities to support 2x growth
- KR1: 35 hires net (180 → 215, below 220 cap)
- KR2: Voluntary attrition <8% annualized
- KR3: Engagement survey score >75
Output: company OKRs approved by exec team + board preview
Week 6 (Nov 8-14): Functional OKRs
Each VP cascades company OKRs into function OKRs.
Example — VP Sales cascade from Company O1:
Function O1: Drive enterprise revenue
- KR1: Close 12 enterprise logos (directly from company KR1)
- KR2: Build enterprise AE team (3 enterprise-experienced hires)
- KR3: Enterprise pipeline $5M+ by Q2
Function O2: Protect mid-market base
- KR1: Mid-market NRR to 115% (from 110%)
- KR2: Mid-market gross retention >93%
- KR3: Expansion pipeline from mid-market $2M
Rule: every functional OKR ties to company OKR. No orphan OKRs.
Week 6 includes VP-to-VP alignment sessions (resource dependencies, shared goals).
Week 7 (Nov 15-21): Team OKRs
Each team lead cascades function OKRs into team OKRs.
Same discipline: team OKRs tie to function OKRs.
Example — Enterprise Sales Team OKRs (from VP Sales function O1):
- KR1: Close 12 enterprise logos (team ownership)
- KR2: Team of 3 AEs, 1 SE, 1 AM fully ramped by Q2
- KR3: Pipeline coverage ratio 4x quota by each quarter
Week 8 (Nov 22-30): OKR Integration + Finalization
- All OKRs reviewed for alignment + feasibility
- Exec team OKR review meeting
- Adjustments if any disconnects
- Final OKR document shared
Month 2 Output: cascaded OKRs at company + function + team levels
December: Budget + Resource Allocation (Weeks 9-12)
Week 9 (Dec 1-7): Budget Drafting
CFO drives with each VP:
- Headcount planning per function (aligned with OKRs)
- Operating expense per function
- Capital requests
- Marketing/sales investment
- Budget reconciles to company financial model
Week 10 (Dec 8-14): Budget Review + Negotiation
- CFO consolidates requests
- Total requests typically exceed capacity — forced prioritization
- Exec team decides final allocation
- Some functions get less than requested (tough decisions)
Week 11 (Dec 15-21): Board Approval
- Final budget presented to board with supporting strategy + OKRs
- Board approval (typically mid-December board meeting)
- Any adjustments made
Week 12 (Dec 22-31): Final Preparations
- Holiday break mostly
- Preparation materials for January rollout
- Dec 29-31: pre-rollout team calibration
Month 3 Output: 2026 budget approved, aligned with strategy + OKRs
January: Rollout + Launch (Weeks 13-16)
Week 13 (Jan 1-7): All-Hands Launch
Company-wide all-hands (1 hour):
- CEO presents 2026 strategic direction (15 min)
- Company OKRs (10 min)
- Key initiatives (15 min)
- Resources + team growth plan (10 min)
- Q&A (15 min)
Then: each VP presents function 2026 plan (30-45 min per function, attended by function)
Week 14 (Jan 8-14): Team-Level Cascades
- Each team lead runs team meeting to cascade team OKRs
- Individual goal-setting conversations with each team member
- Individual OKRs set (where applicable) for top priorities
Week 15 (Jan 15-21): Execution Infrastructure
- OKR tracking tool/system set up (Asana, Lattice, etc.)
- Weekly/monthly check-in cadences established
- Dashboard design for real-time tracking
- Integration with performance management
Week 16 (Jan 22-31): Execution Begins
- First weekly check-ins happen
- Any gaps in rollout identified + addressed
- Q1 execution in motion
- Early signals gathered
Month 4 Output: 2026 plan rolled out + execution underway at all levels
Quarterly Checkpoints (Through Year)
End of Q1 (Early April):
Full day review:
- Company OKR status
- Function OKR status
- Early signals on strategy
- Adjustments needed?
Likely outcomes:
- 2-3 KRs ahead of schedule (amplify)
- 2-3 KRs behind (intervention)
- 1-2 surprises (new opportunity or threat)
Output: Q2 priorities + adjustments to annual plan
End of Q2 (Early July):
- Mid-year review
- Significant course correction if needed
- Hiring plan review
- Customer/market validation of strategy
End of Q3 (Early October):
- Q4 push planning
- 2027 planning KICKOFF
- Strategic questions surfacing for next year
End of Q4 (January of following year):
- Final OKR scoring
- Year retrospective
- What worked, what didn't
- Inputs to next year planning
Stakeholder Roles
CEO:
- Strategic direction (October)
- Final OKR approval (November)
- Budget decisions (December)
- Rollout communication (January)
- Quarterly reviews
COS (Sarah):
- Planning calendar + process (ongoing)
- Pre-work coordination
- Rollout execution
- Quarterly checkpoint facilitation
CFO:
- Budget process ownership (December)
- Financial model + constraints
- Quarterly financial reviews
Each VP:
- Function strategic plan
- Function OKR setting
- Team-level cascade
- Quarterly function review
Each team lead:
- Team OKR setting
- Individual goal conversations
- Weekly/monthly progress
All employees:
- Input during October/November
- Understanding + execution January+
Common Failure Modes
Failure 1: Rushed (all in December)
Symptom: 2-week planning produces incremental plans, not strategic.
Fix: 90-day calendar with October start.
Failure 2: Disconnected (strategy + OKRs + budget separate)
Symptom: strategy says 'enterprise pivot' but budget funds mid-market growth.
Fix: OKRs cascade from strategy + budget follows OKRs.
Failure 3: Top-down only
Symptom: frontline doesn't see reality in plan.
Fix: second-level leadership input Week 3 of October + VP dialogue with teams.
Failure 4: No rollout
Symptom: plan exists in binder, teams don't know it.
Fix: January rollout 4-week protocol.
Failure 5: No checkpoints
Symptom: plan irrelevant by Q2.
Fix: quarterly checkpoints with real adjustment capability.
Failure 6: No stop-doing list
Symptom: team overloaded because plan adds but doesn't subtract.
Fix: explicit stop-doing identification in October offsite.
Key Takeaways
- 90-day planning cycle: October strategy + November OKRs + December budget + January rollout. Prior-year 2-week December rush failed because of compression.
- OKRs cascade company → function → team. Every team OKR ties to function OKR ties to company OKR. No orphans. Fix for 2025's 'OKRs didn't cascade' problem.
- Budget follows OKRs follows strategy. Inversion (budget first) produces incremental thinking. Strategic priorities drive resource allocation.
- Rollout matters more than planning document. January all-hands + function presentations + team cascades + individual conversations. 4-week rollout protocol.
- Quarterly checkpoints with adjustment capability. Annual plan is hypothesis, not locked contract. Q1 data informs Q2 adjustments. Prevent drift.
Common use cases
- CEOs installing disciplined annual planning
- COS/Chief of Staff roles owning planning calendar
- Companies moving from reactive to strategic
- Series B+ companies institutionalizing process
- Teams wanting better strategy-OKR-budget alignment
Best AI model for this
Claude Opus 4 or Sonnet 4.5. Annual planning requires strategic + operational + organizational discipline. Top-tier reasoning matters.
Pro tips
- Start October 1 for calendar-year plan. Last-minute December planning produces last-minute December execution.
- OKRs cascade from company → function → team → individual. Not 'everyone sets OKRs,' hierarchical alignment.
- Budget follows strategy follows OKRs. Inversion (budget first) creates incremental thinking.
- Rollout matters more than planning document. Plan read by 5 execs ≠ plan executed by 500 employees.
- Checkpoints quarterly. Without review cadence, annual plan drifts + becomes irrelevant.
- Version 2 of plan after Q1 learnings. Don't treat year plan as locked.
- Frontline input essential. Top-down-only planning misses reality.
- Stop-doing list is most-missed element. Annual planning = adding. Must also stop.
Customization tips
- Move your fiscal year planning start date to give 90 days. If your FY is April-March, start planning in January (not rushed in March).
- First-year installing this process, expect it to be imperfect. Year 2 and 3 get better. Institutional muscle takes time.
- Tie individual performance reviews to OKR outcomes. Otherwise OKRs feel disconnected from individual work.
- Publish company + function OKRs internally. Transparency drives alignment. Team-level OKRs can be shared within team.
- For startups <50 employees, scale down: 60-day process, fewer OKR layers. But keep the discipline. Structure beats informality even at small scale.
Variants
First Annual Planning
For first-time structured planning. Foundation-building.
Established Rhythm
For companies with annual planning experience. Optimization focus.
Startup (30-50 employees)
Scaled-down version for startup context.
Growth Stage (100-500 employees)
Full process with functional cascades.
Frequently asked questions
How do I use the Annual Planning Framework — Strategy + OKRs + Budget In 90 Days prompt?
Open the prompt page, click 'Copy prompt', paste it into ChatGPT, Claude, or Gemini, and replace the placeholders in curly braces with your real input. The prompt is also launchable directly in each model with one click.
Which AI model works best with Annual Planning Framework — Strategy + OKRs + Budget In 90 Days?
Claude Opus 4 or Sonnet 4.5. Annual planning requires strategic + operational + organizational discipline. Top-tier reasoning matters.
Can I customize the Annual Planning Framework — Strategy + OKRs + Budget In 90 Days prompt for my use case?
Yes — every Promptolis Original is designed to be customized. Key levers: Start October 1 for calendar-year plan. Last-minute December planning produces last-minute December execution.; OKRs cascade from company → function → team → individual. Not 'everyone sets OKRs,' hierarchical alignment.
Explore more Originals
Hand-crafted 2026-grade prompts that actually change how you work.
← All Promptolis Originals