Detroit opened a real fantasy decision when David Montgomery moved to Houston. The answer is not to treat Isiah Pacheco like Montgomery's job simply changed jerseys. The usable move is narrower and more profitable: draft Pacheco as a conditional bench bet after the stable running back tiers are gone.
Here is the key line. Pacheco is worth targeting when his cost still reflects uncertainty, not when the draft room starts treating him as Detroit's solved No. 2 back. You are buying a path into a good offense, not a signed certificate for Montgomery's old touches.
The bet is Detroit's open role, not Pacheco nostalgia
The case starts with the roster change. Montgomery was traded from Detroit to Houston on March 11, and Pacheco now sits in the Lions' running back room behind Jahmyr Gibbs. That creates a role question fantasy managers should care about because Detroit can turn ordinary backfield touches into usable weeks.
The football fit is easy to see. Detroit still needs a back who can absorb contact, close drives, and keep the offense from asking Gibbs to handle every dirty carry. Pacheco's best path is not to become the engine. It is to become the hammer next to the engine.
That is why this is a draftable bet. A secondary back in a dead offense needs everything to break right. A secondary back in Detroit only needs one lane to stay open: early-down work, short-yardage chances, and contingency value if the backfield gets thinner.
The failure case is just as clear. If you draft Pacheco because the name feels familiar and the depth chart looks simple, you are paying for certainty Detroit has not actually shown yet. The role has to win first.
The Montgomery comparison is useful only as a warning
Montgomery's exit matters because it vacates a job, not because it hands that job to Pacheco in full. Detroit trusted Montgomery in a specific way. He could handle contact, protect the offensive rhythm, and give the staff a second back who did not need the offense to change shape.
Pacheco can chase that function, but the evidence does not say he already owns it. His broader tracked 2025 window showed 8.0 carries and 1.8 targets per game. That is usable involvement, not automatic weekly starter volume.
Down the stretch, the role looked a little healthier. Pacheco's closing sample included 9.33 carries and 2.33 targets per game, with his snap share pushing over half the offense. That gives him enough pulse to matter if Detroit gives him the right lane.
It still does not make him Montgomery with a new helmet. Pacheco's recent rushing efficiency was shaky, including negative rush yards over expected per attempt in the tracked rushing data. The draft move is to buy the opportunity, then leave room for the offense to tell us whether he actually earned the trust.
Gibbs is the reason the price has to stay honest
Gibbs is the guardrail on the whole argument. He is not a small obstacle in this backfield. He is the reason Pacheco's ceiling has to be described as conditional instead of clean.
The late-season usage backs that up. Gibbs averaged 14.33 carries and 7 targets in the closing sample, while playing roughly three quarters of Detroit's snaps. That is lead-back behavior with receiving gravity attached, and it limits how much weekly oxygen is left for everyone else.
That does not make Pacheco useless. It defines the bet. You are not drafting him to beat Gibbs. You are drafting him because the Lions may still need a second back who can handle the boring work that becomes interesting near the goal line.
This is where discipline matters. If you want the weekly anchor, pay for Gibbs. If you want cheaper Detroit exposure with a path to touchdown weeks and injury leverage, wait for Pacheco. Those are different bets, and mixing them is how a good bench pick turns into a bad starter bet.
The Lions make a partial role matter
Detroit's offense is the reason this is not just another backup-running-back conversation. The Lions ran 1,088 offensive plays across 17 tracked games last season, which is 64.0 plays per game. Volume does not solve every role problem, but it gives a secondary back more chances to be useful.
The play-calling profile also keeps the door open. Detroit had a 46.04 percent red-zone rush rate in the tracked team data, which means the offense still made room for backs near scoring range. Pacheco does not need seven targets to pay off if he is getting some of the finish-drive work.
That separates a blind stash from a playable stash. The blind stash needs an injury. The playable stash has a weekly job that can matter even before the depth chart breaks. Pacheco is only interesting if Detroit gives him the second version.
At publication, Pacheco is sitting around RB42 with a PPR ADP of 151, which still fits a bench role more than a starter role. That cost works because the football path is partial: early-down carries, some finish-drive chances, and value if Detroit's backfield gets thinner. If the cost climbs into a range where you need immediate flex points, the edge starts to disappear.
The draft rule is simple
Draft Pacheco when your roster already has stable running back points and you can afford to wait on the role. He fits builds that want a bench back tied to a strong offense, especially when the safer volume backs are gone and the board is turning into contingency plays.
Pass when you still need a Week 1 starter. Pass if your league pushes him up because Montgomery left and nobody asks what part of the role is actually available. Pass if the price assumes Gibbs is merely in the way instead of the centerpiece.
The best version of the pick is not complicated. Pacheco becomes Detroit's early-down and finish-drive complement, Gibbs remains the backfield anchor, and your bench gets access to a high-functioning offense without paying premium cost.
The bad version is just as simple. Gibbs dominates the valuable touches, Pacheco needs touchdowns to matter, and you spend September staring at a name you do not feel safe starting.
That is the final draft rule. Pacheco is a buy when he is drafted as a conditional Detroit role bet. He is a pass when the price pretends the condition has already been met.
Ask FantasyGPT about Isiah Pacheco.
Run the player case with FFN rankings, projections, and context already in the loop.
Powered by FFN rankings, projections, and player context.