Skip to main content
RooftopOS
All deployments

Founding design partner

Harte INFINITI

Harte INFINITI is the dealership RooftopOS is built inside — an active operating environment rather than a demonstration site, and the platform's founding design partner.

Location
Hartford, Connecticut
Scope
1 rooftop
Store type
Single-rooftop franchised import dealership

The relationship

This is a founding design partnership rather than a signed customer. The relationship, and the disclosure that comes with it, is set out in full on the customers page.

What it was brought in to do.

Operational problem

Retail-worthy vehicles were leaving through channels the store did not control, and the three direct-buy paths ran as three separate habits with three separate paper trails — no single record of what was offered, by whom, on what basis.

Deployment

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. The desk, the service lane and the accounting office all use it daily.

Current deployment scope.

An application is listed here only where the company record documents it running at this store. The badge is the application’s product status, which is a separate question from where it is deployed.

  • AutoCurbLive

    In production here

    Running in production at the store. This is the application RooftopOS names a deployment for.

What this partnership answers.

A design partner is not a reference account. It is where the workflow is put in front of people who will say so when it is wrong.

  • Whether the workflow survives a working week

    An acquisition step that only holds on a quiet Tuesday is not a step. The partnership tests whether approval, valuation and consent stay in order through a store's ordinary week, including the days nobody has time for software.

  • Whether three acquisition lanes can share one record

    Off the open web, off the service lane, and from a customer in the showroom are three different conversations. The partnership answers whether all three can reach one vehicle record without any being flattened into the shape of another.

  • Where authority actually has to sit

    Who may adjust a number, who approves it, and what must be attached before an offer leaves are configuration questions with real consequences. They get settled against a real desk rather than an assumption about one.

  • What has to be reconstructable a year later

    The record's value is tested by the questions that arrive long after delivery. The partnership is where it becomes clear which events, documents and approvals must be retained for that to be a lookup rather than an investigation.

How outcomes get measured.

Outcome measurement begins with a written baseline and agreed success criteria, so a result cannot be designed backwards from a number somebody wanted. It publishes with its methodology, its sample and its exact window beside it, and only once the dealership has approved it in writing.

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.

Back to all deployments
Contact sales