Solutions
Six outcomes a dealership can be held to.
One platform, one vehicle record underneath it. What changes by outcome is which part of that record does the work — and each outcome adds to the record the next one reads from. Every capability below carries its own status.
Used-car director · general manager
Acquire more vehicles directly
The problem
Sourcing runs through auctions and third-party buyers bidding on vehicles they have never seen. The store pays a fee to compete for cars that were already sitting in its own service drive.
The approach
Run off-street submissions, service-lane vehicles and in-store trades through one pipeline — decode, condition capture, appraisal, approval, offer, check request — with every adjustment attributable to a person and a time.
What it adds to the shared record
Channel, valuation inputs, offer, approval and check request are written to the record, so the car reaches merchandising with its history attached.
Availability, line by line
- One pipeline for direct-from-consumer, service-lane and in-store trade sourcingLive
- Manager approval, override and check request recorded against the vehicleLive
- Service findings carried into the appraisal without re-entryIn Development
Used-car director · marketing
Make inventory ready for market
The problem
Merchandising starts with whatever the feed carried. Equipment is generic, the window label and the website disagree, and nobody notices until a customer does.
The approach
Verify identity and factory equipment from the VIN, build the customer-facing record from that data, and check the advertised price against the store's live site before publishing.
What it adds to the shared record
Verified identity, factory equipment and the advertised price go onto the record, so every later document starts from data already checked once.
Availability, line by line
- VIN-verified identity and factory equipmentLive
- Window label and addendum generated from verified dataLive
- Advertised price checked against the live websiteLive
- Reporting on how long a vehicle takes to become front-line readyPilot
Compliance administrator · general manager
Govern vehicle documents
RooftopOS provides workflow, documentation and recordkeeping, not a legal outcome. Disclosure configuration is agreed during scoping; no coverage list is published.
See the disclosure recordThe problem
Disclosure lives in a drawer of PDFs and a signature pad. Months later, reconstructing what a customer was actually shown takes hours and often cannot be done at all.
The approach
Make the itemized price, the addendum and what the customer accepted or declined part of the vehicle record — time-stamped, attributable and retained — under a disclosure policy the dealership configures.
What it adds to the shared record
Every document version and acknowledgment is retained against the VIN, so answering what a customer was shown is a lookup, not an investigation.
Availability, line by line
- Itemized pricing and addendum presented as one documentLive
- Buyers Guide generated alongside the window labelLive
- Acknowledgment and document history retained against the vehicle, attributable and time-stampedLive
Sales manager · service advisor · technician
Convert vehicle media into action
AutoFilm operates under a limited early-access agreement and is not generally available. No viewer-engagement figure is quoted, because none has been measured.
See sales and service videoThe problem
A shopper gets a text with a stock photo and a price. A service customer approves work they have never seen. Neither store learns why the answer was no.
The approach
Record the actual vehicle — a salesperson walkaround or a technician's inspection — put the next step inside the video, and keep the customer's answer on the record.
What it adds to the shared record
Condition evidence, the finding each clip shows and the customer's decision on it are written to the vehicle's history.
Availability, line by line
- Salesperson walkaround of the specific vehicle on a branded pagePilot
- Video multi-point inspection with time-stamped findingsPilot
- Customer approve, decline or ask a question against each findingPilot
- Declined work retained so it can be re-asked next visitPilot
Not available yet
What the record makes possible next.
The two outcomes below depend on capability that is In Development or Planned. They are published so a group can plan around them, not buy them this quarter.
General manager · fixed operations director
Preserve cross-department history
The record is shared today; the handoffs across it are not automatic. A department can see what another wrote, but it does not yet arrive in the workflow on its own.
See how the record is structuredThe problem
Service finds a tyre at four millimetres, the customer declines, and eleven months later the same store appraises the same car from a blank condition report. Every department re-learns what the last one knew.
The approach
Keep acquisition, merchandising and video events on one continuous record, so the next department opens a vehicle that already has a history instead of a form.
What it adds to the shared record
Nothing new is written here — this outcome is what the record is for. Every event the applications above produce sits on one vehicle timeline.
Availability, line by line
- Every application writes its events to one timeline for the VINLive
- Automatic handoffs — a service finding priced into an appraisal, acquisition context following the VIN into merchandisingIn Development
- Public API for a dealership's own systems to read the recordPlanned
Dealer principal · group administrator
Build multi-rooftop visibility
Group administration has not been exercised across more than one rooftop. Nothing here is a multi-rooftop reference.
See the platform architectureThe problem
Every rooftop runs a different process on a different vendor stack, so group reporting is a spreadsheet exercise and group policy is a memo nobody can enforce.
The approach
A separate tenant per rooftop with group visibility above it: standardized policy where the group wants consistency, store-level autonomy where it does not.
What it adds to the shared record
Each rooftop keeps its own records in its own tenant. Group visibility reads across them rather than pooling them.
Availability, line by line
- A separate tenant per rooftopLive
- Role-based access within a rooftopLive
- Rooftop-level configuration under a group-level policyIn Development
- Consolidated reporting across rooftopsIn Development