TransWealth Fleet & Parking Management runs valet operations that move a daily average of 302 cars. In Q1 2026 they faced the question every operations manager dreads asking out loud: if we cut the driver roster by 47.5%, does service actually survive?
They brought me in as a freelance data analyst to answer it with arithmetic instead of instinct. The deliverable wasn't a dashboard — it was a management review report a leadership team could act on, with the math shown.
The question under the question
Headcount decisions usually get argued with anecdotes — the one bad Saturday, the one idle Tuesday. The real question is structural: how many cars can a smaller team actually move, hour by hour, before quality slips? That's a capacity-modelling problem, and it has a numeric answer.
Four steps from gut feeling to defensible number.
Demand traced from real daily volume, the reduced roster's throughput modelled from cycle times per station, then the model pushed past reality until something broke.
The model runs in Python; the deliverable lands in the format management already reads.
Every scenario is anchored to the operation's actual daily average, not a hypothetical.
What the model said
The headline finding was blunt: even after cutting nearly half the drivers, the remaining team's throughput clears more than 2.5× the current daily demand. The reduction wasn't a gamble — the old roster had been sized for a peak that the data says never arrives.
The reduced team could absorb 2.5× today's volume before service quality degrades — the staffing cut wasn't a risk to defend, it was over-capacity finally measured.
But the model also found the failure point nobody was arguing about. Cars don't queue for drivers — they queue at the entrance and ticketing station, the single point every arriving vehicle passes through. In surge windows, that's where the line forms first.
The constraint wasn't the people being cut.
Driver capacity holds with room to spare; the entrance/ticketing station is what breaks first under surge load. Cutting drivers was safe — ignoring the gate would not have been.
Even at 47.5% fewer drivers, the roster moves more than 2.5× the daily volume. Headcount was never the constraint the operation thought it was.
One station meets every arriving car. During peak surges the queue forms here first — before any driver is even close to busy.
The analysis defended the cut and redirected attention to the part of the operation the cut couldn't fix.
What management got
The report closed with three operating recommendations, each tied to a number the team can watch:
The 2.5× margin is real but not infinite — a standing weekly check catches demand drift long before it becomes a service problem.
Defined volume trip-points that trigger extra coverage, so peak days are handled by rule instead of by panic.
Operational adjustments at the gate — the one station where the queue forms first and the customer feels it most.
The outcome: a 47.5% staffing reduction that leadership could sign off on with the math in front of them — and a watch-list for the one bottleneck that headcount was never going to solve.