Company
A dealership already knows almost everything about a vehicle. Its systems simply cannot see it together.
RooftopOS is a vehicle intelligence platform for automotive retail. Acquisition, merchandising, disclosure, customer video and service activity write to one vehicle record the dealership owns.
Why RooftopOS exists
The information is already in the building. It is just in six systems.
By the time a used vehicle is delivered, a store has appraised it, inspected it, reconditioned it, photographed it, priced it, described it, disclosed it, advertised it and financed it. Each of those steps is recorded — in a different system, in a different format, under a different vendor’s terms.
The consequence is not abstract. It is the appraisal that cannot see what the shop already knows, the window label that drifts from the advertised price, the service recommendation nobody remembers was declined, and the question three years later that takes a week to answer.
RooftopOS’s premise is that the record should be one record, and it should belong to the dealership. Every application writes to the same vehicle history, and the store can have the whole of it exported on request.
Read the founder letterOne vehicle, six systems
Appraisal tool
What the vehicle was worth on the day it was bought
DMS
The deal, the funding, and the accounting entries
Reconditioning software
What the shop found and what it cost to fix
Photo and merchandising vendor
How the vehicle was described and shown
Website provider
The price a customer actually saw advertised
E-signature service
What the customer was handed and acknowledged
Every one of those is true, and none of them can read the others. RooftopOS puts them on one record, per VIN, for as long as the dealership keeps it.
Leadership
Built by an operator, in the order the problems actually arrive.
RooftopOS is led by an automotive retail operator with more than two decades of dealership experience — finance manager and finance director on the F&I desk, and general manager and partner of a used-car dealership. That time was spent in stores rather than at dealer-technology vendors, across franchised mainstream, franchised luxury and independent used-car retail.
Dealership software is usually specified by people who have never had to run the step they are specifying. RooftopOS was specified from inside the workflow: manager approval, appraisal authority and disclosure documents were designed against the desks that answer for them, not against an assumption about one. The three applications exist in the order those problems came up, and each has to hold through an ordinary working week before it earns a page on this site.
Career detail here is the founder’s own account of his own career. RooftopOS publishes no performance statistics for it, and none of it is a statement about the company’s integrations, certifications or partnerships.
Product philosophy
Six constraints, each checkable against another page.
One platform, applications on top of it
RooftopOS is the platform — the intelligence layer and the Shared Vehicle Record beneath everything. AutoCurb, AutoLabels and AutoFilm are applications running on it, not three products that happen to share a logo.
Platform overviewThe record is the product
A vehicle appraised in one department is not re-described from scratch when it reaches the next one. Every application writes to, and reads back from, a single record for the vehicle that the dealership owns.
The three applicationsStatus before story
Every application carries its real status — Live, Pilot, In Development or Planned — from one source of truth, on every page that mentions it. Nothing is described as shipped because it is nearly shipped.
Current product statusThe dealership owns its data
The dealership is the controller and RooftopOS is the processor. Records are exportable on request, tenant data is segregated, and the business model is software rather than the resale of customer information.
Processing terms and vendor listA claim ships with its source, or it does not ship
A figure whose primary document cannot be linked does not render at all — which is why several numbers that were once on this site are gone rather than footnoted. Where a result is modeled, it is labelled modeled rather than reported as an outcome.
A modeled result, labelled as oneCompliance is workflow, not a promise
Documentation and recordkeeping are built around FTC Act Section 5 and state disclosure law. RooftopOS sells the workflow and the record, never a legal outcome, and does not claim a certification it does not hold.
Trust Center
- AutoCurbLive
Vehicle Acquisition
Acquire vehicles directly and manage every step through check request.
- AutoFilmPilot
Sales and Service Video
Turn video into an actionable customer decision.
- AutoLabelsLive
Vehicle Identity and Merchandising
Turn inventory data into verified, customer-facing vehicle experiences.
RooftopOS provides workflow, documentation, and recordkeeping technology. It does not provide legal advice. Dealerships should review configurations and compliance requirements with qualified counsel.
Where the company is now
Early, and specific about it.
None of this has to be taken on trust. Product status, the Trust Center and the changelog are maintained as the record itself, and each is dated so a reader can see when it was last true.
- Leadership
- Founder-led, by an operator working a dealership desk.
- Design partners
- One founding design partner, named on the customers page.
- Applications available
- Two Live, one in Pilot — each carrying its real status wherever it appears.
- Published results
- Measurement begins with a written baseline and agreed success criteria, and publishes with its methodology and window.
- Business model
- RooftopOS is sold as a per-rooftop software subscription configured to the applications, integrations, and implementation scope selected.
- How a store starts
- A scoped sixty-day evaluation on one rooftop, with a baseline and agreed success criteria.
Work with us
The next design partner is a store willing to be measured.
A demo is a working walkthrough of the platform against your own inventory and your own process. The evaluation that follows starts by writing down how your store performs today.