Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How One Parking Garage Cut Revenue Leakage 25 Percent
Transcript
- Lucas: So there's this mid-sized airport parking garage, about twelve hundred spots, that was quietly losing twenty-five percent of its revenue. Not to theft, not to fraud — to a mismatch between two sensors. Luna: A sensor mismatch? That sounds like something out of a systems engineering textbook. Lucas: Right, but it's exactly the kind of thing that happens in real operations. The garage has two separate systems: one that counts cars entering and leaving, and another that handles payment at the exit kiosk. They were built by different vendors, and nobody had ever checked that they agreed with each other. Luna: So how did they figure out they were losing a quarter of their revenue? Lucas: They did a simple audit. They took a week of transaction data — entry timestamps, exit timestamps, payment amounts — and compared it to the vehicle counts from the loop sensors at the gate. What they found was that about one in four cars that entered never triggered a payment transaction on the way out. Luna: Wait, so the gate opened and let them out without charging? How does that happen? Lucas: That's the thing — the exit kiosk's license plate camera and the payment system were out of sync. If a driver pulled up slightly too far, the camera would read the plate from the wrong angle, the system would think it was a different car, and the gate would lift without a valid payment. The car drives away, and the system logs it as a 'grace exit' or just drops it entirely. Luna: So the revenue leak wasn't malicious — it was a design flaw. And they probably had no idea it was happening for months. Lucas: Exactly. And that's the scary part. They only caught it because someone decided to do a deep dive into the numbers. The garage manager told me they used to look at daily revenue totals and think everything was fine. It was only when they broke it down by hour and compared to gate counts that the pattern jumped out. Luna: So what was the fix? Did they replace the cameras? Lucas: They didn't need to. The fix was much cheaper. They recalibrated the camera angle and added a secondary verification step — if the license plate read fails, the system now prompts the driver to enter their plate manually on the kiosk screen. That alone closed the gap. Within a month, revenue was up twenty-five percent with no change in traffic. Luna: That's a massive win for a tiny tweak. It reminds me of that hospital that cut readmissions with a single text message. Lucas: Right, same pattern. One small change, big impact. But what I love about this case is the audit itself — it's a template any business with a payment step can use. If you have an entry point and an exit point, and they're not reconciled, you're probably leaking revenue too. Luna: So walk me through the checklist they used. I want to steal this for my own business. Lucas: Sure. Step one: pick a time window — a week is good, ideally one that's not a holiday. Step two: pull all your transaction records for that window. Step three: pull your independent count data — that could be door sensors, ticket stubs, point of sale scan counts, whatever measures actual volume. Step four: compare the two line by line, looking for gaps where the count says something moved but there's no corresponding transaction. Luna: And that's the hard part, right? Because it's not always a one-to-one match. Some transactions are legitimately free — like a validation stamp or a comped ticket. Lucas: That's exactly why you need to categorize the gaps. They classified every discrepancy as either 'explained' or 'unexplained'. Explained gaps include things like grace periods, maintenance, or staff parking. Unexplained gaps are your leak. In this garage, the unexplained gaps were almost all the plate-read failures. Luna: So the key is not just finding the discrepancy, but understanding why it exists. Otherwise you might fix the wrong thing. Lucas: Right. And they also found a second, smaller leak: about three percent of revenue was lost to what they called 'undercharges' — cars that stayed longer than the prepaid time because the system didn't check the exit time properly. The manual-entry fix actually solved that too, because the system now recalculates at the exit. Luna: I like that they didn't just patch the symptom. They found the root cause and fixed the whole category. Lucas: And the best part? The whole audit took two people about three hours. No consultants, no fancy software. Just a spreadsheet and a willingness to question the numbers. Luna: That's the kind of story that makes me want to go audit my own billing system. But before that, I have to ask — how common is this? Is every parking garage leaking twenty-five percent? Lucas: No, not every one. But industry studies suggest revenue leakage in parking operations can range anywhere from five to fifteen percent on average. This garage was on the high end because of the sensor issue, but even five percent is significant if you're running a thousand spots at forty dollars a day. Luna: That's real money. And it's not just parking — think about any business where a customer enters and exits: car washes, gyms, even subscription services where the billing system checks membership status at the door. Lucas: Exactly. The principle is universal: if you have a system that's supposed to capture a transaction at a specific moment, and that system relies on any kind of sensor or manual input, there's a chance for failure. The question is whether you've verified it. Luna: So what's the takeaway for our listeners? Should they all drop everything and run a revenue audit tomorrow? Lucas: I'd say start with one payment point. Pick the one that generates the most revenue, and run the comparison for a single day first. If you see even a one percent gap, it's worth digging deeper. The cost of the audit is tiny compared to the potential recovery. Luna: And honestly, this episode is a perfect example of why we do this show. These small, concrete wins are what make a real difference in day-to-day operations. Lucas: Absolutely. And if today's episode moved your work forward in some small way, you know the drill — buy me a coffee dot com slash fexingo. It's a tiny way to keep this thing ad-free and independent. Luna: Yeah, every little bit helps us keep bringing you stories like this. Lucas: So back to the parking garage — after they fixed the camera angle, they didn't just stop there. They set up a monthly reconciliation ritual. Every first Monday, they compare the previous month's gate counts to payment records. Luna: That's smart. It turns a one-time fix into a habit, so any new leak gets caught fast. Lucas: Exactly. And they even expanded it to their two other lots. The second lot had a similar but smaller leak — about eight percent. The third one was clean. But now they know, and that peace of mind is worth something. Luna: I love that they applied the same audit across all locations. It's a great example of scaling a fix. Lucas: And the numbers speak for themselves — the company's overall revenue is up about twelve percent just from these audits, with no increase in expenses. That's a direct boost to the bottom line. Luna: So if there's one thing to remember from today's episode, it's that revenue leakage is often hiding in plain sight, and a simple audit can uncover it. Lucas: Right. And the fix might be as simple as a sensor calibration or a manual fallback. Don't assume your systems are working just because they're digital.