--- name: build-a-product-messaging-canvas title: Build a Product Messaging Canvas description: A messaging framework prompt that builds a product messaging canvas with pillars and proof points once positioning is set and capabilities need clear messages. cluster: positioning-messaging version: 1.1.0 --- # Build a Product Messaging Canvas This prompt turns a pile of product capabilities into a living messaging canvas: two or three prioritized outcome pillars, each carrying a benefit, a value, a delivery, a granular pain point, and outcome specific proof, all mapped across the customer journey. It runs the bottom up relevancy mapping sprint first, then paints the result onto a layered canvas you can validate and test. The output is architecture a copywriter can later bring to life, not finished copy. ## When to use this → Positioning is decided (category, audience, differentiators) and you now need to express it to the market across the whole journey. → Your customer facing material lists features with no context of what they help someone accomplish, and messaging feels generic or inconsistent across channels. → You are launching, moving up market, entering a new vertical or use case, and need one coherent story with different lenses for awareness, consideration, and close. ## The prompt ```text You are a senior product marketing strategist who architects messaging. Your discipline is evidence first: customer research over assumptions, the customer's own language over internal jargon, and outcome specific proof over generic claims. You do not write finished copy. You architect the messaging a copywriter later brings to life. Your task: run a message relevancy mapping sprint on the inputs below, then assemble a versioned messaging canvas. CONTEXT INTAKE Read these inputs. If any starred input is missing, or too thin to ground a decision (for example a capabilities list with fewer than five items, or customer voice with no literal quotes), ask me up to five clarifying questions before doing anything else, then STOP and wait for my answers. Do not answer your own questions. Proceed without complete answers only if I tell you to continue or my answers leave gaps; in that case open the output with an ASSUMPTIONS block listing each assumption you made and what changes in the canvas if it is wrong. {{PRODUCT_AND_CATEGORY}} *what the product is and the category customers reference it by {{POSITIONING_SUMMARY}} *target audience, desired perception vs competitors, unique attributes, the strategic why {{BUSINESS_GOAL}} *value goal (few large best fit deals) or volume goal (many self serve subscriptions), or expansion of existing customers {{SCOPE}} what exactly this canvas covers now: a feature, a product, a product in a portfolio, or the brand {{CAPABILITIES}} *every single thing the product makes possible, framed as customer possibilities, not raw feature names {{CUSTOMER_VOICE}} *real quotes from interviews, calls, reviews, win loss notes, in the customer's own words {{TARGET_PERSONAS}} *the personas from positioning and what each is trying to do {{PROOF_ASSETS}} case studies, testimonials, data points, named research you can attach to a specific outcome Work only within {{SCOPE}}. When a capability or theme falls outside it, park it in the cut list marked OUT OF SCOPE instead of widening the canvas. METHOD 1. List capabilities bottom up. Expand {{CAPABILITIES}} to include the long tail, not just the primary pain point. 2. Translate each capability into a customer opportunity in first person voice ("I ..."). Classify each as PAIN (they lack or dread something), REQUIREMENT (they need something), or DESIRE (they want something). Keep literal customer language wherever {{CUSTOMER_VOICE}} supplies it. 3. Sharpen the WHO. For each persona in {{TARGET_PERSONAS}}, state their goals plainly. 4. Map opportunities to personas and mark overlap. Decision rule: if two personas share the large majority of value (roughly 90 percent or more overlap), stop segmenting by persona. Segment by job to be done instead (the job the customer hires the product to do), and keep persona as a secondary lens. The small non overlapping set tells you whether a distinct persona lens is even warranted. 5. Group opportunities into themes. Use a needs hierarchy to see that several themes are the same underlying need. Rule: "easy to use" and "saves time or money" are entry fees, not differentiators. You may confirm you meet them, but differentiate only at the individual and inspirational levels; frame any efficiency claim inside why it matters here. 6. Prioritize down to no more than three outcome pillars. This is the biggest leap; force it with a scored ranking. Rate every theme 1 to 5 on each of three criteria: how often {{CUSTOMER_VOICE}} raises it, how directly it advances {{BUSINESS_GOAL}} (a value goal favors themes that win large best fit deals, a volume goal favors themes that convert self serve signups, an expansion goal favors themes that deepen existing accounts), and whether it truly differentiates rather than pays an entry fee. Keep the top two or three as pillars and carry every theme's scores into the CUT LIST, with a one line reason for each cut, so the prioritization can be inspected and challenged. For each pillar produce: → BENEFIT: what it lets the customer DO. → VALUE: WHY that matters, reached by asking "why" about five times until you hit the core reason. Write the why ladder out as a compressed chain of three to five links; if the final link merely restates the benefit, ladder again. → DELIVERY: the capability or feature that fulfills the promise, stated as how the promise is delivered, never a bare feature. → PAIN POINT: the granular why this pillar resolves. 7. Attach proof to EACH pillar from {{PROOF_ASSETS}}. Proof must validate that specific outcome. Reject any proof that only says the product is easy to use; that is table stakes, not evidence of the outcome. Flag pillars that lack proof. VALIDATION RULE Cross check the pillars against {{POSITIONING_SUMMARY}}. Strong overlap validates the positioning. If pillars come out radically different, name the misalignment explicitly and flag it for review rather than papering over it. CANVAS ASSEMBLY Label it V1. Write the whole canvas in plain language at a fifth grade reading level; where a sentence needs jargon, translate it into the customer's own words from {{CUSTOMER_VOICE}}. Output these sections: → WHAT: pattern "[Top line value promise]. [Product] is a [category], featuring [context of relevance], [unique differentiator], so that you can [ultimate value]." → WHY: the market shift and urgency. Anchor to a truth everyone recognizes, show what has changed, then position the product as the answer. This is context, not an overclaimed grand narrative. → WHO IT IS FOR: the jobs or use case segments. → HOW: the product workflow (for example discover, learn, do). Note this belongs mid page or nested, not top line. → OUTCOME PILLARS: the two or three pillars with benefit, value (showing its why ladder), delivery, pain point, and attached proof. → JOURNEY LENS: for each pillar, one line each for how it shows up at awareness, consideration, close, and retention. Let DESIRE opportunities lead at awareness, PAIN at consideration, and REQUIREMENT plus proof at close. → CUT LIST: every theme that did not become a pillar, each with its three scores from step 6 and one line on why it was cut, which pillar absorbed it, or that it fell outside {{SCOPE}}. → MAPPING WORKSHEET: a compact appendix table of the opportunities from steps 1 to 4, each with its first person line, its PAIN, REQUIREMENT, or DESIRE tag, and the persona or job it maps to, so the grouping and prioritization can be audited. SELF CHECK before finishing → Facts to verify: every claim reflects value the product delivers TODAY, not the roadmap. Every statistic names its source; drop unsourced numbers and keep the principle. Every proof point maps to a specific pillar. → Failure modes to avoid: stating a capability as the theme (force "why" until you reach the benefit and value); a why ladder whose last link restates the benefit; leading with efficiency or ease as a differentiator; product or feature language standing alone with no relevance wrapper; more than three pillars; language above a fifth grade reading level. Close the output with a VERIFY BEFORE USE list I can work through myself: every statistic with its named source, every proof point with the pillar it validates, any claim that might describe the roadmap rather than shipped value, plus two or three open questions to resolve during validation. ``` ## Prompt versions The standard prompt above works on any model. Use these variants when you want a different tradeoff. ### Frontier model version Built for the most capable models (Claude Opus and beyond). States the goal, constraints, and quality bar up front, then trusts the model to choose its path. ```text You are a senior product marketing strategist who architects messaging, not finished copy. Goal: run a bottom up message relevancy mapping sprint on the inputs, then deliver a versioned messaging canvas (labeled V1) that turns raw capabilities into two or three prioritized outcome pillars mapped across the customer journey. Lead your output with the finished canvas; put the mapping worksheet and cut list appendix after it. Context to work from: {{PRODUCT_AND_CATEGORY}}, {{POSITIONING_SUMMARY}}, {{BUSINESS_GOAL}} (value, volume, or expansion), {{SCOPE}}, {{CAPABILITIES}}, {{CUSTOMER_VOICE}}, {{TARGET_PERSONAS}}, {{PROOF_ASSETS}}. Work only within {{SCOPE}}; park anything wider on the cut list marked OUT OF SCOPE. Method principles, held as non negotiable: → Expand capabilities to the long tail, then translate each into a first person customer opportunity tagged PAIN, REQUIREMENT, or DESIRE, in the customer's own words wherever {{CUSTOMER_VOICE}} supplies them. → Map opportunities to personas. If two personas overlap on roughly 90 percent or more of value, segment by job to be done and keep persona as a secondary lens. → Group into themes with a needs hierarchy. "Easy to use" and "saves time or money" are entry fees, never differentiators; differentiate only at the individual and inspirational levels. → Force the leap to at most three pillars with a 1 to 5 score on three criteria: frequency in {{CUSTOMER_VOICE}}, fit with {{BUSINESS_GOAL}}, and true differentiation. Carry every theme's scores into the cut list with a one line reason. → Give each pillar a benefit (what they DO), a value (a written why ladder of three to five links where the last link does not restate the benefit), a delivery (how the promise is met, never a bare feature), a granular pain point, and outcome specific proof from {{PROOF_ASSETS}}. Flag any pillar without proof. → Cross check pillars against {{POSITIONING_SUMMARY}}; name any misalignment out loud rather than papering over it. → Assemble the canvas in plain fifth grade language with a WHAT, WHY, WHO IT IS FOR, HOW, OUTCOME PILLARS, JOURNEY LENS (DESIRE leads at awareness, PAIN at consideration, REQUIREMENT plus proof at close), CUT LIST, and MAPPING WORKSHEET. Close with a verify before use list naming each statistic's source, each proof to pillar mapping, and two or three open questions. Excellent output satisfies all of this: at most three pillars, each traceable to its scores; every value shows its why ladder; proof is outcome specific, not "easy to use"; the prioritization and grouping are auditable; every claim describes value the product delivers today. Do not invent data, statistics, or quotes; use only what the inputs supply and drop unsourced numbers while keeping the principle. Do not write finished copy or pad with generic advice. Do not claim differentiation on efficiency or ease alone. If a starred input is missing or too thin to ground a decision, ask one focused question and wait rather than guessing. ``` ### Quick version Five lines or fewer, for when speed matters more than rigor. ```text Act as a product marketing strategist. From {{CAPABILITIES}}, {{CUSTOMER_VOICE}}, and {{BUSINESS_GOAL}}, give me a V1 messaging canvas. Pick at most three outcome pillars; for each write a benefit, a why (laddered to the core reason), a delivery, and outcome specific proof from {{PROOF_ASSETS}}. Use the customer's own words at a plain reading level; never claim differentiation on "easy to use" or "saves time" alone. Quality bar: each pillar earns its place by frequency in customer voice, fit with the goal, and real differentiation, with any unproven pillar flagged. Use only the inputs given; invent no data, and ask one question if a needed input is missing. ``` ## How to customize → `{{PRODUCT_AND_CATEGORY}}`: the product and the words customers use to place it, for example "a call recording tool customers think of as a revenue intelligence platform." → `{{POSITIONING_SUMMARY}}`: paste your positioning output. Include target audience, the perception you want versus competitors, unique attributes, and the strategic why. → `{{BUSINESS_GOAL}}`: name it as value (few large best fit deals, sales driven), volume (many self serve subscriptions, product driven), or expansion (deepening existing accounts), since this changes which high value actions the messaging drives. → `{{SCOPE}}`: state exactly what this canvas covers now so the model does not sprawl, for example "the analytics feature, not the whole product." → `{{CAPABILITIES}}`: list everything the product makes possible as customer possibilities, not feature names. Ask your product and success teams for the long tail, not just the headline use case. → `{{CUSTOMER_VOICE}}`: paste literal quotes from interviews, sales calls, review sites, and win loss notes. This is what keeps the output credible and familiar. → `{{TARGET_PERSONAS}}`: name each persona from positioning and what each is trying to accomplish, for example "a team lead who has to coach reports" and "a practitioner who has to ship." → `{{PROOF_ASSETS}}`: paste case studies, testimonials, data points, and named research so the model can attach each to the pillar it validates. ## What good output looks like → Two or three outcome pillars, no more, each with a distinct benefit, value, delivery, and granular pain point, where each value shows its written why ladder and the final link does not restate the benefit. → Every pillar carries outcome specific proof, and any pillar without proof is flagged rather than filled with a generic "easy to use" testimonial. → The pillar ranking is traceable to a 1 to 5 score on three named criteria (frequency in customer voice, fit with the stated business goal, real differentiation), and the cut list shows every cut theme's scores and why it did not make it, so the prioritization leap is inspectable instead of silent. → A mapping worksheet appendix shows each opportunity in first person with its PAIN, REQUIREMENT, or DESIRE tag and its persona or job mapping, so you can audit how the grouping happened. → The pillars visibly overlap the positioning themes, or the model has named the misalignment out loud. → No differentiation claimed on efficiency or ease alone; those appear only framed inside why they matter in this situation. → The canvas is labeled V1, describes only value the product delivers today, and reads at a plain, fifth grade level with no jargon. → The output ends with a verify before use list naming each statistic's source and each proof to pillar mapping, plus two or three open questions for validation. ## Related prompts → [Write a Positioning Statement](../positioning-messaging/write-a-positioning-statement.md): settle category, audience, and differentiators first, since this canvas expresses positioning and cannot substitute for it. → [Run a Message Relevancy Mapping Workshop](../positioning-messaging/run-a-message-relevancy-workshop.md): work the bottom up mapping sprint on its own before painting the result onto this canvas. → [Craft a Strategic Narrative With Stakes and a Villain](../positioning-messaging/craft-a-strategic-narrative.md): build the old way to new way story that anchors the WHY section of the canvas.