# A launch-day checklist you can actually use

Check your product page, links, images, UTC schedule and support plan before your launch, then record useful follow-up actions.

## Before you pick a week

Open the product website in a fresh browser session on your phone. Follow the main call to action from start to finish. Do not assume a flow works because it works in your already-signed-in account.

- Check the HTTPS URL, redirects and final destination.
- Make pricing, availability and early-access limits explicit.
- Confirm your contact and privacy pages are reachable.
- Check image ownership and remove private information from screenshots.

## Before submitting to ToastLaunch

Prepare the product name, one-sentence tagline, description, required logo and up to three screenshots. PNG, JPEG and WebP images up to 4 MB are supported; SVG uploads are not. Use PNG, JPEG, or WebP for your submission.

Choose one of the next four launch weeks with a free spot (30 per week), and add the ToastLaunch badge to your website before you submit. Each product website can have one active launch. There is no review queue: launches that break the rules are removed.

## During the week

Be available for questions without repeatedly refreshing the leaderboard. Keep a small note with the questions people ask, the words they use, and any broken links they find.

Share where you have permission and something relevant to contribute. Avoid asking people to vote without looking at the product, creating extra accounts, or promising reciprocal votes. ToastLaunch makers cannot upvote their own launch.

- Verify the published page and Visit link.
- Answer specific questions with specific answers.
- Keep track of real support issues.
- Thank people for useful criticism as well as encouragement.

## After your launch week closes

After your launch week ends, open your Launch Report Card in the dashboard. It shows your views, website visits, votes, and comments.

Write a short follow-up for people who explicitly asked for one. Name what you learned and what you will change. Store the report alongside your own website analytics and conversation notes, rather than treating any single number as the entire story.