Baker Mayfield's revenge game against the Browns is the hook for Week 2. It's not the reason to start him.
Revenge is a narrative. Narratives don't throw touchdowns. What separates a top-12 quarterback week from a QB2 week is dropback volume and matchup, in that order. Motivation is a broadcast segment. The wire copy has Mayfield as a good fantasy option this week because of the Browns, and I'm on the same side of the call. My reasoning just isn't theirs: a quarterback who has to throw for four quarters outscores one who hands off in the fourth, and a matchup that pushes an offense into passing mode is what you're actually buying. "Revenge" is only the label attached to this one.
So start Mayfield. In a single-quarterback league he's a back-end QB1 with a floor you can live with. In superflex he isn't a question at all.
The sit side follows the same logic in reverse. Sit the quarterbacks whose weekly value depends on one deep shot connecting, because that's variance wearing an upside costume. Sit the ones in low-volume, run-first scripts too, no matter how good the name looks on the roster page.
What would change my mind: if the week's practice reports show Mayfield limited, or if his top targets surface on the injury report, the volume case thins out and he drops to streamer status. A revenge game with a depleted supporting cast is a bad week with a good story.
One more caveat on the genre. Revenge-game tags cluster around quarterbacks who happen to be in good spots already, which makes the tag look predictive when it isn't. Treat it as noise and keep the matchup and the volume. When the tag is doing all the work, the week is a coin flip.
Verdict: Mayfield is a start, and I'd make it with the sound off. The story is Cleveland. The points are the volume.
