Royals Urged To Immediately Cut Ties With $13 Million 10-Year Old-timer

Royals Urged to Cut Ties with $13 Million 10-Year Veteran Immediately

It’s becoming increasingly difficult to justify keeping certain players on the Kansas City Royals roster, especially in their struggling outfield.

Jonathan India has had a rough season trying to adjust to left field. Kyle Isbel, as usual, has struggled to hit. MJ Melendez was sent down to Triple-A due to his poor performance at the plate, and Drew Waters, who started strong after his promotion, has since faltered.

However, one outfielder stands out for his damaging performance: Hunter Renfroe. The 10-year MLB veteran, who exercised his 2025 player option for a two-year, $13 million deal, has been shockingly ineffective.

In 30 games and 92 plate appearances, Renfroe has posted a disastrous slash line of .167/.228/.202, with an OPS+ of just 24. His subpar defense in right field only adds to his struggles. All of this has resulted in -1.1 fWAR, making him the least valuable player in MLB this season.

FanSided’s Tremayne Person suggested on Monday that the Royals should cut ties with Renfroe immediately, even if it means absorbing the remaining $7.57 million of his 2025 salary.

“Some may argue that the Royals lack depth in the outfield and can’t afford to part with a veteran like Renfroe,” Person wrote. “But that argument only holds the franchise back. Keeping an unproductive player just because there’s no clear replacement is poor roster management.”

Person makes a compelling point: each at-bat Renfroe takes could be an opportunity to develop younger players or fringe prospects like Waters, Nick Loftin, John Rave, or Joey Wiemer. These players have spent too much time in Triple-A while Renfroe occupies a roster spot.

At this point, keeping Renfroe isn’t about hoping he finds his form; it’s about avoiding the reality of swallowing the cost of his contract. But as Person notes, the contract is already a sunk cost, and holding onto Renfroe is a losing strategy.

Be the first to comment

Leave a Reply

Your email address will not be published.


*