DFS Simulator

MLB DFS Stacking Strategy: 5-Stacks, Bring-Backs, and Runline Correlation

By DFS Simulator TeamPublished July 29, 202611 min read

MLB DFS is the most stack-driven of the major DFS sports — runs are sequential events shared by adjacent hitters, and the same 5 mean projections can produce completely different ceiling distributions depending on how many batting-order slots you cluster. Simulating the joint distribution of a stack is the whole game; sorting hitters by point projection is how new players lose money.

The core mathematical fact about baseball offense is that runs come in bursts. A team doesn't score 6 runs by having 6 independent hitters each get lucky; it scores 6 runs by stringing together singles, walks, and extra-base hits against a pitcher who's tiring in an unfriendly park. The players who benefit are, mechanically, the batters immediately after the ones getting on base. That structural correlation is why stacking wins in MLB even harder than in NFL — and it's why any MLB build strategy that ignores it is leaving equity on the table.

Why a 5-stack beats five uncorrelated bats

Consider five hitters, each projected for 8 fantasy points. Two ways to roster them:

  • Uncorrelated: five hitters from five different teams. Joint expected value: 40. 90th-percentile combined outcome: roughly 55 (the sum-of-independent tails barely stretches above the mean).
  • Correlated 5-stack: five hitters from the same team, batting 1–5. Joint expected value: 40 (same projection). 90th-percentile combined outcome: roughly 78. The correlation multiplies the tail — when the team scores 8 runs, every batter benefits.
The tail asymmetry is what makes stacking a tournament strategy. In cash games (payouts are flat), you want the higher-floor 40 → 55 build. In GPPs (payouts concentrate at the top 0.1%), you want the 40 → 78 build with the shot at the tail. Same players, different roster: different EV.

The DK vs. FD stacking rule that matters

DraftKings caps team stacks at 5 hitters per lineup and runs a 10-player roster (2 pitchers + 8 hitters). FanDuel caps at 4 hitters per team and uses a 9-player roster (1 pitcher + 8 hitters). The difference is not cosmetic: on DK, a full 5-stack with 3 flex plays from a second team is the modal winning build; on FD, a 4-stack with 4 hitters from other games is the equivalent. Trying to run a DK-style 5-stack on FanDuel gets your entry rejected at upload.

DFS Simulator's stacking rules enforce the site's cap at build time — if you load a FanDuel MLB slate and try to configure a 5-batter stack, the constraint panel warns immediately rather than letting you burn iterations on invalid lineups.

Bring-backs and the shootout script

A bring-back in MLB pairs your stack with a hitter from the opposing team — typically batting first or second so they face your stack's pitcher multiple times. The logic: the universe where your stack scores 12 runs is (with high probability) a universe where the game total was 15+ runs, which means the OTHER team also scored heavily.

A leadoff bring-back captures 4–5 plate appearances against the pitcher your stack is targeting; a middle-of-order bring-back captures fewer but with higher per-PA upside (extra-base hit potential). GPPs reward the leadoff choice more often — plate-appearance volume compounds linearly while HR variance is bounded above.

Team-total gating: the Vegas signal that matters

The single most predictive input for which teams are worth stacking is the implied team total from the game's moneyline + total: teams implied at 5.5+ runs are the stackable set for any given night. Below 4.5, you're paying stacking-correlation cost on a distribution whose upper tail is capped by an unfavorable matchup — the joint-ceiling math still works, but the ceiling is lower.

The simulator surfaces implied team totals per slate; the stacking rules panel lets you require a minimum team total for any stack the correlated model considers. This is how you avoid the pathological build of a 5-stack on a team implied at 3.2 runs against a Cy Young starter.

Batting-order lock and the news hour

MLB lineups are officially posted 2–3 hours before first pitch. Before that, projected lineups are estimates — managers slot hitters differently based on the opposing starter's handedness, weather, and rest patterns. A hitter you rostered projected for the 3-hole who ends up batting 7th just lost 15% of his ceiling before first pitch, and you can't know until the confirmed lineups drop.

The correct workflow: build with projected orders, then refresh before lock and re-run the sim if a confirmed order moves a stacked hitter more than one slot in either direction. The DFS Simulator run history keeps every pre-lock build, so a post-slate autopsy can identify which build survived which order changes and which cratered.

Weather is a first-class input

Wind out to right field at Wrigley is a top-decile GPP signal by itself — cheap left-handed power hitters in a rare high-scoring park suddenly leverage the field substantially. Rain risk that could delay or shorten the game caps every player's ceiling. The simulator's weather-aware projections downweight rain-affected slates; for wind edges, the pattern to watch is 10+ mph out "straight away" or to a specific pull-field for which the batting order matches.

Portfolio construction for MLB multi-entry

  1. Pick 3–5 stackable teams (5.5+ implied total, favorable matchup, likely batting-order lock).
  2. For each team, build 2–4 stack variants: different batting-order clusters (1–5, 2–6, 3–7), different flex pieces, different bring-backs.
  3. Diversify pitchers: pair each stack with a pitcher whose upside comes from a different game (not the pitcher throwing AGAINST your stacked team).
  4. Cap exposure per team stack at 25% of your portfolio (one team's rainout shouldn't shred more than a quarter of your entries).
  5. Sort simulated lineups by ceiling for GPPs; by floor for cash. The distinction is starker in MLB than in any other sport because the variance is so wide.

Related reading

Frequently asked questions

Why is stacking more important in MLB DFS than in other sports?

Because runs in baseball are sequential events shared by adjacent hitters in the batting order. A cleanup hitter's home run requires runners on base — usually the players batting 1–3. When an offense erupts, four to five consecutive batters share the rally, which means their fantasy outcomes are heavily correlated, which means the JOINT distribution of a 5-stack has ceiling far above 5 independent hitters at the same projections.

Should I always use a 5-stack in MLB DFS tournaments?

On DraftKings, yes almost always in GPPs — DK allows 5 hitters from one team and the joint-upside math dominates. On FanDuel, the max is 4 hitters per team so 4-stack + mini-stack is the default construction. Cash games are the exception: 3-stack from one team plus 2-stack from a second team gives a much higher floor than concentrated stacking, at the cost of the tournament-winning tail.

What is a bring-back in MLB DFS?

In MLB, a bring-back is a hitter from the OPPOSING team of your stack — typically batting first or second so they get plate appearances against your stack's pitcher. If your stack wins because their game turns into a 12-8 slugfest, the opposing team almost certainly scored too, and your bring-back hitter caught the correlated upside. Common in GPPs (adds 5–8 points of stack ceiling in high-scoring universes); rare in cash.

How do I pick which team to stack in MLB DFS?

Three inputs, roughly in this order: (1) opposing pitcher quality — a soft-tossing left-hander vs. a righty-heavy lineup at Coors Field is the ceiling scenario; (2) implied team total from Vegas — teams projected for 5.5+ runs are the stackable teams; (3) batting-order lock — you need at least 4 consecutive orders to be plate-appearance-adjacent. The simulator ranks stacks by joint expected value using all three signals.

Does the batting-order slot really change a hitter's DFS value that much?

Yes, dramatically. Leadoff hitters average roughly 4.7 plate appearances per game; 9-hole hitters average 3.8. That's ~25% more scoring opportunities from the same player, which is why moving from 7-hole to leadoff on any given day can add 15–20% to a player's ceiling. Batting-order news is the single highest-EV information source in the hour before MLB slate lock.

Keep reading

Put the theory into practice

DFS Simulator runs correlated Monte Carlo sims across 21 sports — up to 50,000 iterations per slate, from $19.99/month.