Tools / Launch checklist generator with dates and calendar

Know what to do on which day

Launch checklist generator

Tell us what you are launching, how it is priced, where it runs, how big the team is and when you go live. The page builds a checklist for your case, ordered by day relative to launch, with a time estimate for each task. Download it as Markdown, or as a calendar file with one all-day event per task.

Everything runs in this page. Your answers are not sent anywhere or stored. The checklist names no specific launch directory or community, so it stays useful whichever ones you choose.

1. What are you launching?

SaaSAppDev toolMCP serverOpen source

2. Does it have pricing?

YesNo

3. Is there a free tier?

YesNo

4. Which platforms?

WebiOSAndroidDesktopCommand line

5. Team size

Just me2 to 56 or more

6. Existing audience

None yetSmallEstablished

7. Demo video ready?

YesNo

8. Docs or quickstart written?

YesNo

9. Public code repository?

YesNo

10. Launch date

40 tasks, about 58 h 20 min

21 days before launch 2026-10-17

Name the 20 people most likely to use it 1 hWrite down real people and the places they already talk. You will message them by name, not post at a crowd.
Write the one-line pitch 45 minOne sentence that says what it does and who it is for. Every other piece of copy is built from this line.

18 days before launch 2026-10-20

Finish the landing page 4 hHeadline, a one-screen demo, who it is for, and one clear action. Check it at phone width.

17 days before launch 2026-10-21

Publish a clear pricing page 2 hShow every price with currency and billing period. State what is included and how cancellation works.

15 days before launch 2026-10-23

Shorten the path to the first success 3 hCount the clicks from signup to the first useful result. Remove every step that is not needed.

14 days before launch 2026-10-24

Record a 60 to 90 second demo 2 hShow the product doing the job from start to finish. No intro slide, no music.

13 days before launch 2026-10-25

Prepare screenshots and a logo set 1 h 30 minA square logo, a wide social image and three to five screenshots with short captions.

12 days before launch 2026-10-26

Set up analytics and a signup event 1 hCount visits, signups and the first meaningful action. Without these you cannot tell which channel worked.
Test checkout end to end with a real card 1 hPay, receive the receipt, cancel, and refund yourself once. Fix anything that confuses you.

11 days before launch 2026-10-27

Create a tracked link for each channel 30 minOne link per launch directory, community and email so you can see where visitors come from.
Check welcome and receipt emails land in the inbox 45 minSend to several mailbox providers and look in the spam folder. Confirm SPF, DKIM and DMARC pass.

10 days before launch 2026-10-28

Check the site in three browsers and on a phone 1 hLook at the signup form, checkout and the first screen after login.
Turn on error monitoring and uptime alerts 45 minYou want to hear about a crash before a user tells you.
Write a one-page quickstart 2 h 30 minFrom zero to first result in under five minutes, with copy-paste steps.

9 days before launch 2026-10-29

Add privacy policy, terms and a contact address 1 hDirectories and payment providers often ask for these, and users look for them.
Test the signup path under a burst of traffic 1 hSend yourself fifty signups in a few minutes. Look for rate limits, slow emails and database locks.

8 days before launch 2026-10-30

Set up a support inbox and canned replies 45 minDraft answers to the five questions you expect most. Reply fast in the first week.

7 days before launch 2026-10-31

Message your 20 people to ask for early feedback 1 h 30 minPersonal messages, no mass blast. Offer early access and ask one specific question.

5 days before launch 2026-11-02

Block your calendar for launch week 20 minYou are support, marketing and engineering at once. Clear the week and plan sleep.

4 days before launch 2026-11-03

Draft all launch posts in advance 2 hWrite the community post, the social thread and the email now, while you are calm.

3 days before launch 2026-11-04

Prepare launch directory submissions 1 h 30 minCollect names, taglines, descriptions, images and links in one document so each submission takes minutes.

1 day before launch 2026-11-06

Final walkthrough as a brand new user 1 hUse a fresh account in a private window on a phone and a laptop. Fix or hide anything broken.

Launch day 2026-11-07

Email your list with one clear action 30 minOne link, one ask, a short message written like a note to a friend.
Go live and post the announcement 1 h 30 minPublish the main post first, then send the email, then the rest. Check every link on the live page.
Reply to every comment and message 3 hAnswer within the hour where you can. Thank people and ask a follow-up question.
Submit to launch directories 2 hUse the document you prepared. Use a different tracked link for each one.
Watch error monitoring and signups 1 hKeep the dashboard open. Fix blocking bugs before anything else.

1 day after launch 2026-11-08

Post in the communities where your users already are 1 h 30 minRead each community's rules first. Lead with the problem and what you learned, not a pitch.
Follow up with early signups personally 1 h 30 minAsk what they were trying to do and whether it worked. This is your best source of product direction.

2 days after launch 2026-11-09

Fix the top three reported problems 4 hShip the fixes and tell the people who reported them.

3 days after launch 2026-11-10

Talk to your first paying customers 1 h 30 minAsk why they paid and what almost stopped them. Use their words on the pricing page.

4 days after launch 2026-11-11

