Founding design partner
Harte INFINITI
Harte INFINITI is the dealership Rooftop is built inside — an active operating environment rather than a demonstration site, and the founder's own store.
- Location
- Hartford, Connecticut
- Scale
- 1 rooftop
- Store type
- Single-rooftop franchised import dealership
- Engagement began
- Not dated
- Measurement window
- In progress
Related-party disclosure
Stated plainly: Harte INFINITI is the store where Rooftop's founder runs F&I. It is a founding design partner, not an arms-length reference. It is the only deployment Rooftop names, there is no second store and no cohort, and nothing here can honestly be described as what dealers typically see.
What it was brought in to do.
Operational problem
Retail-worthy vehicles were leaving through channels the store did not control, and the three ways a store can buy a car directly — off the open web, off the service lane, and from a customer whose trade is still at home — ran as three separate habits with three separate paper trails and no single record of what was offered, by whom, on what basis.
Implementation
AutoCurb runs on the dealership's own domain and under its own brand, with appraisal authority enforced as a role and every adjustment, approval, and consent attributable to a person and a time. It is used by the desk, the service lane, and the accounting office in the ordinary course of business.
Applications deployed here.
The badge is the application’s product status. The line under it is whether this store is running it, which is a separate question and is left open where nothing documents the answer.
- AutoCurbLive
In production here
Running in production at the store. This is the application Rooftop names a deployment for.
- AutoLabelsLive
Not documented here
AutoLabels is Live as a product. Whether it is deployed at this store is not documented anywhere in the company record, so it is not asserted here.
- AutoFilmPilot
Not documented here
AutoFilm is in Pilot as a product. Whether this store is one of the pilot sites is not documented anywhere in the company record, so it is not asserted here.
The measurement plan, then the results.
The plan is published before the result exists, so the measurement cannot be designed backwards from a number somebody wanted. Measurement is running. Nothing publishes from it until the window closes and the dealership approves the result in writing.
- Cohort
- [KEN: supply the cohort this measurement covers]
- Window
- [KEN: supply the exact dated measurement window]
- Sample
- [KEN: supply the sample size and how it is counted]
Measured results
None published. The measurement window is in progress, and nothing is published from it until the methodology, the comparison, the sample size, and the exact window can be published with the number and the dealership has approved it.
A figure with no method behind it is worth less than no figure at all, and this is a related-party deployment, which raises the bar rather than lowering it.
What the store says.
Nothing on file. No quote is published without the exact text, a named person, their title, and their written approval — including a quote from the founder about his own store, which needs the same treatment as anyone else’s and does not count as customer proof.
Open items on this record.
Published rather than hidden. Each is a fact this page would state if somebody supplied it, and none of them will be guessed at in the meantime.
startDate
[KEN: supply the date AutoCurb went live at Harte INFINITI. /changelog shows 2026-04-01, but that file states its own dates are best-effort placeholders, so it is a lead rather than a source.]
applications
[KEN: supply whether AutoLabels and AutoFilm are deployed at Harte INFINITI today, since when, and which teams use them. Until then they stay unverified rather than being counted as deployments.]
measurementPlan.cohort
[KEN: supply the cohort this measurement covers — which vehicles, which lanes, and which people are in scope, and what is deliberately excluded.]
measurementPlan.window
[KEN: supply the exact dated measurement window, start and end, and the baseline period it is compared against.]
measurementPlan.sample
[KEN: supply the sample size and how it is counted — units, appraisals, or repair orders — so a reader can judge the weight of the result before seeing it.]
metrics
[KEN: supply the measured results once a window has closed — the metric, the value, the comparison, the sample size, the exact window, and written approval to publish. A number without all six does not render.]
image
[KEN: supply written authorization and an approved asset before any dealership photograph or OEM wordmark is published here. The manufacturer's mark is the manufacturer's property and the dealership's premises are the dealership's; until both are authorized in writing, this stays a structured placeholder.]
quote
[KEN: supply an authorized quote if one is wanted here — the text, the named person, their title, and their written approval. A quote from the founder about his own store still needs to be written down and approved before it is published as customer proof.]
The next deployment gets the same page, with your numbers in it.
Baseline first, metrics agreed in writing, reviews at day thirty and day sixty, and nothing published about your store without your approval.