# Launch Messaging Prompts Replace anything in [brackets] with your own details. ## Find the news - Here is what we are launching: [product or feature description]. Write the one-sentence news a reporter would lead with. Give me five versions, each under 20 words, and rank them by how surprising and specific they are. - Our buyers are [role] at [company type]. List the three things that changed in their world in the last 12 months that make [product] matter now. For each, suggest one launch headline built on it. - Act as a skeptical [buyer role]. Read this launch announcement: [paste draft]. List the five questions you would ask before believing it, then rewrite the first paragraph so it answers the top two. ## Shape the message - Build a launch message house for [product]: one umbrella message, three supporting pillars, and two proof points under each pillar. Use only the proof I give you here: [paste results, customers, data]. - Write the launch message for each member of the buying group: [list roles, such as CFO, IT lead, end user]. For each role, give their main fear, the one line that answers it, and the proof they will want to see. - Here is our launch copy: [paste]. Highlight every generic word (such as transform, seamless, powerful, or AI-powered) and replace each one with a specific outcome, number, or capability. ## Ship the assets - Using this message house: [paste], write a launch blog post outline with a headline, a two-sentence opening that leads with the news, section headings phrased as buyer questions, and a closing call to action. - Write a 150-word launch email to existing customers about [product]. Lead with what they can now do, include one proof point, and end with one clear next step. - Draft three LinkedIn posts for our CEO announcing [product]: one story-led, one data-led, and one about the problem behind the launch. Keep each under 200 words and in a plain, confident voice. - Create a launch-day FAQ for [product] with the 10 questions buyers, analysts, and journalists are most likely to ask. Answer each in two or three sentences using only the facts I have shared. ## Write the page - Write five headline and subheadline pairs for the [product] launch page using the problem, agitate, solve pattern, aimed at [buyer role]. - Write headlines for [product] using four formulas: a numbered list, a how-to, a question, and a proof-led headline built on a real result I give you: [result]. Give three of each. - Write the "Who this is for" section of the launch page: five specific buyer situations, each with the pain point described in the buyer's own words. - Write a section that lowers the buyer's perceived risk, using only what we actually offer: [pilot terms, guarantees, security commitments, or exit terms]. - Write the copy around our main call to action: the line above the button, the button text, and the reassurance line below it. Give three versions. - Generate 15 call-to-action button labels for [action, such as booking a demo], grouped into low-commitment, value-led, and urgency-led options. Keep each under five words. --- From the AI Marketing Lab: https://derekfrancis.net/lab/ Some prompts are adapted from Marketing Prompts by CoachKit Contributors, shared under the MIT License. MIT License Copyright (c) 2025 CoachKit Contributors Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.