How to build a product launch presentation: one announcement, three decks

Disclosure: NOXI publishes this guide and is one of the tools it mentions; the method works in any presentation software.

Most product launch templates are one slide list that mixes internal and external audiences: a market slide, a feature slide, a timeline, a "thank you". That deck cannot do any of its jobs well. Leadership needs to decide whether the product is ready, customers need a reason to try it today, and sales needs to know what to say, what to charge and what never to promise. This guide treats the launch as one story told three ways. You write a one-page press release and FAQ first, then build a readiness deck with a scorecard and a go/no-go rule, a minute-by-minute keynote, and an enablement deck with objections and pricing rules. The launch metrics, the T-60 to T+30 timeline and the claims check tie the three together, and one fictional product launch on 12 January 2027 runs through every section with its arithmetic shown.

What a product launch presentation is: three decks, one story

A product launch presentation is any deck used to bring a new product or major feature to market, and in practice a launch needs three: one to decide whether to launch, one to announce it, and one to sell it. Each has a different audience, a different decision and a different length.

The quotable rule for the whole guide: write the launch announcement first, then build three decks from it: one to decide, one to announce, one to sell. Teams that build one deck for all three audiences end up with a keynote full of internal risks or a readiness review full of marketing adjectives.

The order matters. The readiness review comes first, about four weeks before launch, because its outcome can move the date. The enablement deck is delivered a week or two before launch so sellers have time to practise. The keynote is the last to be finished and the first the outside world sees.

Launch deck, go-to-market plan and product roadmap: one sentence each

A go-to-market plan decides who you sell to, at what price and through which motion, months before launch; a product roadmap shows what the team will build and in what order; launch decks run the launch event itself and the readiness to hold it. Confusing them is the most common reason a launch meeting goes off track.

If you have an approved GTM plan, the launch decks inherit its numbers: the ideal customer profile, the price and the funnel rates. Do not re-argue them in the readiness review. If you do not have one, the readiness review will expose it, usually on the pricing criterion.

Start from the announcement: the one-page PR/FAQ

The fastest way to keep three launch decks consistent is to write the announcement first as a short press release and a list of frequently asked questions, the PR/FAQ format Amazon calls Working Backwards. The press release becomes the keynote, the FAQ becomes the enablement deck, and the open questions become the readiness scorecard.

Amazon's own description sets the size limits: the press release portion is "a few paragraphs, always less than one page", and the FAQ should be five pages or less (Amazon, An insider look at Amazon's culture and processes). The same page says the FAQ includes an honest assessment of how expensive and challenging the work will be. That second half is what most launch teams skip, and it is exactly what the readiness review needs.

The PR/FAQ template, mapped to the three decks

The example used through this guide is a fictional business-software launch. It starts here, as the summary paragraph of its press release.

Deck 1, the readiness review: 8 slides for the go/no-go meeting

The readiness review is the internal meeting, about four weeks before launch, where each function shows evidence that it is ready and leadership decides go, go with conditions or no-go. It needs 8 slides and 45 minutes, and the decision is recorded on the last slide before anyone leaves.

Three meeting rules make the review a decision rather than a status tour. Send the scorecard two working days ahead and ask owners to update it, not to present it. Name one decision-maker in the invitation; a room of equals rarely says no-go. And record conditions with dates on slide 8 during the meeting, because "we'll follow up" is how an amber becomes a launch-day incident.

The launch readiness scorecard: criteria, thresholds and the go/no-go rule

A launch readiness scorecard lists 10–12 criteria across product, support, sales, marketing, legal and operations, each with a measurable threshold for green, amber and red, a single owner and a current status. The go/no-go decision then follows a written rule instead of the loudest voice in the room.

Google's chapter on reliable launches describes the same idea for engineering: a launch checklist that gives the team action items and pointers, organised under themes such as capacity planning, failure modes, external dependencies and rollout planning, and it notes that load testing is required for most launches (Google, Site Reliability Engineering, Reliable Product Launches at Scale). A product launch scorecard extends that checklist to every function that touches the customer.

The scorecard template, filled in for Tallyfox (15 December 2026)

The go/no-go rule, written before the meeting

Tallyfox scores 8 green and 2 amber out of 10 criteria, no reds, and both ambers sit on criteria that are not hard gates. The decision is therefore go with conditions: the last 2 of 20 support agents are trained by Wednesday 6 January 2027 (owner: support lead), and the load test is re-run at 21,600 accounts after the database connection limit is raised, by Tuesday 5 January 2027 (owner: site reliability lead). Both dates fall before the final confirmation on Thursday 7 January, which is T-5.

Set thresholds before you look at the data. A threshold written after the status is known always lands just below the current number. Keep the criteria count between 10 and 12: fewer hides whole functions, more turns the review into a checklist reading.

