Five reports, five different numbers
The DMS says one thing, the CRM another, the spreadsheet a third. Monday's meeting is spent arguing about whose number is right.
With the lake: one number, one definition, every store.
RooftopLake gives your dealer group its own AI team for the screen work, built on one lake of data that you own.
It's what happens when every job gets its own rented tool, and every tool keeps its own copy of your business.
The DMS says one thing, the CRM another, the spreadsheet a third. Monday's meeting is spent arguing about whose number is right.
With the lake: one number, one definition, every store.
Each problem gets another vendor, another login and another monthly bill per store. The stack grows. The answers don't get clearer.
With your group's AI team: your people lead it. Build the small tools yourself, inside the assistant your team already uses. No new login.
It's your customers, your deals and your service history, but getting a full copy out is slow, limited, or costs extra.
With the lake: your own copy, in your own account, in open formats.
Staff paste work into personal AI accounts to get through the day, sometimes with customer details in it. Under the FTC Safeguards Rule, where that data goes is your responsibility.
With us: business accounts, house rules, a record of use, and a readiness pack for your attorney.
Scroll through one service visit, step by step. It is the direction we are building toward, not a shipped product.
The advisor is busy with the last customer, and nobody types a thing.

The advisor is busy with the last customer, and nobody types a thing.

A plate reader runs only where the store has posted notice and the customer has agreed. Without that, the lane check-in is a tap.

From the lake: her booking, history, the open recall, the work she declined last time, and a draft order.

Eyes on the customer, not the screen. The agent drafted. The person reviews, approves and signs off.
Direction, not a shipped product. Illustration with a made-up customer.
Touch the water, drag the data around, spin the lifecycle, and pick out the helpers. Everything here is made up, and it shows the direction we are building toward, not a shipped product.
Four stills of the same idea: the water and the store, the data, the helpers and the lifecycle. Everything here is made up, and it shows the direction we are building toward, not a shipped product.




Your AI team drafts the agent from a plain-English job sheet.
One governed copy of every store's data, in your own account. Ask a simple question, then flip the switch.
Start small. One job, two stores, read-only, month to month.
Pilot one job at two storesEvery store, every system, cleaned and counted the same way in your own account.
One secure door so any AI assistant you pick can use the lake.
Built for real dealership jobs from the start of a pilot. Yours to change.
Build, test, approve, roll out by store, watch and retire.
Each one is planned to run on your lake in the first weeks of a pilot. They read and report, or they draft for a person to approve. Shown here as illustrations.
Every store's sales, service, parts and cash on one page each morning, counted the same way.
Maps an acquired store's systems to your group's definitions and lists what doesn't match.
Flags cars crossing your age limits at each store, with holding cost and where similar cars are selling.
Shows which leads waited too long for a first reply, by store, source and salesperson.
Finds service work customers declined and drafts a follow-up for your advisors to approve.
Checks claims against the usual rejection reasons before they're submitted.
Every starter comes with its plain-English job sheet and its tests. Change the rules, the wording or the thresholds, and your AI team runs your version through the same checks — build, test, approve, roll out by store, watch and retire.
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.
No one yet. RooftopLake is pre-launch. We're choosing a small number of pilot groups to build the first version with. There are no customer logos on this page because we haven't earned any.
No. The lake copies data out of the systems you already run. Your people keep working in the same screens.
Through the access routes your vendors offer to dealers and their approved partners. Some are simple, some need a contract, and some carry a fee from the vendor. This is the slowest part of any project like this, and we'll tell you where each of your systems stands before you commit to anything.
Reading data is the easy half. Letting an agent write into a system needs that vendor's agreement. Until it's in place, agents prepare the work and a person enters it.
You do. The lake sits in a cloud data account in your group's name. The job sheets, definitions and agents built for you are yours to keep.
Often yes, with conditions, and it depends on your contracts and your state. Your agreements with your DMS, CRM and manufacturer each say something about who may touch the data and how. Part of our onboarding is a readiness pack: your documents, the clauses that matter and a short list of questions, prepared for your attorney to rule on. We don't give legal advice.
Your choice. The door uses an open standard (called MCP) that the major AI assistants share to reach data and tools, so you aren't tied to one AI company, and you can switch as they improve.
Only with rules. Each person and each agent sees just what their role allows, every request is logged, each agent has a spending cap and an off switch, and nothing reaches a customer without a named person's approval.
We hold no security certifications yet and won't pretend to. The Safeguards Rule makes you responsible for checking vendors like us, so before any data moves you get our security plan and contract terms in writing. The first phase uses no credit applications or Social Security numbers, the lake sits in your account, and you can cut off our access at any time.
No. It's about what they spend their day on. Agents take the looking-up, matching and re-keying. Your people keep the customer, the judgment and the sign-off. Staffing decisions stay with you.
Yes. You describe the job in plain English and decide what good looks like. We build it with you at first. Every agent on your AI team gets the same tests and the same sign-off, so your own operations people can safely do more of it over time.
We haven't published pricing. Pilot groups get a flat founding price agreed in writing up front. Ask and we'll tell you straight.
Own the lake. Build the rest. This is the direction we're building toward — tell us the one job you'd fix first.