Skip to the calendar
What Is Launching
Sign in Add your launch

Sat 21 Nov 2026
All times UTC

How to Build a Launch Calendar for Your Own Product

Planning · 9 min read ·

A launch is a set of dated tasks, not a single day. Build a calendar with milestones, owners and buffers, and keep it honest as the date approaches.

Illustration: Monospaced calendar grid in a clean schedule style, with a column of dates in ISO format and one highlighted launch row, dark ink on pale ground

A launch looks like a single date, but it is really a stack of smaller dates, each with a person attached. The screenshots must be ready before the page can be built. The page must be built before the listing can be submitted. The listing must be submitted before anyone can be told. If any item slips, everything downstream slips with it.

A launch calendar is the document that makes those dependencies visible. This article shows how to build one that stays useful instead of becoming wallpaper.

Start from the end

Fix the launch date first, even if it is provisional. Everything else is placed relative to it.

Write the date in an unambiguous form. The ISO 8601 standard, as summarised on Wikipedia, defines a well-defined, unambiguous way to represent dates and times in worldwide communications, putting the largest unit first: 2026-10-02, not 02/10/2026 or 10/02/2026. That one habit removes a surprising amount of confusion between people used to day-first and month-first formats, and it sorts correctly in any spreadsheet.

If your launch has a time, add the time zone or offset, for example 2026-10-02T09:00+01:00, or the UTC form ending in Z.

Layout: one row per task

A plain table works. Use these columns.

  • Date due. In ISO form.
  • Task. One verb and one object: "Write launch page copy".
  • Owner. One name, never a team.
  • Depends on. The task that must finish first.
  • Status. Not started, in progress, blocked, done.
  • Notes. Links, decisions, risks.

Sort by date. The earliest overdue row is your next job. That is the whole system, and it is enough.

Work backwards in blocks

Group the tasks by how far they sit from the date. A "T-minus" notation, where T is launch day, keeps the blocks clear.

T-minus six weeks: decisions. Fix the audience, the one-line pitch, the categories and the target date. Decide who is involved.

T-minus four weeks: assets. Screenshots, thumbnail, tagline, description, video if any. Product Hunt's preparation guidance lists tagline, thumbnail, gallery images and a first comment as the core items, which is a sensible starting kit for any platform.

T-minus three weeks: build. The launch page, the sign-up path, the analytics and the email sequence.

T-minus two weeks: book. Submit the listing or reserve a slot where scheduling applies. Brief helpers. Confirm legal and policy pages.

T-minus one week: test. Dry runs of the sign-up, the emails and the page. Fix what you find.

T-minus one day: freeze. No new features. Final checks of links and times.

T: launch. The run-sheet for the day.

T-plus one to seven: follow-through. Replies, fixes, update, review.

Our separate article on the week-by-week countdown goes through the middle blocks task by task.

Name the owner of every row

Tasks with two owners have none. Even in a team of two, put a single name against each row. If someone is away, write the cover in the notes.

For a solo founder, owners are all you, which is a warning. If thirty rows all carry your name in the same week, the plan is not realistic. Move rows earlier or cut them.

Mark the dependencies

Many launches slip because of waiting, not working. Typical external dependencies:

  • A platform's approval or queue. Some sites schedule entries in slots, so the date may not be yours alone to choose.
  • A designer or freelancer. Their calendar is not yours.
  • A payment or legal check. These can take days.
  • A partner or a customer agreeing to be quoted.
  • A third-party service with its own review time.

Put each in the table with its own due date, and ask early. Anything that depends on other people deserves slack.

Add buffers deliberately

Plans are optimistic by nature. Add buffers where they matter.

  • A spare week before the launch date for the unexpected.
  • A day between "assets done" and "page built" so errors can be caught.
  • Extra time for anything you have never done.
  • A rest day the day before launch. It is a task. Treat it like one.

If you reach T-minus one week with a clean calendar, you have earned a quiet week, and the buffer cost nothing.

Show the dates to the right people

A calendar nobody sees is a diary. Share it with everyone who owns a row. Check it together briefly once a week, ten minutes, at the same time. Ask three questions only: what is done, what is blocked, what changed.

Change the dates in the calendar the moment reality changes. A calendar that says one thing while everyone knows another loses all credibility.

