KC Chiefs should say no thanks to signing Emmanuel Sanders
Emmanuel Sanders is a free agent, but the KC Chiefs shouldn’t be interested in signing him.
To the surprise of no one, the Saints released Emmanuel Sanders to clear up cap space, and now the wide receiver is a free agent once again. While Kansas City Chiefs fans might have an interest in bringing him in to catch passes from Patrick Mahomes, I’ll remind them of when Sanders burned this franchise hard.
The year was 2014 and the Chiefs were in search of a WR2 to put alongside Dwayne Bowe. They thought they had found their guy in Emmanuel Sanders, but lo and behold, last minute, Sanders signed with the AFC West-rival Broncos instead. He went on to have a great three years in Denver and won a Super Bowl with the Donkeys in the 2015 season.
Sanders’ time in Denver didn’t end great, as he was traded to the 49ers, but he went to the Super Bowl with them and lost to the Chiefs. Heh.
Saints are releasing WR Emmanuel Sanders, per source.
— Adam Schefter (@AdamSchefter) March 10, 2021
Sanders didn’t want to come to Kansas City in 2014, so why should the Chiefs give him a shot at a redo now? He spurned them hard seven years ago and while some might say Chiefs fans should get over it after winning a Super Bowl title of their own, I’m still not over it and I certainly don’t want the Chiefs to sign this guy after he essentially gave them the middle finger and then taunted them over the next three years.
More from Chiefs Free Agency
- The Kansas City Chiefs Address Defense with This Mock Draft
- Three Cornerbacks the Chiefs Should Pursue in Free Agency
- What Potential Free Agents Could Sign with the Kansas City Chiefs
- Kansas City Chiefs Should Look at These Free Agent Edge Rushers
- The Chiefs Begin the Offseason. What Can We Look Forward To?
Emmanuel Sanders didn’t want to play with the KC Chiefs before, so don’t let him sign with them now.
Sanders hasn’t indicated that he wants to come to Kansas City, which is worth mentioning, but if he does list them as a team he’d like to sign with (or there become rumblings of interest on either side), then the Chiefs should remind him that he had a chance to be a Chief in the past and decided to screw them over instead. Yes, the team was in a totally different place at that point in time and it’s hard to think Sanders wouldn’t want to catch passes from Patrick Mahomes, but too bad.
This is a strong level of pettiness, I’m well-aware, but Sanders really made things worse than they needed to be in 2014 and I haven’t forgiven him for it. He’s also going to turn 34 years old next week and the Chiefs can get a cheaper option for their WR2 either in free agency or the draft and that’s a better bet than signing Sanders.
Next. Why Losing Sammy Watkins isn't a Big Deal. dark
The Kansas City Chiefs have been to two Super Bowls, winning one, since the Sanders ordeal, but I’ll never forget what he did to this organization. Hopefully, the Chiefs don’t even feign interest in him on the open market.