Messaging Angle from Reviews
Turn the complaints in a competitor's reviews into a sharp messaging angle — the specific pain their customers describe, framed as your strength.
Product Marketing - Messaging
Their customers' complaints, framed as your strength — in the buyer's words
5
Complaint themes
Buyer voice -> angle
Top complaint: 'bill exploded at scale.'
Our flat pricing answers it directly.
Top complaint: 'bill exploded at scale.'
Our flat pricing answers it directly.
| Their complaint | Our angle |
|---|---|
| Bill exploded at scale | Flat, predictable pricing |
| Weeks to set up | Live in a day |
| Support slow | Not our counter |
Why it lands
'Transparent pricing' is a feature. 'Your bill won't explode at scale the way reviewers say theirs did' is a message — because it names the exact pain the competitor's own customers describe.
Overview
Mine a specific competitor's TrustRadius reviews for the recurring complaints, then craft messaging angles that frame those complaints as your differentiation — using the customers' own words — so the message lands because it names a pain the market already feels.
Use cases
Messaging the market already feels
An angle built on a complaint that recurs in competitor reviews resonates instantly — the buyer has felt that pain and recognizes it the moment you name it.
Honest angles that hold up
Mapping only to genuine strengths — and listing the complaints we can't counter — keeps the messaging credible when a buyer pushes back.
View workflow prompt
# Messaging Angle from Reviews
## Parameters
- `{{competitor}}` *(required)* — The competitor whose reviews to mine. Example: `Datadog`
- `{{our_strengths}}` *(required)* — Our genuine strengths to frame against the complaints. Example: `transparent flat pricing, fast setup`
## Purpose
Mine {{competitor}} reviews for recurring complaints and craft messaging angles that frame {{our_strengths}} against those pains in the customers' own words — so the message resonates because it names a frustration the market already voices.
## Process
1. **Mine complaints** — `get_product_reviews` for {{competitor}}; cluster the recurring complaints (price surprises, complexity, support).
2. **Match to our strengths** — map each complaint to a genuine strength in {{our_strengths}}; discard complaints we don't actually counter (honesty preserves credibility).
3. **Draft angles** — for each matched complaint, write a messaging angle that uses the buyer's language and frames our strength as the answer.
4. **Pressure-test** — flag any angle that overclaims relative to our actual capability.
5. **Prioritize** — rank by complaint frequency × strength of our counter.
## Output Format
Markdown with:
- `# Messaging Angles from {{competitor}} Reviews`
- `## Complaint Themes` (cited, with frequency)
- `## Matched Angles` (table: complaint | our strength | angle in buyer voice)
- `## Do-Not-Claim` (complaints we can't honestly counter)
- `## Citations`
## Quality Checklist
- Complaints cite `get_product_reviews`
- Each angle maps to a genuine strength, not an aspirational one
- Angles use buyer language from the reviews
- Complaints we can't counter are listed in Do-Not-Claim, not spun