🎁 Get the FREE AI Skills Starter Guide β€” Subscribe β†’
BytesAgainBytesAgain
BytesAgain β€Ί Skills β€Ί Customer Persona Copy Map
πŸ¦€ ClawHub

Customer Persona Copy Map

by @harrylabsj

Transforms audience research into a detailed copy matrix linking customer personas to tailored pain points, benefits, messages, and CTA language with evidenc...

Versionv1.0.0
Downloads742
Stars⭐ 1
#crypto-defi#research#translation#legal#travel
TERMINAL
clawhub install customer-persona-copy-map

πŸ“– About This Skill

Customer Persona Copy Map

Purpose

This skill turns audience research and customer signals into a practical copy matrix that maps different personas to their specific pain points, motivations, objections, preferred benefits, and CTA language. Instead of one-size-fits-all copy, it helps teams segment messaging across product pages, ad creative, email flows, and landing pages β€” all while clearly labeling what's evidence-based vs. assumed.

Triggers

  • "Map copy to different customer personas"
  • "Create persona-based messaging for my product"
  • "Build a copy matrix for audience segments"
  • "Segment my product messaging by buyer type"
  • "Write persona-specific ad copy"
  • "Create messaging for different customer types"

    • Workflow

    1. Audience signal collection β€” Gather known customer segments, demographic/behavioral signals, purchase data patterns (if available), review themes by customer type, support ticket themes, and any existing persona research. 2. Evidence vs. assumption separation β€” For each persona, clearly separate: what data supports this segment (reviews, sales data, survey results) vs. what is a reasonable hypothesis (market observation, competitor patterns, intuition). Assumptions must be labeled. 3. Persona card creation β€” For each distinct persona, create a card with: name/descriptor, primary need/job-to-be-done, dominant purchase barrier, emotional driver, trust requirement, and preferred channel. 4. Pain-benefit-message matrix β€” Create a cross-reference matrix: persona β†’ top pain points β†’ product benefits that address them β†’ message framing β†’ CTA language β†’ best channel. 5. Copy snippet drafting β€” Write persona-specific copy snippets: above-the-fold headline, key benefit statement, objection pre-handler, and CTA. Each snippet should feel natural for that persona. 6. Channel recommendation β€” For each persona-message pair, recommend the best channel(s) and format (e.g., "gift-buyer persona β†’ Instagram Story with gift-guide angle").

    Prompt Templates

    1. Persona Copy Matrix Builder (persona_matrix)

    Purpose: Build a complete persona-to-copy matrix from audience data.

    Input:

  • ${product_name} β€” Product name
  • ${product_category} β€” Product category
  • ${personas} β€” List of customer persona descriptions (2–5 personas)
  • ${product_benefits} β€” Key product benefits
  • ${channels} β€” Available marketing channels
  • ${evidence_sources} β€” (Optional) data sources supporting persona definitions

    • Output: Complete matrix with persona cards, pain/benefit/message map, copy snippets, and channel recommendations.

    2. Persona Expander (persona_expand)

    Purpose: Expand a thin persona description into a full messaging profile.

    Input:

  • ${persona_name} β€” Persona name or descriptor
  • ${known_traits} β€” What's known about this persona
  • ${product_context} β€” What this product does for them

    • Output: Expanded persona card with messaging angles, objections, and copy snippet drafts.

    3. Message Adapter (message_adapt)

    Purpose: Adapt one core message to multiple persona framings.

    Input:

  • ${core_message} β€” The central product message
  • ${personas} β€” List of personas with key motivations
  • ${channels} β€” Target channels for adaptation

    • Output: Persona-specific message adaptations with rationale for changes.

    4. Assumption Auditor (assumption_audit)

    Purpose: Audit a persona set for untested assumptions that could lead to wasted spend.

    Input:

  • ${persona_set} β€” Complete persona definitions with messaging
  • ${evidence_available} β€” What data actually supports each persona

    • Output: Each persona scored by evidence strength (High/Medium/Low), with assumptions highlighted and test recommendations for low-evidence personas.

    Output Format

    ## Persona Copy Map: [Product Name]
