Skip to content This library is free, offered as dana. If it helps your work, donate here →
penguin tree ai
← back to libraryDonate here

This is one of 3,622 free prompts in the penguin tree ai library. Sign up once and the whole library opens, with new prompts by email.

open the library →

Audience-tailored communication rewriter

Rewrites a single technical or complex message into audience-specific versions for up to 5 stakeholder personas — technical champion, economic buyer, end user, executive sponsor, and procurement — each recalibrated for…

download .md

Purpose

Take one message written for a single audience — usually too technical or too generic — and produce distinct, ready-to-send versions calibrated for each stakeholder who needs to hear it. Solves the recurring B2B problem where a champion's language loses the CFO, or an executive summary strips out the detail the technical evaluator needs to say yes.

When to Use

Invoke this skill when the user asks to:

  • Rewrite a technical explanation so a C-suite economic buyer will understand and care
  • Translate a product or feature update for both a technical champion and a business sponsor
  • Adapt a renewal, expansion, or QBR message for different roles in the same account
  • Reframe a proposal or ROI case for a procurement or finance audience
  • Turn one engineering-heavy email into versions for the whole buying committee
  • Make a complex message land with a non-technical or skeptical stakeholder

Inputs Required

Before starting, collect:

  • Source message: The original text to rewrite (email, update, summary, or talking points)
  • Target audiences: Which stakeholder personas to produce (e.g., technical champion, economic buyer, end user, executive sponsor, procurement)
  • Core outcome: The one action or belief the user wants each audience to arrive at
  • Account context: Company, product/service, and where the account is (evaluation, expansion, renewal, at-risk)
  • Format: Email, Slack/Teams message, one-pager, or talking points
  • Known objections or sensitivities: Anything a specific stakeholder is skeptical or protective about

If target audiences aren't specified, default to technical champion + economic buyer. If the core outcome is missing, infer it from the source message and state the assumption.

Instructions

Step 1: Extract the Invariant Core

Before rewriting, isolate what must survive translation:

  • The one message: The single sentence every version must communicate
  • The requested action: What the reader should do or decide
  • The load-bearing facts: Data points, dates, or commitments that cannot be dropped or distorted across versions
  • Flag anything in the source that is technically true but likely to confuse or alarm a non-technical reader — these get reframed, not deleted.

Step 2: Rewrite Per Audience Using the Persona Profiles

Produce a distinct version for each requested audience. Use the matching profile below.

Technical Champion (evaluator, admin, engineer)

  • Cares about: implementation effort, control, security, how it works, whether it makes them look good internally
  • Vocabulary: precise and technical — do not oversimplify; respect their expertise
  • Proof they trust: architecture detail, docs, specifics, honest limitations
  • Reframe: keep the depth, but connect the technical work to the outcome they'll be credited for internally

Economic Buyer / C-Suite (CFO, VP, budget owner)

  • Cares about: cost, risk, ROI, time-to-value, impact on their metrics, opportunity cost
  • Vocabulary: business language — no feature names or jargon without immediate translation to outcome
  • Proof they trust: quantified impact, comparison to alternatives, peer/competitor benchmarks, risk mitigation
  • Reframe: lead with the business outcome and the number; put mechanism last or in a footnote. Keep it to under 150 words.

End User (day-to-day operator)

  • Cares about: does this make my job easier or harder, what changes for me, what I need to learn
  • Vocabulary: plain and task-oriented
  • Proof they trust: concrete "before vs. after" of their own workflow
  • Reframe: translate every capability into a task they do and how it changes

Executive Sponsor (the person whose initiative this serves)

  • Cares about: is my bet paying off, is this on track, what do I report upward
  • Vocabulary: strategic and outcome-framed
  • Proof they trust: progress against the stated goal, and a clean narrative they can repeat to their boss
  • Reframe: frame the message as evidence their decision was right and give them a sentence they can forward.

Procurement / Finance / Legal

  • Cares about: terms, cost predictability, compliance, risk, comparability
  • Vocabulary: neutral, precise, contractual
  • Proof they trust: explicit numbers, terms, and defensible justification
  • Reframe: strip persuasion, add specificity — what, how much, under what terms.

For each version:

  1. Open with what that audience cares about most — not with what the source opened with
  2. Include only the load-bearing facts, reframed into their language
  3. End with the requested action stated in a way that's easy for that role to say yes to
  4. Match the requested format and a length appropriate to the role (executives shortest)

Step 3: Add a Routing Note

After the versions, provide a 2–4 line note advising the user on sequencing — who to send which version to first, and any handoff risk (e.g., "don't let the champion forward the technical version to the CFO — send the buyer version directly").

Output Format

  • Structure: A short "Core Message" block, then one labeled section per audience, then a routing note
  • Length: 100–150 words per audience version; executive/procurement versions shorter; 700–1,100 words total for a 3–5 audience request
  • Format: Ready-to-send text in the requested format (email, message, one-pager, or bulleted talking points), clearly separated per audience
  • Sections: Core Message → one section per audience (labeled with the persona) → Routing Note
  • Tone: Each version adopts its audience's tone — technical and precise for the champion, outcome-and-number-led for the buyer, plain for the end user, strategic for the sponsor, neutral-precise for procurement

Quality Checklist

Before delivering output, verify:

  • [ ] The single core message survives intact in every version — no version contradicts another
  • [ ] Every load-bearing fact (numbers, dates, commitments) appears consistently across versions
  • [ ] The economic buyer version leads with outcome/number and stays under 150 words
  • [ ] No feature name or jargon appears in a non-technical version without immediate translation to outcome
  • [ ] Each version ends with the requested action framed for that specific role
  • [ ] A routing note is included advising send order and handoff risk

Notes

  • The most common failure is sending the champion's version to the economic buyer — the detail that builds trust with an evaluator reads as noise to a CFO. Route deliberately.
  • Different framing is not spin: the facts and the ask stay constant; only the emphasis and vocabulary change.
  • When an account is at-risk, lead every version with reassurance and evidence of progress before introducing anything new.

How to use this skill

This file is a Claude Code skill in Anthropic's standard format — markdown with YAML frontmatter at the top.

Installing in Claude Code:

  • ~/.claude/skills/<folder-name>/SKILL.md — auto-loads in every session anywhere on your machine (recommended for skills you'll use across multiple projects)
  • <your-project>/.claude/skills/<folder-name>/SKILL.md — auto-loads only when working in that project (recommended for project-specific skills)

Restart Claude Code or open a new session to register.

Using in Claude.ai, ChatGPT, Gemini, or other AI tools:

  1. Drag this file into a new chat, or copy and paste its contents
  2. Send your task or request as your next message — the AI will apply the skill where it fits

For Claude Code skill details: https://docs.anthropic.com/en/docs/claude-code/skills