What this prompt does
This prompt generates the full launch-day content stack for a Product Hunt submission in a single pass. It covers every copy surface you actually need on launch day: the tagline, the product description, the all-important maker first comment, screenshot captions, a Twitter/X thread, a LinkedIn post, and a Hacker News Show HN pitch. Each output is scoped by character and word count variables you control, so you are not left trimming overlong copy the night before your launch.
What makes the template effective is that it anchors everything to your specific audience, traction, and pricing. Product Hunt voters pattern-match corporate speak immediately and downvote it. By injecting real traction figures and actual pricing into the prompt, the AI has the material to write copy that sounds like a founder talking, not a press release. The "authentic, story-driven" instruction on the maker comment is load-bearing — that single adjective pair shifts the AI away from bullet-point feature lists toward a personal narrative, which is what actually converts upvotes.
The seven distinct outputs also mean you are not repurposing the same paragraph across every channel. The LinkedIn post, the HN pitch, and the Twitter thread each serve a different reader intent and community norm. This prompt keeps them separate by design.
When to use it
- You are launching a SaaS product or indie tool on Product Hunt and have less than 48 hours to prepare all copy assets.
- You have traction data (beta users, MRR, waitlist size) and want to work it into the narrative without it feeling like a brag.
- You are a solo founder or small team with no dedicated copywriter, and you need launch-quality copy across five channels simultaneously.
- You want to test multiple tagline angles quickly before committing — run the prompt twice with different
product_descriptionframings, once feature-led and once problem-led. Taglines diverge significantly across these two axes because the compression forces different words to the front. - You are an agency or operator managing a client's Product Hunt launch and need a structured first draft to hand off for review.
Example output
Product: Linkrunner — a broken-link monitor that emails devs when a page 404s in production.
Audience: indie developers and SaaS founders
Tagline: Know when your links die before users do
Description (80 words): Linkrunner watches every URL on your site and alerts you
the moment a link breaks — before a customer screenshots it and posts it on Twitter.
Set up in 60 seconds, no code changes required. Monitors sitemaps, crawls on a
schedule you control, and sends a plain-text email the second something goes wrong.
Trusted by 340 indie makers since beta. Free tier available.
Maker first comment (120 words): I built Linkrunner after losing a client because a
broken checkout link sat unnoticed for 11 days. No alert, no log, nothing — just a
support ticket three weeks later. Spent a weekend building a monitor I wished existed.
Beta launched quietly in February; 340 people signed up without a single ad...
Pro tips
- Feed real traction numbers. "340 beta users" in the
[traction]field produces far more credible copy than leaving it vague. The AI will work specific figures into the description and maker comment naturally. - Set
description_lengthto 80, not 300. Product Hunt truncates long descriptions in the feed. Shorter forces benefit-first writing; you can always pad, but you cannot un-bury a buried lede. - Test feature-led vs. problem-led framings in
[product_description]. The tagline outputs will diverge significantly — problem-led framings push the pain word to the front, feature-led framings push the mechanism. Run both and compare before committing to one. - The HN Show HN post follows different norms than PH copy. If the output sounds promotional, add "HN readers are technical and skeptical — strip adjectives, lead with what it does literally" before regenerating that section alone.
- Map
[screenshot_count]captions to user outcomes, not UI elements. If the AI writes "Dashboard view" as a caption, push back: "describe what the user achieves on this screen, not what they see."
