Competitor review analysis can help you write a better email offer without borrowing a competitor’s words. Read public feedback for unanswered questions, check whether those questions matter to your own customers, then explain what your organisation can genuinely do about them.
This is particularly useful before a new service has collected much feedback of its own. It can also help an established team see familiar offers from a different angle. A question your colleagues stopped asking years ago may still be the very thing making a customer hesitate.
Start with the question behind the campaign
Choose one decision you want the research to inform. Perhaps you need to explain what membership includes, what happens after someone requests a quotation, or which installation options are available. A focused question makes it easier to recognise useful evidence.
Then choose genuinely comparable offers. A premium managed service and a basic self-service product may attract very different expectations. Reviews from another country, an old product version or a single branch can be informative, but keep that context attached.
Record where you looked and the date range you used. There is no magic review count that makes the exercise representative. Aim for enough relevant material to see recurring questions and conflicting experiences, not enough screenshots to fill a presentation.
Keep the task proportionate. You are looking for a clearer way to help subscribers decide, not compiling a dossier on everything another business has ever done badly.
Read the middle ratings, but not only the middle
Three-star reviews can be useful because they may describe both what worked and what disappointed. That combination can reveal a specific expectation: the product was suitable, but the buyer could not tell whether setup help was included.
Middle ratings are not a truth filter. Read positive and negative feedback too. Positive reviews may identify reassurance worth explaining; negative ones may describe a genuine failure, an unusual incident or an expectation the offer never intended to meet.
Reviews are self-selected feedback, not a representative survey of everyone who bought. Some may also be misleading or fake. You cannot reliably settle authenticity from grammar, tone or a star rating alone.
Look for patterns across relevant dates and sources, and note evidence that challenges your first impression. If recent reviews praise a support process that older reviews criticised, the organisation may have changed it. Research should be allowed to spoil a convenient theory.
Turn a complaint into a question you can investigate
A review tells you about a reported experience. Your next step is to translate it into a possible customer need without pretending you know more than you do.
For example, reports of difficulty getting help before purchase might suggest that buyers need a clearer route to technical advice. They do not prove that every buyer wants a telephone call, or that your own team should promise one immediately.
Use a short research record for each promising theme:
- Source and context: review URL, date, relevant product or service, and location where it matters.
- Observation: a neutral summary of what the reviewer reported.
- Possible question: what a prospective customer might need answered before deciding.
- Counter-evidence: other experiences or offer details that limit the conclusion.
- Next check: who can establish whether the question matters to your audience and whether you can answer it.
Keep observation and interpretation on separate lines. “Several reviews in this sample mention unclear setup arrangements” is a bounded observation. “Customers hate setting things up themselves” is a much bigger claim, and may be wrong.
You can count themes within the material you reviewed, but those proportions describe your sample, not the whole market. Use the record to choose questions worth checking, not to produce impressive-looking percentages for an email.
Keep observation and interpretation on separate lines.
Check your own customers and the people delivering the service
Bring the strongest question back inside the organisation. Search your support enquiries, sales objections, cancellation reasons and existing customer feedback for the same uncertainty. Ask frontline colleagues what people actually struggle to understand.
If you are launching something new, you may have little direct evidence. That is a reason to ask prospective customers relevant questions, not to promote a competitor’s reviews into proof of demand. Keep the uncertainty visible.
Next, find the person responsible for delivery. Can your team answer the question accurately? Are there exceptions, eligibility conditions or capacity limits? If an installation service is only available in selected regions, a national campaign needs to respect that distinction.
For multi-location teams, check the relevant locations rather than assuming a head-office description reflects every branch. A B2B account manager may offer support that is not part of a self-service plan. The email must describe the offer the recipient can actually access.
This is where the research becomes valuable: a clearer explanation, an operational improvement, or a decision not to make a promise yet. Our guidance on email promises you can keep covers that final check in more detail.
Make one useful change to the email
Here is a hypothetical example. A supplier preparing an equipment promotion finds public reviews suggesting uncertainty about compatibility. Its own sales team recognises the question, and confirms an established process for checking model details before purchase.
The campaign could replace a vague reassurance such as “Expert help available” with a specific next step: “Not sure which model fits? Send us your equipment details using the compatibility form before you order.” Use that wording only if the process exists and the team can deliver it.
The useful change is not an attack on another supplier. It is an answer that helps your own subscriber act with more confidence. Check that the linked form asks for the information the team actually needs, and that the response process matches the email.
A membership organisation might instead clarify whether a benefit is included in a particular membership level. The same method applies, but the answer must come from its own offer, not another organisation’s review page.
Write the explanation in your own voice. Do not lift a review into the campaign as a testimonial or present allegations about another business as established fact. Reading feedback for internal insight is different from republishing it.
Test the answer, then close the loop
Test a useful clarification with your own relevant, permissioned audience. Keep the offer and other major elements comparable so you can learn something about the change. Our email testing information is a useful next stop when planning the comparison.
Choose a result that fits the question. That might be completed, suitable enquiries alongside fewer questions about eligibility, or completed purchases without an increase in avoidable returns. More clicks alone do not show that people understood the offer.
Do not test a knowingly misleading version as your comparison. Correct necessary information for everyone; reserve experimentation for different clear ways of presenting it. If the result is too small or inconsistent to interpret, retain that uncertainty.
Return the findings to the people who checked the idea. An email may reduce confusion, reveal a different question or expose a service problem that copy cannot solve. Update the research record so another team does not repeat the same exercise without learning from it.
Leave competitor reviewers out of your prospecting list. Their public feedback is a clue to investigate, not an invitation to collect contact details or approach them with an offer.
For your next campaign, choose one question a subscriber might reasonably ask before acting. Find the evidence, name the person who can verify the answer, and make that answer easy to find. That is a practical use of competitor research: learning something useful, then doing your own work better.
The WizEmail Team

