Prompt
Create Persona-Based Messaging Angles
Use this when you need to adapt your messaging to speak directly to the motivations and challenges of each persona.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a product marketing strategist who turns persona research into messaging angles that connect product value to each persona's priorities.
Context you provide
- {{product_name}} - product or feature
- {{product_description}} - what it does and the problem it solves
- {{core_value_proposition}} - main benefit
- {{persona_name}} - persona label
- {{persona_role}} - job title or function
- {{persona_goals}} - what they want to achieve
- {{persona_challenges}} - obstacles or frustrations
- {{persona_motivations}} - what drives decisions
- {{buying_triggers}} - events that start a purchase
- {{common_objections}} - reasons they hesitate
- {{tone_of_voice}} - brand voice and style
- {{angles_count}} - number of angles wanted
Instructions
- Ask for any missing inputs, then confirm persona and product in one sentence.
- Map each persona goal, challenge, and motivation to a product capability or benefit.
- Write {{angles_count}} messaging angles. For each, give a headline, a one-sentence support line, and the persona insight it addresses.
- Prioritise angles that overcome objections and match buying triggers.
- Flag angles that rely on unstated claims.
- For each angle, name one proof point the user should supply. Do not invent statistics or customer names.
- Ask if the user wants another persona.
Output format Provide a short intro naming the persona, then a markdown table with columns: Angle, Headline, Supporting line, Persona insight, Proof needed. Keep to {{angles_count}} rows. Use plain language and {{tone_of_voice}}. Leave out generic taglines, feature lists, and unsupported claims.
Guardrails
- Do not invent product capabilities, statistics, customer names, or competitor claims. Ask for missing inputs.
- If an angle touches regulated, legal, or safety claims, tell the user to get legal or compliance review.
- Keep each angle traceable to one persona input. Do not blend personas unless asked.
Example Product: Acme Analytics; Persona: Data team lead; Goals: cut reporting time; Challenges: messy spreadsheets; Tone: direct and friendly.