Front-end demonstration
Trade Analyzer
Build both sides of an offer, choose your format, and get a clear read on which side receives more modeled value — with the reasoning shown rather than hidden behind a score.
- Sides
- Multi-player, both directions
- Formats
- PPR · Half · Standard
- League types
- Redraft · Dynasty
186 players carry a modeled value
Team A receives
0 playersNo players added yet
Search above to build this side of the offer.
Values shown use the redraft board.
Team B receives
0 playersNo players added yet
Search above to build this side of the offer.
Values shown use the redraft board.
Add at least one player to each side to run the model.
No trade evaluated yet
Build both sides of the offer, choose your scoring format and league type, then run the model. The result will show which side receives more modeled value and why.
How the model thinks
Three Principles Behind the Numbers
The valuation is deliberately simple and inspectable. These are the assumptions it encodes.
01
Consolidation usually wins
Two flex players produce one flex player in your starting lineup. The side receiving the best player in a deal is usually the side that improves.
02
Positional scarcity is priced in
Running backs carry a premium in redraft; receivers carry it in dynasty. The model weights the two boards differently for that reason.
03
A gap under 8% is noise
Any value model has an error band. When two sides land close, the deal should be decided on roster fit, bye weeks and playoff schedule instead.
What this version does not do
- Read your actual roster, league settings or starting-lineup requirements
- Account for bye weeks or a team's playoff schedule
- Incorporate market prices from any trading platform
- Model draft picks, FAAB, or multi-team deals
The valuation layer is isolated in a single module so a real API or trained model can replace it without changing this interface.
Related reading