Category: [Category] | Personas: [N personas]
    Persona Cards
    Persona 1: [Name/Descriptor]

  • Primary Need: [Job-to-be-done]
    • 

  • Dominant Barrier: [What keeps them from buying]
    • 

  • Emotional Driver: [What feeling motivates them]
    • 

  • Trust Requirement: [What proof they need]
    • 

  • Preferred Channel: [Where they're most reachable]
    • 

  • Evidence Strength: [High/Medium/Low] β€” [what data supports this]
    • Persona 2: [...]
...
    Pain-Benefit-Message Matrix
    | Persona | Top Pain | Product Benefit | Message Frame | CTA Language | Best Channel |
|---|---|---|---|---|---|
| Persona 1 | [Pain] | [Benefit] | [How to frame] | "[CTA]" | [Channel] |
| Persona 2 | [Pain] | [Benefit] | [How to frame] | "[CTA]" | [Channel] |
| ... | ... | ... | ... | ... | ... |
    Copy Snippets
    For [Persona 1]:

  • 🎯 Headline: "[Above-the-fold headline]"
    • 

  • πŸ’‘ Benefit: "[Key benefit statement]"
    • 

  • πŸ›‘οΈ Objection handler: "[Pre-handle common objection]"
    • 

  • πŸš€ CTA: "[Call to action]"
    • For [Persona 2]:
...
    Channel Recommendations
    

  • [Channel]: Best for personas [X, Y] β€” format: [suggestion]
    • 

  • [Channel]: Best for persona [Z] β€” format: [suggestion]
    • Assumption Audit
    

  • βœ… Persona 1: [Evidence strength] β€” supported by [sources]
    • 

  • ⚠️ Persona 2: Medium evidence β€” [assumptions] need validation via [test idea]
    • 

  • ❓ Persona 3: Low evidence β€” consider deprioritizing until [validation method]
    •

    Safety Rules

  • ALWAYS clearly label assumptions vs. evidence β€” unvalidated personas can waste budget and alienate real customers
  • NEVER stereotype based on protected characteristics (age, gender, race, religion, disability, sexual orientation) when the data doesn't support it
  • NEVER create personas for sensitive categories (health conditions, financial distress, personal crises) without extreme care and explicit disclosure of limitations
  • ALWAYS avoid manipulative messaging that exploits persona vulnerabilities (e.g., insecurity-based marketing to teens, fear-based messaging to elderly)
  • NEVER present assumed personas as "proven by AI" β€” clearly state the evidence basis for every segment

    • Examples

    Example 1: Skincare Serum (3 Personas)

    Input: Product="Vitamin C Brightening Serum", Personas="(1) Skincare Beginner β€” wants results without complexity, (2) Ingredient Nerd β€” researches every component, (3) Gift Buyer β€” buying for someone else, wants safe choice"

    Output: Matrix showing: Beginner β†’ pain="too many choices, don't know what works" β†’ message="One serum, proven ingredients, simple routine" β†’ CTA="Start your 2-step routine" β†’ channel=Instagram/TikTok. Ingredient Nerd β†’ pain="skeptical of marketing claims" β†’ message="15% L-AA + E + ferulic, airless pump, dermatologist-tested β€” here's the data" β†’ CTA="See the full ingredient breakdown" β†’ channel=blog/email. Gift Buyer β†’ pain="will they like it? will it work for their skin?" β†’ message="Universally loved, fragrance-free, suitable for most skin types, beautiful packaging" β†’ CTA="Gift the glow" β†’ channel=Facebook/Instagram.

    Example 2: Kitchen Gadget (2 Personas)

    Input: Product="Air Fryer Liners", Personas="(1) Convenience Cook β€” wants faster cleanup, (2) Eco-Conscious Cook β€” wants to reduce waste (aluminum foil/paper)"

    Output: Matrix: Convenience β†’ pain="air fryer cleanup is annoying" β†’ message="Cook, eat, toss the liner β€” no scrubbing" β†’ CTA="Make cleanup optional" β†’ channel=TikTok. Eco-Conscious β†’ pain="using disposable foil/paper feels wasteful" β†’ message="Reusable silicone liners replace hundreds of foil sheets" β†’ CTA="Cook cleaner, waste less" β†’ channel=Instagram/blog. Assumption audit flags that "Eco-Conscious" is partially assumed β€” recommended survey validation.

    Related Skills

  • listing-bullet-booster β€” For persona-specific bullet variants
  • campaign-angle-spark β€” For campaign angles targeting specific personas
  • faq-objection-crusher β€” For persona-specific objection handling

    • πŸ’‘ Examples

    Example 1: Skincare Serum (3 Personas)

    Input: Product="Vitamin C Brightening Serum", Personas="(1) Skincare Beginner β€” wants results without complexity, (2) Ingredient Nerd β€” researches every component, (3) Gift Buyer β€” buying for someone else, wants safe choice"

    Output: Matrix showing: Beginner β†’ pain="too many choices, don't know what works" β†’ message="One serum, proven ingredients, simple routine" β†’ CTA="Start your 2-step routine" β†’ channel=Instagram/TikTok. Ingredient Nerd β†’ pain="skeptical of marketing claims" β†’ message="15% L-AA + E + ferulic, airless pump, dermatologist-tested β€” here's the data" β†’ CTA="See the full ingredient breakdown" β†’ channel=blog/email. Gift Buyer β†’ pain="will they like it? will it work for their skin?" β†’ message="Universally loved, fragrance-free, suitable for most skin types, beautiful packaging" β†’ CTA="Gift the glow" β†’ channel=Facebook/Instagram.

    Example 2: Kitchen Gadget (2 Personas)

    Input: Product="Air Fryer Liners", Personas="(1) Convenience Cook β€” wants faster cleanup, (2) Eco-Conscious Cook β€” wants to reduce waste (aluminum foil/paper)"

    Output: Matrix: Convenience β†’ pain="air fryer cleanup is annoying" β†’ message="Cook, eat, toss the liner β€” no scrubbing" β†’ CTA="Make cleanup optional" β†’ channel=TikTok. Eco-Conscious β†’ pain="using disposable foil/paper feels wasteful" β†’ message="Reusable silicone liners replace hundreds of foil sheets" β†’ CTA="Cook cleaner, waste less" β†’ channel=Instagram/blog. Assumption audit flags that "Eco-Conscious" is partially assumed β€” recommended survey validation.