The AI Product Launch Content Kit

A four-stage prompt sequence that turns one product update into a creator video, a launch post and an email, with every claim checked against what the product actually does

<aside> 🚀 FREE STRATEGY CALL Want to grow your product through viral reach? We help teams across iGaming, mobile apps, AI products, and SaaS build creator-led organic distribution generating tens of millions of views at CPMs starting from $0.03.

<aside> 🚀 Book a free strategy call

</aside>

On the call you'll receive:

THE IDEA: Starting launch content from a blank page wastes the best material you have: the release notes. They already say what changed. What they don't say is why a customer should care, how to show it, and how to say it in three different formats without the story drifting. This kit is a prompt sequence that does that work in four stages. Each stage produces an approved block that you paste into the next one, so the creator video, the launch post and the email all tell the same story, and a final check removes anything the product can't actually do.

WHO IT'S FOR: Product marketers, founders and growth teams at AI products (apps, tools, agents, SaaS) who ship updates often and want launch content that is specific, consistent and reviewable. It works with any capable AI assistant: copy a prompt, replace the [BRACKETS], paste the result into the next stage.

THE RULE THAT HOLDS IT TOGETHER: The assistant may only use facts you gave it. Everything else is marked [NEEDS INPUT]. A human approves each stage before the next one starts.


PART 1 - Prepare the four inputs

Before you open the assistant, collect these. Ten minutes here saves an hour of rewrites.

Input What to include Why it matters
Release notes The raw update text, changelog, or a list of what changed, as written by the team The only source of truth about what's new
Target audience One specific type of customer: role, situation, the job they hired a tool for Stops the output from being "for everyone"
Product limitations What the update does NOT do, known errors, plans or regions it isn't available in, anything needing setup Keeps claims honest and gives you "who it isn't for"
Examples you can demonstrate Real inputs and outputs you can show on screen today, ideally from your own product Turns claims into a demonstration viewers can see

The input sheet (copy this and fill it in)

PRODUCT NAME: [name]
ONE-LINE DESCRIPTION: [what the product does, in plain words]
UPDATE NAME: [name of this update]
RELEASE NOTES:
[paste the raw text]

TARGET AUDIENCE: [one specific customer type and the situation they are in]
LIMITATIONS AND CAVEATS:
- [limitation 1]
- [limitation 2]
- [availability, plan, region, setup needed]

EXAMPLES I CAN DEMONSTRATE:
- Example 1: input = [what I type or upload], output = [what the product returns]
- Example 2: [...]

PROOF THAT EXISTS (only real items): [usage numbers, customer quotes with permission, public benchmarks, none]
LAUNCH LINK / NEXT STEP: [where people go]
TONE: [e.g. clear, direct, no hype]

PART 2 - The setup prompt (paste this first, once per session)

This sets the rules for the whole sequence. Paste it at the start of the conversation.

You are helping a product marketing team turn one AI product update into launch content. Follow these rules in every answer:

1. Use ONLY the facts I give you in the input sheet and in approved blocks. Do not invent features, numbers, customer quotes, benchmarks, comparisons or availability.
2. If something is missing, write [NEEDS INPUT: what is missing] instead of guessing.
3. Never claim the product is the best, the fastest, accurate, safe or guaranteed unless the input sheet states exactly that, with its source.
4. Mention relevant limitations honestly. If a limitation changes who the update is for, say so.
5. Write in plain, direct language. No hype words such as revolutionary, game-changing or effortless.
6. Keep a running "Approved Launch Brief". Only add to it what I approve. Every later answer must stay consistent with it.
7. Work in stages. After each stage, stop and wait for my approval.

Reply "Ready" and wait for the input sheet.

Then paste your filled-in input sheet.


PART 3 - Stage 1: Connect the update to a specific customer task

Goal: Move from "what we shipped" to "what a specific person can now do." This is the reason someone would use the product.