About the author
Aaron Pike
Founder and engineer, LeagueFrenzy
I built the LeagueFrenzy projection and valuation engine — the code that reads your league’s actual scoring rules and roster slots, projects points under those rules, and ranks players by what they are worth over the replacement you could really get. I also write the posts on this blog.
The engine’s accuracy is published, not asserted. The backtest runs across eight target seasons, holds out years the model never tuned on, breaks accuracy down by position, and lists the experiments that failed. It is linked below, and it is the right place to argue with me.
The formats I play are the ones consensus rankings handle worst, which is a large part of why this product exists: a 16-team dynasty IDP league, PPR and standard ESPN redraft leagues, and a superflex dynasty. A generic board prices none of those correctly.
Why you should weigh what I write
Every claim below is either independently checkable or stated no more broadly than I can back it.
Built the value engine — and published its backtest
The projection and valuation engine behind every LeagueFrenzy board is mine. Its accuracy is measured over eight target seasons with true holdout years the model never saw during tuning, reported by position, and published alongside the experiments that did not work.
Founder, Aspiretoachieve Studios LLC
LeagueFrenzy is built and published by Aspiretoachieve Studios LLC, the company I founded. Our terms of service name that same entity as the publisher of this site, so the company behind the product and the company behind this byline are one and the same.
Professional software engineering background
The engine is a deterministic pipeline with tests, backtests, and version-pinned outputs, built the way production software gets built rather than as a spreadsheet that grew. That discipline is where the reproducibility claims come from.
Plays the formats the board is built for
A 16-team dynasty IDP league, PPR and standard ESPN redraft leagues, and a superflex dynasty. Tackle scoring, a second QB-eligible slot, and thin waiver wires are not hypotheticals here — they are the leagues that kept exposing what generic rankings miss.
How this blog handles being wrong
Projections are estimates and some of them miss. The backtest reports held-out seasons rather than the flattering in-sample ones, carries a section on the experiments that did not work, and says where the model is still weak; the methodology page names the remaining rough edges too. Posts that get materially revised carry an updated date rather than a quiet edit. If a number here is wrong, the backtest is where the argument should start, and support is how to tell me.
See it on your own league
The board changes when your rules do.
Connect a league and watch the ranking move, or read the blog first.
Try your league free