INT-13 · SEC. 09 Competitive Intelligence

Win/Loss Signal Synthesis

Turn scattered G2, Reddit, and churn-survey quotes into a ranked list of why you actually lose deals.

FORMAT: workflow
DIFFICULTY: advanced
TIME: 15 min
TOOLS: universal
MODELS: any
COPIES: 0 so far

When to use this

You have a pile of unstructured feedback — review site quotes, Reddit threads, lost-deal notes, churn survey responses — and need the real, recurring reasons you lose to a competitor, not the one loud anecdote everyone remembers from the last QBR.

The pattern

Pastes as plain text

My product and the competitor we lose to are named at the bottom of this prompt, followed by the raw signal: review quotes, Reddit thread excerpts, churn survey answers, and lost-deal call notes, with the source labeled on each quote.

From this raw signal:
1. Cluster the complaints and comparisons into themes (e.g. price, missing feature, support quality, ease of setup, performance). Do not invent themes with no supporting quote.
2. For each theme, count how many distinct sources mention it and quote the single clearest example.
3. Separate "why we lose deals" (things said before or during a purchase decision) from "why customers churn" (things said after they were already using the product) — these are different problems even if they sound similar.
4. Rank themes by frequency, not by how dramatic the quote sounds.
5. For the top 3 themes, write one sentence on whether this is a real product gap, a perception/messaging gap, or a sales-process gap, and say what evidence in the raw signal supports that call.

If a theme only has one source behind it, label it "single signal, not a pattern" instead of ranking it.

My product:
Competitor we lose to:
Paste the raw signal below this line, labeling each quote's source (e.g. "G2 review, 2-star:", "Reddit:", "Churn survey:"):

Real example output

Themes found (12 quotes total, 3 sources: G2, Reddit, churn survey):

1. Onboarding time (5 quotes, all 3 sources) — why we lose: buyers compare setup time during trial and pick the faster one. Clearest quote: G2 review, 2-star: "Took us three weeks to get the first integration live, competitor had us running in a day." Classification: real product gap — setup friction is named directly, not just implied.

2. Price at scale (4 quotes, G2 + churn survey) — why customers churn: mentioned mostly by existing customers hitting usage limits, not prospects comparing options. Clearest quote: Churn survey: "Costs tripled once we passed 50 seats, no warning." Classification: perception/messaging gap — the pricing page doesn't show the scaling curve, so the surprise is the actual complaint, not the price itself.

3. Missing native chat-tool integration (3 quotes, Reddit + G2) — why we lose: named as the deciding factor in 2 of 3 quotes. Classification: real product gap.

Single signal, not a pattern: "Support team was rude" (1 churn survey response) — not ranked.

Why it works

Separating pre-purchase loss reasons from post-purchase churn reasons stops two different problems from getting averaged into one vague "we lose on X" conclusion. Requiring a source count per theme keeps one dramatic quote from outweighing a real pattern, and the single-signal label prevents outliers from getting treated as findings.