MBA·LAB·10Phase 01, Pre-MBA

Mud Bay and the Hour That Wasn't Actually Dead

August 23, 2026·4 min read

How I work these cases: Before my MBA starts, I'm practicing the case method on my own. I give an AI a business case and ask it to release the details in stages, the way a class discussion unfolds. I give my read at each stage without looking anything up. Then the real outcome is revealed and I compare it with my reasoning. I call this working a case cold. These posts are my write-ups.

Mud Bay, a 45-store pet retail chain, had made a deliberate strategic bet. It would pay employees more and 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, but profit margin had not. Now the COO wanted to close stores an hour early each night. His argument was that the last hour was quiet enough that the labor savings would outweigh the lost sales.

One co-CEO backed the idea. The other did not, worried that the hour mattered more to the brand than the numbers suggested.

Central question

When a cost-cutting proposal fails its own math, should I reject the idea outright, or 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. A labor-versus-revenue tradeoff can't be reasoned through without the real numbers on both sides.

The math settled the surface question. Revenue at risk in the final hour was $8,700 a day. Labor cost saved by closing early was $1,531.80 a day. That is a gap of roughly 5.7 times, and it contradicts the premise the COO built his proposal on. The "dead hour" was not dead. It was quieter than the rest of the day, which is different from being unprofitable.

The harder question was what that last hour of revenue represented. A meaningful number of people were choosing to shop between 8 and 9pm, and the question is why. For some, it is probably the only window that fits their schedule. If the store closes, the loss is more than that day's sale. It could be a customer who built a routine around that hour and now shops at whichever competitor stays open, permanently. That is a risk to customer access sitting on top of a financial one, and it doesn't show up in a same-day revenue comparison.

There is also a second layer on the employee side. Part of Mud Bay's strategy was that better-treated staff deliver a better customer experience. If closing early is what employees want, there is a version of this decision that supports the company's own values. The problem is using flawed labor-savings math to justify it, when the savings are the much smaller side of the ledger.

My synthesis

Don't close the stores early. Employee scheduling matters, but the numbers used to justify the change don't hold up, and the risk to customer access is larger and harder to reverse than a $1,500-a-day labor line. If Mud Bay wants to improve quality of life for staff, it should solve that directly, through scheduling flexibility or shift design.

Questions I still have

How often is a cost-saving proposal 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 safe to cut and when its low volume is hiding a customer segment with no other option?

Final perspective

I'm not rejecting the underlying concern. I'm rejecting the use of flawed math to justify the change. If the goal is to protect employee time, that is worth solving directly, not by cutting an hour of access that a measurable group of customers depends on.

If you'd like to read more about the case, here it is: Mud Bay's Good Jobs Journey, MIT Sloan case (PDF)