Publish a short write-up of what happened 2 hShare what you shipped, what you learned and what is next. Honest numbers beat hype.

5 days after launch 2026-11-12

Submit to the next batch of launch directories 1 h 30 minSome accept submissions at any time. Pick the ones your users actually read.

7 days after launch 2026-11-14

Review week one numbers 1 hVisitors, signups, first-action rate and the best channel. Decide the single weakest step to fix first.

8 days after launch 2026-11-15

Group feedback into themes 1 hCount how many people raised each issue. Fix the most frequent before the loudest.

9 days after launch 2026-11-16

Thank the people who helped 45 minA short personal note to everyone who shared, commented or tested.

10 days after launch 2026-11-17

Publish a changelog entry 45 minShow that the product moves. List what changed since launch day.

14 days after launch 2026-11-21

Review pricing against what people actually used 1 hLook at which plan people pick and what they ask for. Change one thing at a time.

21 days after launch 2026-11-28

Write up one user story 2 hGet permission, then show a real person's problem and result.

28 days after launch 2026-12-05

Plan the next launch moment 1 hA launch is a series. Choose the next feature or milestone worth announcing.

How to use it

Answer the questions. Pick the product type, say whether it has pricing and a free tier, choose the platforms, team size and audience, and tell the page what you already have ready.
Set the launch date. Choose the day you plan to go live. Every task is dated from it, from three weeks before to four weeks after.
Work through the days. Tick tasks off as you go. Tasks are grouped by day, and each one has a short explanation and a time estimate so you can see whether a week is realistic.
Export it. Download the Markdown to paste into your notes or issue tracker, or the .ics file to import into any calendar app, where each task becomes an all-day event.

How the checklist is built

The checklist comes from a fixed set of rules, not a language model. Each task has a day offset from launch (for example 21 days before) and a condition. A task about a pricing page only appears if you said the product has pricing. Store review tasks appear for iOS and Android. Install and example-project tasks appear for dev tools. Tool testing and documentation tasks appear for MCP servers. Contributor-facing tasks appear for open source projects.

Day offsets are applied to your launch date using calendar days in UTC, so a task three weeks before a date in late March or early January lands on the right day regardless of daylight saving time or your time zone. Tasks before launch day are pre-launch, tasks from launch day to six days after are launch week, and later tasks are post-launch.

Time estimates are rough planning figures for one person doing the task carefully, based on common practice. They are not measurements, and a first-time launch usually takes longer. The calendar file follows the iCalendar format: each task is an all-day event whose end date is the next day, as the format requires, and long lines are folded at 75 bytes. The checklist cannot know your product, so remove what does not apply and add what is missing.

Ready for the launch directory step?

Submit your product to Toolfound for free. Ownership is verified before anything goes live, and your listing gets a permanent page.

Submit your product free

Questions

How far ahead should I start preparing?+

The checklist begins three weeks before launch because that is enough for a landing page, a demo, analytics and a handful of personal conversations. Mobile apps need longer if store review is involved. Start earlier if you have a team that needs sign-off.

Why does the checklist not name launch directories or communities?+

Which places suit you depends on your audience, and lists of them change. The tasks say launch directories and communities in general, and you choose the specific ones. Our launch guides compare options in detail.

How do I use the calendar file?+

Download the .ics file and import it into your calendar app. Each task appears as an all-day event on its date. Events are marked as free time so they do not block your calendar. Re-import after changing your launch date, and delete the earlier events first to avoid duplicates.

Are the time estimates accurate?+

They are planning guides for a careful single person, not measurements. Use the total to check whether the days before launch can hold the work. If not, move the date or cut tasks.

Does it save my checklist or my answers?+

No. Nothing is uploaded or stored. Ticks you make on the page are lost when you leave, so export the Markdown or the calendar file if you want to keep the plan.

Can I change the date after exporting?+

Yes. Change the launch date and every task moves with it. Export again to get a new file.

Startup directories with dofollow backlinks
Campaign URL CSV linter for your tracked links
MCP listing preflight
Redirect checker for your launch links
All free tools

40 tasks, about 58 h 20 min

21 days before launch 2026-10-17

18 days before launch 2026-10-20

17 days before launch 2026-10-21

15 days before launch 2026-10-23

14 days before launch 2026-10-24

13 days before launch 2026-10-25

12 days before launch 2026-10-26

11 days before launch 2026-10-27

10 days before launch 2026-10-28

9 days before launch 2026-10-29

8 days before launch 2026-10-30

7 days before launch 2026-10-31

5 days before launch 2026-11-02

4 days before launch 2026-11-03

3 days before launch 2026-11-04

1 day before launch 2026-11-06

Launch day 2026-11-07

1 day after launch 2026-11-08

2 days after launch 2026-11-09

3 days after launch 2026-11-10

4 days after launch 2026-11-11

5 days after launch 2026-11-12

7 days after launch 2026-11-14

8 days after launch 2026-11-15

9 days after launch 2026-11-16

10 days after launch 2026-11-17

14 days after launch 2026-11-21

21 days after launch 2026-11-28

28 days after launch 2026-12-05

How to use it

How the checklist is built

Questions

Related