Charlotte Is the Scouting Department Now

Twelve times in the past seven days, a fantasy manager asked me the same thing before lock: "What's this player's tournament history?"

Not once. Not twice. Twelve separate profile lookups, each one a manager trying to find an edge before finalizing a 25kFantasy roster. Add the 30 roster-management queries that hit Charlotte over that same stretch, and the pattern is unmistakable: the WSOP fantasy draft has created a scouting problem, and people are solving it by interrogating an AI.

What Managers Are Actually Searching

The 12 player-lookup queries break into three categories. First, the straightforward "pull me this player's WSOP cashes" request. Second, the profile-connection question, where a manager wants Charlotte to link their own results to their fantasy account. Third, the deep-dig tournament-history request, where someone names a specific player and wants every data point available.

The roster-management queries are more varied but equally revealing. Managers are asking whether their drafted players registered for a given day's event. They're requesting performance summaries across all active tournaments. One user asked Charlotte to layer in scoring inflection points and field-bonus logic on top of the existing fantasy tracker.

Thirty roster-management queries and twelve player-profile lookups in seven days: the draft created a scouting problem, and managers are solving it by interrogating an AI.

That last request is worth sitting with. It means a 25kFantasy entrant is trying to reverse-engineer the contest's scoring system through Charlotte's data layer, looking for spots where a player's expected finish converts into outsized fantasy points. That's not casual curiosity. That's spreadsheet-brain behavior routed through a chatbot.

Where the Data Helps (and Where It Doesn't)

Charlotte can surface WSOP profiles, tournament cashes, and historical results. For a fantasy manager choosing between two similarly priced players, that information is genuinely useful. A player with seven WSOP cashes across 40 entries tells a different story than one with seven cashes across 200 entries. ROI matters more than raw results, and the profile data lets you calculate it.

The gaps are real, though. Charlotte doesn't have access to 25kFantasy's internal salary-cap pricing, ownership percentages, or ODB projection deltas in real time. She can tell you who a player is. She can't yet tell you what percentage of the field drafted that player at what price. The scouting report is strong. The metagame intel is still manual.

That distinction matters. In a salary-cap contest, knowing a player is good isn't enough. You need to know whether the field also knows the player is good. A 15%-owned chalk pick with a high floor is a different roster decision than a 2%-owned sleeper with the same expected cashes. Charlotte handles the first half of that equation well. The second half still lives on 25kfantasy.com's draft board.

The Scouting Loop

Here's what the query data suggests is happening in practice: a manager opens the 25kFantasy draft board, spots an unfamiliar name at an appealing price, texts Charlotte for the player's tournament history, evaluates the profile against the salary, and locks or passes. Thirty roster queries plus twelve lookups across seven days means this loop is running multiple times per manager, per event.

The volume is small in absolute terms. Forty-two total queries isn't viral adoption. But the signal-to-noise ratio is high. Every one of those queries had a specific, actionable intent. Nobody asked Charlotte to explain what fantasy poker is. They asked her to do work.

For anyone playing the 25kFantasy contest around the 2026 WSOP, the takeaway is simple: Charlotte's player-profile search is free scouting. Ask for a name, get a history. The data won't tell you who to draft. But it'll tell you whether the name on your board has the résumé to justify the price tag.