Science of Apps - Launchpad · Template

Launch planning template:
a 12-week product launch roadmap

A product launch plan should include eight parts: a goal and metric, the audience and the problem, positioning, the launch size, a readiness check of the product, the channels and launch dates, a week-by-week roadmap with owners, and a follow-up plan with how you'll measure success. Start launch planning about 12 weeks out for a major launch, and test the product before launch day.

By , FounderUpdated 10 min read

Share

Quick answer: What should a product launch plan include?

  1. Eight parts: goal, audience, positioning, launch size, readiness, channels, roadmap, follow-up.
  2. 12 weeks for a major launch; two to four for a small update.
  3. Every task has an owner and a date — or it won't happen.
  4. Week 10: list on the Launchpad and read the product report while there's time to fix things.
  5. Measure against the goal you set in week 1, not against downloads or upvotes.

Key takeaways

  • A launch plan is a list of decisions and deadlines, not a marketing document.
  • The launch size should match the change: not every update deserves a launch day.
  • Product readiness belongs in the plan, with a date, not as an assumption.
  • Channels are chosen by where your audience already is.
  • The follow-up weeks decide whether launch attention becomes users.

Most launches don't fail on launch day. They fail in the planning: no clear goal, a sign-up flow nobody tested, or a launch date picked before anyone checked whether the product was ready. Launch planning fixes that by turning a big, vague event into decisions and deadlines. "Launch planning" is searched about 1,000 times a month and "product launch planning" about 880 (Google Keyword Planner, global 12-month average). This template gives you the eight parts every product launch plan needs, a 12-week product launch roadmap you can copy, and the metrics to judge it by. Platform rules were checked on each platform's own page on 18 November 2026. Jump to the eight parts, the 12-week roadmap or the follow-up.

Parts every launch plan needs
8
Weeks of planning for a major launch
12
Owner for the whole plan
1
List, test and fix before launch day
Week 10

What should a product launch plan include?

Copy this table into a doc or spreadsheet and fill in the right-hand column. If a row is blank, that's the first thing to decide.

#PartThe question it answersFill in
1Goal and metricWhat does success look like, in a number?e.g. 300 activated users in 30 days
2Audience and problemWho is this for, and what pain does it remove?
3PositioningWhat's the one line a stranger should remember?
4Launch sizeIs this a major launch, a feature launch or a quiet release?
5Product readinessCan a stranger sign up and get value without help?Test date:
6Channels and datesWhere is the audience already, and when do we launch there?
7Roadmap and ownersWho does what, by when?See the roadmap below
8Follow-up and measurementWhat happens after launch day, and when do we review?Review at +1 and +4 weeks

Table: Product launch plan template: the eight parts (Science of Apps editorial framework)

Size the launch before you plan it

Not every release deserves a launch day. Matching the effort to the change is the first decision in product launch planning.

Launch sizeWhenPlanning timeChannels
Major launchA new product, or a change that makes it a different productAbout 12 weeksOwn audience, communities, launch sites, press
Feature launchA significant new capability for existing usersTwo to four weeksOwn audience, changelog, communities, a relaunch where allowed
Quiet releaseFixes and small improvementsDaysChangelog and in-product notes

Table: Product launch sizes and how much planning each needs

The 12-week product launch roadmap

Each row is a week. Put an owner's name next to every task.

  1. Week 1

    Goal and audience

    Write the goal and metric; name the audience and the problem; appoint one owner for the plan.

  2. Week 2

    Positioning

    One-line message, three proof points, the main objection and your answer to it.

  3. Week 3

    Readiness audit

    Sign up as a stranger on desktop and mobile; list everything that blocks first value.

  4. Weeks 4–6

    Fix the core flow

    Fix blockers in sign-up, onboarding and the core task; set up analytics and UTM conventions.

  5. Week 6

    Choose channels

    Where your audience already is; shortlist launch sites that fit; check each one's rules.

  6. Week 7

    Build the audience

    Waitlist, build-in-public posts, conversations with early adopters.

  7. Week 8

    Assets

    Tagline, screenshots of the real product, a 30–60 second demo, the launch post, an FAQ.

  8. Week 9

    Book dates

    Schedule launch sites (Product Hunt allows up to 30 days ahead); brief anyone helping.

  9. Week 10

    List and test

    List free on the Launchpad; read the product report; fix critical findings.

  10. Week 11

    Rehearse

    Dry-run the sign-up with five strangers; check every link and tag; draft replies.

  11. Week 12

    Launch

    Own audience first, then launch sites one at a time; reply to everyone all day.

  12. Weeks 13–16

    Follow up

    Personal follow-ups, fixes, a results post, a review at one and four weeks.

