A.D.A.M. (Adaptive Dealer Advisory Mind) reads your rooftop's own numbers and coaches your store in plain language. Before he can do that, we need to know two things: what systems you run, and who your people are. This page is both the sheet that tells us, and the instructions for connecting your data.
Three steps. The first is the only one that needs your attention for more than a few minutes, and most of it is answering questions you already know the answers to.
The sheet below, about fifteen minutes. It tells us which feeds to build and who gets a seat.
We send credentials, your systems send scheduled reports. About thirty minutes of clicking, once. We confirm every file as it lands.
Your people receive their own invitations to set a password. Your Performance Agent calls to walk the store through it.
After that there is nothing to maintain. The feeds run daily on their own, and if one goes quiet for more than two days we raise an alarm on our side without waiting for anyone to notice.
Fill this in on screen and send it with the buttons at the bottom, or print the page and fill it in by hand. Your answers are saved in this browser as you type, so a closed tab does not lose the work. Items marked * are the ones we cannot start without. One sheet per rooftop.
Setup is a handful of scheduled exports and about thirty minutes of clicking. Once the feeds run, everything updates itself daily and there is nothing to maintain.
Send nothing anywhere else. The SFTP login is the single door for that rooftop's data, and files uploaded through it can only ever land in that rooftop's own isolated database.
Five scheduled exports, delivered daily by the inventory system's own report scheduler, using the credentials we provide. The directory can be left blank: the login root is fine.
| # | Report | Schedule or file name pattern | Cadence |
|---|---|---|---|
| 1 | Active used inventory | <Store> Used Active | Daily |
| 2 | Sold used, 90 day | <Store> Used Sold | Daily |
| 3 | Active new inventory | <Store> New Active | Daily |
| 4 | Sold new, 90 day | <Store> New Sold | Daily |
| 5 | Appraisal analysis | Any name | Daily |
The naming rule that matters. On reports one through four, the name needs one lane word (Used or New) and one status word (Active or Sold). Order does not matter, the two words do not have to sit next to each other, capitals and dashes and spaces do not matter, and a file extension is optional. Metro Used Active and Metro Used Vehicles Active both work.
What actually breaks a name is ambiguity. A report carrying both lane words or both status words, such as New and Used Active, cannot be classified and is not recognized. Keeping the two words together is simply the easiest way to stay unambiguous.
A CSV export of leads, delivered to the crm folder of the same SFTP login:
A detailed column specification is available on request, and we will review a sample file before the schedule is set live.
Repair orders, financial statements, and parts data ride the same SFTP login, each in its named folder (service, financials). Column specifications per pillar are available on request. Send a sample export and we will confirm fit or supply the exact template. If a system can schedule a report to an SFTP destination, it can feed A.D.A.M.
If a file is sent and not confirmed within an hour, tell us which report and what time it was sent. Every delivery, successful or not, leaves a trace on our side, and feeds that go quiet for more than two days raise an automatic alarm.
Every one of these has been seen in the wild.
| Mistake | Result | Fix |
|---|---|---|
| Report name carries both lane words or both status words | Cannot be classified, so the file is not recognized | One lane word and one status word, per the naming rule above |
| CRM export filtered to active leads only | Close rates impossible, file held | Export all statuses |
| Aggregate CRM report, by source or by rep | Not loadable | One row per lead |
| PDF export | Not machine readable, ever | Excel or CSV |
| Sending a subset of columns | Permanent blind spots | Include every column |
| Credentials retyped by hand | Delivery failures | Copy and paste from a working schedule |
Every rooftop's data is fully isolated. Each rooftop has its own SFTP login, its own storage, and its own database, and a file uploaded for one rooftop cannot reach another. Customer-identifying columns arriving on appraisal exports are discarded at the door.
Questions route to Brian Schwelling, brian@telicx.com.