返回提示词目录第 1515 页

产品功能转化客户利益文案

围绕指定客群拆解功能带来的实际价值,筛选核心卖点并列出文案所需佐证。

完整提示词

<context>
You help tradespeople, engineers and product makers explain what they sell in the customer's terms. Experts describe what a thing is; buyers want to know what it does for them. The fix is a so-what ladder: feature (what it is), advantage (what it does), benefit (what changes for this customer), and sometimes the deeper outcome (money, time, safety, pride, peace of mind). Two failure modes to avoid: stopping at the advantage ("faster processing") and climbing so high that every line becomes the same vague promise ("peace of mind"). The best line names the benefit and keeps the feature as proof, because benefits without the feature behind them sound like fluff.

Customer: {{customer}}
</context>

<task>
<features>
{{features}}
</features>

1. If you cannot tell what is being sold or who buys it, ask and stop.
2. For each feature, climb the ladder: feature, advantage, benefit for this customer, and the deeper outcome only when it is genuinely different. Stop at the rung where this customer would nod.
3. Translate every piece of jargon into words the customer uses; keep a term only when customers search for it or a regulator requires it, and then explain it in brackets.
4. Rate each feature for this customer: lead (a main reason to buy), support (proof or reassurance), table stakes (expected; mention briefly) or drop (no customer cares, or it belongs in the spec sheet).
5. Write customer-facing lines for the lead and support features: a short headline-style line and a one-sentence version that pairs benefit and feature ("Quieter rooms from the day it's fitted: triple glazing cuts road noise").
6. List what proof each benefit claim needs (test result, standard, warranty, customer quote, number) and whether the input supplies it.
</task>

<constraints>
- Never invent numbers, test results, savings or certifications. If a benefit needs a number that is not given, write the line without it or add [PROOF NEEDED].
- Benefits must follow from the feature; no stretching ("SSO" does not make a team "more innovative").
- Plain, concrete words. No "cutting-edge", "seamless", "world-class" or "peace of mind" unless tied to a specific worry.
- Different customers get different benefits from the same feature; write for the named customer only.
{{> output/uncertainty}}
</constraints>

<output_format>
## So-what ladder
Table: Feature | Advantage | Benefit for this customer | Deeper outcome (or -) | Rating.

## Lines to use
For each lead and support feature: a short line and a one-sentence benefit-plus-feature line.

## Features to drop or move
Bullets: feature and where it belongs instead (spec sheet, FAQ, nowhere), with the reason.

## Proof needed
Table: Claim | Proof needed | Supplied? (yes or no).
</output_format>

可替换内容

  • {{customer}}
  • {{features}}
  • {{> output/uncertainty}}
  • [PROOF NEEDED]

分类与标签

商业营销、产品卖点、客户利益、销售文案、宣传佐证

前往 AI 图片创作