Deck 2, the launch keynote: 10 slides, minute by minute for 20 minutes

A launch keynote for customers, press and partners follows six beats: the customer moment, the problem, the product in one sentence, the demo, the proof, and price and availability, then a single call to action. Ten slides fit a 20-minute slot with two minutes kept free for questions or overrun.

The minute budget adds up to 18 minutes of slides plus 2 of buffer. The demo gets 6 of the 20 minutes, the largest single block, because it is the part people remember and quote. If your slot is 10 minutes, keep slides 1, 4, 5, 8 and 10 and cut the demo to three minutes; for a 45-minute launch webinar, keep this spine and add a guided Q&A, as in our webinar presentation structure.

Slide 9 is where launch keynotes get companies into trouble. A keynote that previews uncommitted features creates sales conversations about things that may never ship. Show only what is on the committed part of your roadmap, with dates, and call the rest "later".

The demo: live or recorded, and the 30-second backup

Demo live when the product is stable and the network is under your control; play a recording when either is uncertain, and always have a 30-second recorded backup of each demo moment ready to play in its place. The audience forgives a recording; it does not forgive two minutes of a spinning loader.

Cut the demo to three moments, each tied to a line in the press release: the setup the customer does once, the moment of value, and the result they can show someone else. For Tallyfox that is: photograph a receipt (moment 1), watch it match the card transaction and land in the report (moment 2), and see the finance manager approve a complete report in one tap (moment 3). Anything that is not one of the three moments, such as settings, integrations and admin screens, goes into the enablement deck.

Rehearse the failure, not just the demo. Decide in advance who says "let me show you the recording" and on which cue, so the switch takes five seconds rather than a visible discussion.

The pricing and availability slide: what customers and press check first

The pricing and availability slide answers seven questions in one view: what it costs, in which currency and per what unit, which plan includes it, what the trial or free terms are, when it is available, where, and on which platforms. Journalists copy this slide into their articles, so every fact on it must be final and approved.

Apple's product press releases end with a section headed "Pricing and Availability" that lists the price, the colours, the order date, the availability date and the countries (Apple Newsroom, 13 October 2026). The keynote slide should carry the same facts, in the same order as the press release, so the two never disagree.

Two wording rules protect this slide. If you call a trial "free", the terms belong on the slide, and the US Federal Trade Commission's small-business guide says a "free" offer tied to a purchase should not raise the price of what is bought. And use "new" for a limited time: the same guide notes that at least one FTC advisory opinion has suggested a six-month limit on calling a product new (FTC, Advertising FAQ's: A Guide for Small Business).

Deck 3, sales and partner enablement: 12 slides plus an appendix

The sales enablement deck teaches sellers, customer success and partners who to sell the new product to, what to say in 30 seconds, how to demo it, what it costs, how to answer the top objections and what never to promise. It is delivered one to two weeks before launch, recorded, and kept as the reference everyone returns to.

The appendix holds the full external FAQ, the claims ledger and any commission or incentive details, which belong in one-to-one conversations rather than on a group slide. The customer-facing sales deck itself is a separate document built per account; our guide on how to build a sales deck covers its structure, and the sales kickoff presentation guide covers the annual event where a big launch often gets its main-stage slot.

Objection handling for Tallyfox (slide 9)

Launch metrics: leading and lagging, with formulas

Launch metrics split into leading metrics, which move in the first days and predict the result, such as invites accepted, activation and support tickets, and lagging metrics, which confirm it weeks later, such as paid conversion, new monthly recurring revenue and retention. Each needs a formula, a target from the launch plan and one owner.

Define activation before launch, in one sentence, with a time window. Tallyfox counts an account as activated when at least 2 of its employees have captured 5 receipts within 7 days of the invite. Without a written definition, the T+7 number will be argued instead of acted on.

The launch math sheet (Tallyfox, first wave)

The T+7 check: what the launch-week slide shows

At T+7, Tuesday 19 January 2027, 2,016 of the 7,200 invited accounts have activated: 2,016 ÷ 7,200 = 28.0%, against the 35% target, a gap of 2,520 − 2,016 = 504 accounts. If activation stayed at 28.0%, the wave would produce 2,016 × 0.12 = 241.92, about 242 paying accounts and 242 × $29 = $7,018 of new MRR, which is $8,758 − $7,018 = $1,740 a month below plan. Support also runs hot: 190 tickets from 2,016 activated accounts is 190 ÷ 2,016 × 100 = 9.4 tickets per 100 accounts, against a target of 8.

