Take a product or feature to market
You are shipping something and marketing is a scramble. Launch it with assets done and owners named.
Take a product or feature to market
You are shipping something and marketing is a scramble.
Launch it with assets done and owners named.
Details
Details
Details
Details
Details
0 to our top channel
The product-led motion this launch chain feeds: usage from a shipped feature turned into the best-converting channel.
Positioning
A tiered launch plan
Briefs for the assets that actually need copy
A demand plan or press pitch when the launch is big enough to call for one
The workflow that solves it, one step at a time.
Each step is the plain question you are already asking. The skills answer them in order, one handing its receipt to the next.
Turns what you do, who it's for, and why you win into one positioning statement and a full message house.
Builds a tiered go-to-market launch plan sized to what the release actually deserves.
Turns a keyword or topic plus an audience into a writer-ready brief that kills the back-and-forth.
The ICP, offers by funnel stage, the channel mix, the content, and the pipeline math backward from target.
The story angle, the target journalists by beat, the pitch, and the follow-up a reporter might actually answer.
Positioning, a tiered launch plan, briefs for the assets that actually need copy, and a demand plan or press pitch when the launch is big enough to call for one.
- All 5 chained skills resolve to real, scored skills.
- Has a problem, an outcome, 2+ steps, and proof from a real build.
- Ships an example chat showing the play run in Claude.
- Reads in plain operator voice, grounded in a real build.
We did not just check the structure. A judge read this play against the full text of every skill it chains (composition), then ran it on a real scenario end to end (simulated). It passed both. Test scenario: Riley, Head of Marketing, is shipping a new integration next month with a real pipeline number behind it, and needs the full launch chain run end to end.
This play runs across the org, not inside sales.
Every function below owns a piece of the play. Skip one and it stalls where most GTM plays stall: in the handoff.
Without it: Positioning gets written against a feature that ships different, or late.
Without it: Reps pitch the old deck and the launch dies in week two.
Without it: Your best customers hear the news from a cold email.
Without it: The demand plan launches with a target and no fuel.
Watch the skills answer in order.
Describe your situation in plain language. The right skill fires on its own and hands its receipt to the next.
Before you run it, I ran it for real.
This workflow is genericized from a real build. Here is the number it moved, and what I actually did.
WHAT I DID ›
If you sell a product people can use before they buy, you already have a product-led channel. The question is never whether it exists. It is whether your usage data has been turned into context a rep can act on. Map the events first. The motion comes after.
Dig into the full build →A launch is only as good as the story reps repeat
The positioning brief and the tiered plan hand the team one story and a dated asset list; the pipeline comes from whether sales still says it the same way in week two. Here is how a marketing leader turns a launch plan into a motion every function runs on cue.
Before launch day, every function reads its piece aloud against the positioning-brief: the rep pitch, the demand copy, the press angle. Anything that tells a different story gets rewritten or cut before it ships.
- 01Certify the field on the story
Reps rehearse the new pitch against the message house and clear a bar before launch day. A launch the field cannot retell is a press release, not a launch.
- 02Tier it before you staff it
Use launch-plan's tiering to size the effort before anyone gets assigned, so a minor ship does not eat the calendar a Tier 1 needs. The demand-gen-plan and pr-outreach steps only run when the tier calls for them.
- 03Run the launch-week standup
Daily during launch week, owners report against the asset list the content-brief step named: shipped, slipped, or blocked. The list came from the plan, so nobody argues about scope in the standup.
- 04Hold the day-30 retro
Compare what shipped to what the plan promised, and what the demand math predicted to what arrived. Fix the template and the tiering rules, not the people.
One plugin. 5 skills, bundled.
The whole playbook installs as a single plugin in Claude Code, no copy-pasting 5 times. Or grab any single step above. It runs on what you paste; connect your stack to go live.