Every Contract You Sign Is Now an AI Contract

A 20 Group surfaced the question every dealership will face in the next 18 months. Almost no contract answers it.
During a recent session with a 20 Group, a dealer described how his BDC manager's job had changed.
Not long ago, that manager spent his day answering emails and texts. Now an AI built into the CRM handles most of the routine replies. His job is to review what it writes, correct it, and train it on real customer conversations. Every correction makes it sharper.
This is what progress is supposed to look like. It's also where I asked the room the question I now ask every dealer: if you cancel that CRM next year, what happens to everything your manager taught it?
In most stores, nobody knows. Not because they didn't think about it, but because the contract never says.
That's the new data problem. It isn't about your records anymore. It's about your learning.
The Asset Nobody Is Counting
For years, the dealer data fight has been about records. Customer files, repair orders, deal jackets. Can I get them out, and what will it cost me?
Those questions still matter. But AI creates a second asset most dealers aren't tracking at all: the intelligence your store generates while it uses someone else's tool.
Think about what that includes. The corrections your BDC manager makes to AI replies. The reasons your used car manager overrides a pricing recommendation, because the car has a rare package or that color sits in your market. The workflows and judgment calls your best people teach a system over months.
In the room, I compared it to training a great manager who then leaves for a competitor. Except this manager never worked for you. They worked for the vendor the whole time, and you paid for their education.
Your records can usually be exported, at a price. Your learning usually can't, because nobody defined it as yours. Most data clauses were written before anyone in our business said the word "agent." They cover what you put into the system, not what the system learned from you.
That's why I tell dealers to treat every technology contract as an AI contract, whether or not the vendor calls it one.
The Friday Test
Here's the first exercise I gave the group. List every piece of software your store pays for. For each one, ask: if we turned it off Friday, would we still open Monday?
The answers sort fast. A handful of systems carry the store: the DMS, the CRM, maybe your desking tool. Everything else is optional. That short list is where your data, and now your learning, is most exposed. It's also where you have the least room to walk away.
The second exercise is less comfortable. Find out what's actually in there.
One group in that conversation was paying its DMS vendor about $1,000 per store per month to clean its data. When the records were properly resolved, more than 400,000 of them disappeared as duplicates or junk. The file also held 33,000 deceased customers.
If you run marketing, sit with that number. Those are people your store may have been mailing, emailing and texting. Picture a family opening a trade-in offer addressed to someone they buried last spring.
That group isn't unusual. Once duplicates are resolved, a typical dealer has somewhere between 17,000 and 35,000 real customers, not the hundreds of thousands the CRM claims. Email addresses decay about 2.5% a month, so a CRM nobody has cleaned in a year can be close to 30% bad. Meanwhile, marketing cost per vehicle sold now runs above $700. At my Chevrolet store, it was about $300.
You're paying premium rent on a database you can't fully see, can't fully trust and, increasingly, can't fully get out.
The Doors Are Closing
Getting your data out is about to get harder, not easier.
This year, at least one major DMS provider shut off automated reports. Expect others to follow. Outside our industry, banks, airlines and retailers are blocking AI agents from logging in on a customer's behalf. I felt it personally. The agent that books my travel used to coordinate flights, hotels and my calendar on its own. One airline blocked it, and I'm back to doing it by hand.
Some of that is legitimate. An AI agent holding a login is a real attack surface. And the workaround many stores rely on, software that signs into the DMS or CRM like a person and scrapes the screen, often violates the vendor's terms. Certified, documented connections are the only route that lasts.
But security is also the most convenient reason a vendor can give for charging more. So when your access changes, don't argue about motives. Apply one test: what replaces what you lost?
A security-driven change gives you an encrypted, authenticated export of the same fields at the same cost. If the replacement is view-only, or suddenly carries a fee it didn't carry before, the driver wasn't security. It was revenue.
The Favor Count
Pull the agreement for every system that passed the Friday Test and find the data section. It's usually about three paragraphs. Then score it: one point for every question you can answer yes from the actual contract language, not from what your rep told you.
One rule for scoring. Language that says the vendor shall is a right. Language that says the vendor may, or ties anything to "then-current policies," is a favor. Favors don't score.
- Does the contract define dealer data to include records the vendor creates about your operations, not just what you enter?
- Does it define the learning your store creates (AI corrections, trained behavior, derived insights) as yours?
- Can you export every field, in a documented machine-readable format, at least daily?
- Is the cost of that export capped at the vendor's direct cost?
- Can you choose your own integration partner without that partner paying the vendor for permission?
- Is the vendor barred from cutting access through technical means, rate limits or retired connections?
- Does the vendor need your written consent to use your data to train models, build benchmarks or sell derived products?
- On cancellation, do you get a complete export by a stated date, read access for a stated period, then certified deletion?
- Are the terms pinned to the version you signed, with every "then-current" struck?
- Do you get an annual list of every third party that received your data?
8 to 10: Clear title. You control the asset. Protect it at renewal.
4 to 7: Lien. You can use your data, but someone else sets the terms. Fix it before the next renewal.
0 to 3: Repo risk. If this vendor changes the deal, you have no recourse. This contract goes first.
Run it in your next managers' meeting. It takes about ten minutes per system. While the contracts are on the table, check the invoices against them too. In the groups my team has reviewed, I have yet to see a DMS contract and its billing line up perfectly.
Where and When You Have Power
A low score isn't a verdict. It's a negotiating list, and you have more standing than you think.
Some states already wrote the rules. Arizona, Oregon, Montana and North Carolina have dealer data statutes. Arizona's is the clearest model: a DMS or CRM provider can't limit a dealer's ability to protect, store, copy, share or use its own system data, by contract or by technical means, and fees are capped at the direct cost of providing access. North Carolina also requires an annual disclosure of third parties that received dealer data. If you operate in one of those states, you may hold rights you aren't using. If you don't, those statutes are the template for what to ask for. Confirm the current text with your counsel before you negotiate.
Your power has a calendar. It peaks twice: before you sign, and 120 to 180 days before renewal. Send your data terms to the vendor's contracts team, not your account rep, who can't change them. Use the same language with every vendor so it reads as policy, not accusation.
Keep terms short where you can. Outside the DMS, where you may have little choice, avoid multi-year agreements. The tools are changing too fast to lock yourself into one that may be obsolete in 18 months, and short terms keep your renewal window open.
The System Is the Solution
I closed that session with a line from Michael Gerber's The E-Myth: the system is the solution. It applies to AI more than Gerber could have imagined.
The stores that win the next 18 months won't be the ones with the most AI tools. They'll be the ones that control the system those tools learn from: their data, their workflows and the intelligence their people create every day.
That BDC manager is doing exactly the right work. Every correction he makes builds an asset. The only question is whose balance sheet it lands on.
Score your contracts this week. Then make sure the answer is yours.

Chrome to Code
with Todd Smith
Todd Smith is the CEO of QoreAI, where his expertise lies at the intersection of AI and automotive, focusing on fraud prevention and data security. With over 30 years in retail, tech, and automotive, Todd has successfully founded and grown multiple startups, including companies recognized by Inc. 500/5000 and Red Herring Top 100. As Managing Director of Kyzor, he invests in and mentors promising automotive tech ventures. Todd's practical application of AI to address identity fraud and enhance dealership data protection has established him as a respected industry voice. His insights on automotive technology and security are frequently sought at major industry events.
Get Curated Insights
Content worth the click

