# Market Launch > Product/Service Launch Playbook Generator — builds a complete, week-by-week, multi-channel go-to-market plan (timeline, email sequences, social posts, press pitches, partner coordination, metrics dashboard, budget allocation) tailored to the user's product, audience, date and budget. Use when the user wants to launch a product/service/feature/course/event, asks for a launch plan, go-to-market (GTM) strategy, launch checklist, launch calendar, Product Hunt launch, or to coordinate a multi-channel launch campaign. FR: "plan de lancement", "lancer un produit", "go-to-market", "stratégie de lancement", "checklist de lancement", "calendrier de lancement", "campagne de lancement". Triggers on: /market launch, market-launch, marketing launch. Do NOT use for ongoing content calendars, paid-ads-only setup (use ads skills) or brand identity (use market-brand) unless part of a launch. - Skill: `agentik-os/market-launch` (Agent Skill) - Install (CLI): `npx skillmds@latest add agentik-os/market-launch` - Raw SKILL.md: https://api.skillmd.com/api/skills/agentik-os/market-launch/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Marketing & Growth - Author: agentik-os (https://skillmd.com/u/agentik-os) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/agentik-os/market-launch --- # Product/Service Launch Playbook Generator ## Skill Purpose Generate a complete, week-by-week launch playbook for any product, service, or feature launch. This skill produces a tactical plan with templates, checklists, email sequences, social posts, and metrics tracking -- everything needed to execute a successful launch. ## When to Use - User is planning to launch a new product, service, feature, or offering - User asks for a launch plan, go-to-market strategy, or launch checklist - User wants to coordinate a multi-channel launch campaign - Triggered by `/market launch` or `/market launch ` ## Dynamic Workflow orchestration A launch playbook is naturally many disjoint workstreams. After Step 1 (context) and Step 2 (launch type) are settled — these are SEQUENTIAL and gate everything — fan the production work out, then verify adversarially, then synthesize one coherent playbook. 1. **Plan (sequential, you alone).** Lock context + launch type + launch date. These are the shared inputs every workstream depends on; never parallelize them. 2. **Fan out (parallel sub-agents, file-disjoint).** Spawn one sub-agent per workstream, each writing to its own scratch artifact so there is no write contention: - `timeline` → 8-week week-by-week plan (Step 3) backward-scheduled from launch date - `emails` → pre-launch + launch sequences (Step 4) - `social` → platform posts: X thread, LinkedIn, visual (Step 5) - `press` → press release + media pitch (Step 6) - `partners` → outreach timeline + partner kit (Step 7) - `metrics+budget` → dashboard (Step 8) + budget allocation (Step 10) 3. **Adversarially verify (≥3 skeptic graders, 2-of-3 consensus).** Grade the assembled draft against this rubric; a finding passes only if ≥2 of 3 agree: - *Specificity skeptic*: any generic, copy-pasteable-to-any-product line? Reject it — every recommendation must bind to THIS product/audience/budget (Key Principles). - *Channel-coherence skeptic*: do email, social, partner and PR dates line up to the SAME launch week, with no contradictory offers/prices/deadlines across channels? - *Evidence skeptic*: every metric target, market claim and "early result" carries a stated source or is explicitly flagged as a placeholder for the user to fill — no invented stats, no fabricated testimonials (Constraints → MUST NOT DO). 4. **Loop-until-dry (unknown-size discovery).** Community/forum lists (Step 1 task) and partner/influencer prospect lists have no fixed size — keep one discovery loop running until it yields no new qualified targets, rather than stopping at an arbitrary count. 5. **Synthesize yourself.** YOU merge the scratch artifacts into ONE `LAUNCH-PLAYBOOK.md` (Output Format). Never paste a sub-agent's section verbatim as the verdict — reconcile dates, dedupe offers, enforce one voice. Disjoint workstreams run parallel; anything sharing the launch-date/offer truth is reconciled by you, serially. ## How to Execute ### Step 1: Gather Launch Context Before generating the playbook, collect these inputs from the user (ask if not provided): 1. **What are you launching?** (product, service, feature, course, event) 2. **Who is the target audience?** (demographics, pain points, existing list size) 3. **What is the primary launch goal?** (revenue target, signups, downloads, awareness) 4. **What is the launch date?** (or desired timeline) 5. **What channels do you have access to?** (email list size, social following, ad budget, partnerships) 6. **What is the price point?** (if applicable) 7. **Do you have existing customers/users?** (for beta, testimonials, case studies) 8. **What is the budget?** (bootstrapped, moderate, well-funded) ### Step 2: Determine Launch Type Select the primary launch strategy based on the user's context: | Launch Type | Best For | Key Channel | Timeline | |---|---|---|---| | Product Hunt | SaaS, dev tools, consumer apps | Product Hunt + Twitter/X | 4-6 weeks prep | | Email List Launch | Course, info product, SaaS with existing list | Email | 6-8 weeks | | Social Media Launch | Consumer product, personal brand | Twitter/X, LinkedIn, Instagram | 4-6 weeks | | Paid Ads Launch | E-commerce, established product | Facebook/Google Ads | 2-4 weeks prep | | Community Launch | Niche product, developer tools | Reddit, Discord, Slack communities | 6-8 weeks | | Partner Launch | B2B, enterprise, marketplace | Partner channels | 8-12 weeks | | Hybrid Launch | Any high-stakes launch | Multi-channel coordinated | 8-12 weeks | ### Step 3: Generate the 8-Week Launch Timeline #### Weeks 1-2: Foundation **Objective:** Lock in positioning, build assets, set up infrastructure. **Tasks:** - [ ] Define launch positioning statement: "For [TARGET] who [PROBLEM], [PRODUCT] is a [CATEGORY] that [KEY BENEFIT]. Unlike [ALTERNATIVE], we [DIFFERENTIATOR]." - [ ] Create launch one-pager (internal alignment doc) - [ ] Set up landing page / waitlist page - [ ] Set up analytics and tracking (UTM parameters, conversion goals, event tracking) - [ ] Create launch-specific email list/segment - [ ] Draft all email sequences (see Email Templates below) - [ ] Brief design team on visual assets needed - [ ] Identify 10-20 potential beta testers or early access users - [ ] Research and list 20+ communities, forums, and groups where target audience gathers - [ ] Set up social media content calendar tool **Deliverables:** - Positioning statement - Landing page live - Email sequences drafted - Beta tester list #### Weeks 3-4: Audience Building **Objective:** Build anticipation, grow waitlist, recruit beta testers. **Tasks:** - [ ] Begin content seeding: publish 2-3 blog posts / threads related to the problem you solve - [ ] Share behind-the-scenes content on social media (building in public) - [ ] Start engaging in target communities (provide value, don't pitch yet) - [ ] Reach out to beta testers with personal invitations - [ ] Collect early feedback and testimonials from beta users - [ ] Begin influencer/partner outreach (see Partner Coordination below) - [ ] Set up referral mechanism for waitlist (e.g., viral waitlist with rewards) - [ ] Create teaser content (sneak peeks, countdowns, problem-awareness posts) - [ ] Record demo video or product walkthrough - [ ] Write press release or media pitch (if relevant) **Content Calendar (Weeks 3-4):** | Day | Content Type | Channel | Theme | |---|---|---|---| | Mon | Problem-awareness post | LinkedIn/Twitter | Why this problem matters | | Tue | Behind-the-scenes | Instagram/Twitter | Show what you're building | | Wed | Educational content | Blog/LinkedIn | Teach something related to your space | | Thu | Social proof | Twitter/LinkedIn | Beta tester quote or result | | Fri | Teaser/countdown | All channels | Build anticipation for launch | **Deliverables:** - 4-6 content pieces published - Beta testers onboarded and providing feedback - Waitlist growing - Partner/influencer commitments secured #### Weeks 5-6: Pre-Launch Intensification **Objective:** Maximize anticipation, finalize assets, prep launch infrastructure. **Tasks:** - [ ] Send pre-launch email sequence to waitlist (see Email Templates) - [ ] Increase social media posting frequency to daily - [ ] Publish case study or results from beta testers - [ ] Finalize pricing and offer structure - [ ] Create launch-day content package (all posts, emails, and graphics ready) - [ ] Brief partners/affiliates on launch plan and provide swipe copy - [ ] Set up live chat or support for launch day - [ ] Test all purchase/signup flows end-to-end - [ ] Prepare FAQ document for support team - [ ] Create urgency mechanism (early bird pricing, limited spots, bonus expiration) - [ ] Rehearse launch day by walking through every step - [ ] Set up real-time dashboard for launch metrics **Deliverables:** - All launch assets finalized and scheduled - Partners briefed and ready - Checkout/signup flow tested - Support team prepared #### Week 7: LAUNCH WEEK **Objective:** Execute the launch with maximum impact and coordinated effort. **Day-by-Day Breakdown:** **Monday - Soft Launch / VIP Access:** - Send early access email to VIPs, beta testers, and top waitlist members - Post on social: "We're live for our early supporters" - Collect first-day feedback and testimonials - Monitor for bugs and issues - Goal: First 50-100 users/customers **Tuesday - Public Announcement:** - Send main launch email to full list - Publish launch blog post - Post launch announcement on all social channels - Submit to Product Hunt (if applicable -- schedule for 12:01 AM PT) - Activate partner/affiliate promotions - Begin paid ad campaigns (if applicable) - Goal: Maximum visibility and traffic **Wednesday - Social Proof Push:** - Share first customer testimonials and results - Repost/retweet customer reactions - Send "look what people are saying" email - Post in communities (with genuine value, not spam) - Respond to every comment, mention, and question - Goal: Build momentum through social proof **Thursday - Objection Handling:** - Publish FAQ or "everything you need to know" post - Send email addressing top 3 objections - Host live Q&A or AMA (Twitter Space, LinkedIn Live, webinar) - Share comparison content (why this vs alternatives) - Goal: Convert fence-sitters **Friday - Urgency and Scarcity:** - Send "early bird pricing ends soon" email - Post countdown content on social - Share final testimonials and case studies - Activate scarcity mechanisms (limited spots, bonus expires) - Goal: Drive final wave of conversions **Saturday/Sunday - Wrap Up:** - Send "last chance" email for any time-limited offers - Compile launch week results - Thank early customers publicly - Begin post-launch content planning #### Week 8: Post-Launch **Objective:** Maintain momentum, collect feedback, plan next iteration. **Tasks:** - [ ] Send post-launch survey to new customers - [ ] Compile and analyze launch metrics (see Metrics section) - [ ] Write launch retrospective (what worked, what didn't, what to change) - [ ] Transition from launch pricing to regular pricing - [ ] Set up onboarding email sequence for new customers - [ ] Plan next content calendar based on launch learnings - [ ] Follow up with media contacts and partners with results - [ ] Identify top customers for case studies - [ ] Begin planning v2 features based on feedback - [ ] Set up ongoing marketing engine (content, ads, email nurture) ### Step 4: Email Sequence Templates #### Pre-Launch Sequence (Weeks 5-6) **Email 1: The Teaser (2 weeks before)** Subject: Something big is coming... Purpose: Build anticipation Content: Hint at the product, share the problem it solves, tease the launch date. Don't reveal everything. CTA: "Stay tuned" or "Make sure you're on the list" **Email 2: The Reveal (1 week before)** Subject: Here's what we've been building Purpose: Show the product, build desire Content: Reveal the product with screenshots/video. Share beta tester results. Announce launch date and any early bird offer. CTA: "Mark your calendar" or "Get notified on launch day" **Email 3: The Social Proof (3 days before)** Subject: "[Beta Tester Name] got [Result] in [Timeframe]" Purpose: Prove it works Content: Feature 2-3 beta tester testimonials with specific results. Address the "does this actually work?" objection. CTA: "Be ready for [launch day]" #### Launch Sequence (Week 7) **Email 4: The Launch (Day 1)** Subject: It's live -- [Product Name] is here Purpose: Drive immediate action Content: Announce the launch. State the offer clearly. Include early bird pricing or bonus. Link directly to purchase/signup. CTA: "Get [Product] now" with primary button **Email 5: The Social Proof Follow-Up (Day 3)** Subject: People are already seeing results Purpose: Convert through social proof Content: Share first-customer testimonials, screenshots of reactions, usage stats. Create FOMO. CTA: "Join [X] others who already [outcome]" **Email 6: The Objection Handler (Day 4)** Subject: "But what if [common objection]?" Purpose: Address hesitations Content: List and answer top 3-5 objections. Include guarantee/risk reversal. Share FAQ. CTA: "Try it risk-free" **Email 7: The Urgency Close (Day 5-7)** Subject: [X hours] left for [early bird / bonus / discount] Purpose: Drive final conversions with urgency Content: Remind of the deadline. Recap the value. Final testimonial. Clear, single CTA. CTA: "Last chance to get [offer]" ### Step 5: Social Media Launch Posts #### Twitter/X Thread Template: ``` Post 1: After [X months/weeks] of building, I'm thrilled to announce [Product Name] is live. [Product] helps [target audience] [achieve outcome] without [pain point]. Here's the story of why I built it (and what it can do for you): [Thread emoji] 1/ Post 2: The problem: [Describe the problem in detail. Make it relatable.] Post 3: The solution: [What your product does, in simple terms. Include screenshot or demo GIF.] Post 4: Early results: [Beta tester results, specific numbers] Post 5: What's included: [Key features as bullet points] Post 6: Special launch offer: [Pricing, early bird deal, bonus] Post 7: Try it now: [Link] [CTA] ``` #### LinkedIn Post Template: ``` I just launched [Product Name], and here's why it matters: [1-2 sentences about the problem] After [talking to X customers / spending Y months building / experiencing this problem myself], I realized [insight]. So I built [Product Name] to [specific outcome]. Early users are already seeing: - [Result 1] - [Result 2] - [Result 3] If you [target audience descriptor], I'd love for you to check it out: [Link] Special launch pricing available for the next [timeframe]. #relevant #hashtags ``` #### Instagram / Visual Platform Template: ``` Image/Carousel: Product screenshots, before/after, or results graphic Caption: [Hook - first line that stops the scroll] The problem: [1-2 sentences] The solution: [1-2 sentences about your product] The results: [specific outcomes from beta users] Launch special: [offer details] Link in bio to get started. [Relevant hashtags - 15-20 for Instagram] ``` ### Step 6: Press and Media Outreach **Press Release Structure:** 1. Headline: [Company] Launches [Product] to Help [Audience] [Outcome] 2. Subheadline: [Supporting detail with a key stat or differentiator] 3. First paragraph: Who, what, when, where, why (the news) 4. Quote from founder/CEO 5. Product details and key features 6. Market context (why now, market size, trend) 7. Customer quote or early results 8. Availability and pricing 9. About the company (boilerplate) 10. Contact information **Media Pitch Email Template:** ``` Subject: [Angle] -- [Product Name] launches to [outcome] Hi [Name], I'm reaching out because you've covered [related topic] and I thought [Product Name] might be interesting for your readers. [One sentence about what it does and why it's newsworthy] [One sentence about early traction or results] [One sentence about what makes it different] I'd love to offer you [exclusive story / early access / founder interview / demo]. Happy to share more details if you're interested. Best, [Name] ``` ### Step 7: Influencer and Partner Coordination **Partner Outreach Timeline:** - Week 3: Initial outreach with personal message - Week 4: Follow up, share product details and demo - Week 5: Confirm participation, send swipe copy and affiliate links - Week 6: Reminder with launch day schedule - Week 7: Day-of coordination, thank you notes - Week 8: Share results, pay commissions, plan ongoing partnership **What to Provide Partners:** - Product access (free account or sample) - Swipe copy for email, social, and blog - Branded graphics and assets - Unique affiliate/referral link with tracking - Commission structure or reciprocal promotion plan - Launch day schedule with specific asks ### Step 8: Launch Metrics Dashboard Track these metrics in real-time during launch week: **Awareness Metrics:** - Website traffic (total and by source) - Social media impressions and reach - Press mentions and backlinks - Email open rates **Engagement Metrics:** - Time on site - Pages per session - Social media engagement rate - Email click-through rates - Demo video completion rate **Conversion Metrics:** - Signup/purchase conversion rate - Revenue generated - Average order value - Cost per acquisition - Email-to-conversion rate **Retention Metrics (Post-Launch):** - Day 1 / Day 7 retention - Feature adoption rate - Support ticket volume - NPS score ### Step 9: Common Launch Mistakes to Avoid 1. **Launching to nobody** -- Build the audience BEFORE the product is ready 2. **No urgency mechanism** -- Without a deadline, people bookmark and forget 3. **Perfectionism** -- Ship at 80% quality; iterate based on real feedback 4. **Single-channel launch** -- Coordinate across email, social, communities, and partners 5. **No follow-up sequence** -- Most conversions happen on days 3-7, not day 1 6. **Ignoring time zones** -- Schedule launches and emails for your audience's active hours 7. **No support plan** -- Launch day will generate support requests; be ready 8. **Pricing confusion** -- Make the offer crystal clear; don't make people calculate 9. **Forgetting mobile** -- Test every email, page, and checkout on mobile 10. **No post-launch plan** -- The launch is the beginning, not the end ### Step 10: Budget Allocation Guide | Budget Level | Allocation | |---|---| | **Bootstrapped ($0-500)** | 100% organic: content, communities, email list, personal outreach | | **Moderate ($500-5,000)** | 40% paid ads, 30% influencer/partner, 20% tools/software, 10% design | | **Well-Funded ($5,000-25,000)** | 35% paid ads, 25% influencer/partner, 20% PR/media, 10% events, 10% tools | | **Enterprise ($25,000+)** | 30% paid ads, 20% events/webinars, 20% PR, 15% influencer, 10% content, 5% tools | ### Step 11: Post-Launch Analysis Framework After the launch, generate a retrospective covering: 1. **Goal vs Actual**: Did you hit your targets? 2. **Channel Performance**: Which channels drove the most conversions? 3. **Email Performance**: Open rates, click rates, conversion rates by email 4. **Top Converting Content**: Which posts, pages, or ads drove the most action? 5. **Customer Feedback Themes**: What are people saying? 6. **What Worked**: Top 3 things that drove results 7. **What Didn't Work**: Top 3 things to change next time 8. **Unexpected Insights**: Surprises from the data 9. **Next Steps**: Immediate actions based on learnings ## Output Format Generate a file called `LAUNCH-PLAYBOOK.md` with: ```markdown # Launch Playbook: [Product Name] ## Launch Date: [Date] ## Launch Type: [Type] ## Primary Goal: [Goal with specific target] --- ## Week-by-Week Plan [Detailed week-by-week tasks with checkboxes] ## Email Sequences [Complete email templates customized for the product] ## Social Media Content [Platform-specific posts ready to customize and schedule] ## Partner/Influencer Plan [Outreach templates and coordination timeline] ## Launch Day Checklist [Hour-by-hour launch day plan] ## Metrics Dashboard [Metrics to track with target benchmarks] ## Budget Allocation [Specific dollar amounts based on stated budget] ## Post-Launch Plan [Week 8+ activities and analysis framework] ``` ## Verify (before declaring the playbook done) Run this checklist against the finished `LAUNCH-PLAYBOOK.md`; fix any failure, then re-check: - [ ] **File written**: `LAUNCH-PLAYBOOK.md` exists with all 7 Output-Format sections present (no placeholder headings left empty). - [ ] **Date consistency**: every email, social post, partner ask and PR date resolves to the SAME launch week and is backward-scheduled from the stated launch date — `grep` the file for the launch date and confirm no contradictory days/weeks. - [ ] **Offer consistency**: price, early-bird/bonus, and deadline are identical across email, social, and partner swipe copy (one offer, stated once, repeated faithfully). - [ ] **Specificity**: zero lines that would read identically for a different product — each ties to the user's product/audience/budget. If the user lacks an input, the placeholder is explicit (`[FILL: …]`), never a fabricated value. - [ ] **Evidence**: every metric target and market/competitor claim has a source or an explicit `[assumption]`/`[FILL]` tag; no invented testimonials or stats. - [ ] **Budget fit**: the Budget Allocation matches the user's stated budget tier (Step 10), with real dollar figures, not the generic table. State the result as a short PASS/FAIL line per item; only report "done" when all pass. ## Key Principles - Every recommendation should be tied to the user's specific product, audience, and resources. Generic advice is useless. - Include specific templates they can copy-paste and customize, not just frameworks. - If the user has run previous skills (market audit, market landing, market brand), incorporate those findings into the launch plan. - Time the playbook to their stated launch date and work backwards. - Always include a "minimum viable launch" option for users with limited resources. - Emphasize that launching is an event, not a moment -- the buildup and follow-through matter more than day one. ## Constraints ### MUST DO - Verify all claims with data or sources - Include actionable recommendations, not just observations - Consider the target audience and business context - Provide specific examples, not generic advice ### MUST NOT DO - Make claims without supporting evidence - Ignore the user's specific business context - Provide generic one-size-fits-all recommendations - Skip competitive or market context when relevant