Structured 60-Day Proof of Value
A scoped sixty-day evaluation on one rooftop, with a measured baseline at the start, success metrics agreed in writing before go-live, two formal reviews, and a deployment decision at the end.
This is an evaluation, not a trial. It is designed so that at day sixty both sides are looking at the same numbers and the decision is obvious to whoever has to sign it.
Terms of the evaluation
- One rooftop.
- Commercial terms for the evaluation period are set in the scoping conversation and confirmed in writing before it starts.
- Nothing converts automatically. Deployment starts when you sign an order form.
- Your data is yours throughout, and is exported on request at any point, including after the evaluation ends.
This page does not price the evaluation. What the evaluation period costs, along with anything else not stated above — scope, the application set, and the order form that would follow — is settled in the scoping conversation and written down before anything is configured. Deployment after the evaluation is quoted against the per-rooftop subscription model. That page publishes the model, not a rate card; the rate for your rooftop comes out of the same scoping conversation.
Apply for an evaluation on your rooftop
What a store needs in place.
These are not paperwork. Each one is a thing that, when missing, is the reason an evaluation produces no usable answer at day sixty.
- An executive sponsor at the store — GM, GSM, or owner
- A named day-to-day owner who will be in the product
- Access to the inventory feed and the website that publishes advertised prices
- Agreement to establish a baseline before go-live, and to review at day thirty and day sixty
Six steps, in order, with an exit condition on each.
Nothing moves forward until the step before it is closed out in writing. That is the whole difference between an evaluation and a trial that quietly runs out of road.
- 1Before go-live
Choose one rooftop and workflow
One store, one workflow, chosen because that is the answer the business needs. A working session with the people who will actually use it — acquisition, sales, service, and whoever owns the website. We agree on scope, users, and what success looks like before anything is configured.
The dealership
- Pick the workflow the store most needs answered in sixty days
- A named owner at the store with authority to make workflow decisions
- Your disclosure and add-on set, and who signs off on changes to it
RooftopOS
- Sit with the teams who would use it and write down how the workflow runs today
- State plainly which parts of it RooftopOS does not touch
- AutoCurb — Live. Operating in production. Available to buy today.
- AutoLabels — Live. Operating in production. Available to buy today.
- AutoFilm — Pilot. Operating under a limited early-access agreement. The AutoFilm application is not generally available and cannot be purchased today.
Step is complete when
A written scope: one rooftop, one workflow, the applications it uses with the shipped status of each, the teams involved, and who owns it at the store.
- 2Before go-live
Establish the baseline
Measure how the store performs today, before anything changes. Without this, nothing at day sixty can be attributed to anything. Decide what would make this a yes, in writing, before anyone has an outcome to defend. Metrics chosen after the fact are not evidence.
The dealership
- Provide current volumes for the workflow being evaluated
- Identify the reports the store already trusts as its own source of truth
- Name the people whose work will be measured, so the baseline is fair to them
- Choose the two or three measures the store will actually act on
- Set the threshold that constitutes success for each one
RooftopOS
- Record the baseline in writing and send it back for confirmation
- Flag anything in the baseline that is too noisy to measure over sixty days
- Write the metrics, thresholds, and measurement method into the evaluation plan
- Say plainly where Rooftop cannot influence a metric, so it is not counted against either side
Step is complete when
A written baseline both sides have signed off on. A one-page evaluation plan with named metrics, thresholds, and a named decision-maker.
- 3Days 1 to 7
Configure the application
Get the rooftop configured and its data verified against the live site, so nothing measured later is measured against the wrong numbers.
The dealership
- Access to the inventory feed and the website that publishes advertised prices
- Brand assets and the domain or subdomain the customer-facing pages will run on
- Confirm users, roles, branding, and the domain the customer-facing pages run on
RooftopOS
- Configuration of the rooftop and its integrations
- Verification that advertised price, inventory, and vehicle data match your live site
Step is complete when
The rooftop is configured, and advertised price, inventory, and vehicle data are verified against your live site.
- 4Days 1 to 7
Train the operating team
Role-based training for each team that touches the workflow, plus a written runbook the store keeps. Managers are trained on approvals and reporting separately from front-line users.
The dealership
- Book training time for each team that touches the workflow
- The user list and the roles each person should hold
- Scheduled time for training. Training is the step stores under-book.
RooftopOS
- Deliver role-based training and leave a written runbook with the store
- A named contact through go-live
Step is complete when
The workflow is running on real vehicles and real customers, and the team can run it without us.
- 5Day 1 to day 60, reviewed at day 30
Run the measured deployment
The workflow runs on real vehicles and real customers while the agreed measures are collected. Check adoption and correct course while there is still time for the change to matter. Most evaluations fail here, quietly, and nobody says so until day sixty.
The dealership
- Attend with the executive sponsor and the day-to-day owner
- Say plainly what is not being used and why
RooftopOS
- Stay in the dashboard alongside the team through the first live days
- Report usage against the plan, by team and by user
- Report progress against each agreed metric, including the ones going the wrong way
- Propose specific configuration or training changes, with owners and dates
Step is complete when
A written thirty-day note: what is working, what is not, and what changes before day sixty.
- 6Day 60 and after
Review results and decide on expansion
Compare the sixty-day result to the baseline, against the metrics agreed on day one. A clean decision on the evidence, with no automatic conversion and no pressure created by a billing date.
The dealership
- Attend with whoever makes the decision
- Challenge the numbers — they were built from your baseline and should survive it
- Decide: deploy, extend the evaluation with a specific reason, or stop
- If deploying, choose the applications and the term for the rooftop
RooftopOS
- Present results against the baseline and each agreed threshold, met or missed
- Provide the full data set behind the result
- Quote the rooftop against the per-rooftop subscription model, or scope a quote for additional stores
- Where a group is going wider than the evaluated rooftop: Group deployments are scoped and quoted. The per-rooftop model does not change — what a group conversation adds is the implementation sequence across stores and the administration layer above them.
Step is complete when
A written results document showing baseline, target, and outcome for every agreed metric. A signed order form, an extension with a stated reason, or a clean stop.