GTM & Operational Strategy

Two complementary modules: the GTM Roadmap (time-axis strategy with evolving platform weights and calibrated targets) and the Operational Strategy (the style manual — voice framework + per-platform caption rules).

GTM Roadmap

The go-to-market engine decides where the brand is going phase by phase. Dual-horizon generation with parallel variants:

1. Generate 3 × 90-day variants in parallel → LLM picks the best
2. Generate 3 × 6-month variants extending the chosen 90-day plan → LLM picks the best

This ensures 90d and 6m are coherent and each horizon is the best of 3.

What a phase contains

• Name — e.g. "Fondamenta", "Trazione", "Scala"
• Objective — one-line job description
• Rationale — data-grounded why (the user reads this)
• Duration — phases together cover the horizon
• Platform weights — MUST EVOLVE phase to phase (the evolution IS the strategy)
• Pillars — 2-4 content pillars/CTAs to anchor
• Goals — 2-4 honest, calibrated targets

The active GTM phase is injected into every planner brief via activeGtmBrief() — the roadmap actually steers production.

Conversational redirect

The user says what to change (e.g. "drop Threads, focus on TikTok"). Anomalia recalculates the WHOLE plan coherently — removing a platform redistributes its weight sensibly. Returns a reply explaining what changed + a changes summary for the UI.

At phase end, reviewPhase() compares real KPIs with targets: on_track → proceed; adjust → propose course correction.

Operational Strategy

The style manual derived from everything the Studio knows. Two parts:

Voice framework

Per-platform rules

One row per connected platform: tone, target length, emoji policy, hashtag policy, typical structure. Example: "Instagram: conversational, warm. Length: 700-1500 chars. Emoji: max 2. Hashtags: 3-5 niche. Structure: hook → 3 short paragraphs → question."

The rules are converted to platformInstructions that the content production pipeline already consumes.