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.
- No software fee for the sixty-day evaluation period.
- Nothing converts automatically. Deployment starts when you sign an order form.
- Your data is yours throughout, and is exportable at any point including after the evaluation ends.
Anything 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 from the published per-rooftop pricing.
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
Ten 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
Operational discovery
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
- A named owner at the store with authority to make workflow decisions
- Access to the inventory feed and the website that publishes advertised prices
- Your disclosure and add-on set, and who signs off on changes to it
Rooftop
- Sit with the teams who would use it and write down how the workflow runs today
- State plainly which parts of it Rooftop does not touch
Step is complete when
A written scope: which workflows are in the evaluation, which teams are involved, and who owns it at the store.
- 2Before go-live
Baseline measurement
Measure how the store performs today, before anything changes. Without this, nothing at day sixty can be attributed to anything.
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
Rooftop
- 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
Step is complete when
A written baseline both sides have signed off on.
- 3Before go-live
Application selection
Decide which applications the evaluation actually covers. Rooftop is the platform; AutoCurb, AutoLabels and AutoFilm are applications running on it, and an evaluation does not have to include all three.
The dealership
- Pick the workflow the store most needs answered in sixty days
- Confirm which teams will be measured, so scope and baseline agree
Rooftop
- AutoCurb — Live. Operating in production. Available to buy today.
- AutoLabels — Live. Operating in production. Available to buy today.
- AutoFilm — Pilot. Operating with selected dealerships. The AutoFilm application is not generally available and cannot be purchased today.
Step is complete when
A named application set for the evaluation, with the shipped status of each stated in writing.
- 4Days 1 to 7
Configuration and implementation
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
Rooftop
- 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.
- 5Days 1 to 7
User onboarding
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
Rooftop
- Deliver role-based training and leave a written runbook with the store
- Stay in the dashboard alongside the team through the first live days
Step is complete when
The workflow is running on real vehicles and real customers, and the team can run it without us.
- 6Agreed before day 30
Agreed success metrics
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
- Choose the two or three measures the store will actually act on
- Set the threshold that constitutes success for each one
- Confirm who reads the results and who makes the deployment decision
Rooftop
- 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 one-page evaluation plan with named metrics, thresholds, and a named decision-maker.
- 7Day 30
30-day operating review
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
Rooftop
- 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.
- 8Day 60
60-day results review
Compare the sixty-day result to the baseline, against the metrics agreed on day one.
The dealership
- Attend with whoever makes the decision
- Challenge the numbers — they were built from your baseline and should survive it
Rooftop
- Present results against the baseline and each agreed threshold, met or missed
- State what the store would need to change to hold the result at scale
- Provide the full data set behind the result
Step is complete when
A written results document showing baseline, target, and outcome for every agreed metric.
- 9After day 60
Paid deployment decision
A clean decision on the evidence, with no automatic conversion and no pressure created by a billing date.
The dealership
- Decide: deploy, extend the evaluation with a specific reason, or stop
- If deploying, choose tier and term from the published pricing
Rooftop
- Quote against the published per-rooftop pricing, or scope a group quote for additional stores
- If the answer is no, export your data and close the account
Step is complete when
A signed order form, an extension with a stated reason, or a clean stop.
- 10Where applicable
Expansion plan
Only where a group is going wider than the evaluated rooftop. Group pricing is quoted, not published. The per-rooftop model stays — what changes is the rate per rooftop, the implementation plan, and the administration layer above the stores.
The dealership
- Number of rooftops, and which applications each one needs
- Whether stores share inventory, appraisers, or a central acquisition desk
- DMS and inventory-feed footprint across the group
- Reporting the group office needs above the store level
Rooftop
- Write the implementation plan for the remaining rooftops if the group is going wider
- Pricing stays per rooftop. It does not become per VIN, per deal, or per user.
- Group administration and cross-store reporting are part of the connected tier, not a separate product.
Step is complete when
Rooftop does not publish a group rate card. Any number quoted to you comes from a scoped conversation and is written into the order form.