customer-benefit-communication

name	customer-benefit-communication
description	Identify and articulate customer benefit in all forms of customer communication for IT service providers, managed service providers, SaaS companies, and any business that communicates technical work to non-technical customers. Use this skill when writing, reviewing, or improving any customer-facing text: emails, status updates, proposals, support replies, reports, newsletters, or presentations. The skill analyzes communication for missing benefit statements, then rewrites it so the customer clearly understands the value they receive — in terms they care about, not technical jargon. Activate even when the user doesn't explicitly mention "benefit" — any customer communication can be improved.
license	MIT
compatibility	Works in any agent that supports Agent Skills. No external tools required.
metadata	{"author":"Christian Pedersen (@dkmaker)","version":"1.0","language":"multilingual"}

Customer Benefit Communication

Transform technical, feature-focused customer communication into benefit-driven messages. Customers are typically non-technical decision-makers — they care about what your product or service does for them, not how it works.

Every piece of communication must answer: "What does this mean for me and my business?"

Workflow

1. Detect — Identify channel, recipient role, and lifecycle stage. Read assets/step-1-detect.md for classification tables.

2. Analyze — Scan for benefit gaps (feature-only statements, jargon, missing outcomes). Read assets/step-2-analyze.md for red/green flag patterns.

3. Research — If the communication mentions specific products or services, read assets/product-knowledge.md for product knowledge and benefit framing starters. Then use web search to verify current features, pricing, and capabilities before making specific product claims. Product info changes frequently — never rely solely on cached knowledge.

4. Rewrite — Apply the Benefit Bridge Formula and tone adaptation. Read assets/step-3-rewrite.md for the formula, examples, and tone guide.

Deliver output as: A) Brief gap analysis → B) Rewritten communication ready to send.

Match the input language. Use "you/your" (or local equivalent) — make the customer the subject.

Company Context

See assets/company-profile.md for the company's profile, differentiators, products, and customer proof points. Use as background context when writing — never recite it directly to the customer.

Gotchas

• Never invent metrics. Only use numbers the company has verified and approved.
• Don't oversell. Honest, understated benefit beats inflated claims every time.
• "Benefit" ≠ only money. Peace of mind and time saved often matter more than cost.
• Customers are not technical. Translate everything into plain language.
• Match the scope. A support reply needs one benefit sentence, not three paragraphs.
• Respect the original intent. Enhance with benefit framing — don't change the message.
• Match the input language. If the original is Danish, reply in Danish. If English, English.