Launch Strategy

When the user wants to plan a product launch, feature announcement, or release strategy.

How to use it

  1. Hit Copy SKILL.md — or use the Claude Code line below to get every file.
  2. Claude: ⋯ → Download .md, then Customize → Skills → Add → Upload skill.
    ChatGPT: make a Project and paste it into Instructions.
    Neither? Paste it at the top of a new chat — it works for that chat.
  3. Describe your job in plain words. The AI follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit coreyhaines31/marketingskills/skills/launch#main ~/.claude/skills/launch

For one project only, change the path to .claude/skills/launch. This skill also uses product-marketing-context.md — copying SKILL.md alone won't be enough. See the folder on GitHub.

Not working?
  • Check which app you pasted it into — the steps above name the right one.
  • Some skills need the paid tier of Claude or ChatGPT.
Step-by-step guide with screenshots · Ask in the forum

Paste into Claude, ChatGPT or Cursor.

Show the full text382 lines
launch/SKILL.md382 lines14.8 KBpushed 29d agoRawView on GitHub

Launch Strategy

You are an expert in SaaS product launches and feature announcements. Your goal is to help users plan launches that build momentum, capture attention, and convert interest into users.

Before Starting

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.


Core Philosophy

The best companies don't just launch once—they launch again and again. Every new feature, improvement, and update is an opportunity to capture attention and engage your audience.

A strong launch isn't about a single moment. It's about:

  • Getting your product into users' hands early
  • Learning from real feedback
  • Making a splash at every stage
  • Building momentum that compounds over time

The ORB Framework

Structure your launch marketing across three channel types. Everything should ultimately lead back to owned channels.

Owned Channels

You own the channel (though not the audience). Direct access without algorithms or platform rules.

Examples:

  • Email list
  • Blog
  • Podcast
  • Branded community (Slack, Discord)
  • Website/product

Why they matter:

  • Get more effective over time
  • No algorithm changes or pay-to-play
  • Direct relationship with audience
  • Compound value from content

Start with 1-2 based on audience:

  • Industry lacks quality content → Start a blog
  • People want direct updates → Focus on email
  • Engagement matters → Build a community

Example - Superhuman: Built demand through an invite-only waitlist and one-on-one onboarding sessions. Every new user got a 30-minute live demo. This created exclusivity, FOMO, and word-of-mouth—all through owned relationships. Years later, their original onboarding materials still drive engagement.

Rented Channels

Platforms that provide visibility but you don't control. Algorithms shift, rules change, pay-to-play increases.

Examples:

  • Social media (Twitter/X, LinkedIn, Instagram)
  • App stores and marketplaces
  • YouTube
  • Reddit

How to use correctly:

  • Pick 1-2 platforms where your audience is active
  • Use them to drive traffic to owned channels
  • Don't rely on them as your only strategy

Example - Notion: Hacked virality through Twitter, YouTube, and Reddit where productivity enthusiasts were active. Encouraged community to share templates and workflows. But they funneled all visibility into owned assets—every viral post led to signups, then targeted email onboarding.

Platform-specific tactics:

  • Twitter/X: Threads that spark conversation → link to newsletter
  • LinkedIn: High-value posts → lead to gated content or email signup
  • Marketplaces (Shopify, Slack): Optimize listing → drive to site for more

Rented channels give speed, not stability. Capture momentum by bringing users into your owned ecosystem.

Borrowed Channels

Tap into someone else's audience to shortcut the hardest part—getting noticed.

Examples:

  • Guest content (blog posts, podcast interviews, newsletter features)
  • Collaborations (webinars, co-marketing, social takeovers)
  • Speaking engagements (conferences, panels, virtual summits)
  • Influencer partnerships

Be proactive, not passive:

  1. List industry leaders your audience follows
  2. Pitch win-win collaborations
  3. Use tools like SparkToro or Listen Notes to find audience overlap
  4. Set up affiliate/referral incentives (for channel partner launches, use Introw to manage deal registration and commissions)

Example - TRMNL: Sent a free e-ink display to YouTuber Snazzy Labs—not a paid sponsorship, just hoping he'd like it. He created an in-depth review that racked up 500K+ views and drove $500K+ in sales. They also set up an affiliate program for ongoing promotion.

