Solutions
The same record, doing a different job in each department.
Rooftop is one platform with one vehicle record underneath it. What changes by department is which part of that record does the work. Each solution below names the applications involved and what is actually running today.
The problem
Sourcing runs through auctions and third-party buyers who bid on vehicles they have never seen. The dealership pays a fee to compete for cars that were often already in its own service drive.
How Rooftop handles it
Run off-street submissions, service-lane vehicles and in-store trades through one pipeline — decode, condition capture, appraisal, manager approval, customer offer, check request — with every adjustment attributable to a person and a time.
What the store gets
- One pipeline for direct-from-consumer, service-lane and in-store trade sourcing
- Appraisal with condition evidence attached rather than typed from memory
- Manager approval and override recorded against the vehicle
- Check request and accounting handoff from the same record
- Declined offers retained so the vehicle can be re-approached later
The problem
Merchandising starts with whatever the feed happened to carry. Equipment is generic, the window label and the website disagree, and nobody notices until a customer does.
How Rooftop handles it
Verify identity and factory equipment from the VIN, generate the window label and addendum from that verified data, and check the advertised price against the store's own live site before publishing.
What the store gets
- VIN-verified identity and factory equipment
- Window label and addendum generated from verified data
- Advertised price checked against the live website
- Vehicle Passport a shopper can scan from the glass
- Document history retained against the vehicle
The problem
Disclosure lives in a drawer of PDFs and a signature pad. When a question comes back months later, reconstructing what a customer was actually shown takes hours and often cannot be done at all.
How Rooftop handles it
Make the itemized price, the addendum, and what the customer accepted or declined part of the vehicle record — time-stamped, attributable, and retained — under configurable dealership policy.
What the store gets
- Itemized pricing and addendum presented as one document
- Documented customer acknowledgment with time stamp and attribution
- Configurable dealership disclosure policies rather than a fixed template
- Signature and related records retained against the vehicle
- Buyers Guide generated alongside the window label
Sales manager · salesperson
Sales Engagement
AutoFilm is in pilot. Published so a store can plan around it, not because it can be bought today.
The problem
A shopper gets a text with a stock photo and a price. Nothing distinguishes the store from the other four tabs open on the same vehicle, and nothing captures why the customer went quiet.
How Rooftop handles it
Send a personal walkaround of the actual vehicle with the next step inside the video, and keep the customer's response on the record rather than in one salesperson's phone.
What the store gets
- Salesperson walkaround of the specific vehicle
- Branded customer video page
- Test-drive, appointment and trade actions inside the video
- Customer response tracked against the vehicle record
- Manager visibility into activity and follow-up
The problem
A technician finds work, an advisor relays it by phone, and the customer decides without seeing anything. Declined work disappears, so the same finding is rediscovered a year later from scratch.
How Rooftop handles it
Capture the inspection as time-stamped video evidence, let the customer accept, decline or ask a question against each finding, and keep declined work on the record so it can be re-asked at the next visit.
What the store gets
- Video multi-point inspection with time-stamped findings
- Customer accept, decline or ask-a-question against each item
- Declined-work history retained against the vehicle
- Advisor and manager visibility into customer responses
General manager · used-car director
Customer and Vehicle Retention
Each application writes to the Shared Vehicle Record today. The automatic handoffs between them — service findings flowing into appraisal, acquisition context following the VIN into merchandising — are what is being built. They are not automatic yet.
The problem
The store loses track of a vehicle the moment it is delivered, then re-acquires it years later through an auction — bidding against strangers for a car whose entire service history it wrote itself.
How Rooftop handles it
Keep ownership, service and decision events on one continuous record so an equity or reacquisition opportunity surfaces from history the dealership already owns.
What the store gets
- Ownership and service events on one vehicle timeline
- Declined recommendations available at the next visit
- Prior condition and service context available at appraisal
Dealer principal · group administrator
Dealer Groups
Rooftop is deployed in one store today. Group-level administration and consolidated reporting are being built and are not in production. [KEN: supply the first multi-rooftop deployment when one exists]
The problem
Every rooftop runs a slightly different process on a slightly different vendor stack, so group-level reporting is a spreadsheet exercise and policy is a memo nobody can enforce.
How Rooftop handles it
Separate tenants per rooftop with group-level visibility above them, standardized policy where the group wants consistency and store-level autonomy where it does not.
What the store gets
- Tenant separation per rooftop
- Role-based permissions across stores
- Rooftop-level configuration under group-level policy