LLM as Disconfirmation Engine
Point the model at where your strategy does NOT fit — and reverse-engineer competitors from their public docs
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 3
- Confidence
- 87%
Clowes reframes how PMs should use general LLMs: not to confirm what they hope to see, but to provoke the answers they don't want to hear. Feed customer interviews plus your strategy and ask where they diverge; paste a competitor's public positioning and ask whether it fits the customer data better than yours; summarize a competitor's likely strategy from their public documents. The value comes only when you push at the edges.
Origin
Clowes' applied technique using off-the-shelf ChatGPT/Claude, framed around disconfirmation rather than confirmation.
Core principles
- 01Straight-up general LLMs are good enough for most of this work
- 02Ask where your strategy does NOT fit the customer data, not where it does
- 03Public documents are usually a derivative of the underlying strategy, so models can infer it
- 04Value only emerges when you provoke the problems you don't want to hear
- 05LLMs collapse weeks of manual summarization into a fast, structured pass
How to run it
- 1
Test your strategy against customer voice
Paste a batch of customer interviews and your strategy into the LLM and ask it to find where the strategy does not fit what customers talked about.
Pro tip Explicitly instruct: 'tell me where my strategy does not fit' — the negative framing is the whole point.
Watch out People spend far too much time looking for what they hope to see, not what they're missing.
- 2
Check competitor fit against your customers
Copy a competitor's positioning documents into the LLM and ask whether their positioning is a better fit for what your customers said than your own.
Pro tip This surfaces where a rival's story would resonate more with your base — a direct threat signal.
- 3
Reverse-engineer competitor strategy from public docs
Feed a competitor's public documents and ask the model to summarize their probable product strategy. Because public materials derive from real strategy, the output is often 'creepily' accurate about what they'll likely do next.
Pro tip Ask for ranked likelihoods ('more likely they'll do this than that') to prioritize your response.
Watch out Treat the output as a hypothesis about a moving target, not a fixed fact — information has a decay rate.
In the wild
Clowes describes summarizing a competitor's public documents into a probable product strategy: 'it's actually surprisingly good... it will give you crazy insights... at times creepy like oh they will probably do this.' Work that formerly took reading vast material and using your brain as a summarization machine now happens 'really really quickly in a very structured way.'
→ Hard-won competitive insight produced rapidly, provided you provoke the answers you don't want.
Common mistakes
Using the LLM to confirm your hopes
Asking where your strategy fits, rather than where it fails, wastes the tool — 'people spend far too much time looking for what they're hoping to see not for what they're not looking to see.'
Reaching for a specialized PM tool first
Clowes finds 'the straight up LLM are good enough' for most of this; overinvesting in bespoke research tooling before exhausting the general models is premature.
Is it for you?
Best for
PMs and strategists who want to pressure-test strategy and competitor positioning quickly with off-the-shelf ChatGPT or Claude
Not ideal for
Decisions requiring current, verified facts where the model's stale or hallucinated output could mislead — data has a decay rate
From the transcript
“this is my strategy tell me where my strategy does not fit what these customers talked about”
“you can take your competitor's public documents and you can ask it to summarize what their strategy probably is and it's actually surprisingly good at…”
“only if you push at the edges provoke the provoke the answers you don't want to hear”
“mostly I find that the the straight up llm and are good enough”
From the episode
Why great AI products are all about the data
Shaun Clowes (CPO Confluent, ex-Salesforce, Atlassian)