Designed the first PLO solver in a browser as its sole designer, still live four years on with 120+ paying subscribers

Studying Pot-Limit Omaha with a solver meant buying a $5000+ PC to run MonkerSolver, so most players studied without one.

And a solver answers with a matrix of frequencies. The players who needed it most could not read it. The engine was proven, so the open question was the interface.

I was designing a learning tool for a game I did not play, so I learned it through players:

• Beginners and pros, who showed the gap. Beginners could not say what they needed, and pros played on intuition
• Leads of poker stables, who teach players at every level, as my main collaborators
• Every new screen validated with a stable lead, to find what confused, what held and where a screen asked too much

I broke the solver’s matrix into 3 surfaces, each answering one question a player actually asks:

• Preflop, for "what should I play here", with range charts across stack sizes, positions and rake.
• Postflop, for "how does my hand do on this board", with equity visuals in place of the matrix.
• GTO Trainer, for practice, with up to 4 tables tuned to feel like a real session and no custom bets, so the drill stays on correct play.

Most importantly, I treated the interface as the product. With no onboarding team, every screen had to teach on its own, and the marketing site led with the player’s question, not the engine.

I designed it alone over 10 months, from research to the design system, while engineers owned the engine.