Marketing · Launches & campaigns
The Best Prompt for a Product Launch
The best prompt for a product launch has the model ask before it plans. This one collects the launch brief, lets the model put up to five clarifying questions to you, and then produces a plan sized to the launch: the core message, a timeline counted back from your date with an owner for every task, an asset list, a go or no-go check, metrics and prepared responses to the likeliest problems.
Product Launch Plan Prompt
A two-turn prompt: the model asks its key questions, then builds a launch plan with a message, dated timeline, readiness check, metrics and risks.
- Works with
- ChatGPT, Claude, Gemini
- Difficulty
- Intermediate
- Complexity
- Conversation
- Variables
- 7
- Version
- 1.0
Customize this prompt
Fill in what you know. Anything left blank stays as a [bracketed placeholder]. Nothing you type leaves your browser.
7 variables · fields marked * matter most
# Role You are a product marketing lead planning a launch with me. You scale the plan to the size of the news and the size of the team. # Launch brief - What is launching: [What is launching] - Type of launch: [Type of launch] - Who it is for: [Who it is for] - Launch date: [Launch date] - What success looks like: [What success looks like] - Audience and channels we already have: [Audience and channels you already have] - Team and budget: [Team and budget] # Before you plan Ask me up to five questions whose answers would change the plan, such as whether pricing is final, whether existing customers get early access, or what must be ready in the product on day one. Number them and stop. Wait for my reply. If I answer "skip", proceed and list what you assumed at the top of the plan. # Then produce the launch plan 1. Launch message: one sentence saying what is new, for whom, and why it matters to them now. Then three supporting points, each tied to something in the brief. 2. Launch size: recommend a small, medium or large launch and justify it from the brief. A minor update does not need a campaign; say so if that is the case. 3. Timeline: a table of tasks in three phases (before launch, launch day and week, after launch). Columns: timing relative to the launch date (for example "T-14 days"), task, owner role, channel, what done looks like. 4. Asset list: every piece of content or collateral the timeline requires, with the task it supports. 5. Readiness check: the go or no-go items to confirm two days before launch, covering product, pricing and checkout, support, tracking and legal or compliance where relevant. 6. Measures: three to five metrics linked to the success definition, when to read each, and "baseline needed" where I gave no starting figure. 7. Risks: the three most likely things to go wrong, with a prepared response for each, including what to do if the date slips. 8. Thirty-day review: the questions to answer one month after launch. # Constraints - Use only channels and audiences listed in the brief unless you label a new one as optional and explain the cost. - Total workload must fit the stated team. Flag any week that looks overloaded. - Do not invent press contacts, partners, influencers, customer quotes or performance benchmarks. - No task without an owner role and a timing. # Output format Numbered headings as above, tables for the timeline, asset list and measures. Keep the prose brief; the tables are the plan.
Use it when you are
- Planning the release of a new product or a major feature with a small team
- Coordinating marketing, product and support tasks around a fixed launch date
- Deciding how much fanfare an update deserves before committing time to it
- Preparing a relaunch or repositioning of an existing product
- Building a first draft of a launch plan to review with stakeholders
Why this prompt works
Questions come first because launches hinge on unknowns
Whether pricing is final or existing customers get early access changes the entire plan, and a form cannot anticipate every such detail. Letting the model ask up to five questions, then stop, surfaces the specific gaps in your brief. The "skip" option keeps it usable when you are in a hurry.
The plan is sized before it is built
Not every release merits a campaign. Asking for a small, medium or large recommendation, with permission to say a minor update needs little, prevents a three-week program for a feature that deserves a changelog entry and an email. The saved effort can go to the releases that do deserve attention.
Everything is counted back from a real date
Relative timings such as T-14 days, combined with an owner role and a definition of done for every task, turn advice into a schedule. The rule that no task may lack an owner or a timing removes the vague "build buzz" lines that pad many launch plans.
Readiness and risk are treated as part of marketing
Launches fail on checkout bugs, unprepared support teams and missing tracking as often as on weak messaging. The go or no-go check and the prepared responses, including a slipped date, make the plan cover the day things go wrong. Deciding those responses in advance is far easier than improvising them in public.
It plans with what you have
Restricting the plan to listed channels and requiring the workload to fit the stated team keeps the output realistic. New channels may appear only as labeled options with a cost, so you can see what is core and what is extra.
How to use it
- Fill in the brief with a real launch date, a measurable definition of success and an honest account of who is available to work on it.
- List every channel and audience you already own, with rough sizes if you know them.
- Send the prompt and answer the model's questions in one reply. Type "skip" for any you cannot answer yet.
- Check the launch size recommendation before the timeline. If you disagree, say why and ask for the plan at a different size.
- Move the timeline table into your project tool, assign named people to each owner role, and adjust dates around holidays and release freezes.
- Return to the same conversation after launch and work through the thirty-day review questions with your actual numbers.
AI model compatibility
| Model | Status | Notes |
|---|---|---|
| ChatGPT | Expected to work | If the model starts planning without asking its questions, reply "Stop. Ask the questions first." and it should return to the first step. |
| Claude | Expected to work | Paste supporting material such as a product spec or pricing notes inside tags like <spec> beneath the brief so the questions it asks are about real gaps. |
| Gemini | Expected to work | Answer the clarifying questions in the same conversation, numbered to match, so each answer is tied to its question. |
“Expected to work” means the prompt uses plain, model-independent structure and has been reviewed for that — not that it has been run on that model. A model is marked Tested only when a test record is published below.
Worked example
Scenario: An illustrative hiking app introducing a paid tier to its existing free users.
# Role You are a product marketing lead planning a launch with me. You scale the plan to the size of the news and the size of the team. # Launch brief - What is launching: Trailhead Pro, a paid tier of our hiking route app with offline maps and group trip planning, $6/month - Type of launch: Major feature or new tier - Who it is for: Existing free users who hike at least monthly, especially those who organize trips for friends - Launch date: May 6 - What success looks like: 1,500 paid subscribers in the first 60 days and no rise in support response time - Audience and channels we already have: In-app messages to 40,000 monthly users; email list of 22,000; Instagram account; a blog; a small group of beta testers - Team and budget: One marketer, one designer two days a week, two support staff; $3,000 for paid promotion # Before you plan Ask me up to five questions whose answers would change the plan, such as whether pricing is final, whether existing customers get early access, or what must be ready in the product on day one. Number them and stop. Wait for my reply. If I answer "skip", proceed and list what you assumed at the top of the plan. # Then produce the launch plan 1. Launch message: one sentence saying what is new, for whom, and why it matters to them now. Then three supporting points, each tied to something in the brief. 2. Launch size: recommend a small, medium or large launch and justify it from the brief. A minor update does not need a campaign; say so if that is the case. 3. Timeline: a table of tasks in three phases (before launch, launch day and week, after launch). Columns: timing relative to the launch date (for example "T-14 days"), task, owner role, channel, what done looks like. 4. Asset list: every piece of content or collateral the timeline requires, with the task it supports. 5. Readiness check: the go or no-go items to confirm two days before launch, covering product, pricing and checkout, support, tracking and legal or compliance where relevant. 6. Measures: three to five metrics linked to the success definition, when to read each, and "baseline needed" where I gave no starting figure. 7. Risks: the three most likely things to go wrong, with a prepared response for each, including what to do if the date slips. 8. Thirty-day review: the questions to answer one month after launch. # Constraints - Use only channels and audiences listed in the brief unless you label a new one as optional and explain the cost. - Total workload must fit the stated team. Flag any week that looks overloaded. - Do not invent press contacts, partners, influencers, customer quotes or performance benchmarks. - No task without an owner role and a timing. # Output format Numbered headings as above, tables for the timeline, asset list and measures. Keep the prose brief; the tables are the plan.
What a good response should contain
- A first reply containing only numbered questions, for example about annual pricing, a free trial of the paid tier and what happens to features that are currently free
- After your answers, a one-sentence launch message aimed at trip organizers, with three supporting points drawn from the brief
- A timeline table that leans on in-app messages and email, with owner roles limited to the people listed
- A readiness check that includes payment flow testing, support macros for billing questions and subscription tracking
- Metrics tied to the 1,500-subscriber goal and support response time, with "baseline needed" where no starting figure was given
This is an illustrative scenario showing how to fill in the prompt and what to look for. It is not a recorded model output. Recorded outputs will be published here once this prompt has a test record.
Testing and editorial review
Status: Untested. Reviewed for structure and clarity by the editorial team. No recorded model test yet.
No test record has been published for this prompt yet. When it is tested, this section will show the model and version, the date, the inputs, the actual output and notes against our seven-point rubric. We do not publish numerical scores.
| Author | TheBestPromptFor Editorial Team — The editorial team writes, reviews and maintains the prompts and guides on TheBestPromptFor. Prompts are drafted with AI assistance and reviewed against published editorial standards. |
|---|---|
| Published | November 15, 2026 |
| Last reviewed | November 15, 2026 |
| Last tested | Not yet tested |
| Version history |
|
Limitations and things to check
- The plan reflects only what is in your brief and answers. It knows nothing about your product roadmap, release process or internal approvals.
- Task durations are estimates. Confirm them with the people who will do the work.
- It will not find press contacts, partners or creators for you, and is instructed not to invent them.
- Legal and compliance items in the readiness check are prompts to consult the right person, not a complete list for your industry or region.
Alternative prompts
Marketing
Marketing Strategy Prompt
Turns your business facts into a focused strategy: a diagnosis, one priority segment, positioning, three channels at most, and a phased plan sized to your budget.
- ChatGPT
- Claude
- Gemini
Marketing
Email Sequence Prompt
Maps a welcome, nurture, cart or win-back sequence first, then writes each email with one job, one call to action and only the proof you supply.
- ChatGPT
- Claude
- Gemini
Marketing
Social Media Content Calendar Prompt
Plans two to four weeks of posts sized to the time you really have, built on content pillars and your own material, with week-one captions drafted.
- ChatGPT
- Claude
- Gemini
Web Design
Landing Page Design Prompt
Plans a single-goal landing page: message match with the traffic source, section order, first-screen spec, form design and draft copy using only your real proof.
- ChatGPT
- Claude
- Gemini
Related resources
Technical guide
Prompt Chaining: Breaking a Task Into Linked Prompts
How to split a large task into a sequence of focused prompts, design the handoffs between them, and debug the chain when a step goes wrong.
Guide
How to Improve AI Responses
A diagnostic approach to weak AI answers: name the fault, trace it to the gap in your prompt, then follow up precisely or rewrite and start again.
Frequently asked questions
What if I do not have a firm launch date?
Enter a target date anyway and say it is provisional when the model asks its questions. The timeline uses relative timings, so shifting the date moves everything with it, and the risks section includes a response for a slipped date.
Does this work for a physical product?
Yes, with more detail in the brief. Mention inventory, lead times, retail or marketplace partners and shipping dates, since these constrain the timeline more than marketing tasks do. Expect the model's questions to focus on stock and fulfillment readiness.
Why does the model ask questions instead of producing the plan straight away?
A launch plan built on a wrong guess about pricing, audience access or product readiness has to be redone. A short round of questions costs a minute and usually removes the largest assumptions. You can bypass it by replying "skip".
Sources and references
- Prompt engineering overview — Anthropic
- Prompt design strategies — Google AI for Developers
Was this prompt useful?
No account needed. Do not include personal information.