annual-planning

Annual Planning Workflow

Overview

The kickoff-of-year workflow. Max Growth runs the planning sessions with the user, then issues per-domain quarterly briefs so each domain orchestrator (PMM, Brand, Content, Digital, Growth, Field, PR, Channel) can start their Q1 work against a single source of truth.

Phases

1. Inputs — Refresh company-context (run bootstrap if missing).
2. Strategy — Pick the 2-3 dominant motions per quarter.
3. Resourcing — Budget split + headcount + dependency map.
4. Domain briefs — Issue annual brief packs to each domain.
5. Cadence — Set the quarterly re-plan ritual.

Source Fidelity

These rules override the persona.

• Never invent numbers about the user's business or industry. Metrics, percentages, dollar amounts, audience sizes, conversion rates, benchmarks — all numbers must come from a source: the user's input, a WebSearch result cited inline, or a file the user shared. Anything else is fabrication.
• Missing data → ask, don't fill. If a step needs a number the user hasn't provided, ask one focused question before proceeding. Do not insert a plausible default.
• Label examples. Sample emails / posts / dashboards / sequences that contain numbers must be prefixed Example — illustrative, not benchmarks.
• Persona is style, not authority. Identity backstory ("Built X for Y companies", "Former Head of Z") is for tone — not a license to invent client names, study results, proprietary stats, or "I've seen this in 30+ companies"–style claims.

On Activation

1. Load configuration (tolerant of missing files):

   • Try {project-root}/_bmad/config.yaml. If present, read core.user_name, core.communication_language, core.document_output_language, and marketing-growth.output_folder.
   • Try {project-root}/_bmad/config.user.yaml. If present, its core.user_name and core.communication_language override the shared values.
   • For any value still missing, use defaults: user_name = there, communication_language = English, document_output_language = English, output_folder = {project-root}/_bmad-output.

2. Confirm company-context exists: {output_folder}/company-context/icp.md, positioning.md, kpis.md. If any missing, route the user to /company-context-bootstrap first.

3. Load and execute the sibling workflow.yaml phase by phase. Delegate to specialist agents as directed.

4. Save outputs to {output_folder}/work/{yyyy}-annual-plan/.