Preflop Range Simplification: Turning Complex GTO Charts Into Play You Can Remember

Preflop mixed frequencies are hard to execute fully. This article organizes the GTO Wizard presenter's flow: keep pure strategies in the current solve, match overall structure with memorable frequencies, then let the opponent re-adapt and compare EV at the root node. The 0.2%-0.3% of pot target is the presenter's experience value in that specific demo and cannot be used as a universal standard.

PokerSlate illustration
PokerSlate illustration

Author: PokerSlate AI-assisted editorial desk · Editor: PokerSlate separate AI editorial review

Published:
Updated:
Reviewed:

Complexity Is Free for Computers, Expensive for Humans

The video opens with two preflop charts side by side: the original GTO chart full of mixed frequencies, and the presenter's own simplified version. According to the presenter, the solver rates both as equally exploitable, winning the same amount against a perfect counter-strategy. That claim is the premise of the whole piece, and it should be taken with a grain of salt: it only holds if the simplified strategy actually passes the root-node measurement described later, not because simplification itself is automatically free.

The presenter's core point is blunt: a simple strategy executed well will beat a complex strategy executed poorly over time. The big-blind defense chart against a button open in a single-raised pot is used as the counterexample. It looks beautiful but is full of mixed frequencies that nobody actually memorizes in real life; most people just play by feel. The reason is that complexity is a free resource for computers but not for humans. Once human execution slips, theoretical optimality never materializes. So the goal here is not to find a better size, but to consciously trade a little theoretical EV for executability.

01PokerSlate

The Cost of Simplifying and the Acceptance Line

01

Why simplify

Complexity is free for computers but expensive for humans; unmemorized theory never turns into EV.

02

Exploitability defined

GTO EV minus simplified EV: the most you lose against a perfect counter.

03

Discount the reading

A theoretical value, not actual loss; real opponents cannot play the maximal exploit.

04

Target ranges

Stop at 0.1%; 0.2–0.3% is the professional sweet spot, above 0.4% iterate again.

05

Complexity power law

The closer the tighter; microscopic coverage leaks are nearly uncapturable in practice.

Conceptual illustration, values are organized from the video narration and are not measured conclusions; values belong only to that video demo setup.

Measure Exploitability at the Root Node, Not at the Decision Point

The presenter evaluates simplification cost with exploitability, also called Nash distance here: how much EV you would lose at most against a perfect counter-strategy. In the presenter's comparison, it is calculated as the baseline GTO EV at the same root node minus the simplified-strategy EV after the opponent's best response. The key operational detail is that the measurement must be taken at the root node, meaning the first non-folded node of the street. If you simplify the big blind's response to a button open, measure before the button gets to act, not when facing the open, because the button will adjust its opening strategy to your simplification, and measuring in the wrong place introduces strange conditional logic.

Another easily missed reminder: exploitability is a theoretical value, not your actual loss. Real opponents neither will nor can play the maximal exploit, so half a percentage point of exploitability does not mean losing half a percentage point in real games. It is simply the only quantifiable objective yardstick available, so discount it when you use it. The presenter's target is to stop once the gap is within 0.1% of the pot, which is already close enough. The 0.2–0.3% range is his sweet spot for professionals building charts. Above 0.4% usually deserves a few more iterations, but for an ultra-simple chart aimed at recreational players, a much larger number is acceptable.

The closer you get to GTO, the harder progress becomes, which the presenter calls a hidden power law of complexity. Going from 5% to 1% mostly fixes macro leaks, such as folding too much or failing to get money in with strong hands — mistakes that really do get punished in practice. Going from 0.2% to 0.1% usually fixes micro leaks, such as coverage of a specific six of spades on a specific turn card on one line — mistakes only a machine could catch, with extremely slow information transfer and almost no practical relevance. He splits practical exploitability into two layers: big-picture hand selection and overall frequencies really do get punished, while tiny coverage imbalances are only theoretically exploitable and too noisy to be discovered.

Six-Max Demo: Lock Pure Strategies First, Then Match Frequencies With 50/50s

The presenter first calibrates the measurement with a heads-up small-blind-versus-big-blind example: GTO and the node-locked simplified version both show 53.8% big-blind EV. He then admits viewers care more about six-max cash games, so he opens a new big-blind-versus-button solve live, with bet sizes adjusted for demo purposes only, such as setting the 3-bet size to 12.5BB based on editing the preset tree, while keeping the 4-bet all-in option. He iterates quickly in fast mode and measures precisely in classic mode; multi-way and deep pots generally call for classic, heads-up shallow pots call for fast. Before starting, back up the original solve as the baseline by right-click duplicating the tab or saving the Spot.

