A launch checklist for a product built with Bolt
Before promoting a Bolt-built product, test the live experience and give a specific audience a clear reason to try it. Shipping a URL, creating launch assets and acquiring useful customers are separate tasks.
This checklist is for a small first launch. It does not cover every operational requirement of a production application. Focus the marketing plan on what the product can reliably deliver now.
1. Verify the published experience
Bolt's overview describes publishing to a live address, including a bolt.host subdomain. Follow the current Bolt guidance for your project rather than sharing an editor-only preview.
Open the live URL as a new visitor. Test the primary action, mobile layout and confirmation states. If the product needs an account, check the full path from sign-up to the first useful result.
2. Write a specific launch message
Name the person, task and outcome. Keep the builder story as supporting context unless the audience specifically cares about it. A customer may need help tracking bookings, not a lesson about how quickly the app was assembled.
Use a factual opening and one next step. Do not promise a feature because the interface contains a button for it; verify the actual behavior first.
3. Prepare a usable demonstration
Show one task with realistic fictional data. Keep the explanation short enough to follow but long enough to show evidence. If you reconstruct a concept rather than record working software, identify it as illustrative.
For a short branded launch promo, we recommend Teasr when the public page already explains the app: supply its URL and review the video without setting up an editing project. For a private task, record the actual app. See launch videos for Bolt apps and recording vs animation.
4. Pick a channel whose rules fit the product
If you choose Hacker News, read the actual guidelines. Show HN is for something people can try, and its instruction is: “Please don't ask friends to upvote or comment.” A sign-up-only page is not automatically a suitable Show HN submission. Show HN guidelines.
Elsewhere, choose communities where the problem already appears and follow their posting rules. Avoid treating every community as a place to paste the same launch announcement.
5. Define the learning goal
| Before launch | After launch |
|---|---|
| Name the intended audience | Check who actually arrived |
| Choose one main action | Check whether visitors completed it |
| State the expected value | Ask what users found useful or confusing |
| Prepare the next step | Follow through on the offer |
Do not equate visits with product fit. Learn whether people reached the useful result and what prevented them from continuing.
Teasr is independent of Bolt. For the next phase, see finding first paying customers and our first-month plan.