Borrowed channels give instant credibility, but only work if you convert borrowed attention into owned relationships.


Readiness Gate: Are You Ready to Launch?

Run this before the phased mechanics. Products don't market themselves—but a product that isn't ready won't market either. The launch mechanics only pay off if what you're launching is worth launching.

Two failure modes kill launches from opposite ends:

  • Stealth Mode — launching too late. "Procrastination in a fancy suit." You keep polishing in private, waiting for the product to be perfect. It never ships, and nobody learns you exist.
  • "Just One More Feature" — never launching. Every proposed launch date gets pushed for one more thing. The scope creeps forever; the launch never comes.

The middle path is SLC — Simple, Lovable, Complete (Jason Cohen), the antidote to shipping a bare MVP that's minimal but unlovable. Don't launch a stub nobody wants; don't wait for a bloated everything-app. A launchable v1 is:

  • Simple — it does one thing. Not many things poorly. One clear job, done well.
  • Lovable — people want to use it, not just tolerate it. An MVP asks users to suffer through a stripped-down experience "to give feedback." SLC gives them something they'd choose. If nobody would be sad to lose it, it isn't lovable yet.
  • Complete — it's a whole experience for that one thing, not a stub with obvious holes. Complete at its chosen scope, not a teaser of a bigger promise.

The gate: If it's not yet Simple, Lovable, and Complete, you're in "Just One More Feature" territory only when adding scope is what's missing—otherwise you're in Stealth Mode and should ship. Cut scope until one thing is lovable and complete, then launch that. SLC gives you a real launch now instead of a perfect launch never.

Quick check before running the phases:

  • Does it do one clearly-defined thing? (Simple)
  • Would a target user choose to use it, not just endure it? (Lovable)
  • Is that one thing a whole experience, with no glaring stubs? (Complete)
  • Are you polishing past this bar? → Stop. You're in Stealth Mode. Ship.
  • Are you still adding new things to the scope? → Stop. You're in "Just One More Feature." Cut back to SLC.

Pass the gate, then run the phases below.


Five-Phase Launch Approach

Launching isn't a one-day event. It's a phased process that builds momentum.

Phase 1: Internal Launch

Gather initial feedback and iron out major issues before going public.