Product readiness: week 10 in detail

Launch traffic is the least patient traffic you'll ever get. If the first screen confuses people or sign-up breaks on a phone, the launch is wasted, and you rarely find out why. That's why this roadmap tests the product two weeks before launch day: early enough to fix things, late enough that you're testing the real thing.

Science of Apps product investigation page with the headline Product intelligence that shows its work
A product investigation: every finding backed by a measurement or pinned to its screen.Image: Science of Apps · © Science of Apps · source

The Science of Apps Launchpad does two jobs in week 10. It gives the product a free, permanent launch page that every channel can link to, ranked by relevance and never payment. And it tests the product: a free baseline check of landing page, discoverability and speed as the listing goes live, and, if you want it, a full investigation of 22 areas with 39 automatic measurements in a real browser on desktop and mobile, 74 expert checks and five verdicts, reviewed by an analyst and private to your team.

Week 10 of your plan

Know what launch-day visitors will hit

List free, then order the report that fits: the first impression, or the full diagnosis with a 90-day roadmap.

Economy

See what new customers see

  • Store listing and homepage, screen by screen
  • Scorecard against 60 Laws of UX
  • Customers, competitors and the fixes worth most
≈ 40 pagesDelivered within 3 hours
Most popular
Premium

The full diagnosis and the plan

  • Every screen, every finding, every flow
  • All 60 laws with evidence and fixes
  • 8 strategy chapters and a 90-day roadmap
≈ 95 pagesDelivered within 24 hours

Researched from your live product and fact-checked against the evidence.

Choosing channels and launch dates

Pick channels by where your audience already spends time, then check each one's rules before you put it in the plan.

Product Hunt homepage showing Top Products Launching Today with upvote and comment counts
Product Hunt: schedule up to 30 days ahead; launches go live at 12:01 AM Pacific.Image: Product Hunt · Screenshot shown for commentary, 16 Nov 2026 · source
  • Product Hunt: schedule up to 30 days ahead; launches go live at 12:01 AM Pacific. Never ask for upvotes; Product Hunt can flag your account for it. If your last launch was less than two months ago, you need a relaunch request.
  • Show HN: for something people can try, ideally without sign-ups. Landing pages, sign-up pages and fundraisers don't qualify, and asking friends to upvote isn't allowed.
  • Your own channels: email list, existing users, social accounts and communities you already take part in. These come first on launch day.
Hacker News Show page listing numbered Show HN posts with points and comment counts
Show HN: for projects people can try, not landing pages.Image: Hacker News · Screenshot shown for commentary, 16 Nov 2026 · source

Follow-up and measurement

Write down now when you'll review results and what counts as success. Then tag every launch link.

Google Analytics Help page URL builders: Collect campaign data with custom URLs
Tag every link with utm_source, utm_medium and utm_campaign.Image: Google · Screenshot shown for commentary, 18 Nov 2026 · source
WhenReviewDecide
Launch day +1Sign-ups, activation, top questions, bugsHotfixes; FAQ updates
+1 weekResults by channel (UTM), activation rateWhich channels to repeat
+4 weeksRetention, revenue or goal metric vs the targetNext launch, next fixes, what to stop

Table: Product launch follow-up reviews

Google Analytics advises always using utm_source, utm_medium and utm_campaign when you tag links. Use one campaign name for the launch and a different source per channel.

Product launch steps people skip

Checklist: Product launch steps people skip — No written goal; Picking the date before the readiness check; Too many channels on one day; Assets made the night before; No owner per task; No follow-up weeks.
Product launch steps people skip
  • No written goal — you can't tell whether it worked
  • Picking the date before the readiness check — the date should follow the fixes
  • Too many channels on one day — you can't reply properly everywhere
  • Assets made the night before — screenshots and demos take longer than you think
  • No owner per task — shared tasks are nobody's tasks
  • No follow-up weeks — attention fades in days; follow-up turns it into users

The closer people get to a goal, the harder they push, the goal-gradient effect, which works on teams as well as users: a visible roadmap with weekly milestones keeps a 12-week launch moving.

Ready to plan your launch?

How we built this template

The eight-part structure, launch sizes and roadmap are Science of Apps editorial guidance. Platform rules (Product Hunt scheduling and upvotes, Show HN eligibility, UTM parameters) come from each platform's own help pages, read on 18 November 2026. The Launchpad's terms come from its homepage, investigation page and pricing page, read the same day. Search volumes are Google Keyword Planner's global 12-month averages. Science of Apps runs the Launchpad.

