Quote:
|
Quote:
|
Quote:
|
Quote:
I mean, feel free to argue it all day long that we should keep him but I'm 100% on the other side of that fence and not changing my position on it. If he is usable come playoff time, sign him to a short deal then. Otherwise, just use the 7.2m to get someone who can help the entire season. The only way I'd say keep him is if there is an injury guarantee I don't know about. |
Quote:
|
This. I saw enough of him to want him back. The injury may be a way for them to sweeten the deal enough to get him to extend a couple more years at a reasonable price without breaking the bank.
|
Quote:
|
Quote:
I hope that makes sense as to what I am trying to ask. |
Quote:
You'd get a good young player for a few more years at a potentially large discount (queue that one guy who lost his shit when they signed him to this deal flipping his shit again) while also getting a potential nice savings next year. Say they turn his 1/$10.5M cap hit into a new deal. Add two years to the deal and turn his $6.7M base into a $1.1M base and drop the 330k game bonus while giving him a $9M signing bonus over the course of those 3 years. He gets more cash in his recovery year, the Chiefs get him late in the season as a reinforcement for the playoff push for just $3M more, and you have him presumably at a pretty good price for his age 28 and 29 season as a core defender. The risk, I guess, would be that he's not available in 2024 at all. Or that he doesn't come back well in 25 and 26. Payoffs seem pretty nice, though. Is it worth a $3M gamble against the 24 cap? Is it worth more? I can see a route where, if they're confident in his recovery and his availability next year, KC decides to avoid a complete dead cap situation and save themselves a little in 24 (about $3M I guess, with the structure I'm discussing) to have him available at the end of the year and potentially at another discount in 25 and 26. Risk is that you end up throwing an extra $3M against the 24 cap and $6M against future caps down the drain if he doesn't come back right. |
Quote:
|
And re: Mahomes restructuring...
Any year KC can avoid a big restructure of his deal is a good one because it gives them future flexibility. But the current deal is kind of structured in a way that if they start restructuring, they can continue to avoid the painful one-year cap hit by continuing to restructure and push money forward over five years until he hits a season where his base salary is low enough the restructure bonuses are no longer an issue. The next 4 seasons are the "Big" hits in Mahomes' current deal. KC could easily keep moving big portions of his roster bonus forward every year and pay off the CC in 2028, when his cap hit is currently scheduled to drop below $30M. If you look at the contract, it's pretty clear they were building in 2028 as an out. 2024 restructure: $35M, pushing $7M in each year to 25, 26, 27, 28 New 24 cap hit: $29m New 25 cap hit: $68M 2025 Restructure: $35M, pushing $7M in each year to 26, 27, 28, 29 New 25 CAP HIT: $40m New 26 cap hit: $77M 2026 restructure: $40M, pushing $8M in each year to 27, 28, 29, 30 New 26 cap hit: $42M New 27 cap hit: $82M 2027 restructure: $40M, pushing $8M in each year to 28, 29, 30, 31 New 27 cap hit: $47M Restructures in 28 due: $23M Restrucutres in 29 due: $23M Restructures in 30 due: $16M Restructures in 31 due: $8M And that's the plateau where you probably do his final contract. He'll be 33. You've got some money pushed forward in restructures you still have to pay off. But you have the flexibility to design the last contact in a similar way, a nice 7-or-8-or-10 year long deal that lets you continue to flexibly push money forward as needed. |
Quote:
|
I'm in on the bargain extension for Omenihu. It would be a great deal for the team moving forward.
|
Quote:
|
Quote:
Trigger the option in 2025 over, say, a 3-year extension while re-writing 2024 to vet minimum and performance escalators would be most ideal. You can still then free up 5-ish million. |
All times are GMT -6. The time now is 05:28 PM. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2024, vBulletin Solutions, Inc.