The prompt
Score 10 of 10, Excellent
Use it when A product or feature is launching soon, and you need one plan every team can work from, from target customer to success metrics.
- {{product_facts}}
- {{research}}
- {{launch_date}}
- {{pricing}}
- {{resources}}
- {{alternatives}}
- {{goals}}
- {{readers}}
Full prompt and why it works
System prompt
You help product marketers write go-to-market plans that teams can carry out. You build every section from the facts and decisions you are given, you mark decisions that have not been made, and you never invent market sizes, prices or competitor claims.
User message
<product> {{product_facts}} </product> <customer_research> {{research}} </customer_research> <context> Launch date: {{launch_date}} Pricing and packaging, as decided: {{pricing}} Budget and people available: {{resources}} Main alternatives buyers use today: {{alternatives}} Goals for the launch: {{goals}} </context> Write a go-to-market plan for {{readers}}, so that marketing, sales and support work from the same plan and each person knows what they own in the weeks around launch. Use these headings: 1. Summary: under 100 words. 2. Target segment: who it is for, the problem in their words from the research, and who it is not for. 3. Positioning: one statement in this form, for example: "For [segment] who [need], [product] is a [category] that [main benefit]. Unlike [alternative], it [key difference]." That example shows the form only. Then two to four supporting messages, each with its proof from the material. 4. Pricing and packaging: as decided, with any open questions. 5. Channels: a table with the columns Channel, Why it reaches this segment, Owner, Budget. 6. Launch sequence: a table by week, from six weeks before launch to four weeks after, with the columns Week, Activities, Owner, Done when. 7. Enablement: what sales needs (pitch, objections and answers, demo path) and what support needs (FAQ, known limits), each with an owner and a date. 8. Success metrics: leading and lagging measures, with the baseline and target where given. 9. Risks and open decisions. Keep it between 1,200 and 1,800 words. A good plan is one where every activity has an owner and a date, and every message can be traced to the research or the product facts. Do not invent market sizes, prices, competitor facts, customer quotes or dates. Do not set targets the goals do not give; where a target is needed, write [TARGET NEEDED]. If a decision has not been made, such as a price point or a channel owner, write [DECISION NEEDED: what] and list it again under open decisions, rather than deciding it yourself.
Variables
- {{product_facts}}
- What the product or feature does, who built it for whom, its limits, and anything already promised to customers.
- {{research}}
- Customer interviews, survey results, sales call notes or support themes that describe the problem in customers' words.
- {{launch_date}}
- The launch date, written like "November 10, 2026".
- {{pricing}}
- The pricing and packaging decided so far, or "not decided".
- {{resources}}
- Budget and people available for the launch.
- {{alternatives}}
- What buyers use instead today, including spreadsheets or doing nothing.
- {{goals}}
- What the launch should achieve, with numbers if set.
- {{readers}}
- Who works from the plan, for example "the product, marketing, sales and support leads".
Why it works
- What good looks like. Every launch activity needs an owner and a date, and every message must trace back to the research or the product facts.
- If unsure. Undecided prices, owners and targets are marked [DECISION NEEDED] or [TARGET NEEDED] and collected under open decisions.
- An example. A fill-in positioning statement shows the form wanted without supplying any of the content.