Actions:

  • Recruit early users one-on-one to test for free
  • Collect feedback on usability gaps and missing features
  • Ensure prototype is functional enough to demo (doesn't need to be production-ready)

Goal: Validate core functionality with friendly users.

Phase 2: Alpha Launch

Put the product in front of external users in a controlled way.

Actions:

  • Create landing page with early access signup form
  • Announce the product exists
  • Invite users individually to start testing
  • MVP should be working in production (even if still evolving)

Goal: First external validation and initial waitlist building.

Phase 3: Beta Launch

Scale up early access while generating external buzz.

Actions:

  • Work through early access list (some free, some paid)
  • Start marketing with teasers about problems you solve
  • Recruit friends, investors, and influencers to test and share

Consider adding:

  • Coming soon landing page or waitlist
  • "Beta" sticker in dashboard navigation
  • Email invites to early access list
  • Early access toggle in settings for experimental features

Goal: Build buzz and refine product with broader feedback.

Phase 4: Early Access Launch

Shift from small-scale testing to controlled expansion.

Actions:

  • Leak product details: screenshots, feature GIFs, demos
  • Gather quantitative usage data and qualitative feedback
  • Run user research with engaged users (incentivize with credits)
  • Optionally run product/market fit survey to refine messaging

Expansion options:

  • Option A: Throttle invites in batches (5-10% at a time)
  • Option B: Invite all users at once under "early access" framing

Goal: Validate at scale and prepare for full launch.

Phase 5: Full Launch

Open the floodgates.

Actions:

  • Open self-serve signups
  • Start charging (if not already)
  • Announce general availability across all channels

Launch touchpoints:

  • Customer emails
  • In-app popups and product tours
  • Website banner linking to launch assets
  • "New" sticker in dashboard navigation
  • Blog post announcement
  • Social posts across platforms
  • Product Hunt, BetaList, Hacker News, etc.

Goal: Maximum visibility and conversion to paying users.


Product Hunt Launch Strategy

Product Hunt can be powerful for reaching early adopters, but it's not magic—it requires preparation.

Pros

  • Exposure to tech-savvy early adopter audience
  • Credibility bump (especially if Product of the Day)
  • Potential PR coverage and backlinks

Cons

  • Very competitive to rank well
  • Short-lived traffic spikes
  • Requires significant pre-launch planning

How to Launch Successfully

Before launch day:

  1. Build relationships with influential supporters, content hubs, and communities
  2. Optimize your listing: compelling tagline, polished visuals, short demo video
  3. Study successful launches to identify what worked
  4. Engage in relevant communities—provide value before pitching
  5. Prepare your team for all-day engagement

On launch day:

  1. Treat it as an all-day event
  2. Respond to every comment in real-time
  3. Answer questions and spark discussions
  4. Encourage your existing audience to engage
  5. Direct traffic back to your site to capture signups

After launch day:

  1. Follow up with everyone who engaged
  2. Convert Product Hunt traffic into owned relationships (email signups)
  3. Continue momentum with post-launch content

Case Studies

SavvyCal (Scheduling tool):

  • Optimized landing page and onboarding before launch
  • Built relationships with productivity/SaaS influencers in advance
  • Responded to every comment on launch day
  • Result: #2 Product of the Month

Reform (Form builder):

  • Studied successful launches and applied insights
  • Crafted clear tagline, polished visuals, demo video
  • Engaged in communities before launch (provided value first)
  • Treated launch as all-day engagement event
  • Directed traffic to capture signups
  • Result: #1 Product of the Day

Post-Launch Product Marketing

Your launch isn't over when the announcement goes live. Now comes adoption and retention work.

Immediate Post-Launch Actions

Educate new users: Set up automated onboarding email sequence introducing key features and use cases.

Reinforce the launch: Include announcement in your weekly/biweekly/monthly roundup email to catch people who missed it.

Differentiate against competitors: Publish comparison pages highlighting why you're the obvious choice.

Update web pages: Add dedicated sections about the new feature/product across your site.

Offer hands-on preview: Create no-code interactive demo (using tools like Navattic) so visitors can explore before signing up.

Keep Momentum Going

It's easier to build on existing momentum than start from scratch. Every touchpoint reinforces the launch.


Ongoing Launch Strategy

Don't rely on a single launch event. Regular updates and feature rollouts sustain engagement.

How to Prioritize What to Announce

Use this matrix to decide how much marketing each update deserves:

Major updates (new features, product overhauls):

  • Full campaign across multiple channels
  • Blog post, email campaign, in-app messages, social media
  • Maximize exposure

Medium updates (new integrations, UI enhancements):

  • Targeted announcement
  • Email to relevant segments, in-app banner
  • Don't need full fanfare

Minor updates (bug fixes, small tweaks):

  • Changelog and release notes
  • Signal that product is improving
  • Don't dominate marketing

Announcement Tactics

Space out releases: Instead of shipping everything at once, stagger announcements to maintain momentum.

Reuse high-performing tactics: If a previous announcement resonated, apply those insights to future updates.

Keep engaging: Continue using email, social, and in-app messaging to highlight improvements.

Signal active development: Even small changelog updates remind customers your product is evolving. This builds retention and word-of-mouth—customers feel confident you'll be around.


Launch Checklist

Pre-Launch

  • Landing page with clear value proposition
  • Email capture / waitlist signup
  • Early access list built
  • Owned channels established (email, blog, community)
  • Rented channel presence (social profiles optimized)
  • Borrowed channel opportunities identified (podcasts, influencers)
  • Product Hunt listing prepared (if using)
  • Launch assets created (screenshots, demo video, GIFs)
  • Onboarding flow ready
  • Analytics/tracking in place

Launch Day

  • Announcement email to list
  • Blog post published
  • Social posts scheduled and posted
  • Product Hunt listing live (if using)
  • In-app announcement for existing users
  • Website banner/notification active
  • Team ready to engage and respond
  • Monitor for issues and feedback

Post-Launch

  • Onboarding email sequence active
  • Follow-up with engaged prospects
  • Roundup email includes announcement
  • Comparison pages published
  • Interactive demo created
  • Gather and act on feedback
  • Plan next launch moment

Task-Specific Questions

  1. What are you launching? (New product, major feature, minor update)
  2. What's your current audience size and engagement?
  3. What owned channels do you have? (Email list size, blog traffic, community)
  4. What's your timeline for launch?
  5. Have you launched before? What worked/didn't work?
  6. Are you considering Product Hunt? What's your preparation status?

Related Skills

  • marketing-ideas: For additional launch tactics (#22 Product Hunt, #23 Early Access Referrals)
  • emails: For launch and onboarding email sequences
  • cro: For optimizing launch landing pages
  • marketing-psychology: For psychology behind waitlists and exclusivity
  • programmatic-seo: For comparison pages mentioned in post-launch
  • sales-enablement: For launch sales collateral and enablement materials
1---
2name: launch
3description: "When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas. For the offer being launched (bonuses, guarantees, scarcity, naming), see offers."
4metadata:
5 version: 2.0.2
6---
7 
8# Launch Strategy
9 
10You are an expert in SaaS product launches and feature announcements. Your goal is to help users plan launches that build momentum, capture attention, and convert interest into users.
11 
12## Before Starting
13 
14**Check for product marketing context first:**
15If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
16 
17---
18 
19## Core Philosophy
20 
21The best companies don't just launch once—they launch again and again. Every new feature, improvement, and update is an opportunity to capture attention and engage your audience.
22 
23A strong launch isn't about a single moment. It's about:
24- Getting your product into users' hands early
25- Learning from real feedback
26- Making a splash at every stage
27- Building momentum that compounds over time
28 
29---
30 
31## The ORB Framework
32 
33Structure your launch marketing across three channel types. Everything should ultimately lead back to owned channels.
34 
35### Owned Channels
36You own the channel (though not the audience). Direct access without algorithms or platform rules.
37 
38**Examples:**
39- Email list
40- Blog
41- Podcast
42- Branded community (Slack, Discord)
43- Website/product
44 
45**Why they matter:**
46- Get more effective over time
47- No algorithm changes or pay-to-play
48- Direct relationship with audience
49- Compound value from content
50 
51**Start with 1-2 based on audience:**
52- Industry lacks quality content → Start a blog
53- People want direct updates → Focus on email
54- Engagement matters → Build a community
55 
56**Example - Superhuman:**
57Built demand through an invite-only waitlist and one-on-one onboarding sessions. Every new user got a 30-minute live demo. This created exclusivity, FOMO, and word-of-mouth—all through owned relationships. Years later, their original onboarding materials still drive engagement.
58 
59### Rented Channels
60Platforms that provide visibility but you don't control. Algorithms shift, rules change, pay-to-play increases.
61 
62**Examples:**
63- Social media (Twitter/X, LinkedIn, Instagram)
64- App stores and marketplaces
65- YouTube
66- Reddit
67 
68**How to use correctly:**
69- Pick 1-2 platforms where your audience is active
70- Use them to drive traffic to owned channels
71- Don't rely on them as your only strategy
72 
73**Example - Notion:**
74Hacked virality through Twitter, YouTube, and Reddit where productivity enthusiasts were active. Encouraged community to share templates and workflows. But they funneled all visibility into owned assets—every viral post led to signups, then targeted email onboarding.
75 
76**Platform-specific tactics:**
77- Twitter/X: Threads that spark conversation → link to newsletter
78- LinkedIn: High-value posts → lead to gated content or email signup
79- Marketplaces (Shopify, Slack): Optimize listing → drive to site for more
80 
81Rented channels give speed, not stability. Capture momentum by bringing users into your owned ecosystem.
82 
83### Borrowed Channels
84Tap into someone else's audience to shortcut the hardest part—getting noticed.
85 
86**Examples:**
87- Guest content (blog posts, podcast interviews, newsletter features)
88- Collaborations (webinars, co-marketing, social takeovers)
89- Speaking engagements (conferences, panels, virtual summits)
90- Influencer partnerships
91 
92**Be proactive, not passive:**
931. List industry leaders your audience follows
942. Pitch win-win collaborations
953. Use tools like SparkToro or Listen Notes to find audience overlap
964. Set up affiliate/referral incentives (for channel partner launches, use [Introw](../../tools/integrations/introw.md) to manage deal registration and commissions)
97 
98**Example - TRMNL:**
99Sent a free e-ink display to YouTuber Snazzy Labs—not a paid sponsorship, just hoping he'd like it. He created an in-depth review that racked up 500K+ views and drove $500K+ in sales. They also set up an affiliate program for ongoing promotion.
100 
101Borrowed channels give instant credibility, but only work if you convert borrowed attention into owned relationships.
102 
103---
104 
105## Readiness Gate: Are You Ready to Launch?
106 
107Run this **before** the phased mechanics. Products don't market themselves—but a product that isn't ready won't market either. The launch mechanics only pay off if what you're launching is worth launching.
108 
109Two failure modes kill launches from opposite ends:
110 
111- **Stealth Mode** — launching too late. "Procrastination in a fancy suit." You keep polishing in private, waiting for the product to be perfect. It never ships, and nobody learns you exist.
112- **"Just One More Feature"** — never launching. Every proposed launch date gets pushed for one more thing. The scope creeps forever; the launch never comes.
113 
114The middle path is **SLC — Simple, Lovable, Complete** (Jason Cohen), the antidote to shipping a bare MVP that's minimal but unlovable. Don't launch a stub nobody wants; don't wait for a bloated everything-app. A launchable v1 is:
115 
116- **Simple** — it does *one* thing. Not many things poorly. One clear job, done well.
117- **Lovable** — people *want* to use it, not just tolerate it. An MVP asks users to suffer through a stripped-down experience "to give feedback." SLC gives them something they'd choose. If nobody would be sad to lose it, it isn't lovable yet.
118- **Complete** — it's a *whole* experience for that one thing, not a stub with obvious holes. Complete at its chosen scope, not a teaser of a bigger promise.
119 
120**The gate:** If it's not yet Simple, Lovable, and Complete, you're in "Just One More Feature" territory only when adding scope is what's missing—otherwise you're in Stealth Mode and should ship. Cut scope until one thing is lovable and complete, then launch that. SLC gives you a real launch now instead of a perfect launch never.
121 
122**Quick check before running the phases:**
123- [ ] Does it do one clearly-defined thing? (Simple)
124- [ ] Would a target user *choose* to use it, not just endure it? (Lovable)
125- [ ] Is that one thing a whole experience, with no glaring stubs? (Complete)
126- [ ] Are you polishing past this bar? → Stop. You're in Stealth Mode. Ship.
127- [ ] Are you still adding new things to the scope? → Stop. You're in "Just One More Feature." Cut back to SLC.
128 
129Pass the gate, then run the phases below.
130 
131---
132 
133## Five-Phase Launch Approach
134 
135Launching isn't a one-day event. It's a phased process that builds momentum.
136 
137### Phase 1: Internal Launch
138Gather initial feedback and iron out major issues before going public.
139 
140**Actions:**
141- Recruit early users one-on-one to test for free
142- Collect feedback on usability gaps and missing features
143- Ensure prototype is functional enough to demo (doesn't need to be production-ready)
144 
145**Goal:** Validate core functionality with friendly users.
146 
147### Phase 2: Alpha Launch
148Put the product in front of external users in a controlled way.
149 
150**Actions:**
151- Create landing page with early access signup form
152- Announce the product exists
153- Invite users individually to start testing
154- MVP should be working in production (even if still evolving)
155 
156**Goal:** First external validation and initial waitlist building.
157 
158### Phase 3: Beta Launch
159Scale up early access while generating external buzz.
160 
161**Actions:**
162- Work through early access list (some free, some paid)
163- Start marketing with teasers about problems you solve
164- Recruit friends, investors, and influencers to test and share
165 
166**Consider adding:**
167- Coming soon landing page or waitlist
168- "Beta" sticker in dashboard navigation
169- Email invites to early access list
170- Early access toggle in settings for experimental features
171 
172**Goal:** Build buzz and refine product with broader feedback.
173 
174### Phase 4: Early Access Launch
175Shift from small-scale testing to controlled expansion.
176 
177**Actions:**
178- Leak product details: screenshots, feature GIFs, demos
179- Gather quantitative usage data and qualitative feedback
180- Run user research with engaged users (incentivize with credits)
181- Optionally run product/market fit survey to refine messaging
182 
183**Expansion options:**
184- Option A: Throttle invites in batches (5-10% at a time)
185- Option B: Invite all users at once under "early access" framing
186 
187**Goal:** Validate at scale and prepare for full launch.
188 
189### Phase 5: Full Launch
190Open the floodgates.
191 
192**Actions:**
193- Open self-serve signups
194- Start charging (if not already)
195- Announce general availability across all channels
196 
197**Launch touchpoints:**
198- Customer emails
199- In-app popups and product tours
200- Website banner linking to launch assets
201- "New" sticker in dashboard navigation
202- Blog post announcement
203- Social posts across platforms
204- Product Hunt, BetaList, Hacker News, etc.
205 
206**Goal:** Maximum visibility and conversion to paying users.
207 
208---
209 
210## Product Hunt Launch Strategy
211 
212Product Hunt can be powerful for reaching early adopters, but it's not magic—it requires preparation.
213 
214### Pros
215- Exposure to tech-savvy early adopter audience
216- Credibility bump (especially if Product of the Day)
217- Potential PR coverage and backlinks
218 
219### Cons
220- Very competitive to rank well
221- Short-lived traffic spikes
222- Requires significant pre-launch planning
223 
224### How to Launch Successfully
225 
226**Before launch day:**
2271. Build relationships with influential supporters, content hubs, and communities
2282. Optimize your listing: compelling tagline, polished visuals, short demo video
2293. Study successful launches to identify what worked
2304. Engage in relevant communities—provide value before pitching
2315. Prepare your team for all-day engagement
232 
233**On launch day:**
2341. Treat it as an all-day event
2352. Respond to every comment in real-time
2363. Answer questions and spark discussions
2374. Encourage your existing audience to engage
2385. Direct traffic back to your site to capture signups
239 
240**After launch day:**
2411. Follow up with everyone who engaged
2422. Convert Product Hunt traffic into owned relationships (email signups)
2433. Continue momentum with post-launch content
244 
245### Case Studies
246 
247**SavvyCal** (Scheduling tool):
248- Optimized landing page and onboarding before launch
249- Built relationships with productivity/SaaS influencers in advance
250- Responded to every comment on launch day
251- Result: #2 Product of the Month
252 
253**Reform** (Form builder):
254- Studied successful launches and applied insights
255- Crafted clear tagline, polished visuals, demo video
256- Engaged in communities before launch (provided value first)
257- Treated launch as all-day engagement event
258- Directed traffic to capture signups
259- Result: #1 Product of the Day
260 
261---
262 
263## Post-Launch Product Marketing
264 
265Your launch isn't over when the announcement goes live. Now comes adoption and retention work.
266 
267### Immediate Post-Launch Actions
268 
269**Educate new users:**
270Set up automated onboarding email sequence introducing key features and use cases.
271 
272**Reinforce the launch:**
273Include announcement in your weekly/biweekly/monthly roundup email to catch people who missed it.
274 
275**Differentiate against competitors:**
276Publish comparison pages highlighting why you're the obvious choice.
277 
278**Update web pages:**
279Add dedicated sections about the new feature/product across your site.
280 
281**Offer hands-on preview:**
282Create no-code interactive demo (using tools like Navattic) so visitors can explore before signing up.
283 
284### Keep Momentum Going
285It's easier to build on existing momentum than start from scratch. Every touchpoint reinforces the launch.
286 
287---
288 
289## Ongoing Launch Strategy
290 
291Don't rely on a single launch event. Regular updates and feature rollouts sustain engagement.
292 
293### How to Prioritize What to Announce
294 
295Use this matrix to decide how much marketing each update deserves:
296 
297**Major updates** (new features, product overhauls):
298- Full campaign across multiple channels
299- Blog post, email campaign, in-app messages, social media
300- Maximize exposure
301 
302**Medium updates** (new integrations, UI enhancements):
303- Targeted announcement
304- Email to relevant segments, in-app banner
305- Don't need full fanfare
306 
307**Minor updates** (bug fixes, small tweaks):
308- Changelog and release notes
309- Signal that product is improving
310- Don't dominate marketing
311 
312### Announcement Tactics
313 
314**Space out releases:**
315Instead of shipping everything at once, stagger announcements to maintain momentum.
316 
317**Reuse high-performing tactics:**
318If a previous announcement resonated, apply those insights to future updates.
319 
320**Keep engaging:**
321Continue using email, social, and in-app messaging to highlight improvements.
322 
323**Signal active development:**
324Even small changelog updates remind customers your product is evolving. This builds retention and word-of-mouth—customers feel confident you'll be around.
325 
326---
327 
328## Launch Checklist
329 
330### Pre-Launch
331- [ ] Landing page with clear value proposition
332- [ ] Email capture / waitlist signup
333- [ ] Early access list built
334- [ ] Owned channels established (email, blog, community)
335- [ ] Rented channel presence (social profiles optimized)
336- [ ] Borrowed channel opportunities identified (podcasts, influencers)
337- [ ] Product Hunt listing prepared (if using)
338- [ ] Launch assets created (screenshots, demo video, GIFs)
339- [ ] Onboarding flow ready
340- [ ] Analytics/tracking in place
341 
342### Launch Day
343- [ ] Announcement email to list
344- [ ] Blog post published
345- [ ] Social posts scheduled and posted
346- [ ] Product Hunt listing live (if using)
347- [ ] In-app announcement for existing users
348- [ ] Website banner/notification active
349- [ ] Team ready to engage and respond
350- [ ] Monitor for issues and feedback
351 
352### Post-Launch
353- [ ] Onboarding email sequence active
354- [ ] Follow-up with engaged prospects
355- [ ] Roundup email includes announcement
356- [ ] Comparison pages published
357- [ ] Interactive demo created
358- [ ] Gather and act on feedback
359- [ ] Plan next launch moment
360 
361---
362 
363## Task-Specific Questions
364 
3651. What are you launching? (New product, major feature, minor update)
3662. What's your current audience size and engagement?
3673. What owned channels do you have? (Email list size, blog traffic, community)
3684. What's your timeline for launch?
3695. Have you launched before? What worked/didn't work?
3706. Are you considering Product Hunt? What's your preparation status?
371 
372---
373 
374## Related Skills
375 
376- **marketing-ideas**: For additional launch tactics (#22 Product Hunt, #23 Early Access Referrals)
377- **emails**: For launch and onboarding email sequences
378- **cro**: For optimizing launch landing pages
379- **marketing-psychology**: For psychology behind waitlists and exclusivity
380- **programmatic-seo**: For comparison pages mentioned in post-launch
381- **sales-enablement**: For launch sales collateral and enablement materials
382 

Discussion

From GitHub

2 comments on 1 thread

## Placement decision (recorded) - **Canonical / public leaderboard → marketing-skills.com.** Neutral, open, MIT-credible — the citable authority asset and backlink magnet. Its value is *perceived neutrality*, so it must stay editorially independent (methodology-first; Magister is a footnote, not a sponsor banner). - **Reference / embed → magistermarketing.com.** Magister captures commercial value by *pointing at* the neutral board ("we route to the best model per task, proven by the open benchmark"), embedding it via a shared component/iframe with `rel=canonical` back to marketing-skills.com.read the rest

## Cost & time — the benchmark is triaxial Quality is one axis; **cost and latency are the other two.** Every run logs: - **Tokens** (input+output) — the price-stable base. Dollars = tokens × a **versioned pricing table** ("as of" date; account for batch/cached-input discounts and tiers). - **Latency** — p50/p95, TTFT + total, over many runs (noisy — never one-shot). **The metric that decides routing is cost/latency *per accepted output*, not per call.** A cheap model that fails half the time isn't cheap — you regenerate. So `cost-per-PASS = $/output ÷ pass-rate` and `time-per-PASS` fuse qualiread the rest

Alternatives

Also in Launch planning