Lineup builder
Week 3 main slate · 13 games · 659 players · locks Sun, Sep 27, 1:00 PM ET
Nine slots, $50,000, our projection. Lock who you want and exclude who you don’t; the builder finds the best lineup that obeys you, then the next best that differs by as many players as you ask, and it says which of your rules cost what. Salaries are from the value board; the projection is our Sleeper number in DraftKings scoring.
Settings
Locks and excludes
A lock is in every lineup whatever it costs, and it beats the ownership cap because it is you overruling the Sharp Model on purpose. An exclude is never used. Both stay in your browser and nowhere else.
Lineups
Nothing built yet. Set the rules above and press Build.
What this is and is not
The search is exact. Each lineup is the highest projection available under your locks, excludes, cap, stack and uniqueness rule, not a good one found quickly; if the search ever has to stop early it says so above the lineups. It optimises projected points and nothing else. It does not know which contest you are entering, and a lineup that is right for a fifty-fifty is wrong for a large field.
The Sharp Model’s estimate from salary, value and team total. Not DraftKings’ actual ownership, which is only published after lock. The ownership cap and the summed figure under each lineup are the Sharp Model’s numbers, and a stack of twenty lineups built to dodge it has dodged our guess at the field, not the field.
The CSV is DraftKings’ upload layout, one lineup a row, each cell the player’s name and the id DraftKings’ own player list gave for this slate. It has not yet been through DraftKings’ uploader from this site. If DraftKings rejects it, that is the news we need.