Front-end demonstration
Fantasy Tools
Four tools that genuinely run against the data shipped with this build, and an honest list of the ones that cannot exist without a backend. Every tool shows its reasoning — a verdict you cannot inspect is not worth acting on.
- Working tools
- 6
- Week
- 1
- Players on the board
- 186
Available now
Tools That Work Today
Each of these runs entirely on the local demonstration data — no account, no league connection, no waiting.
Every tool on this page reads the same illustrative local board: a sample Week 1 slate, 186 ranked players, and generated usage and schedule data. Nothing here is a live feed, a market consensus or a trained projection model, and no tool claims an accuracy it has not earned.
Not built yet
What Needs A Backend
These are the tools people ask for that a front-end build genuinely cannot fake. Each one names the dependency that is actually missing.
League Sync
Needs backendImport your actual roster, scoring rules and matchup from ESPN, Yahoo or Sleeper so every other tool works on your team instead of a roster you typed in by hand.
Requires: OAuth against each platform, a credential store, and per-provider API clients with their own rate limits.
Assistant GM alerts
Needs backendA push notification when a lineup change is warranted — a starter downgraded to out on Sunday morning, or a bench player who has overtaken a starter since you last looked.
Requires: A live injury and transaction feed, a scheduled job to diff lineups against it, and push notification infrastructure.
Trending adds and drops
Needs backendA ranked live list of which players are being added and dropped across the whole user base, windowed by hours. The highest-signal waiver input most managers ever see, because it is pure social proof.
Requires: Transaction data across many leagues plus a time-windowed aggregation service. The waiver wire page ships a static illustrative version today.
Draft room and board
Needs backendA live draft board with everyone's picks on one screen, colour-coded by position so a positional run is visible before you read a single name, plus a cast mode for the big screen.
Requires: Realtime multiplayer sync, draft state persistence, and a second rendering target for cast mode.
League history and awards
Needs backendChampions, all-time standings, weekly highs, playoff and toilet-bowl brackets. Multi-year memory is the reason leagues stay put, and it is what fuels the rivalry the rest of the product trades on.
Requires: A persistent multi-season datastore and league identity that survives a season rollover.
Watchlist and alerts
Needs backendOne-tap tracking from any player row, feeding a personal news and injury feed. The interaction is cheap enough that watchlists build themselves without a decision.
Requires: User accounts, per-user persistence, and a notification pipeline off the news wire.
Why the split matters
A tool that quietly invents its inputs is worse than no tool: it produces a number that looks the same as a real one. The four working tools above are built on data this build actually holds, and each states what it cannot see. The list on this side stays unbuilt until the thing it depends on exists.
