Deshaun Watson Starts in Tampa With Shedeur Sanders Waiting Behind Him

Cleveland head coach Todd Monken confirmed this week that Deshaun Watson will start Sunday against Tampa Bay, holding the line after a 34-10 road loss to Jacksonville in which Watson threw a first-drive interception and finished 16 of 22 for 205 yards, with most of the yardage coming on a 46-yard touchdown on the final drive. Monken said he anticipated Watson would be the starter, which is the least committal phrasing a first-year head coach can use while still naming a quarterback.

The reporting around the team suggests the runway is short. Executives around the league reportedly expect Watson to be benched in favor of Shedeur Sanders by Cleveland's home opener in Week 3. That is speculation rather than a team decision, but it is speculation with fantasy and betting consequences right now, because it changes how to price everything in this offense over the next two weeks.

What Week 1 actually showed

The box score is more flattering than the game was. Watson's completion rate looked fine, the interception came on the opening possession, and the touchdown came after the outcome had been decided. Strip the last drive and what remains is an offense that could not sustain anything against a Jacksonville defense that spent the afternoon dictating terms.

Context matters here in both directions. Watson had not started an NFL game in nearly two years, having missed most of 2024 and all of 2025 with multiple Achilles injuries, and rust is a real thing for a quarterback who lost that much time. It is also true that a team playing a rookie behind a quarterback on a short leash rarely improves in week two of an offense it is still building.

The Week 2 environment

Tampa Bay is favored by roughly 9.5 points, one of the largest numbers on the board. The Buccaneers opened with a 33-27 loss to Cincinnati, which tells you they can score and cannot stop anyone, and that combination is a meaningful input for Cleveland's pass catchers even in a game the market expects them to lose.

A double-digit underdog on the road is a pass-volume environment by the middle of the third quarter. That is the one reason to look at this Cleveland offense at all this week. The counterargument is that garbage-time production from an offense averaging in the low teens in expectation is not something to build a lineup around.

Fantasy fallout

Quinshon Judkins is the asset in this offense and the situation only helps him. With Dylan Sampson on injured reserve, Judkins became the clear workhorse, and a back with no competition for touches survives a quarterback change in a way receivers do not. He is a weekly starter regardless of who takes the snaps, though managers should expect the touch mix to skew toward receptions if the game gets away from Cleveland early.

The receiving group is where the quarterback question bites. Jerry Jeudy and the rest of the Cleveland pass catchers are being asked to produce in an offense that may switch quarterbacks mid-stream, against a spread that implies they will be chasing. That is a fade in season-long lineups and a tournament-only play in DFS.

Watson himself is not startable in any format. A quarterback with a public expiration date, a low implied team total and no rushing production is the definition of a player to leave on waivers.

The Sanders question

Sanders is the interesting fantasy asset, and the window to acquire him is now rather than after he is named. Rookie quarterbacks in their first starts are volatile and usually bad for fantasy purposes, but they also come with rushing production that Watson no longer provides, and the Cleveland schedule after the home opener is not brutal.

In dynasty and deep leagues, Sanders is worth a bench spot this week. In redraft, he is worth a stash only for managers carrying two quarterbacks or in superflex formats. The move nobody should make is dropping a functional starter to speculate on a quarterback who has not been named.

Betting angle

The number to attack is Cleveland's team total rather than the side. A 9.5-point spread with the total where it sits puts Cleveland in the mid-to-high teens, which is roughly the right price for an offense with this much uncertainty. The value, if there is any, sits on the over for that team total in the specific scenario where Tampa Bay builds an early lead and Cleveland throws 40 times, and on the under if the game stays close and Cleveland leans on Judkins.

There is also a live-betting angle worth having ready. If Cleveland falls behind by three scores in the first half, the market's assumption of a Watson benching mid-game becomes a real possibility, and the volatility in that scenario is exactly what in-game markets misprice.

The Verdexed model take

Verdexed's quarterback projections treat a benching risk as a usage discount applied to every skill player rather than a separate variable, which is the correct structure for a team in Cleveland's position. The practical result is that the model prefers the running back and fades the passing game entirely, and that the spread is close to fairly priced while the team total offers more room.

It also argues against paying for Tampa Bay's ceiling. Teams favored by double digits against bad offenses are the most publicly bet side in football every week, and the Buccaneers just gave up 33 points at home. A defense that cannot get off the field can keep a bad opponent in a game longer than a nine-and-a-half-point spread implies.

What happens next

Watson starts Sunday. If the offense looks like it did in Jacksonville, the Week 3 home opener becomes the most likely date for the change, and the fantasy relevance of every Cleveland pass catcher gets re-rated at that point.

The actionable items this week are narrow and clear: start Judkins, bench the Cleveland receivers, stash Sanders in dynasty, and look at the Cleveland team total rather than the side.