Use a simple tool

You do not need project-management software. A shared spreadsheet is enough. If you prefer a calendar app, create a separate calendar for the launch, with an event per milestone, so it can be switched on and off.

Whichever you use, keep one master. Copies drift.

Handle time zones in the calendar

If your team or audience spans zones, store times in UTC in the master and show local times next to them. State the zone for any time that goes out of the team. Daylight saving changes happen on different dates in different places, and Wikipedia notes that around a third of the world's countries use it, so a gap between two cities can shift by an hour for part of the year.

Include the public side

The calendar is not only internal. Think about the dates the public will see.

  • The date you announce.
  • The dates of teaser posts.
  • The date of any early access.
  • The date your listing goes live.

If you publish these, mark them clearly as public and keep them correct. Structured data standards reflect the same discipline: Google's guidance on event markup requires a start date in ISO 8601 with a time zone offset, and says that when an event's status changes, you should keep the original start date and mark the change instead of deleting it. The principle applies to your own communication: when a date moves, say that it moved and give the new one.

Review and update

A launch calendar is a living plan.

  • Weekly: update statuses and shift dates honestly.
  • At T-minus two weeks: do a go or no-go review. Are you on track?
  • At T-minus three days: check every external dependency.
  • After launch: archive it, with notes on what took longer than planned. That becomes the template for next time.

Common mistakes

  • Starting from today. Plan from the date backwards.
  • Too much detail. Fifty tiny tasks swamp the plan. Keep tasks at half-day size or larger.
  • No owner.
  • Hiding the slip. If a task is late, say so.
  • Ignoring dependencies.
  • Forgetting follow-through. The week after matters.
  • Making the date sacred. A date is a commitment, but not at any cost. See our article on when to delay.

A starter template

Copy this into a spreadsheet and adjust.

  1. T-6w: Decide audience, pitch, categories, date. Owner: founder.
  2. T-5w: Draft launch page copy. Owner: founder.
  3. T-4w: Capture screenshots with demo data. Owner: designer.
  4. T-4w: Write alt text for each image. Owner: founder.
  5. T-3w: Build launch page. Owner: developer.
  6. T-3w: Install analytics and tag links. Owner: developer.
  7. T-2w: Submit listing or book slot. Owner: founder.
  8. T-2w: Brief helpers. Owner: founder.
  9. T-1w: Dry run of sign-up and emails. Owner: developer.
  10. T-1d: Click every link on phone and desktop. Owner: all.
  11. T: Launch run-sheet.
  12. T+1d: Thank, save evidence, triage feedback.
  13. T+7d: Review and write notes.

On this site

Our calendar page shows what is launching today, this week and soon, and launch weeks begin on Monday in UTC. The submit page is where you start. A launch entry is currently $5 and picks its own week; a free listing joins the free queue, which runs 1-2 weeks, so build that wait into your plan, or upgrade it to a full launch at the same price. The upcoming page lists the next launches, so you can see who shares your week. The people behind the project are named on the about-founders page.

A note on estimating durations

Most people underestimate how long things take, and the error is largest for work that involves other people. A useful habit is to estimate each task twice: once for how long it takes if nothing goes wrong, and once for how long it takes if one thing goes wrong. Put the second figure in the calendar. When a task finishes early, you gain slack; when it finishes late, you were already prepared. Review your estimates after the launch, comparing each with the real time, and keep the comparison for next time. After two or three launches you will know your own multiplier, and your calendars will become reliably accurate.

The takeaway

A launch calendar is a list of dated tasks with owners, built backwards from the date, with buffers and visible dependencies. Write dates in ISO form, share the plan, update it honestly and review it weekly. That is all it takes to turn a nervous date into a manageable project.

Questions and answers

What goes on a launch calendar?
The launch date, every task that must finish before it, the owner of each task, any dependency on other people, and buffers for things going wrong.
How do I write dates so nobody is confused?
Use the ISO 8601 format, year first, such as 2026-10-02, and state the time zone or UTC offset with any time.
Should I plan backwards or forwards?
Backwards. Fix the launch date, then place each task before it, working from the end towards today.
How much buffer should I add?
Add slack to anything that depends on other people or on approvals. A common rule is to assume tasks take longer than expected and leave a few spare days before the date.

Sources

Related guides

Support