LaunchRepoYour launch plan
Synthetic example: a fictional two-person team (Mira builds and supports, Jon markets) launching on a fictional date. Hours are example assumptions. Replace the date, the names and anything else with your own.
Your date and names are saved only in this browser (localStorage). Nothing is sent to LaunchRepo.
| Date | Day | Area | Task | Owner | Hours | Done when |
|---|---|---|---|---|---|---|
| Sun, Jan 31, 2027 | T−30 | Product | Freeze the launch scope | Mira | 2 | A list of what ships at launch and what waits |
| Tue, Feb 2, 2027 | T−28 | Channels | Write the positioning sentence | Jon | 3 | One sentence: who, what problem, why now |
| Tue, Feb 2, 2027 | T−28 | Users | Publish imprint and privacy policy where needed | Mira | 3 | Both pages linked in the footer |
| Fri, Feb 5, 2027 | T−25 | Channels | Create personal accounts on the launch platforms | Jon | 1 | Logins saved, profiles filled in |
| Tue, Feb 9, 2027 | T−21 | Product | Finish the landing page with titles and share image | Mira | 6 | Page live with title, description and Open Graph tags |
| Tue, Feb 9, 2027 | T−21 | Assets | Make logo, screenshots and a short demo | Jon | 8 | Square logo, wide screenshots, demo video |
| Fri, Feb 12, 2027 | T−18 | Product | Test checkout and onboarding in test mode | Mira | 4 | A success and a declined test payment went through correctly |
| Tue, Feb 16, 2027 | T−14 | Assets | Write the pitch in three lengths | Jon | 3 | 60, about 160 and 500 characters |
| Tue, Feb 16, 2027 | T−14 | Channels | Choose directories and submit the slow free ones | Jon | 4 | Every submission recorded with its state |
| Sat, Feb 20, 2027 | T−10 | Users | Set up welcome and receipt emails with SPF/DKIM | Mira | 3 | Test emails arrive in the inbox, not in spam |
| Tue, Feb 23, 2027 | T−7 | Channels | Draft launch posts and the first comment | Jon | 3 | Drafts saved per platform |
| Tue, Feb 23, 2027 | T−7 | Product | Check speed, contrast and keyboard use | Mira | 4 | No blocking issue on a phone |
| Sat, Feb 27, 2027 | T−3 | Users | Prepare answers to the questions you expect | Mira | 2 | A short FAQ document |
| Mon, Mar 1, 2027 | T−1 | Product | Dry run: sign up and pay from a phone | Mira | 2 | A fresh account works end to end |
| Tue, Mar 2, 2027 | T0 | Channels | Publish and post in the planned order | Jon | 4 | Every post live, links checked |
| Tue, Mar 2, 2027 | T0 | Users | Answer comments and emails all day | Mira | 6 | No unanswered question at the end of the day |
| Tue, Mar 2, 2027 | T0 | Product | Watch errors and fix what breaks | Mira | 4 | Error log checked every few hours |
| Thu, Mar 4, 2027 | T+2 | Channels | Record the state of every listing | Mira | 1 | Tracker updated with evidence |
| Tue, Mar 9, 2027 | T+7 | Users | Talk to five first users | Mira | 5 | Five notes with what they expected |
| Tue, Mar 9, 2027 | T+7 | Product | Fix the top three onboarding problems | Mira | 8 | Fixes shipped and announced |
| Tue, Mar 16, 2027 | T+14 | Channels | Follow up on pending listings | Jon | 3 | Each pending listing has a next date |
| Thu, Apr 1, 2027 | T+30 | Channels | Review results by channel and pick the next launch moment | Jon | 3 | Numbers per channel and a date for the next launch |
Workload per person
- Mira 50 h · 13 tasks
- Jon 32 h · 9 tasks
Roles and workload
The plan uses three roles instead of job titles, so it works for a solo founder as well as a small team. Put the same name on several roles and the workload adds up per person.
- Build
- Product, landing page, checkout, quality and fixes.
- Market
- Positioning, assets, copy, channels and follow-ups.
- Support
- Legal pages, emails, replies, user conversations and records.
How to adapt the plan
- Move the launch date first. All 22 tasks keep their distance to launch day, so the plan shifts in one step.
- If you work alone, enter your name in all three roles. The workload table then shows your total hours, which is the honest check of whether 30 days are enough.
- Change tasks after exporting: the CSV opens in any spreadsheet, the Markdown pastes into a README, an issue or a note. Add your own rows there.
- Keep the order of the slow tasks. Accounts, directories and emails have waiting times you cannot shorten on launch day.
Blank files without dates
Prefer to start from an empty sheet? These files contain the same 22 tasks with their day offsets and roles, without dates or names.
Plan or checklist?
This template answers when and who. The SaaS launch checklist answers what: 30 tasks with the reason and an official source for each, to tick off and export.
Frequently asked questions
- Is the launch plan template free?
- Yes. You can use it in the browser, download CSV or Markdown and print it without an account or email address.
- Can I use it in Google Sheets or Excel?
- Yes. Download the CSV and import it into Google Sheets, Excel or Numbers. The file is UTF-8, so accents and CJK characters stay intact.
- Is the example a real launch?
- No. The team, the names and the date are synthetic, and the hours are example assumptions. Replace them with your own.
- How long before launch should I start?
- The template starts 30 days before launch day because free directory queues and account setup take time. With less time, keep the order and compress the gaps.
- Where are my date and names stored?
- Only in this browser’s localStorage. Nothing is sent to LaunchRepo, and “Back to the example” clears them.
Hand the directory rows to your agent
LaunchRepo gives your coding agent the playbooks, dashboard and tracker for the directory submissions in this plan, so the “Channels” rows get done and recorded.
See pricing