The T+7 slide therefore names one fix and one owner, which is what the readiness review promised: an in-app setup checklist that prompts the finance manager to invite two employees, live by Friday 22 January (owner: product manager). The wave-2 rule, written in the readiness deck, decides what happens next: the remaining 18,000 − 7,200 = 10,800 accounts are invited at T+14 only if wave-1 activation has reached at least 32% and there are no open P0 bugs; otherwise wave 2 waits one week.

Avoid importing "average activation rate" benchmarks from the web into the launch deck. They mix products, definitions and time windows; your own beta and waitlist history are the only defensible baseline.

Launch timeline: T-60 to T+30 with owners

A product launch timeline runs from T-60, when the announcement and date are approved, through the readiness review at T-28 and a final confirmation at T-5, to launch day and the reviews at T+7, T+14 and T+30. Each checkpoint has an exact date, one owner and one deliverable someone can check.

Mind the calendar. A January launch means the T-14 and T-5 work falls in the year-end holidays, so schedule it before people leave and name deputies. If you are launching around a trade show such as CES, which runs 6–9 January 2027 in Las Vegas (Consumer Technology Association, CES 2027), decide early whether to launch into the show's news cycle or a week clear of it, and set the embargo time accordingly.

Claims and proof: substantiate before launch day

Every performance claim in a launch keynote, press release or enablement deck needs evidence in hand before launch day, not a plan to gather it afterwards. In the United States, the Federal Trade Commission says advertisers must have proof before the ad runs, for both the claims they state and the claims customers reasonably take from the ad.

The FTC's guide for small business makes three points that apply directly to launch slides: advertisers must have evidence to back up their claims, the law requires that proof before the ad runs, and the FTC looks at both express and implied claims. On endorsements, the same guide says they must reflect the honest experience of the endorser, and consumer endorsements must reflect what typical users experience (FTC, Advertising FAQ's: A Guide for Small Business). Other countries have their own advertising rules; check them with counsel for each launch market.

The launch claims ledger

Keep the ledger in the enablement appendix so sellers repeat only approved claims. Our company profile presentation guide uses the same claims-ledger method for logos, testimonials and certifications.

B2B, consumer and app launches: what changes on the slides

The three-deck structure holds for every launch type; what changes is where the weight sits. B2B launches put weight on the enablement deck and the pricing rules, consumer launches on the keynote, press and availability, and app launches on store readiness, onboarding and activation in the first week.

For an internal launch, the keynote is often a slot in the company meeting rather than an event; our all-hands meeting presentation guide shows how to fit a short launch segment into the run of show.

Launching in the Gulf or in two languages: Arabic-English launch decks

A launch in the Gulf usually needs the customer-facing decks in Arabic and English: the keynote and the pricing slide in both languages, the enablement deck in the language your sellers and partners work in, and the readiness review in the language of the leadership team. Build the English and Arabic versions from the same approved PR/FAQ so the facts cannot drift.

Three rules prevent most bilingual launch errors. Translate the approved PR/FAQ first and have a native reviewer approve the product name, the promise and the price line before any slide is built. Put prices in the local currency with a clear note on whether tax is included, rather than converting a US price on the day. And check every right-to-left slide in its final file, because timelines, tables and process arrows read in the opposite direction in Arabic. Our guide to the bilingual Arabic-English presentation covers formats, mirroring and a two-direction QA checklist in detail.

Worked example: Tallyfox's readiness review in 8 titles

Tallyfox's readiness review for Mobile Receipts is held on Tuesday 15 December 2026, at T-28, with the chief operating officer as the decision-maker. Its eight slides carry the scorecard, the launch math and the go/no-go rule from the sections above, and each title states its finding.

Slide 5 is where the review usually turns. The chief financial officer's first question is "what if activation is lower?", and the answer is ready: at 28% activation the wave yields about 242 paying accounts and $7,018 of new MRR, $1,740 a month below plan. That sensitivity is why the deck commits to a T+7 check with a named fix, and why wave 2 is gated on 32% rather than opening automatically. The same numbers then flow into the keynote's pricing slide and the enablement deck's targets, unchanged.

Here are two slides from this article's worked example, as NOXI built them, unedited.

The pass/fail checklist before launch day

Run the three decks through one checklist at T-5. Each line is a question a launch leader, a journalist or a seller is likely to ask, and each has a pass condition you can see on the slides.

Close the keynote on the call to action rather than a "thank you" slide, and leave that slide on screen during questions so the one action you want stays visible.

3 AI prompts for the three launch decks

The prompts below assume the PR/FAQ and the scorecard already exist; replace each bracket with your own value and tell the tool to use only the facts in your files. A model should draft the slides from your announcement, never invent a beta result or a price.

How to build the launch decks in NOXI

NOXI turns your PR/FAQ and scorecard into structured decks and can match the style of a template you already use. It is free, with no card and no watermark; uploading files needs a free account, and a full deck uses about 25 of the 1,000 monthly credits.

