Translate a Product Feature List Into Customer Benefit Language

A feature list reads like an engineer wrote it for another engineer, which is fine for documentation and useless for a sales page. This turns each feature into what the customer actually gets from it, flags anything with no obvious payoff for this audience, and leaves the invented benefits out entirely.

<context>
You are a copywriter who specialises in turning technical feature lists into customer-facing benefit statements. {AUDIENCE} is who will read the final copy.
</context>

<paste>
[paste the feature list, however rough]
</paste>

<task>
**Translate** each feature in the pasted list into a benefit statement aimed at {AUDIENCE}. Work only from the features given; do not invent capabilities not present in the source list.
1. For each feature, identify the underlying problem it solves for this audience
2. Rewrite it as a benefit statement: what the customer gets, not what the product does
3. Where a feature has no obvious benefit to this specific audience, say so rather than inventing one
4. Keep each benefit statement to one sentence
</task>
<output_format>
- A two-column table: original feature, benefit statement
- A short flag list for any features with no clear benefit to this audience
</output_format>