product-launch
Plan and execute a product launch for a solopreneur business. Use when launching a new product, feature, service, or major update. Covers pre-launch strategy, building anticipation, launch day execution, post-launch momentum, and measuring launch success. Trigger on "product launch", "launch my product", "launch strategy", "how to launch", "launch plan", "go-to-market launch".
What this skill does
# Product Launch
## Overview
A launch is your best opportunity to create momentum, generate buzz, and acquire customers at scale in a short window. Most solopreneurs launch quietly and wonder why no one notices. This playbook shows you how to launch with impact — turning launch day into launch week, and launch week into sustained growth.
---
## Step 1: Define Your Launch Goals
A launch without clear goals is just noise. Before planning tactics, answer:
**What does success look like?**
- Revenue target? (e.g., $10K in first month)
- User/customer target? (e.g., 100 signups, 20 paying customers)
- Awareness target? (e.g., 10K impressions, 500 email signups)
- Press/social mentions? (e.g., featured on Product Hunt, 3 industry blogs)
**Pick 1-2 primary goals.** Everything in your launch plan should ladder up to these.
**Launch goal → Tactic mapping:**
- Revenue goal → Pre-sales, launch discounts, urgency
- User growth → Free tier, viral loops, community activation
- Awareness → PR outreach, influencer partnerships, paid ads
- Validation → Beta program, early adopter interviews, feedback loops
---
## Step 2: Build Your Pre-Launch Strategy (4-6 Weeks Out)
Great launches are won in the pre-launch phase. You build momentum BEFORE launch day, so when you hit "go," there's an audience ready to act.
**Pre-launch timeline:**
### 6 Weeks Before Launch: Build Your Waitlist
Create a simple landing page with:
- Headline stating the problem + solution
- Bullet points of key benefits
- Email signup form ("Join the waitlist — launching [date]")
- Social proof if you have any (testimonials from beta users, logos, early results)
Drive traffic to the waitlist from:
- Your existing email list ("something new coming — sign up to get early access")
- Social media (tease the launch, link to waitlist)
- Relevant communities (Reddit, Slack, forums — if allowed, or via helpful engagement)
**Goal:** 50-200 waitlist signups by launch (or 10x your target customer count).
### 4 Weeks Before Launch: Create Launch Content
Prepare content to go live on launch day and the week after:
- Launch blog post (the story, the problem, the solution, the demo)
- Demo video (2-3 min walkthrough showing the product in action)
- Social posts for launch week (7-10 posts across platforms)
- Email sequence for waitlist (3 emails: 1 week before, launch day, 3 days after)
- FAQ or help docs (so people can self-serve questions)
**Rule:** All content should be DONE 1 week before launch. Launch week is for execution, not creation.
### 2 Weeks Before Launch: Seed Early Reviews
Reach out to:
- 5-10 people in your network who would be ideal customers
- Ask them to try the product early (give them beta access or a preview)
- Request honest feedback + a testimonial if they like it
- If appropriate, ask if they'd share on launch day
**Why this matters:** Social proof on day 1 builds credibility. "Just launched!" with zero reviews = risky click. "Just launched — here's what early users are saying" = trust.
### 1 Week Before Launch: Notify Your Audience
Send an email to your list and post on social:
- "Launching [Product] in 7 days"
- Brief reminder of what it does
- Exclusive launch offer or bonus (e.g., "First 100 customers get 30% off")
- CTA: "Mark your calendar" or "Reply with questions"
**Goal:** Build anticipation. Prime people to act on launch day.
---
## Step 3: Launch Day Execution
Launch day is a coordinated push across all channels. Treat it like an event, not a quiet announcement.
**Launch day checklist (complete in this order):**
- [ ] **8 AM:** Publish launch blog post on your site
- [ ] **8:30 AM:** Send launch email to waitlist ("We're live! Here's what's new.")
- [ ] **9 AM:** Post on Product Hunt (if relevant — tech/SaaS products perform well here)
- [ ] **9:15 AM:** Post on Twitter/X (thread format works best — announce, explain value, demo link, ask for RT)
- [ ] **9:30 AM:** Post on LinkedIn (longer post with story + value + CTA)
- [ ] **10 AM:** Post in 2-3 relevant communities (Reddit, Slack, Discord — add value, don't spam)
- [ ] **12 PM:** Respond to every comment, reply, and question across all channels
- [ ] **6 PM:** Send launch email to your main email list (not just waitlist — your full audience)
- [ ] **Throughout the day:** Engage on social, thank supporters, amplify user posts
**Launch day content structure (social posts):**
```
HOOK: "Today's the day — we're launching [Product]!"
PROBLEM: "We built this because [specific pain point we kept hearing]."
SOLUTION: "Here's what it does: [3 key features or benefits]."
DEMO: "See it in action → [link to demo video or site]"
CTA: "Try it free / Grab the launch discount / Let me know what you think"
```
**Pro tip:** Schedule posts in advance so you're not scrambling. Use Buffer, Hootsuite, or native platform scheduling.
---
## Step 4: Launch Week Momentum (Days 2-7)
Launch day is just the start. Most solopreneurs go quiet after day 1 and lose all momentum. Extend the launch into a full week.
**Daily launch week content (1 post/day on social, 1-2 emails over the week):**
- **Day 2:** Share a customer testimonial or early result ("Here's what [User] said after trying it")
- **Day 3:** Behind-the-scenes content ("Why we built this / What we learned building it")
- **Day 4:** Feature deep-dive ("Here's how [Feature X] works and why it matters")
- **Day 5:** Use case or case study ("How [Customer] uses [Product] to solve [Problem]")
- **Day 6:** Objection handling ("Wondering if this is right for you? Here's who it's for — and who it's not for.")
- **Day 7:** Last call + urgency ("Launch week ends tonight — grab your [discount/bonus] before it's gone")
**Email sequence (to waitlist + main list):**
- **Launch day:** "We're live! Here's how to get started."
- **Day 3:** "Already seeing results — here's an early win from [Customer]."
- **Day 6:** "Launch offer ends in 24 hours — don't miss it."
---
## Step 5: Post-Launch Follow-Up (Week 2+)
The launch window closes, but the work continues. Now you shift from hype to retention and iteration.
**Week 2 priorities:**
- [ ] Thank everyone who supported the launch (email, DM, or public post)
- [ ] Survey early customers ("What's working? What's confusing? What should we improve?")
- [ ] Fix any critical bugs or UX issues that surfaced during launch
- [ ] Analyze launch metrics (see Step 6)
- [ ] Share a post-launch recap ("Here's what we learned from launch week")
**Week 3-4 priorities:**
- [ ] Turn early customers into case studies or testimonials
- [ ] Re-engage people who signed up but didn't convert (email: "Still on the fence? Here's what you need to know.")
- [ ] Plan next content or feature announcement to maintain momentum
- [ ] If launch went well, consider a second wave (submit to more directories, reach out to press, run ads)
---
## Step 6: Measure Launch Success
Track these metrics to evaluate how the launch performed:
| Metric | What It Tells You | How to Track |
|---|---|---|
| **Waitlist signups** | Pre-launch interest | Landing page analytics |
| **Launch day traffic** | Reach and attention | Google Analytics |
| **Conversion rate** | Traffic → signups/purchases | Analytics + CRM |
| **Revenue (if applicable)** | Immediate $ impact | Stripe/payment processor |
| **Email open/click rates** | Engagement with launch emails | Email tool (ConvertKit, Mailchimp) |
| **Social engagement** | Reach and amplification | Platform analytics (Twitter, LinkedIn) |
| **Customer feedback** | Product fit and satisfaction | Surveys, support tickets, conversations |
**Post-launch review (1 week after):**
- Did you hit your primary goal(s)?
- What worked better than expected? (do more of this)
- What underperformed? (diagnose why — messaging? channel? timing?)
- What would you do differently next launch?
**Rule:** Document your learnings. Every launch teaches you something. Write it down so you don't repeat mistakes or forget what worked.
---
## Launch StrRelated in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.