What this prompt does
This prompt assigns the AI a senior B2B SaaS product marketer role and makes it draft a go-to-market plan tight enough to execute the following week. You provide the [feature_name], [product_name], [primary_persona], and [pricing_model]. It returns an ideal customer profile, three message variants tuned to the persona and adjacent buyers, an activation path with the aha moment named, pricing-impact options, launch mechanics across channels with owners, and a 30-60-90 day metric plan — all in under 800 words.
The structure works because it ties the launch to what actually shipped. By grounding the activation path in [feature_name] and naming the aha moment, the prompt keeps the messaging honest rather than aspirational. [primary_persona] aims the three message variants at the right buyer, and [pricing_model] shapes the pricing-impact options (include in plan, paid add-on, or usage-based) so they fit your existing structure. The 30-60-90 metric plan turns the launch into something measurable instead of a one-off announcement.
When to use it
- You just built a feature and need a GTM plan that matches what shipped.
- You want messaging tied to the real activation path, not invented positioning.
- You need three message variants for the primary persona and adjacent buyers.
- You are deciding whether to bundle, charge for, or meter a new feature.
- You want launch mechanics with owners across email, in-app, docs, and social.
- You need a 30-60-90 metric plan you can commit to publicly.
Example output
You get a scannable plan with headers: an ICP describing industry, size, role, and the pain the feature removes; three persona-tuned message variants; an activation path from signup to first value with the aha moment named; pricing-impact options against your model; launch mechanics across channels with owners; and a 30-60-90 day metric plan with leading and lagging indicators — all under 800 words.
Pro tips
- Make
[feature_name]match what actually shipped, so the activation path describes real behaviour rather than a roadmap wish. - Define
[primary_persona]precisely, since the three message variants are tuned to that buyer and adjacent ones. - Use
[pricing_model]to anchor the pricing options; the model weighs bundling versus add-on versus usage-based against your existing structure. - Treat the 30-60-90 metrics as the part you commit to publicly, and tighten them until each is measurable.
- Re-run the message variants if they sound interchangeable; good variants should feel aimed at distinct buyers with distinct pains.
- Name the aha moment in the activation path explicitly, since the whole plan hinges on getting a new user to that first-value moment quickly.
- Assign real owners to the launch mechanics, since a channel with no owner is a step that quietly does not happen on launch day.
