Skip to main content
GTOPokerGTO Solver
StrategyPokerGTO Solver Team8 min read

Evidence-First Exploits: Test a Specific Opponent Tendency

exploitevidencestatsdecision
Evidence-First Exploits: Test a Specific Opponent Tendency

Define a testable deviation

An exploit is a response to a specific opponent tendency, not a permanent label such as “always bluffs.” Specify position, action line and size, and identify what evidence would change your view.

Use relevant opportunities and uncertainty

Neither 20,000 total hands nor two weeks of repetition proves an exploit. A rare node can remain poorly sampled inside a large database, and observed showdowns do not represent all hidden hands. Keep formats and situations separate and consider selection bias, dependent observations and changing opponents.

Compare plausible models before changing play

  1. Write the baseline and the hypothesized opponent deviation.
  2. Count the matching opportunities rather than all hands.
  3. Check whether an adjustment remains reasonable if the estimate is wrong within a plausible range.
  4. Document the change and a reason to reduce or reverse it. Review action evidence separately from short-term results.

The site's equity and solver tools can help compare assumptions, but do not verify hidden opponent cards or automate an exploit policy. A winning sample alone is not proof of positive long-run EV.

Practice On Site

Frequently Asked Questions

When should I change the baseline strategy?
When relevant evidence supports a specific deviation and the adjustment withstands plausible estimation error. A calendar interval or total-hand threshold is not proof.

Related Articles