Justin Houston: Why The All-Pro LB Might Leave The Kansas City Chiefs
By Nick Floyd
Oct 26, 2014; Kansas City, MO, USA; Kansas City Chiefs outside linebacker Justin Houston (50) celebrates after sacking St. Louis Rams quarterback Austin Davis (9) (not pictured) during the second half at Arrowhead Stadium. The Chiefs won 34-7. Mandatory Credit: Denny Medley-USA TODAY Sports
Well, “Franchise Tag Monday” has come and gone, and there were no surprises from the Kansas City Chiefs.
The club was the first out of the gate to tag a key player, and their choice was elite pass-rusher Justin Houston. Houston, who was offered a substantial raise at just over $13 million, now has until July 15 to get a long-term deal done. Otherwise, history may end up repeating itself (to the tune of 120 percent more than this year’s salary).
Houston is coming off his best year in the Chiefs defense, almost surpassing the NFL record for sacks with 22. Obviously, he deserves a huge payday—and rightfully so. Houston, along with Tamba Hali and Dontari Poe, anchored the Chiefs pass rush in 2014. It was thought that a possible deal was in the works at the beginning of 2014, but the two sides could not agree to terms. Now that he has been franchised, it would seem that a deal could still be possible if Kansas City is able to clear some cap room.
The most interesting thing isn’t that they franchised Houston, but how. Using the non-exclusive tag allows Houston to talk with other teams. If he is able to find something he likes, the Chiefs will have the option to match the contract. If no deal for the Chiefs can be reached, the signing team will have to give up two first-round picks in compensation. The non-exclusive tag also offers more cap relief than its exclusive counterpart.
While no one in the Chiefs Kingdom wants to see Justin go to another team, especially not one in the AFC West, there is a possibility that he may. The biggest problem the Chiefs and Houston face is the amount of money he wants. Rumors are abound that he is wanting a deal similar, if not beyond, what Texans star JJ Watt received. Now that he has been franchised, Kansas City once again finds itself over the cap and will need to clear another $2.9 million-plus, per Spotrac, just to fit under the ceiling. Unless the Chiefs are able to do some much-needed restructuring of a few overpaid players (Dwayne Bowe), we’re going to see a few more cap casualties.
There are some benefits for the Chiefs if Houston leaves.
Now, before everyone gets angry, let’s explore what these might be.
General manager John Dorsey loves himself some draft picks, and getting two first-rounders is a little intriguing, even if they are lower picks. If the Chiefs secure the first-round picks, there is a slight chance that they’ll use them to move up in the draft.
Another reason why Houston’s departure may not be bad is the fact the Chiefs have a replacement waiting in the wings. Dee Ford sat behind Hali and Houston all year, hopefully soaking in the information and the experience from the two veterans. Don’t forget Ford, out of Auburn, was compared to another elite pass-rusher in Denver’s Von Miller. Yes, Hali is getting old and has been susceptible to injuries as of late, but how much of Houston’s production was based on having Tamba on the other side?
Ideally, the Chiefs will work out a deal with No. 50. However, there are other players whom they need to focus on besides Houston—players who want longer deals.
But even if the sky turns dark and Houston walks, it won’t be the end of the Chiefs’ dominant pass rush, it will just be a change.
What do you think, Addicts? Is Houston gone? What will it take for the Chiefs to hang onto him?
Sound off below.
Go Chiefs!
Next: Could Justin Houston Become A Salary-Cap Casualty?