Software Launch Studio

Crafts the Product Hunt launch package - ranked taglines, the card description, the first maker comment, reply templates - and sets the PH-specific mechanics: launch timing, hunter choice, and the first-hour momentum plan. Use when someone asks "write our Product Hunt tagline", "draft our maker comment", "when should we launch on Product Hunt", "do we need a hunter", or "how do we get momentum in the first hour". Do NOT use for running the whole launch day in real time across channels - use launch-day-runbook instead - for choosing the launch date and beat calendar across channels - use launch-plan-sequencer instead - or for a scrappy indie launch beyond PH - use side-project-launch instead.

Writes App Store and Play Store listing copy to platform-specific rules - iOS name, subtitle, and hidden keyword field; Android title, short description, and keyword-woven full description - delivering every field with character counts, a ranked keyword list, and title options to A/B test. Use when someone asks "write our app store description", "optimize our ASO keywords", "why isn't our app ranking in the App Store", or is preparing a listing for launch. Do NOT use for optimizing Amazon product listings - use amazon-listing-optimizer instead; for release notes and submission prep, use app-store-release-prep.

Structures launch-day announcement posts for X and LinkedIn to platform mechanics - a single long-form X post with a native clip and the link in a reply as the default (the multi-post thread is the escape hatch for genuinely serial stories), no outbound link in the ranked unit, the LinkedIn founder post timed to the golden-hour window with the URL in the first comment, and first-hour reply choreography. Use when someone asks "where should the link go in our launch thread", "structure our launch announcement for X and LinkedIn", "when should the founder post the launch on LinkedIn", "why do launch posts with links in them get no reach", or launch day is set and the announcement posts need their platform shape. Do NOT use for a general educational or story thread - use tweet-thread-builder instead - or for everyday LinkedIn content - use linkedin-post-writer instead; for the Product Hunt page itself, use product-hunt-launch.

Runs the community side of a software launch - the Show HN package (the title convention, the link-versus-text post decision, the author's first technical comment, and a criticism-response register) plus seeding etiquette for subreddits, Slack and Discord groups, and newsletters, each timed to its own community rhythm rather than the Product Hunt clock. Use when someone asks "how do we launch on Hacker News", "write our Show HN post and first comment", "which communities should we seed our launch in", "how do I respond to harsh comments on our launch post", or the launch plan names Hacker News or community channels and only the big-platform posts exist. Do NOT use for the X and LinkedIn announcements - use launch-thread-anatomy instead - or for the Product Hunt page itself - use product-hunt-launch instead; for ongoing community building beyond the launch window, use channel-strategy.

Runs the pre-launch audience build - a 4-8 week teaser arc with one escalating reveal per week, the Product Hunt Coming Soon page as the platform-native pre-commitment surface, the 200-signup channel-strategy fork that picks the launch play (velocity versus feedback) and never blocks the date, a final 7-10 day countdown, and the three-wave launch-day notification plan on explicit T-plus offsets - including a runnable play-fork calculator. Use when someone asks "do we have enough waitlist signups to launch", "plan our teaser campaign before the launch", "should we run a velocity launch or a feedback launch", "how do we warm up an audience before launch day", or a launch is more than two weeks out and no pre-commitment engine exists. Do NOT use for a paid course open-cart sequence - use launch-email-sequence instead - or for always-on nurture automations - use email-drip-builder instead; for the full dated launch calendar, use launch-plan-sequencer.

Assembles the self-serve press kit - one ungated press URL with a one-paragraph boilerplate, a fact sheet where every number carries a date and a source, founder bios with high-resolution headshots, an SVG plus PNG logo pack in light and dark modes, 3-5 full-resolution product screenshots, and press mechanics with a single-exclusive default for early-stage launches (the embargo blast is the escape hatch) and the embargo datetime stated in the pitch subject line. Use when someone asks "build our press kit", "what goes on a press page", "prepare embargoed materials for journalists before our launch", "why isn't our launch getting press coverage", or press outreach is planned within two weeks of a launch. Do NOT use to write the press release itself - use press-release-writer instead - or to track coverage after it lands - use media-monitor instead; for producing the screenshots, use marketing-screenshot-craft.

Builds the accelerator demo-day showcase package to the one-minute compression standard - a spoken script capped at 150 words that opens with the strongest traction metric, one slide carrying 10 or fewer words at 40pt or larger on a white background, the canonical eight-line content order, and a three-rung live-demo fallback ladder. Use when someone asks "write my demo day pitch", "compress our pitch to one minute", "what goes on the one slide for demo day", "our accelerator pitch buries the traction", or an accelerator batch presentation or startup showcase is under two weeks away. Do NOT use for a full fundraising deck - use pitch-deck-builder instead - for rehearsal and investor Q&A drills - use pitch-practice-coach instead - or for a sales-demo walkthrough - use demo-script instead.

Turns launch-day results into the second launch - a metrics checklist filled during the day itself (hourly rank, referrer split, signup count), a public day-plus-2 retrospective shipped within 48-72 hours as an X post and a LinkedIn document post, permanent placement of earned badges and coverage on the site, and the conversion-ratio readout that calibrates the next launch cycle. Use when someone asks "write our launch retrospective", "we launched two days ago, what should we post now", "turn our launch numbers into a follow-up post", "how do we get a second wave of attention from the launch", or any product launch ended within the last three days and the numbers are still fresh. Do NOT use for an incident or outage postmortem - use postmortem-writer instead - or for the social post mechanics themselves - use launch-thread-anatomy instead; for adapting the writeup across more platforms, use content-repurposing.