Connected applications
Three applications. One compounding data advantage.
Each one solves a complete dealership workflow on its own. Each one writes to the same vehicle record — so a store that runs two knows more about a car than a store that runs one, and the third starts from what the first two already established.
RooftopOS is the platform underneath all three. It holds one record per VIN for the life of the vehicle; an application is how a department reads that record before it acts and writes back what it learned. Nothing here is sold as a bundle, and there is no required order.
Acquire vehicles directly and manage every step through check request.
Off-street submissions, service-lane vehicles and in-store trades run through one pipeline — decode, condition capture, appraisal, manager approval, customer offer, check request — with every adjustment attributable to a person and a time.
Start here if too much inventory is bought at auction, and the cars that walk in through the service lane are handled three different ways.
Open AutoCurb- Who runs it
- Used-car director, desk manager, service advisor, accounting
- What it produces
- An appraisal with its assumptions retained, an offer, an approval trail attributable to a person, and an accounting handoff.
- What it displaces
- the trade-in widget and the instant-cash-offer form
Turn inventory data into verified, customer-facing vehicle experiences.
Identity and factory equipment are verified from the VIN, the customer-facing record is built from that verified data, and the advertised price is checked against the store's own live site before anything publishes.
Start here if the window label, the website and the disclosure record have to agree on one vehicle, and today they are assembled separately.
Open AutoLabels- Who runs it
- Merchandising manager, compliance administrator, F&I
- What it produces
- Window label, addendum, Buyers Guide, a customer-facing Vehicle Passport, and a document history retained per VIN.
- What it displaces
- the addendum printer and a generic e-sign
Turn video into an actionable customer decision.
A salesperson walkaround or a technician's inspection is recorded against the specific vehicle, the next step sits inside the video, and the customer's answer stays on the record rather than in one person's phone.
Start here if a recommendation is explained once and nothing about that conversation survives to the next visit.
Open AutoFilm- Who runs it
- Salesperson, service advisor, technician
- What it produces
- Timestamped video indexed to the finding it shows, with approve, ask a question, or decline attached to each recommendation.
- What it displaces
- the generic walkaround video and standalone video-MPI tools
Where all three meet
Whichever you start with, every application strengthens the same VIN.
One record per VIN, opened once and never restarted — each application writes its own part of it, and the next one begins from what the last established. That is also what makes the second application a store adopts cheaper to put in than the first: it opens against a record that is already populated.
Each column below is what one application takes off the record before it acts, and what it puts back when it is finished.
- AutoCurb
- Reads
- Decoded identity, trim and factory equipment, plus any inspection history already held against that VIN.
- Writes
- Acquisition channel · valuation inputs · offer terms · approval · check request
- AutoLabels
- Reads
- VIN identity, decoded equipment and recall status, plus the condition and acquisition context already on the record.
- Writes
- Verified identity and equipment · itemized pricing · disclosures · document set
- AutoFilm
- Reads
- The vehicle a recording belongs to, together with open recommendations and work a customer has previously declined.
- Writes
- Condition evidence · service history · the customer's decision on each item
Shared Vehicle Record
One continuous record connects every event, document, and decision across all applications.
Illustrative product data. The counts below are the size of this demonstration record itself, not a measurement of anything in production.
- VIN
- 2T3P1RFV5MC164821
- Events on this record
- 10
- Documents generated
- 2
- Latest event
- 2027-04-10
- AutoCurb
- AutoLabels
- AutoFilm
AutoFilm is in Pilot, and the handoffs between applications are In Development — a department can read what another wrote, but it does not yet arrive in the workflow on its own. Product status is where every badge on this page resolves from, and the platform page sets out what the record holds and who in the store can see it.
Land with one workflow. Expand through the record.
Run one application against your own inventory and your own process. The second one starts from what the first already knows, and it is a decision you make after the first one has earned it rather than at the point of sale.