SaaS launch assets checklist

Direct answer

Prepare launch assets as a reusable kit: positioning copy, product facts, screenshots, demo, social image, maker story, tracked links, support answers, and backup files. Every asset should help a target user understand or try the product—not merely decorate the campaign.

Copy kit

• One sentence naming the user, job, and outcome.
• Short and long descriptions using the same verified facts.
• A launch announcement and founder or maker comment.
• Pricing, access, privacy, security, and limitation answers.
• Channel-specific calls to action that comply with community rules.

Store final copy in one shared document so last-minute edits do not create contradictory claims.

Visual kit

Create a readable logo or thumbnail, a social preview image, and three to five screenshots that follow the main user journey. Use real interface states and remove private customer data. Add concise captions. Record a short demo that reaches value quickly, includes captions, and still makes sense without sound.

Export source files plus optimized web versions. Verify aspect ratios and file limits against each platform’s current documentation.

Delivery kit

Prepare a canonical landing URL, campaign-tagged links for each channel, product documentation, status page, contact path, and optional press folder. Test social cards with production URLs. Keep a plain-text copy of every scheduled post and an alternate image host in case a platform upload fails.

Launch-day folder

/launch
  /copy
  /images
  /video
  /press
  links.csv
  faq.md
  runbook.md

The runbook should list schedule and timezone, account owners, publishing links, monitoring dashboards, known risks, rollback authority, and the next update time.

Final quality check

Ask someone unfamiliar with the product to review the kit. They should identify the intended user, problem, result, price model, and first action without a verbal explanation. Then open every asset on mobile and verify that text remains readable and links reach the correct production page.

Sources

• Product Hunt: preparing for launch
• Product Hunt Featuring Guidelines
• Show HN Guidelines

<!-- faq:start -->

Frequently asked questions

How many screenshots should a SaaS launch include?

Use enough to explain the core journey without repetition, commonly three to five. Each image should answer a distinct question or demonstrate a meaningful step.

Do I need a launch video?

No. A short video helps when motion or workflow is difficult to explain, but clear screenshots and a product people can try are better than a rushed promotional video.

<!-- faq:end -->