The Naked QB Problem: Why Unstacked Quarterbacks Hurt Your Best Ball Roster
The Naked QB Problem
A “naked” QB is a quarterback you roster with none of his pass-catchers. In best ball tournaments the problem isn’t that he scores badly — it’s that his big weeks don’t compound with anyone else on your roster, so you capture only half the value of his ceiling. Stacking fixes the correlation; naked QBs waste it.
| Setup | When your QB throws for 4 TDs | Net effect on your roster |
|---|---|---|
| Naked QB | You get the QB points only | One good score, no multiplier |
| QB + 1 pass-catcher | QB and his WR/TE spike together | Two spike scores in the same week |
| QB + 2 (double stack) | QB plus two correlated hits | A genuine tournament-winning week |
| QB + bring-back | Your stack and an opponent’s WR benefit from a shootout | Ceiling on both sides of the game |
Stacking is one of the most established edges in best-ball tournaments, and the “naked QB” is its opposite — the quiet default that costs you nothing on paper and a lot in practice. Understanding why is core to building rosters that can actually win a large field.
Why Naked QBs Cap Your Ceiling
Best-ball tournaments are won by ceiling weeks, not average weeks — your best players auto-start, so what matters is how high your roster can spike in a given week. Correlation is what turns one player’s big game into several big games on your roster at once.
When your QB throws four touchdowns, those touchdowns went to someone. If that someone is on your roster — his WR1, his TE — then your QB’s huge week and your pass-catcher’s huge week happen in the same week, stacking two spike scores into one lineup. That’s a tournament-winning week.
A naked QB breaks that link. He can throw for 400 yards and four scores, and you capture only the quarterback points, because the receivers who caught those touchdowns are on someone else’s roster. You got a good week from one player instead of a great week from two or three. Over a season and a large field, that lost correlation is the difference between advancing and going home.
The Correlation Math, Simply
Fantasy points in a passing game are shared, not independent. A quarterback’s ceiling game is, by definition, also a ceiling game for his top pass-catchers. Stacking deliberately buys both ends of that shared outcome:
- A QB + his WR1 means one real-life event (a big passing day) lights up two of your players.
- A double stack (QB + two pass-catchers) widens the net — if the yardage or touchdowns go to either receiver, you benefit.
- A “bring-back” (adding an opposing pass-catcher) captures the shootout scenario, where both teams throw and both sides of the game pay off.
A naked QB opts out of all of this. You’re betting on a quarterback’s ceiling while owning none of the players who share it.
When a Naked QB Is Actually Acceptable
Stacking is a strong default, not an absolute law. A naked QB is defensible when:
- You’re late in the draft filling a QB2/QB3 and the correlated pieces are long gone. A cheap naked QB for bye-week coverage is fine — you’re buying availability, not ceiling.
- The stack pieces cost too much. If forcing a stack means badly overpaying for a mediocre WR, the correlation isn’t worth the drafted-in loss of value. Don’t torch your roster to force a stack.
- In lower-variance contests (small fields, cash-style formats), correlation matters less because you’re chasing floor, not a massive ceiling.
The key distinction: a naked QB1 you built your roster around is a mistake; a naked QB2 you grabbed late for coverage is just roster management.
Worked Example: The Wasted Shootout
Two managers each roster the same high-upside quarterback. Manager A also drafted that QB’s top WR and his pass-catching TE — a double stack. Manager B drafted the QB naked, spending those picks on unconnected players.
In Week 6 the QB’s team gets into a 38–35 shootout: he throws for 380 yards and four touchdowns. Manager A’s lineup explodes — the QB spikes, the WR spikes on two of those scores, and the TE chips in — three big scores from one game, stacked into one week. Manager B gets exactly one big score: the quarterback. Same QB, same real-life game, and Manager A captured roughly triple the value from it.
Common mistake: drafting a quarterback you’re excited about without any plan to stack him, then filling the roster with unconnected “best available” pass-catchers. In a tournament, an unstacked QB1 leaves most of his ceiling on the table — his best weeks don’t compound with anyone you own. If you’re investing real draft capital in a QB, invest a pick or two more in the pass-catchers who share his upside.
How to Fix a Naked-QB Roster
If you look up mid-draft and realize your QB1 is naked, you have options: draft his pass-catcher on the way back through the rounds (even a round or two early is often worth the correlation), add a bring-back from a projected shootout opponent, or — if the pieces are truly gone — accept it and make sure your other rosters in the portfolio are properly stacked. In a multi-entry set, a single naked QB is survivable; making it your default across every roster is not.
Stacking won’t win every week, but it’s how best-ball rosters buy the correlated ceiling that wins tournaments. Treat naked QBs as the exception you tolerate late, not the default you build around.
For more on correlation, roster shape, and tournament construction, continue with best-ball stacking strategy, best-ball tournament strategy, and best-ball QB strategy. The best ball hub has the full library.