Events like The Southwest Car Wash Association Expo bring with them plenty of opportunities for chance encounters with acquaintances from around the industry. Not just on the show floor, but running into other car wash operators at dinner or over drinks around Fort Worth is just part of it. And those conversations, as they always seem to, eventually drift toward work. Comparing notes. Sharing stories. Talking shop.
This year, one of those conversations stuck with me.
I ran into an operator I’ve known for a while. He is someone running a solid business, clearly on top of things. They have strong culture, clean sites, and a growing membership program. We grabbed drinks, caught up, and eventually landed where we always do: talking about what’s working, what isn’t, and what’s quietly eating away at the business when no one’s looking. The “leaky buckets” as we’ve come to call them.
He mentioned offhand that his team had just finished their monthly reporting push. The way he said it, a kind of weary exhale, made me ask a follow-up question.
“What does that process actually look like?”
He walked me through it. And about halfway through his answer, something clicked for both of us at the same moment. This wash was losing time every single week. And nobody had ever called it that. It wasn’t obvious. It didn’t show up on a balance sheet. It wasn’t called out in KPIs or discussed in meetings. Yet it was directly tied to all of those things.
It was hiding in the way their data lived; scattered across siloed systems, locked behind portals, or accessible only on someone else’s timeline.
Each month, as the team prepared for reporting and leadership meetings, managers and key personnel were spending hours, sometimes the equivalent of an entire working day or more, just collecting data from different systems to get to something usable.
Not analyzing it. Not acting on it. Just assembling it and in some cases cleaning it.
Some data was easy to get. Some is prohibitively complicated. Some was gathered from a web portal. Some was only accessible with a request to a provider.
Exports from the POS. Membership data from another platform. Transaction logs pulled separately. Attendant commissions tracked on a spreadsheet, hand keyed from paper receipts. Revenue numbers that needed to be reconciled across systems that didn’t quite speak the same language.
Spreadsheets layered on spreadsheets. Tabs built to translate one dataset into another. Someone always responsible for “tying it all together.”
And every time, it took longer than it should.
By the time the team actually sat down to review performance, they were already behind. Not because they lacked discipline or care, but because the process itself demanded it. The problem was, staff just accepted it as the status quo. These reports were legacy. The metrics were key to the business. The team simply assumed that this was how it was done.
That’s when the real cost became clear.
This operator wasn’t losing time in big, dramatic ways. There wasn’t a broken process that everyone could point to. No single failure to fix.
They were losing time in fragments, and it didn’t just stop at the monthly meeting. Area Managers were burning valuable time pulling together KPIs for weekly meetings. Site Leads were burning valuable time calculating data for daily standups.
An hour here. Two hours there. A half day at the end of the month. A full day leading into a leadership meeting. Each instance felt reasonable on its own. Necessary, even.
But stacked together, it was days. Every single month. Across nearly every level.
Days spent not improving the business, but trying to understand it.
And the most dangerous part? None of this shows up cleanly anywhere. There’s no line item for “time spent stitching together data.” No KPI for “manual reporting fatigue.” No alert that tells you your team is buried in exports instead of making decisions.
From the outside, everything still works. Reports get built. Meetings happen. The business moves forward.
But underneath, there’s drag.
Decisions take longer. Insights arrive late. Opportunities sit unnoticed until they’re no longer opportunities. Teams spend more time looking backward than moving forward.
In that moment, my friend recognized the problem clearly, and what it would take to solve it. What AMP changes isn’t just where your data lives. It changes how quickly you can move once you have it, how easily it can be accessed, understood, studied, and shared.
When your systems are connected, reporting stops being a monthly scramble. Conversations start with clarity instead of cleanup. The time that used to be spent gathering information gets redirected toward using it.
Patterns show up sooner. Problems surface earlier. Opportunities become visible while they’re still actionable.
And maybe most importantly, your team gets their time back. Not in theory. In hours. In days.
The kind of time that never appears on a report, but quietly determines how fast your business can actually grow.
I’m happy to report that this friend is in the early stages of bringing the AMP proposal to his team to develop a transition plan and a path to taking their time back.