Frequently asked questions

What should a product launch presentation include?

It depends on the audience, so build three decks. The readiness review includes the announcement, a scorecard, open items with owners, launch targets, the launch-week plan, risks and the go/no-go decision. The keynote includes the customer moment, the problem, the product, a demo, proof, price and availability and a call to action. The enablement deck includes buyers, talk track, pricing rules and objections.

How do you present a new product?

Start with one customer and the problem they face, introduce the product in one sentence, then spend the largest block of time on a demo of three moments: setup, the moment of value and the result. Follow with proof from a beta, the price and availability, and one call to action. In a 20-minute slot, give the demo about 6 minutes.

How many slides should a product launch deck have?

About 8 slides for a 45-minute readiness review, 10 slides for a 20-minute launch keynote, and 12 slides plus an appendix for sales enablement. For a 10-minute launch slot, keep five keynote slides: the customer moment, the product in one sentence, the demo, price and availability, and the call to action.

What is a launch readiness review?

A launch readiness review is a decision meeting held a few weeks before launch, in which the owners of product, support, sales, marketing, legal and operations report against agreed criteria and an accountable leader decides whether the launch goes ahead. The evidence is a scorecard with thresholds and owners; the output is a recorded decision with any conditions and dates.

What is a go/no-go meeting?

A go/no-go meeting is the point where a launch is approved, approved with conditions or postponed. Write the rule before the meeting: all green means go; any red, an amber on a hard gate, or three or more ambers means no-go; one or two ambers, each with an owner and a fix date before the final confirmation, means go with conditions.

What is the difference between a product launch plan and a go-to-market strategy?

A go-to-market strategy decides, months ahead, who the product is for, how it is priced, which sales motion and channels it uses and whether the economics work. A product launch plan runs the launch itself: readiness criteria, the announcement, the event, enablement, the timeline from T-60 to T+30 and the launch metrics. The launch plan inherits its customer, price and targets from the approved GTM strategy.

How do you structure a product keynote?

Use six beats in ten slides: the customer moment, the problem, why now, the product in one sentence, a demo of three moments, proof, a customer voice, price and availability, committed next steps and one call to action. In a 20-minute slot that is about 18 minutes of slides with 2 minutes kept for questions or overrun.

What metrics should you track after a launch?

Track leading metrics in the first days, such as activation rate (activated ÷ invited) and support tickets per 100 accounts, and lagging metrics over the following weeks, such as trial-to-paid conversion, new monthly recurring revenue and month-2 retention. Define activation in one sentence before launch, give every metric a target and an owner, and review it at T+7, T+14 and T+30.

Can AI make a product launch presentation?

Yes, if you give it the facts. Write the PR/FAQ and the readiness scorecard first, then ask an AI presentation tool to build each deck from those files only, with action titles and formulas shown. Check every number, price and date against your sources before sharing, and keep claims to those you can prove with beta data.

Sources & methodology

How this guide was made: the three-deck map, the PR/FAQ-to-deck mapping, the slide structures and minute budgets, the readiness scorecard and go/no-go rule, the launch math sheet, the timeline and the checklists are editorial recommendations based on common product and launch practice, not published standards. Tallyfox and every name and figure in its example are fictional, and every calculation is shown. The sources below support the facts about the world; all were checked on 16 October 2026.

• [1] Working Backwards and the PR/FAQ: a press release of a few paragraphs, always less than one page, and an FAQ of five pages or less that includes an assessment of cost and difficulty — Amazon, What's it like to work at Amazon? An insider look at Amazon's culture and processes (excerpt from Working Backwards by Colin Bryar and Bill Carr).
• [2] Google's definition of a launch, the launch coordination checklist and its themes, gradual rollouts with canaries, and load testing required for most launches — Google, Site Reliability Engineering, chapter "Reliable Product Launches at Scale" (Rhandeev Singh and Sebastian Kirsch with Vivek Rau).
• [3] Proof before the ad runs, express and implied claims, "free" offers, the suggested six-month limit on "new", and endorsements reflecting honest and typical experience — Federal Trade Commission, Advertising FAQ's: A Guide for Small Business (April 2001, edited January 2025).
• [4] The "Pricing and Availability" section of a product press release, listing price, colours, order and availability dates and countries — Apple Newsroom, Apple announces the next generation of HomePod mini (13 October 2026).
• [5] CES 2027 dates and location: January 6–9, 2027, Las Vegas — Consumer Technology Association, CES 2027.

Build your launch decks in NOXI, free: the readiness review with its scorecard, the 20-minute keynote and the enablement deck, from one PR/FAQ and in the style of your own template, exported as an editable PowerPoint or PDF.