KC Chiefs: C.J. Spiller Will Not Add Anything to Chiefs Offense

Oct 15, 2015; New Orleans, LA, USA; New Orleans Saints running back C.J. Spiller (28) against the Atlanta Falcons during the second half of a game at the Mercedes-Benz Superdome. The Saints defeated the Falcons 31-21. Mandatory Credit: Derick E. Hingle-USA TODAY Sports
Oct 15, 2015; New Orleans, LA, USA; New Orleans Saints running back C.J. Spiller (28) against the Atlanta Falcons during the second half of a game at the Mercedes-Benz Superdome. The Saints defeated the Falcons 31-21. Mandatory Credit: Derick E. Hingle-USA TODAY Sports /
facebooktwitterreddit

The KC Chiefs signed running back C.J. Spiller to a contract on Friday morning. While the news of signing anyone at a key position tends to excite fans, don’t get too amped up about this one, Chiefs Kingdom. It’s going to result in nothing.

Any time the Kansas City Chiefs sign anyone, fans immediately look up that guy’s stats and ooh and aah where needed. In the case of signing of C.J. Spiller, a lot of fans seemed puzzled by the move.

There were some who were likely questioning if this meant that the Chiefs were officially going to move on from Jamaal Charles (tweet below), but I’m here to tell you that this move won’t be a very effective free agent signing.

Spiller, a first-round draft pick by the Bills in 2010, hasn’t lived up to that first-round hype. He’s spent the last three seasons with four different teams and has only had one good season as a pro NFL running back.

That season saw Spiller take the football 207 times for 1,244 yards and six touchdowns. He’s been a bust ever since then and this signing will likely not evolve into much of anything.

More from KC Kingdom

It’s no secret that the KC Chiefs need a new running back moving forward. Charles is aging and was banged up all of last season, Spencer Ware and Charcandrick West disappointed in 2016, and Knile Davis is not even in discussion when it comes to that starting job in the future.

With a draft class that’s deep with running backs, the Chiefs will likely turn to the 2017 NFL Draft to find their future franchise running back. C.J. Spiller is not going to be that.

During his tenure with the New Orleans Saints, a team that inked him to a four-deal deal before 2015, Spiller only started two games and lasted one full season there.

Matt Conner of Arrowhead Addict said it best in regards as to what this signing means,

"At this point, the signing of Spiller is more about curiosity than anything, a longing to simply look closer at a player to see what might be left. It does nothing to really address the concerns at running back and should not preclude the Chiefs from making further moves to bolster the position in the upcoming NFL Draft."

Couldn’t have said it any better myself.

Next: 30 Best Free Agent Signings in Chiefs History

Spiller has been incredibly injury prone during his time in the NFL and that’s never something a team wants in its running back corp. I’ll be shocked if C.J. Spiller ends up making any type of impact for the Kansas City Chiefs come the regular season.

What do you make of this signing, Chiefs Kingdom? Will C.J. Spiller end up doing anything as a member of the Chiefs or will he be a failed signing?