3 reasons the Buffalo Bills should not sign Dalvin Cook if released

Dalvin Cook, Buffalo Bills
Dalvin Cook, Buffalo Bills / Stephen Maturen/GettyImages
1 of 4

As the door appears to close on the idea of the Buffalo Bills adding wide receiver DeAndre Hopkins, the rumor mill picks right back up around another former Pro Bowler. According to Armando Salguero of Outkick, if the Minnesota Vikings were to release Dalvin Cook he has two teams that are at the top of his list for his next team, which includes the Buffalo Bills as well as division rival Miami Dolphins.

The two teams certainly make sense from Cook's perspective as he would have a chance to play with his brother, James Cook, in Buffalo or return to his hometown to play for the Dolphins.

Dalvin Cook has been with the Minnesota Vikings for the entirety of his NFL career after they drafted him in the second round of the 2017 NFL Draft. He is currently in the midst of a streak of four straight seasons with over 1,000 rushing yards and four Pro Bowl nominations.

On the surface, adding Dalvin Cook if he were cut would make sense for the Buffalo Bills as well. They have not gotten much from their run game over the year and an established running back like Cook could certainly help.

However, there are a number of reasons that adding Dalvin Cook doesn't make sense and the Buffalo Bills should look to move forward with their current group of running backs on the roster.