Translate your feature list into a benefit table sellers can quote
Runs every feature through the full translation chain — feature, advantage, buyer benefit, cost of lacking it, and a quotable sentence per persona — then routes the three strongest rows to specific assets and honestly flags parity features not worth leading with. It turns the raw feature list into language sellers can actually say out loud.
You are a messaging translator who fixes the most common disease in B2B copy: feature-speak. Engineers ship 'real-time bidirectional CRM sync' and somehow that exact phrase ends up in cold emails to CFOs. Your craft is the translation chain: feature (what it is) to advantage (what it does) to benefit (what the buyer gets) to stake (what it costs them to lack it). Most copy stops one or two links short.
I'll give you a feature list. Build a translation table where each feature gets:
1. Feature — the plain technical description, one line.
2. So what — the advantage, mechanically: what it does that the old way doesn't.
3. Which means — the benefit in the buyer's world: time, money, risk, status. Quantified wherever my input allows.
4. Without it — the stake: what the buyer eats today because they lack this. This column powers cold email and discovery questions.
5. Say it like this — one quotable sentence a seller can use verbatim, written for a specific persona, no jargon.
After the table: pick the three strongest rows and mark which asset each belongs in (cold email opener, demo talk track, pricing page bullet, one-pager). Then flag any feature that resists translation — parity features with no meaningful benefit — and say so honestly rather than inventing one; knowing which features NOT to lead with is half the value.
Rules: no benefit inflation ('saves time' must become how much time for whom), no translating every feature into the same generic benefit, and persona matters — the same feature translates differently for an ops manager and a CFO, so I'll tell you who we sell to.
Before you write anything, interview me. Ask me these questions ONE AT A TIME, waiting for my answer each time:
1. Paste your feature list — raw from the website, docs, or a product deck.
2. Who are the two personas that matter most in your deals?
3. What do customers actually say these features let them do? Any quotes, numbers, or before/after stories help.
4. Which features do competitors also have, as far as you know?
Once you have my answers, build the table for both personas where translations differ.How to use it
- 1
Copy the prompt into Claude, ChatGPT, or any LLM.
- 2
Paste the feature list raw — website, changelog, product deck; no pre-editing needed.
- 3
Feed question 3 with customer quotes and numbers; the 'which means' column is only as sharp as that input.
- 4
Ship the three routed rows into their assets first — cold email, demo track, pricing bullet.
- 5
Drop the table into your enablement doc so new reps inherit the translations instead of re-deriving them badly.
Best practices
The 'without it' column is the sleeper asset — it converts directly into discovery questions and cold email problem statements.
Respect the parity flags: leading with a feature every competitor has positions you as interchangeable no matter how nicely it's phrased.
Run both personas when they differ in altitude — the ops manager buys the mechanism, the CFO buys the stake.
Refresh the table each major release, or pipe it into your n8n or Clay enrichment flow so messaging assets update from one source.
Example: what this looks like in practice
A marketer at an expense-management startup pastes eleven features including 'real-time receipt OCR' and 'multi-entity ledger support'. Personas: controllers and CFOs. From question 3 she adds a customer quote about closing books four days faster. The table translates OCR for controllers as 'no more receipt-chasing Slack messages — employees photograph it and it's coded' with the stake 'your team spends roughly two days a month transcribing paper'; for the CFO the same feature rolls up into the four-day close. Two features get flagged as parity — every competitor has them — and are pulled from the homepage hero. The 'without it' column becomes her SDR team's new discovery question bank in Apollo sequences.
Best fit
This prompt is one gear in a bigger machine. We orchestrate 20+ tools into outbound systems our clients own — and guarantee the results.
Apply for a Pilot Spot → →Frequently asked questions
A feature is what the product has ('real-time CRM sync'); a benefit is what the buyer gets because of it ('your pipeline report is never a day stale'). The full chain runs feature, advantage, benefit, stake — and most B2B copy stops at the feature or a vague advantage. The stake, what it costs the buyer to lack it, is where cold email and discovery language comes from.
More sales copywriting & assets prompts
Generate an outcome-first value proposition buyers can repeat
Builds a complete value proposition system — primary line, three angle variations, a disqualifier, and channel-ready versions — instead of one throwaway tagline. The interview forces buyer, outcome, mechanism, and proof out of your head first, so the output is positioning you can defend, not word salad you'll rewrite next quarter.
Write a case study from a raw customer interview transcript
Turns a raw, rambling customer interview into a publish-ready case study — result-led headline, snapshot metrics box, four-part story, and verbatim pull quotes — while refusing to invent quotes or numbers. If the transcript is missing a strong metric, it tells you exactly what to ask the customer instead of papering over the gap.
Align your cold email and landing page so the click doesn't break the story
Audits your cold email and landing page side by side, finds where the story breaks between click and page, and fixes the cheaper side with minimum edits. The 'message spine' it outputs becomes a five-line contract both assets obey, so the next person who edits either one doesn't silently reintroduce the mismatch.