Two ways in — your team, or a test drive.
The journey starts one of two ways. Enter your FPL manager ID and Pocket Scout reads your real squad — your players, your bank, the exact free transfers you're holding. Or click "Explore without a team" and it builds a sample dream XV from the season's best returns, so you can try the whole thing before you ever type in an ID.
Your whole gameweek, on one screen.
The pitch paints instantly: every player rated 0–10 on a position-aware scale, and a verdict banner across the top calling this week's move — the transfer to make, who to captain, and whether to play a chip. No spreadsheets, no twelve open tabs — just your team and what to do with it.
Transfers, captaincy, and chips — sorted to your budget.
Open the breakdown and the week's hardest calls become a clear plan across three horizons: an immediate This Week move, a multi-gameweek Long Term outlook, and a season-long Chips strategy. It plans inside your real budget — tell it how many free transfers you're holding (0–5) and it works within that, stacking moves or banking one rather than burning it on a marginal swap. Every move is judged in expected points, so when nothing clears the bar it tells you to hold — the opposite of the churn most tools push.
Then ask it anything.
"Should I captain Haaland this week?" "Who's a rotation risk before the run-in?" "Is it worth taking a hit?" The questions managers stew over all week get an instant, specific answer — a chat that knows your actual squad and the plan it just built, and talks you through the call like a mate who's done the homework.
Advice that holds up when you check it.
Managers check the numbers afterward, so the hard figures are computed before any language model is involved: a deterministic base phase rates your squad and proposes moves straight from the FPL API, and only then does Claude reason over those numbers to explain the call. The model is the pundit; it never invents the underlying stats.
Most FPL chatbots happily hallucinate prices, form, and fixtures. Pocket Scout fetches real stats through tool calls before it answers — and if the evidence isn't there, it says so instead of making one up. It also treats every message as a question to answer, not an instruction to obey, so it can't be talked off its own plan.
A real app, with decisions earned by data.
Pocket Scout is a deployed full-stack TypeScript app — not a notebook demo — guarded by a 331-test suite so behaviour stays pinned as the model and rules evolve. And it was built eval-first: a point-in-time backtest over ten seasons of FPL data drove the model, and the calls that shaped it were made on evidence, including the honest negatives.
I built Pocket Scout because I'm one of those eleven million managers, and the weekly decisions — who to bring in, who to captain, when to burn a chip — are genuinely hard and genuinely fun to argue about. I wanted a smart, opinionated advisor that actually knows my team, so "what should I do this week?" is one question away.
The part I'm proudest of is letting evaluation overrule intuition. More than once the data killed a change that felt obviously right — and the eval harness got the final word, not me. That's the same bar I hold every project on this site to.
See it live — or dig into the build.