I scraped 200 reviews to write one paragraph
Hey,
A few weeks ago I spent an afternoon collecting reviews for a client.
Not their reviews. Their competitors’. Filtered to 1-3 stars. Across 8 apps. About 200 reviews, pulled and sorted by app and rating.
When you read 200 of them in one sitting, you stop seeing individual complaints. You start seeing categories of failure. The same promises broken in the same ways, across every major player in the category. Different words, same complaint.
That was the brief.
Every app in a category is making the same implicit promises to merchants. Promises about reliability, simplicity, support, trust. Some apps deliver on most of them. But there are always one or two promises the entire category keeps breaking, and almost nobody has claimed that gap.
You don’t find that by studying your own app.
You find it by reading what merchants say when they’ve stopped being polite.
The 1-star reviews are where that happens. They describe exactly what merchants needed, what they were told they’d get, and where it fell apart. Read enough of them together, and you can see the opening.
For this client, the analysis surfaced a specific failure pattern that showed up across six of the eight apps. Not mentioned anywhere in their competitors’ listings. Not addressed in any of the marketing. Just sitting there in the reviews, repeated in different words, by merchants who’d moved on.
That became one paragraph in their positioning. The most important one.
The data collection is one part of the work. Knowing what you’re looking for, which complaints signal a real positioning gap versus which are just noise, is the harder part. I’ve done this across enough categories that the signal surfaces fast. And translating a pattern of frustration into a claim that’s accurate and actually owns something takes a different kind of work than copywriting.
If you want this done for your app (the data sweep, the pattern analysis, and the positioning brief that comes out of it), that’s what a sprint covers.
Ohad
