Pierre Strong

Pierre Strong Jr. — RB, GB — 2026

Verdict

AVOID (high confidence), judged against a free/undrafted price. Strong is the low-standalone / low-contingent quadrant of the handcuff 2×2 (rb.md §7) — a roster clog. He is currently projected off Green Bay's 53 (Jacobs/Brooks/Lloyd carried as the only three RBs in post-minicamp projections — SI, 6/2026), and even the full injury cascade dead-ends: the team profile projects a Lloyd/Brooks/Martinez committee if Jacobs misses time, with Strong not even a named member. The sliver of the market tempted here — deep-league handcuff hunters chasing the Jacobs legal flag with a 4.37-forty veteran name — is wrong because the succession claims run through Chris Brooks (top backup) and MarShawn Lloyd (2024 R3 capital), not through a 27-year-old on a reserve/future deal who played zero snaps in 2025. Nothing about him is worth a pick or a waiver claim while Damien Martinez-type darts exist in the same backfield.

Projection & comps

Bottom-up (GB team volume from data/team-profiles/GB.md: ~27.5 rush att/g, ~30 pass att/g; Strong's share ≈ 0 in the base case):

The true blow-up branch (Jacobs suspended/injured AND Strong beats Brooks+Lloyd+Martinez for committee lead) is a <5% tail, not the p80 — it is excluded from the ceiling per §2 of the scoring framework.

• Games-played risk: high — driven by roster status, not injury (waived by CLE with an injury designation 8/26/2025 is the only recent health flag; Wikipedia, fetched 2026-07-08).
• Comps (veteran RB4/bubble seasons): Patrick Taylor GB 2023 (~25 PPR), Kene Nwangwu MIN 2023 (KR specialist, ~15 PPR), Tyrion Davis-Price SF 2023 (~10 PPR), Pierre Strong himself CLE 2024 (35.2 PPR — his best season), Jordan Mason SF 2023 (~50 PPR — the efficient-RB3-behind-a-bellcow ceiling shape).
• No external projection for him exists in data/projections/ (directory absent) — consistent with a zero-projection player.

Usage profile (rb.md §2 table)

2025 sample: none — zero REG-season snaps (GB practice squad all year; elevated Weeks 7 and 15 plus one other game-day promotion, played 0 snaps — heavy.com, 1/2026; confirmed by absence from data/stats/2025/ rushing/receiving/snap_counts, pulled 2026-07-07). Last live sample is 2024 CLE:

2024 line: 26/108/0 rushing, 22 tgt–14 rec–104–0 receiving, 35.2 PPR in 13 active games; plus 12 kick returns for 265 yards (weekly.csv, depth_charts.csv list him as KR). Career NFL: 99 carries, 499 yds (5.0 YPC), 2 TD; 26 rec, 193 yds; ~125 touches over 4 seasons, never above RB3 (Wikipedia career table, fetched 2026-07-08; 2024 values cross-checked against nflverse).

Efficiency: career 5.0 YPC is sample-size noise (99 carries, inflated by a 10.0 YPC rookie blip on 10 attempts). MTF/touch, YAC/att, RYOE: UNVERIFIED — no qualifying NGS season row (ngs_rushing.csv 2024 has no Strong entry) and no charting subscription data. Per rb.md §5 this is irrelevant anyway: never pay for efficiency without volume, and he has neither proven.

Pedigree (weighted up only when the NFL sample is thin — his is thin but *old*): 2022 R4 #127 (NE) — day-3 capital, and the decay rule voids it in year 5: "believe the NFL usage record, not the pick." Athleticism is real: 4.37 forty (fastest RB, 2022 combine), 9.66 RAS. College: SDSU (FCS) — 4,527 rush yds/40 TD in 48 games, ~57+ receptions 2019–21 (14/21/22), clearing the ≥40-reception three-down signal, with the required RAS ≥8 confirmation for FCS production (prospect-pedigree §4). Sources: nfldraftbuzz/RAS via search, Wikipedia, gojacks.com (fetched 2026-07-08). Four NFL seasons of RB3-or-worse usage have decisively overruled all of it. Age 27 (turns 28 Dec 2026; Sleeper 2026-07-07) — at the positional cliff age, though with ultra-low mileage (~125 pro touches), which softens the cliff but doesn't create opportunity.

Context (from data/team-profiles/GB.md, built 2026-07-07)

• Offense: LaFleur wide-zone/Shanahan tree — a genuine scheme fit for a one-cut 4.37 speed back — on a good offense (Vegas win total 9.5–10.5, positive script lean; ~27.5 rush att/g). This is why the *backfield* has value; it doesn't transfer to slot #4–5 on it.
• Depth chart (post-minicamp, SI 6/2026 + team profile): Jacobs (every-down, 13 rush TD in 2025) → Chris Brooks (top backup) → MarShawn Lloyd (2024 R3; two injury-lost seasons, ran behind Brooks all spring) → Strong ⟷ Damien Martinez (camp battle for a spot that may not exist) → Jaden Nixon. Strong and Brooks handled RB work in an OTA session Jacobs skipped (SI 6/2026) — depth-chart trivia, not a role signal.
• Contract: reserve/future deal signed 2026-01-12, one of 16 PS signings (heavy.com 1/2026) — the minimum-commitment contract tier; per rb.md §9 the team told you the plan.
• Jacobs legal flag: arrested May 2026 (five counts incl. felony strangulation), released without formal charges, Brown County DA still investigating, back at practice, NFL discipline possible (ESPN/NFL.com 6/2026). This is the one live volatility source above him — but the contingent value it creates flows to Brooks/Lloyd/Martinez, per the profile's explicit committee projection.
• Game script (§4 check): moot at zero snaps — but note even the positive-script lean (9.5+ win total) feeds Jacobs' clock-killing role, not the RB4.
• Roster math: projections carry three RBs; Strong's realistic path to the 53 is (a) Lloyd injured in camp, or (b) GB keeps four — and his KR speed under the current kickoff rules is his best special-teams argument for (b). 2024 depth charts listed him as CLE's KR.

Tripwires (re-run this eval if any fire)

• MarShawn Lloyd injury in training camp — the single event that puts Strong on the 53; re-run as GB RB3.
• Jacobs charged/suspended (Brown County DA decision or NFL discipline) — re-run the entire GB backfield; Strong only matters if tripwire 1 also fired.
• Preseason usage signal: Strong running two-minute/passing-down reps with the 1s or named KR1 — the earliest hard evidence of a roster lock (rb.md §9).
• Final cutdown (~2026-08-31): waived/PS → drop from all watchlists permanently; makes the 53 → re-check standalone role.
• Chris Brooks injured or traded — vacates the top-backup claim and reshuffles succession.