Read your reviews like a detective, not a fan

Most founders read reviews the way a fan reads them — scanning for praise, wincing at complaints, and moving on. Detectives read differently. They're not looking for a verdict. They're looking for patterns, words, and the moment something went wrong.

Reviews — yours, and especially your competitors' — are one of the richest, cheapest research datasets available to you. People write them in their own words, unprompted, often at the exact moment of frustration or delight. That's gold.

Start with the one-star and two-star reviews

Five-star reviews tell you what's working. One- and two-star reviews tell you where the gap is — the thing a competitor promised and didn't deliver, or the workflow that quietly breaks at scale. That gap is often exactly where your positioning should live.

Read at least 30 negative reviews of your top two or three competitors. Don't summarize yet — just collect. You're looking for:

• Repeated phrases or complaints (if three people say the same thing, it's a pattern, not an outlier)
• The specific moment in the workflow where things fall apart
• The words people use to describe the problem — these are often better headline copy than anything your team would write

Build a simple pain ledger

Turn your notes into a ledger: one row per distinct pain, with a column for how many times you saw it and a column for a representative quote. Rank by frequency. The top three or four rows are your starting list of pains to address in your messaging — and likely your product roadmap too.

"I switched because the old tool was great until we hit 50 users, then everything slowed to a crawl and support went silent."

— a real one-star review, lightly anonymized

This single sentence tells you about a churn trigger (scale), a broken promise (support), and a buying trigger (team growth past 50). That's three positioning angles from one quote.

Don't stop at your category

Some of the best signal comes from adjacent categories — tools your buyers use around the problem you solve. If you're building for engineering teams, read reviews of project management tools, not just competitors in your exact space. The complaints about "too much process" or "nobody reads the docs" often point straight at the job your product needs to do.

Where to start this week

Pick your top competitor, pull their 20 most recent one- and two-star reviews, and build the pain ledger above. You'll likely find your positioning statement is already half-written — by your competitor's unhappiest customers.