How it works

Under the surface. How RooftopLake works.

The door, the access rules, the data feeds and your group's AI team, each one shown working. Your people lead it. Every screen is an illustration with made-up data.

Scroll to dive in
02 — The door

One secure door. Any assistant you choose.

One door stands in front of the lake. Every request is checked against who is asking, written to a log, and held for a named person if it would change anything or reach a customer.

Who sees what

Pick a role. Everything starts closed, and you open only what each job needs. Illustration: an example starting point; your group sets the rules.

    Every look, draft and approval is written to a log that lives in your account. People sign in with your group's own sign-in, and access ends the day someone leaves.

    Filling the lake

    Only through routes you approve.

    In this order. You can switch any feed off yourself.

    1. ROUTE 1A certified feed from your DMSA nightly copy through a data-extract service your DMS already certifies. You approve it. Nobody shares a login.
    2. ROUTE 2Leads, phones and websiteA copy of every lead as it arrives, plus your phone and website numbers through their own connections.
    3. ROUTE 3Reports your systems already sendScheduled reports and exports fill the gaps. This is how a first pilot starts without waiting on a contract.
    4. ROUTE 4Your DMS's official connectionWe apply on day one. It takes longest, and it's the only proper way for an agent to write anything back.
    5. NEVERNo back doorsNo shared passwords, no screen scraping, no unofficial connections to your DMS.
    Feed board6 of 6 feeds on · all fresh
    • Fresh · 2:10 am
    • Fresh · 2:14 am
    • Fresh · 4 min ago
    • Fresh · 3:02 am
    • Fresh · 12 min ago
    • Fresh · 9 min ago

    Illustration. Try switching one off. Every feed shows when it last arrived, and you're told if one goes stale or changes shape.

    Agents do the work. People decide.

    The same pattern, at every desk.

    Pick a desk. These are the workflows we intend to build with our pilot groups, not finished products. Where a system doesn't let outside software write to it yet, the agent drafts and a person enters it.

    Agents do the work

    • Prepare each booked visit the night before, from the appointment
    • Pull history, open recalls and work declined last time
    • Draft the repair order and line up a loaner, ready when the lane check-in confirms the car has arrived (a plate reader only where the store has posted notice and the customer has agreed)
    • Update the draft when the advisor says or taps a change on a tablet

    Your people decide

    • Greet the customer by name
    • Confirm why they're here
    • Approve any added work
    • Review and sign off the repair order

    Needs from the lakeService history, appointments, recalls, parts, loaners

    Agents earn trust one step at a time

    No agent starts with the keys. Each one moves up only when your managers say it has earned it, and you can move it back down.

    1. STEP 1WatchIt reads and reports. It changes nothing.
    2. STEP 2DraftIt prepares the work. A person sends it.
    3. STEP 3Do, with approvalIt does the work after a named person says yes.
    4. STEP 4Do, within limitsIt handles routine cases inside limits you set, and asks about the rest.
    04 — Your AI team

    Add to your AI team the way you'd hire a manager.

    You wouldn't hand a new hire the keys to every store on day one. Agents get the same treatment: a clear job, a test on your own history, a supervised trial at one store, then the group. Every agent follows the same steps, and you hold the off switch.

    We run it with you

    You don't need a data team to start.

    Most groups can't hire data engineers, AI specialists and a compliance desk. RooftopLake is the product and the service that runs it, until your own team is ready to take more of it on.

    01

    We build and run the lake

    We set up the cloud data account in your name, connect the feeds, watch them every day, and fix them when a vendor changes something.

    02

    We set up your team's AI

    Business accounts for the assistant you choose, connected to the door, with each person's access and your house rules built in. No customer data in personal accounts.

    03

    We train your people

    Short, practical sessions for managers and staff: what to ask, how to check an answer, when to say no. Plus the tools and guides to build small things themselves.

    04

    We line up the legal homework

    What do your DMS, CRM and manufacturer agreements allow? We gather the documents, the questions and the public rules, so your attorney can answer quickly. We aren't attorneys and don't give legal advice.

    Pilot groups

    We're pre‑launch, and looking for a few groups to build this with.

    A pilot is one job at two of your stores, run with us directly while the product takes shape. You shape it around your stores, and you see every result first.

    Emails hello@rooftoplake.com. No form, no sales sequence.

    • You work directly with the people building it.
    • A small first pilot: one job, two stores, read-only, month to month.
    • Founding pricing, flat and agreed in writing before any work starts.
    • Your data stays yours, and you can leave in any month with all of it.
    • We never name you publicly unless you ask us to.

    Own the lake. Build the rest.

    Tell us the one job you'd fix first. If we're a fit, we'll show you how we'd build it.