Skip to main content

Why Bills Signing Dalvin Cook Would Make Sense

The Buffalo Bills are already being discussed as a candidate to sign Pro Bowl running back Dalvin Cook, who is set to be released by the Minnesota Vikings.

The Buffalo Bills are potentially interested in both of the NFL's hottest free agents:  receiver DeAndre Hopkins, formerly of the Arizona Cardinals, and the most recently-released running back, Dalvin Cook.

The Minnesota Vikings' release of Cook was a long time coming after an offseason where rumors of their parting of ways made headline news. After being unable to trade him due to his large contract, the Vikings informed Cook on Thursday that they plan to release him.

Immediately, the Bills are being mentioned as a team who could sign him. But does this linkage between Buffalo and Cook even make sense? 

Cook, 27, was the lead back in Minnesota from the moment he was drafted in the second round of the 2017 NFL Draft out of Florida State. He rushed for over 1,000 yards in 2022, his fourth-straight season doing so. A 1,000-yard rusher is something the Bills haven't had since LeSean McCoy back in 2017.

Despite making additions this offseason at the position by signing Damien Harris and Latavius Murray to compete with James Cook, the young brother to Dalvin, it doesn't seem the Bills have a true No. 1 back.

The same argument about why Buffalo should sign Hopkins can be used in favor of Cook. The addition of Cook gives quarterback Josh Allen another weapon to utilize, along with making defenses have to respect the running game. When the Bills needed their running game against the Cincinnati Bengals in the playoffs, they could never get going, averaging just 3.4 yards per carry. 

What better way is there for the Bills to improve one of their remaining weaknesses on offense than by signing an elite back like Cook?


Thanks for reading our SI-powered coverage of your Buffalo Bills ... Bills Mafia!

Follow Harrison Reno on Twitter

You're a member of Bills Mafia hungry for more Buffalo coverage? Read here.