David Montgomery played nine snaps in Houston's Week 5 win over Tennessee on October 11, 2026, before leaving with a groin injury. Woody Marks took over from there, and the following day head coach DeMeco Ryans called Montgomery week-to-week and said Marks would carry the load. That is the entire premise of this article: a backfield that had been a competitive timeshare through four games became, in the space of one series, Marks' job to lose.
The scale of the shift is worth sitting with. In Week 5, Marks played 56 of Houston's 66 offensive snaps, an 85 percent share, and turned that into 19 touches — 15 carries and four catches on 29 routes run. That is not a committee role. That is a lead back's workload, delivered in a single afternoon after an injury created the opening.
From Competitive Timeshare to Feature Back
It is tempting to treat Marks as a player who was already Houston's best option and simply needed the snaps. The record through four games does not support that framing cleanly. Before Montgomery's exit, Marks had played 122 offensive snaps to Montgomery's 146 — a real gap, but not a blowout, and consistent with a genuine two-back rotation rather than a bench role. Over that stretch Marks produced 149 rushing yards, 54 receiving yards and two touchdowns, solid complementary numbers but not workhorse production. The condition that changed is not Marks' talent evaluation — it is Montgomery's health. Strip that away and Marks was a committee back on a track to finish as a low-end flex option, not a top-15 running back.
That distinction matters for how durable this claim should be treated. Marks did not win a job competition in camp or get handed a bigger role by scheme design. He inherited one because the incumbent got hurt. The receiving profile underneath it is real and encouraging — zero dropped passes on the season to that point, and 29 routes run in the Week 5 workload alone — but the baseline role before the injury was a 45-55 snap split, not anything close to three-down control.
David Montgomery Still Has First Claim on This Job
Houston traded for David Montgomery from Detroit in March 2026, and he opened the season as the starter on the depth chart, with Marks behind him. That is the direct competition any bullish Marks case has to answer, and it does not go away just because Montgomery is out. Ryans' own language draws the distinction clearly: he called Marks "dynamic" and said he would carry the load, but he also said Montgomery would remain week-to-week, which is coach-speak for expecting him back, not for a long-term or season-ending absence. If Montgomery returns healthy, Houston has already shown it values him enough to have traded for him and started him over Marks to open the year. There is no reporting suggesting Houston plans to bench Montgomery once healthy in favor of Marks — the dossier simply does not support that outcome.
The rest of Houston's offense is unchanged and worth noting for context, not because it drives Marks' workload directly. C.J. Stroud remains the starting quarterback, which matters for Marks' receiving role out of the backfield — a stable, established passer tends to use a reliable-handed back on passing downs rather than rotate blindly. Houston's skill talent beyond the backfield, led by Nico Collins, has not changed in a way that pulls targets away from Marks specifically. The one confirmed roster change that affects his workload is the addition of Montgomery himself, and that remains the swing factor in every direction this role can go.
“Dynamic, will carry the load for us.”
— DeMeco Ryans, October 12, 2026
“He'll still be week-to-week. As I mentioned, we'll see how he continues to progress.”
— DeMeco Ryans, October 12, 2026
The Strongest Case Against Betting on This Lasting
The honest counter-argument is that this entire case extrapolates one injury-created workload into a season-long projection, and that is a mistake fantasy managers make constantly with backup backs. Marks has one game of lead-role evidence. Before that, he was splitting time closely enough with Montgomery that neither back looked like a clear bellcow. He also carries a reported history of getting banged up in-game, which raises its own durability question even if Montgomery stays out. A single week of 85 percent snaps does not establish that Marks can hold up to a full workhorse workload over a full season, and Houston's coaching staff has given no indication it intends to permanently reduce Montgomery's role once he is healthy.
That case is reasonable, and it should temper how this is sized in lineups and trade packages. But it does not erase the opportunity. The receiving-down role is the part of this profile that travels regardless of Montgomery's timetable — zero drops and 29 routes in a featured game is the kind of usage that keeps a back fantasy-relevant even in a reduced role. The question is not whether Marks is talented enough for lead work; the Week 5 tape answers that. The question is purely how long Montgomery stays out, and that is a medical timeline nobody outside the Texans' building can forecast with confidence.
The Call: Add Him Now, Price the Risk Honestly
Marks is a priority waiver and trade target for as long as Montgomery is out, full stop. The workload — 85 percent of snaps, 19 touches, four catches on a near-full route tree — is lead-back production, and the receiving role gives him a weekly floor that does not depend on positive touchdown variance. Treat him as a top-15 running back in PPG for the duration of this window. What should not happen is treating this as a permanent depth-chart change. Montgomery was Houston's starter entering the season and remains the presumptive lead back once healthy, and nothing in Ryans' comments suggests that calculus has shifted. Roster him as high-end flex insurance with real league-winning upside in the short term, but do not pay a long-term asset price for a role that one healthy practice report from Montgomery could shrink back down.