Ship the launch with assets done and owners named.
“We are shipping a feature in three weeks and nobody has said who owns the launch. What now?”
Builds a tiered go-to-market launch plan sized to what the release actually deserves.
What this skill does
Turns "we are shipping something" into a plan someone can run. It sizes the launch to a tier, then fills in the audiences to reach, the channels to reach them, the assets each channel needs, a timeline with a real launch day, the owner for every piece, and the handful of metrics that decide whether it worked. No orphaned tasks, no launch day where the assets are not done.
Inputs
- Works today with: what you are shipping, who it is for, why it matters, and the date you want to launch. Paste it and the skill returns the tiered plan now.
- More powerful connected to a CRM or a marketing tool: it sizes real audience segments and picks the channels that reached them last time.
- Sharper with a web-analytics tool: it sets baseline metrics from your real traffic, so the win condition is grounded, not guessed.
- Sharper with a content or social tool: it can slot the assets into a real publishing calendar instead of a static list.
How it works
- 1Tier the launch (T1 / T2 / T3)
First decision, everything follows from it. T1 is a major bet: full channel push, sales enablement, press. T2 is a standard feature: email, blog, social, in-app. T3 is a minor update: changelog and one in-app note. The skill recommends a tier from WHAT and lets you override.
- 2Audiences
Names who needs to hear it, in priority order: existing users who benefit today, prospects it unblocks, and internal teams (sales, support) who field the questions. Real segment sizes when a CRM is connected, named segments when not.
- 3Channels and assets
Maps each audience to the channels that reach them, and each channel to the exact asset it needs: the email, the blog post, the social thread, the in-app note, the sales one-pager. Every asset has a channel and every channel has an audience. Nothing floats.
- 4Timeline and owners
Back-plans from launch day across LEAD_TIME: asset drafts, reviews, a go or no-go, launch, and follow-up. Every item has a named owner. An unowned task is flagged before it becomes a launch-day surprise.
- 5Win metrics
Two or three metrics that decide success, matched to the tier and the goal: adoption of the feature, signups from the campaign, pipeline influenced. Baselines come from a connected analytics tool, or are labeled "set a baseline" when none is connected. A launch with no win condition is just noise.
Output format
LAUNCH PLAN · shipping: bulk-export feature · recommended tier: T2
Audiences (priority):
1. Existing power users (benefit today)
2. Prospects who asked for export
3. Support + sales (will field questions)
Channels -> assets -> owner -> due:
Email release note to power users PMM L-2
Blog how-to with screenshots PMM L-3
In-app tooltip on the export button PM L-1
Social 3-post thread PMM L-day
Sales one-pager + talk track PMM L-2
Timeline (LEAD_TIME 14):
L-14 kickoff -> L-5 drafts done -> L-2 review + go/no-go
-> L-day ship -> L+7 follow-up post
Win metrics (T2):
- Feature adoption among power users (set a baseline)
- Export-related tickets down (set a baseline)
Next: connect a CRM to size the power-user segment for real.
Tips
- Every asset has a channel, an owner, and a due date before launch day. No orphans.
- The tier is stated and justified. A T3 does not get a T1 budget.
- Win metrics are named up front, with a baseline or a clear "set a baseline" flag.
- Illustrative audience sizes and metric targets are marked as examples, never presented as your real data.
Write positioning your whole team can repeat the same way.
Turns what you do, who it's for, and why you win into one positioning statement and a full message house.
Get quoted by answer engines and clicked in search.
Audits a page or site on both tracks and returns effort-vs-impact ranked fixes so an AI answer engine will quote you.