launch_skill

Overview

This skill helps founders plan and execute an effective product launch for bootstrapped SaaS with zero budget or audience. It covers building a waitlist, seeding an audience, preparing launch assets, Product Hunt tactics, beta programs, pricing choices, and a 30-day post-launch momentum plan. Use it to turn launch day into sustained growth rather than a one-time spike.

How this skill works

I guide you through a 4–6 week pre-launch cadence: build a waitlist, seed an initial audience, prepare launch assets, and align channels for a coordinated launch week. For Product Hunt or multi-channel launches I provide timing, hour-by-hour actions, and supporter-checklists. Post-launch, I map a 30-day follow-up plan to convert early attention into users, feedback, testimonials, and a repeatable acquisition channel.

When to use it

• You need a step-by-step plan to get first 100+ users with no budget
• Preparing a Product Hunt listing and launch-day playbook
• Designing and running a focused beta program before public launch
• Coordinating a multi-channel launch week (email, social, communities)
• Planning post-launch 30-day momentum and roadmap adjustments

Best practices

• Build an audience first — spend 4–6 weeks warming a waitlist before launch
• Coordinate channels to peak simultaneously; don’t stagger major announcements
• Prioritize engagement over raw upvotes — comments and replies matter most
• Treat beta users as partners: give direct access, ask specific questions, and act on feedback
• Pick one pricing incentive for launch (discount, extended trial, or early-adopter tier) and avoid stacking offers

Example use cases

• Create a waitlist landing page with email capture and share-to-move-up mechanic
• Run a 2–4 week beta with 10–50 partnered users and scheduled check-ins
• Prepare Product Hunt assets: tagline, gallery images, maker comment, and 20+ committed supporters
• Execute a 7-day launch-week timeline with day-by-day posts and email cadences
• Plan a 30-day post-launch schedule: bug fixes, a feature release, lessons learned post, and growth channel tests