Model it in your own numbers.
Five values you enter, multiplied out, with the formula shown. Every result is labelled modeled, and none of them is a measured outcome at any dealership. No RooftopOS price goes into it, so nothing here is a payback period, an ROI percentage, or a net saving.
Using your store’s assumptions.
Enter all five values. Nothing is filled in for you, because a number this page supplied would be a claim about your store that RooftopOS is in no position to make.
How many dealership locations the model should cover.
Read it off your own sales report.
Share of used inventory you would source direct rather than through the auction. Between 0 and 100.
Your number, not ours. What your store believes it avoids per unit bought direct. RooftopOS publishes no figure for this.
Valuation, instant-offer and sourcing tools. Read it off your invoices — no typical figure is assumed here.
Enter all five values on the left and the model runs here. Until then there is nothing to show — this page has no default store, no typical dealership, and no starting number of its own.
No payback period, no ROI percentage and no net figure. Each needs a RooftopOS price, and subscriptions are quoted per rooftop rather than listed — so there is no published rate to put into this arithmetic, and inventing one would make the number look derived when it was assumed. How pricing works.
How we computed this.
No marketing fog. Every number above is derived from the five values you set — and where a figure would have had to come from us, it is not there:
Average savings per direct unit
Yours to enter, not ours to assert. A unit bought direct from a consumer avoids some mix of auction fees, transport, and reconditioning variance — how much is a fact about your lanes and your segments. The field opens empty and nothing is modelled until you fill it in, because a number this page supplied would be an unmeasured claim about your store.
Current spend on the tools RooftopOS replaces
Valuation, instant-offer and sourcing tools, per rooftop per month. Read it off your own invoices. No typical figure is assumed here, and no provider is named — naming one would imply a certification or a partnership, and RooftopOS claims neither.
Direct-acquisition adoption
Share of your monthly used acquisitions that come in direct rather than through the auction. Set it to a number your store can defend. RooftopOS publishes no adoption figure of its own: none has been measured over an agreed window, reviewed, and authorised for publication.
No RooftopOS price is in this model
A connected deployment is scoped and quoted per rooftop rather than listed, so /pricing publishes no rate — and neither does this page. Nothing is subtracted from the total for what RooftopOS would cost, which is why the headline is a combined figure before that cost rather than a net saving.
No payback period and no ROI percentage
Both are ratios against a price. With no published price there is nothing honest to divide by, so neither is shown. The figure your store would pay comes out of the scoping conversation and is confirmed in the order form.
See it on your store, not in a spreadsheet.
Custom-branded, on your domain, measured against your own baseline. Sixty days, a review at day thirty and day sixty, and a deployment decision on the numbers. Commercial terms for the evaluation are set in the scoping conversation and confirmed in writing before it starts, and nothing converts automatically.