A $2,000 monthly AI tool often carries usage charges, integration fees, training rights and renewal terms outside the sales proposal. Ask these eight questions before signing.
A GM signed an AI voice agreement for $1,500 a month.
The proposal called the service “unlimited.” The usage schedule defined unlimited as 500 minutes. Every added minute cost $2.50.
The dealership ran 800 minutes above the allowance.
The math:
800 minutes × $2.50 = $2,000 in overage charges
$1,500 subscription + $2,000 overage = $3,500 monthly bill
The next problem sat in the data clause. The vendor received broad rights to use de-identified dealership conversations for product development and model training.
Then the GM missed a 90-day nonrenewal deadline. The agreement renewed for 12 months, creating another $18,000 commitment.
Our review of 12 anonymized AI vendor contract samples found eight recurring problems. The samples covered AI chat, voice, BDC, pricing, recon and service products.
The contract counts below refer only to those 12 samples. Terms differ by vendor, product and dealership configuration.
Eight Questions to Ask Before Signing an AI Vendor Contract
| # | Question to Ask | Where the Risk Hides | Cost Exposure | Samples With Similar Terms | Contract Fix | Savings or Protection |
| 1 | What usage is included, and what is the overage rate? | Usage schedule, order form or fair-use policy | $16,000 to $32,400 yearly in modeled overages | 9 of 12 | Fixed allowance, rate cap, 80% alert and monthly ceiling | Stops surprise usage bills |
| 2 | Who owns dealer data, and does the vendor train models with dealer data? | Data license, privacy terms or product-improvement clause | Customer-data and competitive-information exposure | 10 of 12 | Dealer ownership, no training without written consent, no resale | Protects customer and operating data |
| 3 | Does the agreement renew automatically? | Term, renewal and termination section | $18,000 added commitment in the dealer example | 11 of 12 | Month-to-month after initial term, 30-day notice | Avoids forced renewal |
| 4 | Who bears loss from incorrect AI output? | Warranty disclaimer and limitation-of-liability section | Incorrect price, payment or appointment promise | 12 of 12 | Human approval controls, defined liability and incident process | Limits pricing and compliance loss |
| 5 | Which integrations and API calls are included? | Interface schedule, API terms or partner fees | $20,400 yearly in the four-integration example | 7 of 12 | Five integrations and 50,000 monthly API calls included | Removes hidden connection fees |
| 6 | What uptime does the vendor promise? | Service-level agreement | Up to 36 hours of monthly downtime under a 95% SLA | 8 of 12 | 99.5% minimum, higher target for voice, service credits | Reduces outage exposure |
| 7 | Does the vendor provide notice before changing the AI model? | Product-update and modification rights | Lower appointment or response performance | 9 of 12 | Advance notice, test period and rollback right | Protects established workflows |
| 8 | How do we export and delete data after termination? | Data-return, deletion and survival clauses | $5,000 extraction example plus retained data | 6 of 12 | Free export and deletion certificate within 30 days | Cuts exit cost and privacy exposure |
Contract locations and page numbers differ. Review the master agreement, order form, usage schedule, data-processing terms and linked online policies together.
#1: Is “Unlimited” Truly Unlimited?
Nine of the 12 contract samples contained a usage allowance, overage charge or fair-use restriction.
One proposal advertised unlimited AI voice service for $1,500 a month. The order form referred to an online usage schedule. That schedule included 500 minutes and priced each added minute at $2.50.
The word “unlimited” did not match the billing formula.
A dealer running 800 added minutes each month would pay:
800 minutes × $2.50 = $2,000 monthly
$2,000 × 12 = $24,000 yearly
Another vendor priced AI chat by conversation. The subscription included 1,000 conversations, followed by a $0.50 charge for every added conversation.
Ask the vendor to define a billable unit. A voice minute might include hold time, transfers, voicemail and post-call processing. A conversation might restart after a set period or include spam.
Proposed contract language:
“Monthly fees include the usage stated in the Order Form. Provider shall notify Dealer at 80% and 100% of the allowance. Overage charges shall not exceed $0.50 per voice minute or the stated rate approved by Dealer. Total monthly overage charges shall not exceed $1,000 without Dealer’s written approval.”
Require a live usage dashboard. A month-end invoice arrives too late.
Question: “Show the included volume, overage rate, billable-unit definition and monthly maximum in the signed order form.”
#2: Does the Vendor Train Its Model With Your Data?
Ten samples gave the vendor some right to use customer interactions, prompts, transcripts, performance information or de-identified data for analytics and product development.
A broad license does not prove the vendor sold dealership data to a competitor. The risk comes from unclear permission.
An AI voice platform might receive:
- Customer names and phone numbers
- Vehicle interests
- Appointment details
- Trade information
- Call recordings
- Sales scripts
- Pricing responses
- Employee performance data
“De-identified” needs a contract definition. Removing a customer’s name does not automatically remove every link to a dealership, market, vehicle or transaction.
Dealers covered by the FTC Safeguards Rule have responsibilities tied to service providers holding customer information. The FTC states covered financial institutions must take steps to ensure their service providers safeguard customer information. FTC Safeguards Rule
Proposed contract language:
“Dealer retains all right, title and interest in Dealer Data. Provider shall use Dealer Data only to deliver the contracted services. Provider shall not use Dealer Data to train a general-purpose or shared model without Dealer’s prior written consent. Provider shall not sell Dealer Data or disclose dealership-specific insights to another dealer.”
Also require written approval before a subcontractor receives the data.
Question: “List every use of our transcripts, prompts and customer records, including model training, benchmarking and product development.”
#3: Does the Contract Renew for Another 12 Months?
Eleven reviewed samples included an automatic renewal clause or a notice deadline requiring close attention.
The common structure looked like this:
“This Agreement renews for successive twelve-month periods unless either party provides written notice at least ninety days before expiration.”
A $1,500 monthly agreement creates another $18,000 commitment after a missed deadline.
$1,500 × 12 months = $18,000
An early termination clause might demand every remaining payment. The dealership then pays for a tool no longer in use.
Proposed contract language:
“After the Initial Term, this Agreement shall continue on a month-to-month basis. Either party may terminate upon thirty days’ written notice. No renewal term longer than one month shall arise without a new written agreement signed by both parties.”
Request email notice as an approved method. Enter renewal alerts 180, 120 and 90 days before expiration.
Question: “Strike the annual automatic renewal and show the revised termination clause before we sign.”
#4: Who Bears the Loss When the AI Gives a Wrong Answer?
All 12 samples contained a disclaimer covering inaccurate, incomplete or unintended AI output.
A customer asks an AI chat agent for the price of an F-150. The bot quotes $45,000. The approved selling price is $50,000.
The dealer now faces a customer complaint, an advertising review and a $5,000 pricing dispute.
A disclaimer inside the chat does not replace operating controls. Price, payment, trade value, credit decision and incentive claims need approved data sources and escalation rules.
NIST’s Generative AI Profile calls for ongoing monitoring, testing and risk management around generative AI systems. Those controls belong in the dealership workflow and the vendor agreement. NIST AI 600-1
Proposed contract terms should address:
- Approved data sources
- Human approval for price and payment changes
- Prompt and response logs
- Immediate shutdown controls
- Error-notification deadlines
- Indemnity for vendor-caused infringement or security failures
- A negotiated liability cap with exceptions for confidentiality and data breaches
A vendor might reject full responsibility for every generated response. The dealership should still reject a contract leaving all loss with the dealer when the vendor’s defect, unauthorized change or security failure caused the event.
Question: “Show the exact clause governing incorrect output, incident response and liability.”
#5: Are Integrations and API Calls Included?
Seven samples charged separately for integrations, API traffic or both.
Assume four connections:
- CRM
- DMS
- Inventory feed
- Call-tracking platform
At $300 monthly per integration:
4 × $300 = $1,200 monthly
Add 50,000 API calls at $0.01 each:
50,000 × $0.01 = $500 monthly
Total added cost:
$1,200 + $500 = $1,700 monthly
$1,700 × 12 = $20,400 yearly
The sales proposal might show a $2,000 subscription while the integration schedule adds another $1,700.
Proposed contract language:
“The subscription includes five active integrations and 50,000 API calls per month. Added integrations require Dealer’s written approval and shall cost no more than $150 monthly. Provider shall notify Dealer at 80% of the included API allowance.”
Define responsibility for setup, authentication changes and troubleshooting.
Question: “Provide one fee table covering every integration, API call, implementation charge and support fee.”
#6: What Happens When the AI Platform Goes Down?
Eight samples contained a weak service commitment, limited credits or no meaningful remedy.
A 95% monthly uptime promise permits about 36 hours of downtime during a 30-day month:
720 monthly hours × 5% = 36 hours
A 99.5% commitment permits about 3.6 hours:
720 × 0.5% = 3.6 hours
For AI voice, even 3.6 hours hurts if the outage lands on Saturday afternoon. Ask how the vendor measures downtime and which events it excludes.
Proposed language:
“Provider shall maintain 99.5% monthly uptime for chat and workflow services and 99.9% for production voice routing, excluding scheduled maintenance announced at least seventy-two hours in advance. Dealer receives a service credit for failure to meet the applicable level.”
Credits rarely repay lost appointments. Add a termination right after repeated failures.
Question: “Show your last 90 days of production uptime and the credit calculation.”
#7: Does the Vendor Give Notice Before Changing the Model?
Nine contracts allowed the provider to change models, prompts, routing logic or features at its discretion.
A model update might improve cost for the vendor and reduce performance for the store. The BDC sees the damage later through lower contact, appointment or show rates.
Set a baseline before launch:
- Contact rate
- Qualified-conversation rate
- Appointment rate
- Transfer success
- Opt-out rate
- Error rate
Proposed contract language:
“Provider shall give thirty days’ notice before a material model, routing or workflow change. Dealer receives access to testing before production release and retains a rollback right for thirty days after deployment.”
Avoid a guaranteed sales result. Tie the clause to measurable system performance and defined error thresholds.
Question: “Which changes require notice, and how quickly will you restore the prior version after a failed release?”
#8: How Do You Export and Delete Dealer Data?
Six samples lacked a clean, no-cost exit process.
One exit example included a $5,000 extraction charge. Another permitted retention for up to one year after termination, subject to broad exceptions.
The contract should state:
- Export format
- Included data
- Export deadline
- Deletion deadline
- Backup treatment
- Subprocessor deletion
- Written deletion certificate
Proposed language:
“Provider shall deliver Dealer Data in CSV, JSON or another documented standard format at no charge within thirty days of termination. Provider and its subprocessors shall delete Dealer Data within thirty days after confirmed export, except records required by law. Provider shall issue a written deletion certificate.”
The FTC has also warned AI companies to honor privacy and confidentiality commitments when using customer data. Federal Trade Commission
Question: “Show the data-export fields, deletion timeline and certificate form before contract approval.”
AI Vendor Math: Where the $20,000 Annual Risk Comes From
Do not add every scenario and call the total guaranteed savings. Some costs overlap and others arise only at renewal or termination.
A realistic modeled year might include:
Usage overages: $2,000 monthly for eight high-volume months = $16,000
Two unplanned integrations: $300 monthly each × 12 = $7,200
Total avoidable cost = $23,200
A dealer negotiating lower overage rates, included integrations and a monthly ceiling might protect about $20,000 in one year.
The $18,000 automatic renewal is a separate contract exposure:
$1,500 monthly × 12 months = $18,000
Put these eight fields on the approval sheet before signing:
- Included usage and overage ceiling
- Dealer-data ownership and training rights
- Renewal and cancellation dates
- AI-output controls and liability
- Integration and API charges
- Uptime and service credits
- Model-change notice and rollback
- Data export and deletion
A $2,000 monthly AI product is a $24,000 yearly decision before usage, integration and exit charges enter the invoice. The contract should show the maximum monthly cost, not the lowest sales-demo price.
Related: The 6 DMS Contract Traps That Cost Dealers $18,000 at Renewal
Sponsored by Gas.net — powering dealership growth through intelligent data.
Alt text: “Gas.net connects franchise dealers with integrated analytics and marketing tools.”