MLB DFS Command Center

What the command center pulls together

This page is a single view of one MLB slate. It collects the outputs that normally live on separate tools: the confirmed and projected starting pitchers, the projection board for hitters and pitchers, the team stacks ranked by range of outcomes, the home run model, and the value plays where projected points are high against salary. The point is to answer the question of where to start on a slate without opening six tabs.

Each block links back to the full tool behind it. The command center shows the top of each list, and the underlying page shows every row with the filters and the model weights.

How to use it before lineups lock

Work from the environment down to the player. Start with the pitchers, because a starter sets the run environment for nine hitters and is the largest single decision on a baseball slate. Then read the stacks, since baseball scoring is correlated and a lineup built from unrelated hitters gives up most of its ceiling. Then use the home run calls and the value board to fill the remaining slots.

Check the slate again after lineups are posted. A hitter who was projected in the middle of the order and lands eighth loses plate appearances, and a scratched starter changes the whole game environment for both teams.

Where each number comes from

Projections come from the same engine that feeds the projections page and the optimizer, so the numbers here and there always agree. Home run calls come from the hybrid home run model rather than from the projection engine, which is why a hitter can rank highly for home runs and only moderately for total points. Stacks are ranked on a range of outcomes rather than on a mean, because a stack is a ceiling play.

Park factors and first pitch weather are already inside the projections, so you do not need to apply them a second time by hand. They are published separately so you can see what moved a number.

Frequently asked questions