Key terms, defined

  • Launch planning: deciding the goal, audience, size, channels, timeline and follow-up of a launch before it happens.
  • Product launch roadmap: a week-by-week schedule of launch tasks with owners and deadlines.
  • Launch size: how big a launch is, matched to how big the change is.
  • Product readiness: whether a stranger can sign up and reach value without help.
  • Activation: a new user reaching the product's first moment of value.
  • UTM parameters: tags on a link that tell analytics the source, medium and campaign of a visit.

Frequently asked questions

What should a product launch plan include?

Eight parts: a measurable goal, the audience and the problem you solve, positioning and a one-line message, the launch size, a product readiness check, the channels and launch dates, a week-by-week roadmap with owners, and a follow-up plan with the metrics you'll judge success by. Everything else is detail inside those parts.

How far in advance should product launch planning start?

For a major launch of a new product, about 12 weeks: enough to test the product, fix the critical issues, build an audience, prepare assets and book launch dates. A small feature update needs two to four weeks. Product Hunt lets you schedule a launch up to 30 days ahead.

What are the steps of the product launch process?

Set a goal and metric; define the audience and positioning; size the launch; test and fix the product; publish a permanent page; prepare assets and messages; warm up your audience; launch on your own channels first, then launch sites; reply to everyone; measure against the goal; turn feedback into fixes and plan the next launch.

What is a product launch roadmap?

A week-by-week timeline of every launch task with an owner and a deadline, usually from about 12 weeks before launch day to four weeks after. It turns the plan into a schedule so dependencies, such as a fixed sign-up flow before a launch date, are visible early.

How do you measure whether a product launch worked?

Against the goal you wrote down in week one: sign-ups, activated users, trials, revenue or qualified conversations. Tag each channel's link with UTM parameters so you know which sources brought users who stayed, and review results at one week and four weeks after launch.

Who should own the product launch plan?

One person, usually the founder in an early startup or a product marketing manager in a larger team. They own the plan and the deadline; each task inside it has its own owner. Without a single owner, launch tasks drift because everyone assumes someone else has them.

Sources

  1. Product Hunt Help Center — Launch FAQ and myths: scheduling and upvotes (checked 18 Nov 2026)
  2. Hacker News — Show HN guidelines (checked 18 Nov 2026)
  3. Google Analytics Help — URL builders: collect campaign data with custom URLs (checked 18 Nov 2026)
  4. Science of Apps — Launchpad: launch your product free (checked 18 Nov 2026)
  5. Science of Apps — Product investigation (checked 18 Nov 2026)
  6. Science of Apps — Pricing: free listing, Economy and Premium reports (checked 18 Nov 2026)
  7. Checked November 18, 2026. Figures that change — fees, salaries, prices — are reviewed every six months; if something is out of date, tell us.
Pass it on

Know someone who'd enjoy this?

Send it to them — one tap, no sign-up. Good ideas travel best between friends.

Keep exploring

Where to go from here

Join free

Get the ideas, not the noise.

Sign up with Google and we’ll send you short UX psychology tips by email — why people tap, stall and leave, and what to do about it. Unsubscribe anytime. Prefer something to keep? Get the free Laws of UX guide as a PDF.

Get the free Laws of UX PDFFree · no spam · unsubscribe anytime
Free, forever

Launch day ends. Your listing shouldn't.

In this template, week 10 is when you list free on the Science of Apps Launchpad: your permanent launch page goes live and your product is tested with a detailed report, in time to fix what matters before launch day.

Free PDF · 74 pages · 2 editions

The Laws of UX, in one field guide

60 research-backed principles in 6 categories — what each one means, why it works on the human brain and how to use it on your own screens. Written by Sushant Singh, founder of Science of Apps, who has scaled consumer apps to lacs of users and spent 10+ years leading product across startups and digital businesses in the US, EU & India.

Pick your edition
Free PDF · 90 pages · 2 editions

100+ Subscription Paywalls, decoded

110 real paywalls from top apps, taken apart, rated out of 5 and decoded with the Laws of UX — plus the frameworks, copy and checklists to ship your own. By Sushant Singh, founder of Science of Apps.

  • 110 paywalls rated
  • 34 Laws of UX
  • 12 frameworks

Which paywall scored 4.8 out of 5, and which scored 2.6? It’s all inside.

Pick your edition
Free PDF · 188 pages · 2 editions

Unmistakable: the logo book

How the world’s greatest logos are made, chosen and kept — and how to make yours. 98 short lessons and 19 true stories for founders, designers and the curious. By Sushant Singh, founder of Science of Apps.

  • 98 lessons
  • 19 true stories
  • 60+ real logos

Why did a $35 sketch become the Swoosh, and why did Gap lose its nerve in six days? It’s all inside.

Pick your edition