David Montgomery Is the Texans' Clear RB1 After Trade From Detroit and Mixon's Release
By Verdexed NFL Desk
David Montgomery is the Houston Texans' clear No. 1 running back for 2026 after the team acquired him from the Detroit Lions and cleared the depth chart ahead of him. The trade, combined with Houston's earlier release of Joe Mixon, hands Montgomery an unambiguous lead role on a roster that suddenly has a defined hierarchy at the position.
Per reporting, the Texans sent offensive lineman Juice Scruggs plus a Day 3 pick package, reported as a fourth-round and a seventh-round selection, to Detroit for Montgomery. The exact compensation has not been officially itemized, so it is best attributed to reporting, but the structure points to a sensible price for a veteran back on a clear role rather than a premium acquisition.
Why Montgomery wanted out of Detroit
Montgomery's exit from Detroit was rooted in usage. He was unhappy with his reduced role behind Jahmyr Gibbs, whose ascent turned what had been a true committee into a backfield increasingly tilted toward the explosive younger back. For a runner who values early-down and short-yardage work, a diminishing share in Detroit made a move to a lead job elsewhere appealing.
Houston offered exactly that. With the Texans, Montgomery steps into a No. 1 role rather than splitting touches with a clear-cut alpha ahead of him. The change of scenery answers the usage complaint directly: instead of ceding early-down and goal-line work, he becomes the back the offense is built around in those situations.
Mixon's release cleared the runway
The path to Montgomery's lead role opened when the Texans officially released Joe Mixon on March 6, 2026, with a failed-physical designation that cleared roughly 8 million dollars in cap space. Mixon missed all of 2025 with a foot injury that required surgery, and the specifics of that injury were never disclosed, leaving his football future clouded.
That release did two things at once. It removed the incumbent lead back from the equation and it freed cap room, part of which effectively financed the move for Montgomery. The sequence left Houston without an established starter and then filled the vacancy with a proven early-down runner, producing the clean hierarchy that now defines the backfield.
Fantasy fallout: a capped but real RB2
Montgomery projects as a mid-tier RB2 with genuine red-zone and early-down upside. A lead back who handles short-yardage and goal-line work carries a reliable touchdown-equity floor, and that profile fits how Houston now appears set to deploy him. For managers seeking a dependable early-down anchor, he is a sensible target in that tier.
The ceiling, however, has limits. Montgomery turns 29 in June 2026 and took a statistical step back in 2025, two factors that argue against expecting a true workhorse breakout. The combination of age and a recent dip caps the upside even as the role secures the floor. Managers should value the role and the touchdown equity while pricing in the age curve rather than betting on a return to peak production.
Woody Marks is the other half of the story. Marks led Houston with 703 rushing yards in 2025 and projects as a change-of-pace and passing-down complement, a role that gives him standalone value in PPR formats. He logged 14 or more total touches in eight of Houston's final 11 games, evidence of a back who can carry a meaningful workload when given the chance.
That usage history makes Marks both a priority handcuff and a sneaky standalone PPR flex. He sits on the borderline of RB2 value if Montgomery were to miss time, and even in a complementary role his pass-game work gives him a floor that pure backups lack. The projected touch split between the two remains exactly that, a projection, which is why the backfield deserves monitoring rather than firm conclusions.
Betting angle: a split worth tracking
The backfield-split uncertainty is the heart of the betting angle. Montgomery is the clear lead back, but the precise division of carries, targets, and goal-line work between him and Marks is not yet settled, and that ambiguity has direct implications for player props. Anytime-touchdown markets and rush-attempt totals for both backs are worth watching as the picture firms up.
The disciplined read is to treat the split as live information through the summer. If camp reporting suggests Marks retains a larger passing-down and change-of-pace role than expected, Montgomery's rush-attempt and touchdown props shift accordingly, and vice versa. Bettors who track the camp usage signals get the earliest read on where the value sits before the markets fully settle.
The Verdexed model take
The model views Montgomery as a secure-role, capped-ceiling back: the lead job is real, the touchdown equity is real, and the age-plus-dip combination keeps the upside in check. It values him squarely in the mid-tier RB2 range, rewarding the role while discounting expectations of a workhorse renaissance at 29.
Marks is the more interesting model case. His 2025 production and his late-season touch volume give him a credible standalone floor and elevate his contingent value as a handcuff. The model treats the touch split as the key unsettled variable, leaning on camp reps to resolve how much standalone value Marks holds and how firmly Montgomery controls the early-down and goal-line work.
What's next
The markers to watch are training-camp usage and any early reporting on how Houston intends to divide the backfield, particularly on passing downs and at the goal line. Those signals will determine whether Montgomery is a high-floor RB2 with touchdown upside or whether Marks carves out enough work to compress that ceiling.
The actionable takeaway is twofold. Draft Montgomery as a mid-tier RB2, valuing the role and red-zone work while respecting the age and the 2025 step back. Prioritize Marks as a handcuff with standalone PPR appeal, and treat him as a borderline RB2 in any scenario where Montgomery misses time. For bettors, monitor anytime-touchdown and rush-attempt props through camp, because the backfield split that decides their value is still being written.