No, Cam Newton should not be the Chiefs backup quarterback

Nick Wright says the Kansas City Chiefs should call on Cam Newton to be their backup quarterback.

Listen, Nick. I love your work. You’re a great Kansas City guy. But, come on. This take?? It’s awful.

Cam Newton? Really? We all saw how that experiment worked out in New England with the Patriots and then in 2021 with the Carolina Panthers—again.

In New England, in 15 games, Newton threw for 2,657 yards and 8 touchdowns on 242 completions—not to mention 10 interceptions. In Carolina, in 8 games, he threw for 684 yards and 4 touchdowns on 69 completions—and 5 picks.

Is this backup quarterback material? Absolutely. But, that’s not how Newton views himself. When announcing that he would be throwing at Auburn’s Pro Day on Tuesday, he said, “How these randoms keep getting jobs? … Ain’t 32 motherf–kers better than me.”

To that I say: Newton is right. There aren’t 32 QBs better than him. That number is too low. He wants to be a starter, not a backup. But, to find a starting position, he may have to look a to the XFL, USFL, or even FCF.

If Cam Newton could be more realistic and less egotistic, I would be on Nick Wright’s side here, but Newton is way too full of himself. I would prefer someone like former Los Angeles Chargers quarterback Chase Daniel. Sure, he’s on the older end, but a homecoming for the former Mizzou Tiger would be a fitting final destination for the veteran QB.

I love Nick Wright. But this is one of his worst takes. There are better options for backups out there. Even sticking with Shane Buechele would be a better option than going with Cam Newton. There’s no way around this being a terrible idea for the Kansas City Chiefs.