Mud Bay, a 45-store pet retail chain, had made a deliberate strategic bet: pay employees more, price below competitors, and let a better customer experience drive the growth that would eventually justify the added cost. Sales had grown under that strategy. Profit margin hadn't. Now the COO wanted to close stores an hour early each night, arguing the last hour was quiet enough that the labor savings would outweigh the lost sales. One co-CEO backed the idea. The other didn't, worried the hour mattered more to the brand than the numbers suggested.
Central question
When a cost-cutting proposal fails its own math, is the right response to reject the idea outright, or to separate the flawed justification from the underlying need it was trying to address?
Key ideas
Before building any framework, I asked for the actual economics, Mud Bay's revenue model and cost structure, not just the strategic story around them. That's the right instinct in any case, regardless of industry: a labor-versus-revenue tradeoff can't be reasoned through without knowing the real numbers on both sides of it.
The math settled the surface question cleanly. Revenue at risk in the final hour came out to $8,700 a day. Labor cost saved by closing early came out to $1,531.80 a day, a roughly 5.7x gap, and a direct contradiction of the premise the COO built the proposal on. The "dead hour" wasn't dead. It was quieter than the rest of the day, which is a very different thing from being unprofitable to staff.
The harder part of the case was what that final hour of revenue actually represented. A meaningful number of people were choosing to shop specifically between 8 and 9pm, and the honest question is why. For some, it's likely the only window that fits their schedule at all. Cut it, and the loss isn't just that day's sale, it's potentially the customer who structured their routine around being able to shop then, permanently, to whichever competitor stays open. That's a brand-accessibility risk sitting directly on top of a financial one, and it doesn't show up cleanly in a same-day revenue comparison.
There's a second layer on the employee side. Part of Mud Bay's whole strategic bet was that better-treated staff deliver a better customer experience. If closing early is genuinely what employees want, there's a real version of this decision that supports the company's own stated values rather than undercutting them, the problem is using flawed labor-savings math to justify it, when the actual numbers show that savings is the smaller side of the ledger by a wide margin.
My synthesis
Don't close the store early, not because employee scheduling doesn't matter, but because the numbers used to justify the change don't hold up, and the customer-accessibility risk on the other side is larger and harder to reverse than a $1,500-a-day labor line. If Mud Bay wants to genuinely address quality of life for staff, that's worth solving directly, through scheduling flexibility or shift design, rather than by quietly cutting an hour of access a real, measurable slice of customers depend on.
Questions I still have
How often does a cost-saving proposal get evaluated only against the cost it removes, without pricing the specific revenue it puts at risk? And is there a general rule for when a quiet period is genuinely safe to cut versus when its low volume is disguising a customer segment with no other option?
Final perspective
The recommendation isn't a rejection of the underlying concern, it's a rejection of using flawed math to justify it. If the goal is genuinely to protect employee time, that's worth solving directly, rather than by quietly cutting an hour of access a real, measurable slice of customers depend on.
If you'd like to read more about the case, here it is: Mud Bay's Good Jobs Journey, MIT Sloan case (PDF)