Right site, wrong machine.

The subject was an existing single-bay in-bay automatic on a 0.9-acre corner parcel at a signalized intersection, carrying roughly 24,000 vehicles per day across the two frontages. The in-bay unit processed cars one at a time, at a practical throughput of roughly twelve vehicles per hour. The sponsor's proposal was a conventional path: acquire and modestly upgrade the existing operation, financed with a standard SBA 7(a) note sized to the in-bay site's historical cash flow.

The historical numbers were unremarkable, and on those numbers the deal was small and the coverage thin. The analytical question was whether the historical cash flow described the site's demand — or only the capacity of the machine sitting on it.

The conventional approach to an existing operating wash underwrites the historical cash flow. The in-bay unit's trailing revenue and expenses produce a stabilized cash flow, a coverage figure, and a supportable loan. On that basis the site was a modest single-bay automatic generating modest single-bay economics, and the financing followed the numbers down to a small, thin-coverage deal.

The reading was internally consistent. It was also answering a question about the machine rather than a question about the site.

An in-bay automatic and a conveyor tunnel are not two points on a continuum of the same business. They are different throughput economics on the same parcel. The in-bay unit's roughly twelve-vehicle-per-hour ceiling is a hard constraint independent of how many cars pass the site or how many would convert. A site that could draw two hundred washes on a strong day cannot express that demand through a machine that processes a fraction of it. The historical cash flow was not measuring demand. It was measuring the bay.

The documented economics of in-bay-to-tunnel conversion make the point concrete. Converting a single in-bay automatic to even a short conveyor — a forty-five to one-hundred-five-foot mini-tunnel — raises practical throughput several-fold, and operators that have made the conversion on suitable sites report step-changes in both volume and membership: one documented conversion produced a materially higher first month as a mini-tunnel and a sharp increase in plan membership, because the format unlocked the membership model that a single bay cannot efficiently support.

The relevant analysis was therefore not what the in-bay unit had earned. It was what the parcel — 0.9 acres, signalized, 24,000 vehicles per day across two frontages — could earn under a format matched to its demand, net of the conversion cost and the conversion-specific risks the conventional refinance never had to consider.

Site-versus-format separation. The analysis decoupled the parcel's demand potential from the in-bay unit's historical output, sizing demand against the trade area and frontage traffic at a count-appropriate capture rate rather than against the machine's trailing revenue.

Conversion feasibility and cost. The parcel was tested for its capacity to accommodate a mini-tunnel — lot geometry, stacking and circulation, queuing length, and utility capacity. The conversion budget was built against documented mini-tunnel conversion ranges rather than ground-up tunnel costs, preserving the existing structure and land and producing a materially lower basis than a new build.

Zoning and entitlement risk. Car wash use is frequently conditional or non-conforming even on commercially zoned parcels. The analysis flagged the entitlement path for the format change as a specific, sized risk rather than an assumption — the most common way a conversion pro forma understates its true cost and timeline.

Membership unlock. The post-conversion projection added the Unlimited Wash Club revenue line that a single in-bay unit cannot meaningfully carry, built bottom-up as a member ramp, and isolated the membership revenue as the largest single driver of the difference between the in-bay economics and the converted economics.

Throughput-constrained downside. The model's downside case held the conversion to a conservative throughput well below the format's ceiling and tested the entitlement path taking longer than planned, to confirm the converted economics cleared coverage even if the upside did not fully materialize.

The conventional file would have presented a small refinance on thin historical coverage. The reframed file presented two paths on the same parcel: the in-bay economics the sponsor proposed to refinance, and the converted economics the site could support, with the conversion cost, the entitlement risk, and the membership unlock all sized. The lender could underwrite a larger loan against the converted cash flow precisely because the analysis separated the demand the site held from the capacity of the machine that had been suppressing it. The SOP's special-purpose documentation requirement was met by addressing the format decision itself, which is where the value — and the risk — of the project actually sat.

The analysis converted a thin single-bay refinance into a format decision with a defensible upside and a sized, bounded risk. The inflection was that the historical cash flow described the wrong thing. The constraint on the site was never its demand. It was the machine in the bay.

• 01An in-bay automatic and a conveyor tunnel are different throughput economics on the same parcel, not two versions of one business. A single bay's historical cash flow can describe the machine's capacity rather than the site's demand.
• 02Conversion economics beat ground-up when the parcel suits a mini-tunnel, because the existing structure and land hold the basis down. The membership revenue a tunnel unlocks, and a single bay cannot, is typically the largest driver of the difference.
• 03Format change carries entitlement risk. Car wash use is often conditional or non-conforming even on commercial parcels, and an unsized zoning path is the most common way a conversion pro forma understates its true cost.
• 04Underwriting an existing wash means asking whether the historical cash flow measures demand or capacity. When the machine is the binding constraint, the right analysis is the format the site could carry, not the one it currently runs.