with the skill
# Testimonial edit
**Diagnosis:** This is someone else's quote, so I can't add detail to it. Anything I invent (a time saved, a result, a "before" story) would be a fabricated endorsement. The quote is generic: every sentence could be about any software, and "great," "really helped," and "works well" give a prospect nothing to believe. The fix is better raw material from John, not better wording from us.
## What's weak
| Line | Problem |
|---|---|
| "CloudSync is great!" | Empty praise. Doesn't say what's great. |
| "It really helped our company." | Helped how? Which problem, what changed? |
| "The team was very responsive" | The one semi-concrete claim, but there's no example or timeframe. |
| "The product works well." | Says nothing about the work it does. |
| "We would recommend it to anyone looking for a solution." | Filler. "A solution" to what? |
| "John S., CEO" | No company, no full name, no photo. Readers discount anonymous-looking proof. |
## Option 1: Safe trim (needs John's approval)
If you can't get more from him, cut to the strongest line and don't change his words:
> "The team was very responsive and the product works well."
Show the rest (26 more lines)
> **John S., CEO, [NEED: company name]**
This is shorter and more credible than the original, but still modest proof.
## Option 2: Get a better quote (recommended)
Send John 3 questions and ask for a sentence or two on each:
1. What were you doing before CloudSync, and what wasn't working?
2. What's different now? Any number you can share (hours saved, errors cut, cost, team size)?
3. Can you give an example of when our team responded quickly? What was the issue and how long did it take?
Then build the quote from his answers. Here's the structure with placeholders:
> "[NEED: before state, e.g. what broke or took too long]. Since switching to CloudSync, [NEED: specific result with a number or timeframe]. When [NEED: specific issue], the team [NEED: what they did] within [NEED: time]."
> **[NEED: full name], CEO, [NEED: company]** + photo and logo
Get his sign-off on the final wording before publishing.
## Presentation fixes
- **Add a pull-quote headline** from his best specific line, set larger above the full quote.
- **Complete the attribution:** full name, company, logo, and a headshot if he'll allow it. Link to a case study if one exists.
- **Place it near a CTA** so it answers hesitation at the moment of decision.
If you send me John's answers to those three questions, I'll edit them into a finished testimonial.