gtm-launch

name	gtm-launch
description	Plan, coordinate, and iterate startup go-to-market launches using real adoption and retention evidence. Use when the agent needs to organize launch phases, coordinate channels and assets, define launch metrics, or drive toward repeatable go-to-market and early product-market-fit signals.

GTM Launch

Purpose

Run launch work as a measured operating loop rather than a one-day event. Coordinate channels, messaging, and learning windows around the signals that matter.

Operating Frame

• Optimize for qualified usage and retention, not raw attention.
• Coordinate channels in parallel only when the message, asset, and metric owner are explicit.
• Keep launch state current across phases so iteration decisions do not rely on memory.
• Label major claims as evidenced, inferred, or unverified.

Minimum Inputs

• Primary launch goal
• Target audience and wedge
• Available channels, assets, and owners
• Metrics already tracked and any guardrails

If critical facts are missing, ask for the single highest-leverage unknown or mark the assumption as provisional and continue.

Workflow

1. Define the launch goal: awareness, activation, pipeline, revenue, or retention proof. Choose one primary outcome and name the guardrail metrics that must not degrade.
2. Break the launch into phases: pre-launch setup, launch window, read period, and iteration round.
3. For each channel, record audience, message, asset, owner, success metric, failure condition, and follow-up action.
4. Maintain a launch state log with date, action taken, result, interpretation, and next move. If the work becomes multi-lane, use $team to coordinate parallel channel execution against the same brief.
5. Read metrics in sequence: reach first, then activation, then retention or revenue. Avoid declaring success from top-of-funnel noise while the lower funnel is weak.
6. Decide whether to double down, iterate, narrow the wedge, or stop based on the predefined thresholds.

Required Outputs

• Launch brief
• Channel plan
• Metric tree with leading and lagging indicators
• Phase log
• Decision rules for iterate, expand, or stop

Default Output Format

Use this section order unless the user needs a calendar, dashboard, or team brief:

1. Launch goal
2. Audience and wedge
3. Channel plan
4. Metric tree
5. Phase log
6. Read-period interpretation rules
7. Iterate, expand, or stop decision
8. Recommended next skill

Verification Gate

Do not call the launch successful on impressions, signups, or press alone. Require evidence that the intended user took the intended action and that the signal persists past the initial spike.

Handoff

• Use $growth-engine when the launch creates a repeatable funnel worth optimizing.
• Loop back to $value-validation if the market response contradicts the original wedge.