When the user wants to plan a product launch, feature announcement, or release strategy — 'Product Hunt,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'launch checklist,' 'GTM plan,' 'we're about to ship.' For ongoing marketing after launch, see marketing-ideas.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Plan SaaS product launches and feature announcements that build momentum, capture attention, and convert interest into users.
Product context: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it first and tailor output to it; only ask for what it doesn't cover.
The best companies launch again and again — every feature, improvement, and update is a chance to capture attention. A strong launch isn't a single moment; it's getting the product into users' hands early, learning from real feedback, making a splash at every stage, and building momentum that compounds.
Structure launch marketing across three channel types. Everything should ultimately lead back to 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 audience relationship, compounding content value.
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 — every new user got a 30-minute live demo. This created exclusivity, FOMO, and word-of-mouth through owned relationships; years later their original onboarding materials still drive engagement.
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: pick 1-2 platforms where your audience is active, drive traffic to owned channels, never rely on them as your only strategy.
Example — Notion: Hacked virality on Twitter, YouTube, and Reddit where productivity enthusiasts were active, encouraging the community to share templates and workflows — but funneled all visibility into owned assets: every viral post led to signups, then targeted email onboarding.
Platform tactics: Twitter/X threads that spark conversation → link to newsletter; LinkedIn high-value posts → 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.
Tap 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: (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.
Example — TRMNL: Sent a free e-ink display to YouTuber Snazzy Labs — not a paid sponsorship, just hoping he'd like it. His in-depth review racked up 500K+ views and drove $500K+ in sales; an affiliate program sustained ongoing promotion.
Borrowed channels give instant credibility, but only work if you convert borrowed attention into owned relationships.
Launching is a phased process that builds momentum, not a one-day event.
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 the prototype is functional enough to demo (not necessarily production-ready).
Goal: Validate core functionality with friendly users.
Put the product in front of external users in a controlled way.
Actions: create a landing page with early access signup form; announce the product exists; invite users individually to test; MVP working in production (even if still evolving).
Goal: First external validation and initial waitlist building.
Scale up early access while generating external buzz.
Actions: work through the 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 the early access list; early access toggle in settings for experimental features.
Goal: Build buzz and refine product with broader feedback.
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 a product/market fit survey to refine messaging.
Expansion options: (A) throttle invites in batches (5-10% at a time), or (B) invite all users at once under "early access" framing.
Goal: Validate at scale and prepare for full launch.
Open the floodgates: 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.
Powerful for reaching early adopters, but not magic — it requires preparation.
Pros: exposure to tech-savvy early adopters; credibility bump (especially Product of the Day); potential PR coverage and backlinks.
Cons: very competitive to rank well; short-lived traffic spikes; significant pre-launch planning required.
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 for what worked; (4) engage in relevant communities, providing value before pitching; (5) prepare your team for all-day engagement.
On launch day: treat it as an all-day event; respond to every comment in real-time; answer questions and spark discussions; encourage your existing audience to engage; direct traffic back to your site to capture signups.
After launch day: follow up with everyone who engaged; convert Product Hunt traffic into owned relationships (email signups); continue momentum with post-launch content.
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 (value first); treated launch as an all-day engagement event; directed traffic to capture signups. Result: #1 Product of the Day.
The launch isn't over when the announcement goes live — now comes adoption and retention.
It's easier to build on existing momentum than start from scratch — every touchpoint reinforces the launch.
Don't rely on a single launch event; regular updates and feature rollouts sustain engagement.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Act as a Senior Accessibility Engineer to audit a page, component, or design against WCAG 2.2 AA. Produces a triaged finding list (critical/serious/moderate), focus-order map, contrast report, ARIA decision tree, and a screen-reader test plan. Use when shipping new UI, hardening an existing flow, or preparing for VPAT/accessibility conformance.
The English summary is being prepared. Showing the original description.
When the user wants to plan, design, or implement an A/B test or experiment — "split test," "variant copy," "multivariate test," "hypothesis," "statistical significance," "how long should I run this test," or comparing two versions. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.
The English summary is being prepared. Showing the original description.
When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, full variations — for any paid platform; 'ad copy variations,' 'RSA headlines,' 'bulk ad copy,' 'creative testing,' 'write me some ads.' For campaign strategy and targeting, see paid-ads. For landing page copy, see copywriting.
The English summary is being prepared. Showing the original description.
When the user wants content cited by LLMs or surfaced in AI-generated answers — 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'AI Overviews,' 'optimize for ChatGPT/Perplexity/Claude,' 'AI citations,' 'zero-click search.' For traditional technical/on-page audits, see seo-audit. For structured data, see schema-markup.
The English summary is being prepared. Showing the original description.
When the user wants to set up, improve, or audit analytics tracking and measurement — "GA4," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "tracking plan," "attribution," "Mixpanel," "Segment," "are my events firing," or how to measure marketing results. For A/B test measurement, see ab-test-setup.
The English summary is being prepared. Showing the original description.
Architectural decision advisor for cloud, data, and SaaS distributed systems. Use when the user asks "should we use X or Y", weighs a tradeoff, or needs a decision matrix, scaling analysis, cost-at-scale review, data-tier design, multi-tenancy model, or API/resilience guidance. For full technical blueprints, use enterprise-design.
The English summary is being prepared. Showing the original description.