Step one is always to take inventory of pure strategies in the current solve. In the original solution some hands are pure folds and some are pure raises, such as TT-plus, suited AJ and AK that strictly prefer raising over calling in that solve. The presenter keeps the pure strategies in the current solve first; this does not mean the same action is still required after the setup or opponent ranges change. Then clear the remaining mixed raises and rebuild frequencies from a blank slate. In the first simplification, the observed overall fold rate is 53% while the GTO baseline is 55%, so add some marginal hands to folds to match frequencies. For the mixed part, use a memorable execution: set the groups that need mixing to a uniform 50% raise and 50% call, with the exact hand selection depending on indifference in that specific solve. When node-locking, make sure to check the option to not lock previous nodes, allowing the button to dynamically adjust its opening range to the simplified big-blind strategy, then read exploitability at the root node.

02PokerSlate

Guess-and-Check Workflow

01

One spot at a time

Work on one spot at a time, such as big blind versus button.

02

Record the root-node baseline

Duplicate the original as a baseline; iterate in fast, measure precisely in classic.

03

Lock pure strategies

Lock pure folds and pure raises first, then clear the remaining mixed frequencies.

04

Match overall frequencies

Make every mix a 50/50 with Broadways, suited connectors, and small suited aces as the skeleton, matching original frequencies.

05

Let the opponent adapt

Select the option to not lock previous nodes, allowing the button to adapt its opening range to your simplified big blind strategy before you read exploitability at the root node.

Conceptual illustration, step order follows the video demo; values belong only to that video demo setup.

Use the Three-Part Diagnosis to Push Attempt Two to a Tie

The first result is 53.7% at the root node versus 54.2% for the original solution, a gap of half a percentage point. The presenter says many players could stop here, but it can get better. The diagnosis has three parts. First, look at the opponent's response. Facing the 3-bet, the opponent's fold rate rises from around 61% to around 64% with fewer raises, which means your 3-bet is too tight and too strong. Second, look at the raise-versus-call comparison in Compare EV: large green areas want to raise, gray hands are close to indifferent, and the conclusion is the same — not enough raising, and a too-strong structure. Third, unlock locally: free only one or two hands to see how the solver wants to fine-tune them, rather than unlocking the whole strategy.

For the second attempt, save the score before editing. Change some of the too-strong Broadway hands back to calls and bring in suited gappers, checking the original solution to confirm those hands really are indifferent to 3-betting. Offsuit A4 is unlocked alone as an experiment; the solver wants to raise it half the time, so lock it at half. Offsuit AQ is made a pure raise, and pocket nines are strengthened too. The reading returns to the root node: the simplified version is 54.2%, and the original is also 54.2% — essentially tied. The presenter admits he got a bit lucky this time; it is not normally this fast.

03PokerSlate

Three-Part Diagnosis and Finish

01

Read the opponent's response

Extra folds mean you are too tight; fewer raises mean your structure is too strong.

02

Raise-versus-call comparison

Large green areas want to raise — a signal of too little and too-strong raising.

03

Local unlock probes

Free only one or two hands, e.g. offsuit A4, to see whether the solver wants half or full raising.

04

Accept the caveman equilibrium

Unexploitable overall with wrong single-hand incentives; when good enough, move to the next spot.

Conceptual illustration, with no reliance on any unknown hole cards; values belong only to that video demo setup.

Memorize the Recipe, Don't Be a Perfectionist

Even when the totals tie, individual hands can still have the wrong incentives, for example AQ is put into the raising range even though the solver does not like raising it there. In the presenter's words, this is not a Nash equilibrium, it is a caveman equilibrium meaning a rough simplified strategy, and a close demo root-node EV reading does not prove that all hands satisfy Nash equilibrium incentives. The goal was never perfection; once it is good enough, move on to the next spot, because there are far too many spots to simplify.

The recipe collapses into steps. Work on one spot at a time; don't simplify everything in the same tree. Solve GTO and record the baseline at the root node. Lock the pure strategies. Use 50/50s to bring overall frequencies close to GTO. After locking, compare again at the root node. Save the best score each round, and revert to the highest score if a try fails. Along the way, rotate through opponent responses, Compare EV, and local unlocks to find direction, pushing until exploitability is 0.2–0.3% in fast mode; only use classic mode to push to 0.1% if you want to be thorough. The presenter considers the former good enough and the latter optional.

Local reading context

For readers who can read preflop charts and want to turn complex solves into executable strategy. This article uses video demos such as six-max BB vs BTN; all EV, frequencies and accuracy targets are constrained by the respective ranges, stacks, rake, trees and solver modes. This article did not rerun a solver; build a new baseline before moving to nine-max or other spots and do not copy demo hands and thresholds directly.

Related reading and tools

Original sources and verification

  • GTOWizard

    This strategy comes from a GTOWizard video published March 12, 2026, running 24 minutes 45 seconds with 99 screenshots. Its core claim is rewriting preflop mixed-frequency charts into memorable node-locked simplifications, validated by root-node exploitability; the targets and diagnostic methods all come from that video.

    Verified:

This article is adapted from the video: GTOWizard · How to Build Simple Preflop Ranges You’ll Actually Remember ↗