How do you convince non-technical stakeholders to slow down and fix backend issues?

Pushing fast to land early clients worked well for us at first, but rushing out features eventually caught up to us. Minor changes started taking weeks and random bugs kept popping up.

It was hard to get our business team on board with slowing down until we framed technical debt using a simple analogy. Comparing code maintenance to keeping a store organized helped them see why ignoring cleanup hurts speed in the long run.

What analogy or approach has worked best for you when asking non-tech partners for dedicated cleanup time?