Jump to content
  • Welcome!

    Register and log in easily with Twitter or Google accounts!

    Or simply create a new Huddle account. 

    Members receive fewer ads , access our dark theme, and the ability to join the discussion!

     

Bill Barnwell on Matt Kalil roster status


TheSpecialJuan

Recommended Posts

Just now, LinvilleGorge said:

How? You're still going to have to pay him an additional $7M. His dead cap is just that. There's no way to get to the it back. It'll hit us no matter what. That's a terrible excuse to throw good money after bad.

who cares about getting it back if you arent going to use it. 

Link to comment
Share on other sites

Honestly, I was intrigued by his potential. I really thought playing with his big brother would light a fire under him - that's like a dream scenario. Oh well. We live and we learn. 

The only way I'd keep him on the team at this point is if he was seriously being considered as a starter at LG. No other reason to throw away an additional 7.25M for a bench warming backup. 7.25M is not backup money - not even for QBs. 

And as I say that, I remember the team is currently on the hook to pay 5M to a #4 WR

Link to comment
Share on other sites

9 minutes ago, ericr0319 said:

this is my take - if we do not plan on making any other moves than it is better to keep him. 

cuttin him (post june 1) saves us 7.25 mil, but cost us 9.8 next year. if we arent spending that 7.25 this year, pay him

if we cut him next year (post june 1) saves us 11 mil next year and only cost is 4.9 the following. 

 

if he is on the roster it doesn't mean he has to start. he is good DEPTH. need depth on the oline. yes i dont like paying someone that kind of money for depth, but keeping him this year is better for us next year, especially if we are done with big splashes in FA. he has no future on this team and we could still draft OL in the 1st round. 

but that 7.25m could roll over even if you don't use it.

Better way to look at it, if you cut him this year you have to account for $14.7m in dead money.  Wether you want to spread it out with a June 1st cut is irrelevant to the point i'm making.

If you keep him for one year and release him next year you will have to account for $21.95m in cap space.

What is the better deal?

One year of Kalil playing at $21.95m

or

Zero years of Kalil playing at $14.7m

The only question that really should matter is, "is his expected production worth $7.25m?"

If not you release him.

Link to comment
Share on other sites

15 minutes ago, ericr0319 said:

this is my take - if we do not plan on making any other moves than it is better to keep him. 

cuttin him (post june 1) saves us 7.25 mil, but cost us 9.8 next year. if we arent spending that 7.25 this year, pay him

if we cut him next year (post june 1) saves us 11 mil next year and only cost is 4.9 the following. 

 

if he is on the roster it doesn't mean he has to start. he is good DEPTH. need depth on the oline. yes i dont like paying someone that kind of money for depth, but keeping him this year is better for us next year, especially if we are done with big splashes in FA. he has no future on this team and we could still draft OL in the 1st round. 

Yeah I'm down with that,  hes good depth unless he goes down again costing the team $ and a hole on the line.

I was skeptical when we signed him, but was hoping for the best......

 

 

Link to comment
Share on other sites

There is no good solution on this and why it is so difficult to make a decision. Any decision the Panthers make on Matt Kalil, is a bad one because of the contract.

 I don’t guess there’s any chance that he would be willing to give the Panthers a break.  

Link to comment
Share on other sites

11 minutes ago, LinvilleGorge said:

How? You're still going to have to pay him an additional $7M. His dead cap is just that. There's no way to get to the it back. It'll hit us no matter what. That's a terrible excuse to throw good money after bad.

If we aren't going to use all our cap room this season, there's no point in cutting him now. Waiting a year makes the cap hit reduced the next two after that. This provides us more cap space to work with next year than if we June 1st him this year. 

Link to comment
Share on other sites

He should be, and I expect he will be, gone as a June 1st designation at some point. Better to eat the hit now and have extra money to roll over or spend than wait a year and eat more later. As others have pretty much said.

Link to comment
Share on other sites

1 minute ago, Cracka McNasty said:

He's owed, what, roughly $15 million more?

Pay half this year.

Cut him next and spread the remaining 7.5 over two years at 3.25 each between 2020 and 2021. 

If we aren't going to use all our cap room this season, there's no point in cutting him now. Waiting a year makes the cap hit reduced the next two after that. This provides us more cap space to work with next year than if we June 1st him this year. 

If you aren't using that cap room this year, you can roll ot over and have it largely negative his dead money next year. We can move on right now if we want to do it and we absolutely should.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...