Assemble the condition, battery-health, warranty and recall evidence on a used EV and draft the listing — with the value, the range claim and the decision to publish left to a named person.
Take the unit in from a trade-in, a lease return, an auction buy or a car already standing in inventory.
02
Pull the service records, prior damage, title brands and the battery and drivetrain warranty as recorded.
Reason
03
Record every battery state-of-health reading on file with where it came from, when, and on what tool.
04
Run the VIN through the recall and campaign lookups your store uses and note what each returned, and when.
05
Set out charging capability, connector and conditioning as the build record states them for this VIN.
Decide
06
Hold back any value, offer, range figure or claim that the battery or the coverage is sound.
07
Flag thin, stale or disagreeing evidence and say what the appraiser should verify before it is listed.
Out
08
Hand over an appraisal file and a draft listing carrying the disclosures the store requires.
09
Retain every reading, its source and date, what the manager changed, what was published and by whom.
→Product statement
The agent gathers, dates and drafts. The value, the condition claim and the decision to publish stay with a named person at the dealership.
Example workflow
One unit, end to end
AgentHuman
1Unit taken inTrade-in at the desk, lease return, auction buy or a car already standing in inventory
2VIN decoded and matchedResolved to one VIN and one build record before any history or reading is read
3Evidence gatheredService records, prior damage, title brands, warranty terms and the recall and campaign lookups
4Battery evidence datedEach state-of-health reading with its source, its tool and the conditions it was taken under
No human action required
Stages 1 to 4 run without a person in the loop — the decode, the retrieval and the battery evidence are finished before a manager opens the file, and nothing has been listed yet.
5DecisionSplits on how the evidence stands, and on what a listing would have to assert
Evidence agrees and is dated
Reaches the used-car manager ready to read.
Readings disagree or a claim is needed
Held for the used-car manager to resolve.
Used-car manager
Reads the file, the readings behind it and what the agent refused to state, sets the number themselves, then publishes under the store's name.
Approve file · Correct · Order inspection
Approved — handed back▼
6File saved against the stock numberHeld unpublished on the stock record; nothing reaches a marketplace at this stage
7Outcome evaluatedWhat the manager corrected, what was published, and disclosure and evidence misses by cohort
Corrections
Every claim the manager adds back, or strikes out, is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Stating a value, an offer or a trade figure.
Pricing a unit or setting a listing price.
Calling a battery healthy, degraded or sound.
Stating a range the vehicle will achieve.
Automation boundaryAgent acts unaided
✓Decode the VIN and match one build record.
✓Gather service records, damage, title brands and warranty terms.
✓Record each battery reading with its source, tool and date.
✓Assemble the appraisal file and draft the listing copy, unpublished.
The appraisal file is written to the stock record, never to a marketplace. A named person sets the value and publishes.
Confirming coverage, or that a warranty transfers.
Saying a unit has no open recall.
Deciding the as-is or warranty disclosure.
Publishing a listing to any marketplace.
Example output
One appraisal file, annotated
Everything the agent puts up is attached to the reading and the record it was taken from.
Appraisal output · one used EVIllustrative example
Unit
Battery reading
Matched to
File status
Confidence
Battery condition
Trade-in EV, one prior owner
Dash estimate, cold morning
One VIN, one build
Unpublished — manager to value
88%
Not stated by the agent
As receivedThe unit as it arrived and the reading as it was taken, with its conditions beside it — nothing here is adjusted.
Evidence usedVIN and build matchBattery reading, datedRecall lookup, timestamped
Why no health claimA dash estimate off a cold pack is not a diagnostic result. The claim is the manager's.
ActionApprove fileCorrectOrder inspection
What the score decidesConfidence decides how much the manager verifies, not what the listing is allowed to claim.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Every unit taken inTrade-in, lease return, auction or lot stock
03Evidence & draft
Date every reading to its source
Use the build record, the service and damage history, the warranty terms and the readings as they were actually taken.
01Approved path
The evidence arrives assembled
Battery readings, warranty terms, recall lookups and damage history land in one dated file instead of across four systems.
02Human review
Hold the listing where a claim starts
Copy that would have to state a value, a range or a sound battery waits for the manager who answers for the advert.
04Build an evidence trail
Retain every reading, its source and date, the recall lookup, the draft, the manager's correction and what was published — on both paths.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
DMS & inventoryCDK Global · Tekion vAuto · Stock and appraisal records
A number read off the dash, a pack replaced under a campaign and an auction unit with no service file are where the manager sends the evidence back before anything is listed. File quality is reported by cohort, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Dash-only battery readings
5.6%
2.8×
Review
Recall-replaced battery packs
4.4%
2.2×
Review
Auction units, thin history
3.6%
1.8×
Watch
Recent same-model trade-ins
1.4%
0.7×
Normal
Bar: manager-correction rate lift vs. same-model trade-in baseline · scale 0–4.0× · tick at 2.0×2 of 4 slices over threshold
Evidence-linked improvement
A reading without a source is not evidence
A manager sending the file back is not one bad appraisal. It changes the provenance rule, the disclosure list or the source the agent is allowed to read.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Manager corrections, disclosure misses or disputed readings rise in a cohort.
02Diagnose
Narrowed to the build decode, the source read, the age of the reading, the warranty term or the draft.
03Improve
The provenance rule or the disclosure list changes under your used-car manager's sign-off, version-linked.
04Verify
Re-run on stored units from that cohort, including the ones that were listed and pulled.
05Learn
The pulled listing is kept as a test case, and the claim it carried enters your store's advertising notes.
Learn → DetectThe return edge. The next unit is drafted against one more claim this store has already had to take back.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, decode and retrieval, battery evidence, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Workflow discovery and automation-boundary definition.
02DMS, inventory and listing-feed access assessment.
03Disclosure rules and unstated claims.
04VIN decode and build-record matching.
05History, title-brand and recall retrieval.
06Battery-evidence and provenance rules.
07Warranty term, transfer and coverage read.
08Appraisal file assembly and listing drafting.
09Claim-withholding and disclosure testing.
10Cohort slice testing across evidence sources.
11Stock-record write-back and manager handoff.
12Observability, deployment and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne rooftop, one sourceProductionLive inventory and feedsAdvancedWhole group inventory
Introduced at Pilot
Appraisal file with dated, sourced readings✓✓✓
Withheld value, range and battery claims✓✓✓
A named person values and publishes✓✓✓
Store disclosure and wording templates✓✓✓
History, title-brand and recall retrieval✓✓✓
Baseline evaluation✓✓✓
Introduced at Production
Stock-record write-back and manager handoff—✓✓
Drafts shaped for your syndication feeds—✓✓
Observability and evaluation—✓✓
Introduced at Advanced
Additional battery-diagnostic sources——✓
Group inventory and rooftop controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on rooftops, DMS and inventory integrations, battery-evidence sources, listing feeds, disclosure approvals and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your approved disclosures and what a listing may never claim→Disclosure rules and unstated claimsWeek 1
02Read access to the DMS, the inventory tool and your listing feeds→DMS, inventory and listing-feed access assessmentWeek 2
03The battery-evidence sources you trust, and who actually takes them→Battery-evidence and provenance rulesWeek 3
04How warranty terms and transfers are recorded for your franchises→Warranty term, transfer and coverage readWeek 3
05Listings that had to be corrected or pulled, and what they claimed→Evaluation suite, regression cases and failure-mode testingWeek 4
06The model mix you actually take in, thin-history units included→Cohort slice testing across evidence sourcesWeek 5
07A named used-car manager to value the unit and publish it→Manager handoff, then supervised valuation and publishingWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Phases are drawn over the weeks they actually occupy. Week 5 is where the cohort testing ends and the first units are listed.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Withheld claims, store disclosures and the automation boundaryW2DMS and inventory access, VIN decode and build-record matchingW3History, recall and warranty retrieval, and battery-evidence provenanceW4Disclosure checks, claim-withholding tests and the evaluation suiteW5Cohort testing, stock-record write-back, then the first units listedW6Managers value and publish from live files, then Agent Care starts
Reading the bandProvenance rules are fixed in week 3, so nothing reaches evaluation carrying an undated reading.
At the end of W6Managers have valued and published from live files, with every claim traceable to the reading and the date behind it.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Automotive AI agent
Build a listing agent around the evidence you can stand behind.
Show us a month of used EVs you took in — the battery readings you had, the warranty terms you quoted and the listings that had to be corrected. We'll rebuild those files from the same evidence and show you which readings could never have carried the claim the listing made.
