Growth strategy playbook

Growth Strategy Playbook

What this does

Turns research into a 12-month, executable growth strategy. The output is one markdown playbook a client can fund and a team can run: a sharp thesis, a small set of strategic pillars (each with named tactics, an owner, and a KPI), a real M1–M12 calendar anchored to the client's actual seasonal moments, a phased budget and tooling stack, a KPI dashboard with monthly targets, a risk register, an honest account of which tactics the team will and won't use, and three outcome scenarios with explicit decision gates.

When to use it

• Converting a research dossier and competitive matrix into a forward plan.
• Scoping or justifying a retainer or annual engagement.
• Building a client-ready roadmap with budget, calendar, and projected outcomes.
• Re-planning a growth program at the start of a new year or after a pivot.

This is the downstream "what we'll do" companion to client-research-dossier (baseline) and competitive-intel-matrix (field). Pull the wedge, quick wins, and seasonal events from those before drafting.

How to use it

1. Restate the strategic thesis in a TL;DR: the single bet, the target outcome, and the time horizon. Anchor it to the defensible wedge from the research.
2. Define the strategic frame — the through-line that makes the pillars cohere (e.g. "infrastructure capture, not audience expansion").
3. Design the pillars (typically 4–6). Each pillar gets named tactics, a single owner, and a primary KPI. Use the design guidance in references/pillar-and-calendar.md.
4. Build the M1–M12 operating calendar, sequencing pillar tactics across phases (foundation → build → scale → optimize) and pinning them to the client's real seasonal events. Same reference covers calendar construction.
5. Lay out the tech + tooling stack with phased cost (what's needed in months 1–6 vs. 7–12), then an investment plan with line items.
6. Build the KPI dashboard: each pillar's metric with a month-by-month target curve.
7. Write the risk register and the will/won't gray-hat playbook — calibrated tactics the team will use vs. explicit lines it won't cross.
8. Close with Conservative / Base / Optimistic scenarios (revenue, spend, ROI) and the go/no-go decision gates that move the plan between them.
9. Use the full skeleton in references/playbook-template.md as the section order and structure.

Inputs

• The research dossier and/or competitive matrix (or equivalent baseline).
• The client's real revenue/growth target and time horizon.
• Known seasonal events, launch dates, and constraints (budget, capacity, legal).
• Engagement shape if known (retainer tier, project line items).

Output

A single markdown file, typically growth/01_<Client>_12-Month_Growth_Strategy.md, following the template skeleton end to end. Pairs naturally with a separate financial model (xlsx).

Notes & constraints

• Every pillar must have an owner and a KPI; a pillar without a measurable target is a wish, not a strategy.
• Tie the calendar to real dated events (the client's launches, holidays, award cycles, regulatory deadlines) — not generic "Q2 content push."
• Scenarios must be honest: state which figures include existing baseline vs. true incremental lift, and show the payback period.
• The will/won't playbook is non-negotiable — name the gray-hat lines the team refuses to cross so the client trusts the calibrated tactics.
• Keep numeric assumptions in the model/spreadsheet; the playbook narrates and references them. Use forward-slash paths.