Launch Strategy

Turn a launch into a repeatable distribution loop, not a one-off announcement.

Establish The Launch Object

Clarify:

• What is launching: company, product, feature, integration, report, tool, community, offer.
• Who should care first.
• What changes for them.
• What proof exists today.
• What conversion should happen after attention arrives.
• Deadline, embargo, launch surface, team capacity, and assets.

If the product is not ready for broad traffic, plan a smaller learning launch.

Pick The Launch Mode

Choose the smallest useful launch mode:

• Learning launch: small audience, fast feedback, weak proof is acceptable.
• Feature launch: one meaningful product change, several angles, repeated weekly or monthly.
• Campaign launch: bigger coordinated push across owned, social, community, partner, and press surfaces.
• Relaunch: sharper positioning, stronger proof, or a new audience for something already live.

Do not wait for a "big announcement" if the feature creates a new reason to talk to the market.

Find The Launch Angles

Turn the launch object into 3-5 angles:

• Demo: what people can see working.
• Use case: who this helps and when they would use it.
• Pain: the annoying problem this removes.
• Technical detail: what builders, operators, or power users would find interesting.
• Proof: early result, quote, customer example, benchmark, or before/after.
• Founder POV: why this matters now and what the category gets wrong.

Each angle should become a different asset or post. Avoid posting the same announcement everywhere.

Build The Launch Checklist

Create operating lanes:

• Readiness gates: product, page, analytics, onboarding, support, sales, creative.
• Proof capture: demo clips, screenshots, quotes, early numbers, objections, FAQs.
• Asset creation: X post, X Article, short demo video, screenshots, launch page, changelog, email, founder LinkedIn post, community post, directory listing.
• Audience routing: who gets private preview, public announcement, customer email, partner prompt, sales follow-up, or community post.
• Response coverage: who monitors comments, DMs, email replies, support, and sales handoffs.
• Follow-through: quote post, reply follow-up, customer story, teardown, use case post, webinar, lifecycle touch, retargeting.

Each lane needs owner, asset, deadline, risk, and success signal.

Asset Checklist

For a feature launch, prepare the assets that match the audience and proof:

• X post: punchy launch post, founder POV, demo clip, or short thread.
• X Article: longer story, teardown, launch essay, or product breakdown when there is enough substance.
• Short video: 20-90 second demo, screen recording, founder walkthrough, or before/after.
• Screenshots/GIFs: one clear visual per important use case.
• Launch page/changelog: what changed, who it is for, why it matters, and how to try it.
• Customer email: plain announcement for users, customers, waitlist, or newsletter.
• LinkedIn post: business pain, customer story, team lesson, or category POV.
• Community posts: rewrite for Reddit, Indie Hackers, Peerlist, DevHunt, Product Hunt, Hacker News, niche Slack/Discord groups, or forums.
• Sales note: short message for active deals, lost deals, champions, and high-intent accounts.
• Internal FAQ: expected objections, pricing questions, bugs, support answers, and escalation paths.

Channel Selection

Choose channels by audience and proof fit:

• Founder social for narrative and speed.
• Email for owned conversion.
• Communities for category-specific feedback.
• X for fast demos, founder POV, quote posts, and iteration.
• LinkedIn for business pain, customer proof, hiring, and partnership angles.
• Hacker News for technical novelty, hard-won lessons, or builder relevance.
• Reddit for specific pain, workflows, before/after stories, and honest discussion.
• Product Hunt, DevHunt, Betalist, Peerlist, Indie Hackers, and directories when their audience matches the product.
• Partners for borrowed trust.
• Direct outreach for high-intent accounts.
• Product directories only when the audience actually browses them.
• Paid amplification only after the message has shown organic pull.

Launch Sequence

Use a simple sequence unless the launch needs a larger campaign:

1. Before: collect proof, record demo, prepare page, write channel-specific angles, brief responders.
2. Day 1: publish the clearest owned announcement and primary social post.
3. Day 2-3: post the strongest alternate angle in a community or second social channel.
4. Day 4-5: turn replies, objections, and demos into follow-up posts.
5. After: summarize learning, route leads, update onboarding, and choose the next launch angle.

Treat good replies and objections as raw material for the next post, not as the end of the launch.

Output

Launch thesis:
[why this deserves attention now]

Launch mode:
[learning launch / feature launch / campaign launch / relaunch]

Primary audience:
[who]

Conversion goal:
[desired action]

Angle map:
| Angle | Audience | Core claim | Proof | Best channel | Asset |

Readiness gates:
| Gate | Owner | Ready when | Risk |

Launch checklist:
| Item | Owner | Asset needed | Deadline | Ready? | Risk |

Asset plan:
- X post:
- X Article:
- Video:
- Screenshots/GIFs:
- Launch page/changelog:
- Email:
- LinkedIn:
- Community posts:
- Directory listing:
- Sales note:
- Internal FAQ:

Launch sequence:
| Day | Channel | Angle | Asset | Owner | Success signal |

Response coverage:
| Surface | Owner | What to watch | Escalation |

Follow-through:
1. [post-launch action]
2. [post-launch action]
3. [post-launch action]

Risks:
- [risk] -> [mitigation]