The Product Launch Sequence Planner: Turn One Announcement Into a Multi-Touch Campaign
Why this prompt matters
A single-touch launch wastes the attention cycle that a real campaign could capture. Industry data on SaaS email engagement consistently shows that only 20-30% of an email list opens a single launch email, and feature adoption rates for features announced once and never mentioned again regularly sit under 10% six months later, even for genuinely useful features. A sequenced launch recaptures the users who missed, ignored, or forgot the first announcement — often the difference between a feature nobody uses and one that becomes a retention driver.
What we use it for
Your team built a long-requested bulk CSV export feature for your project management SaaS tool. Launch is set for Tuesday, you have an email list of 40,000 paying users, a LinkedIn company page, and an in-app banner slot. You know you want to announce it, but if you just send one email, most people won't see it and the ones who do will forget by the time they need the feature.
Prompt
Role: Act as a senior product marketing lead who has planned and run dozens of feature and product launch campaigns across email, social, and in-product channels. Context: [DESCRIBE THE PRODUCT OR FEATURE LAUNCHING] [TARGET AUDIENCE: who needs to hear about this] [LAUNCH DATE] [AVAILABLE CHANNELS, e.g., email list, LinkedIn/Twitter, in-app banner, blog, Slack community] [KEY DIFFERENTIATOR OR MAIN BENEFIT — the one thing that matters most to this audience] Task: Build a complete multi-touch launch sequence spanning pre-launch teaser, launch-day announcement, and post-launch reinforcement, with a distinct message angle and channel for each touch. Constraints: - Each touch must use a DIFFERENT angle — do not repeat the same hook or benefit statement across touches - Specify exact timing relative to launch day (e.g., T-minus 3 days, T-plus 1 week) - Label each touch's primary job: "Proof" (social proof, data, or customer quote), "Urgency" (deadline, limited rollout, or FOMO), or "Education" (how it works, why it matters) - Match copy length to the channel — do not write blog-length copy for a tweet, or a one-line caption for an email - If I haven't given you enough information about the differentiator or audience, ask me before inventing a generic one Output format: 1. A sequence table: Touch # | Timing | Channel | Primary Job (Proof/Urgency/Education) | Draft copy 2. A short paragraph explaining why the touches are ordered this way and what would break if two touches were swapped
Result
Example run (Context given: a project management SaaS tool launching a long-requested bulk CSV export feature; audience is 40,000 existing paying users; launch is next Tuesday; channels are the email list, an in-app banner, and the company LinkedIn page; the key differentiator is that competitors require a paid add-on for bulk export, this is included free.)
Touch 1 — T-minus 3 days — In-app banner — Education: "Bulk export is coming Tuesday. No more exporting projects one at a time — select as many as you need and download them all as CSV in one click." (Shown only to users who have manually exported 2+ projects in the last 30 days, since they feel this pain most directly.)
Touch 2 — Launch day — Email to full list — Proof: Subject: "You asked, we built it: bulk CSV export is live." Body leads with the three most common support-ticket phrasings of this request, quoted directly, followed by a 10-second GIF of the feature in action. No pricing mention — this is included in every plan, which is stated once, plainly, near the end.
Touch 3 — T-plus 2 days — LinkedIn post — Urgency/Education blend: A short post contrasting the old one-at-a-time export flow against the new bulk flow, framed around time saved ("what used to take 20 exports now takes one"), with a comment inviting users to share their own time-savings estimate — designed to generate organic proof in the replies rather than asking the company to assert it.
Touch 4 — T-plus 1 week — Email to non-openers of Touch 2 only — Education (shorter, benefit-first): Subject: "Still exporting one project at a time?" One sentence re-stating the benefit, one GIF, one button. No repetition of the backstory from Touch 2, since this segment never saw it.
Rationale: The sequence opens with education (not proof) because the audience doesn't yet know the feature exists — leading with a customer quote before anyone knows what's being praised would fall flat. Proof comes on launch day, once there's something concrete to react to. The urgency touch is deliberately soft (time-saved framing, not a countdown) because this is an included feature with no deadline — manufacturing false urgency here would read as insincere. Swapping Touch 1 and Touch 2 would mean leading with a customer quote about a feature nobody has seen yet, which has nothing to anchor to and would underperform.
Most feature launches get one email and maybe a tweet, and then the team moves on. That single touch reaches whoever happens to open that specific email on that specific day — everyone else simply never finds out the feature exists. The Product Launch Sequence Planner exists to fix that by forcing a structured, multi-touch campaign instead of a single announcement.
Why the prompt is structured this way
The constraint that every touch must use a different angle is the core of this prompt. Left unconstrained, a model asked to write "three posts about the same feature" will often just rephrase the same benefit statement three times with different adjectives. Explicitly requiring distinct angles — and then labeling each touch's job as Proof, Urgency, or Education — forces the model to actually vary the persuasion strategy instead of the wording, which is the difference between a sequence and three copies of the same email.
Requiring exact timing (T-minus/T-plus) rather than vague ordering like "first, then, finally" matters because launch sequences live or die on timing discipline. A teaser sent the morning of launch isn't a teaser, and a reinforcement email sent three months later isn't reinforcement — it's a second launch. Forcing specific day offsets makes the sequence something you could actually drop into a content calendar, not just a list of ideas in the right conceptual order.
Matching copy length to channel is a detail that's easy to skip but changes whether the output is actually usable. A model without that constraint will often draft all touches at roughly the same length regardless of platform, producing a LinkedIn post that reads like an email and a tweet-length banner message that gets cut off on mobile. Naming the channel in the Context section and enforcing length-matching in the Constraints section is what makes each piece of output copy-paste-ready rather than something you still need to rewrite for its actual destination.
The final instruction — explain what would break if two touches were swapped — exists because a sequence that merely sounds plausible in order is different from one where the order is load-bearing. Asking the model to justify the sequencing surfaces whether it actually reasoned about audience psychology (what does someone need to know or feel before the next touch lands) or just produced three plausible-sounding posts in a row.
How to get the most out of it
The quality of the differentiator you provide in Context directly determines the quality of the Proof touch — if you can't name the one thing that matters most to this audience, the model will either guess at something generic or, per the Constraints, ask you to clarify, which is the correct outcome. This prompt works best for launches with at least three realistic touchpoints: a true single-channel, same-day announcement doesn't need a sequence, but almost any feature with an existing user base and more than one channel benefits from spreading the message across days instead of hoping everyone who matters opens one email.