Assemble the title, registration and tax package for a delivered vehicle, track the clock the selling state actually runs, and flag what is missing before your title clerk signs anything.
Stages 1 to 4 run unaided, and nothing is signed at any of them — 49 CFR 580.6(b) wants an individual, and the clerk's lane opens at the confidence gate.
5DecisionBranches at the confidence threshold
High confidence
Goes to the title clerk to approve.
Low confidence
Adds an office-manager read first.
Clerk approval
The package is held with its documents, the state rule and the confidence.
Approve · Amend · Send to manager review
Approved — released for signature▼
6Title systems updatedOnly where write access and approval policy allow it
7Outcome evaluatedAmendments, state rejections, days to transfer and corrections after submission
Amendments
Every clerk amendment is counted, including rejections raised after submission.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Signing or certifying the odometer disclosure.
Filing the title application under a clerk's credential.
Choosing which of the three mileage certifications is true.
Authorising a power of attorney for odometer disclosure.
Automation boundaryAgent acts unaided
✓Assemble the package for the state that will title the unit.
✓Carry each document forward with its date, source and signatory.
✓Compute the clock from that state's trigger and that deal's type.
✓Flag what is missing or stale, and hold the package.
Any write happens inside the boundaries agreed at implementation, never as a signature.
Issuing, re-issuing or voiding a temporary tag.
Remitting collected sales tax or filing the return.
Deciding a vehicle is exempt from odometer disclosure.
Changes to state rule sets, deadlines or approval boundaries.
Example output
One deal, annotated
Everything the agent assembles is attached to the document it was drawn from.
Titling output · single dealIllustrative example
Deal
Prepared line
Clock position
Rule applied
Confidence
Signature required
Texas dealer-financed
Odometer disclosure drafted from the reading the clerk recorded
Day 12 of 45
43 TAC §215.144
91%
Named title clerk
As receivedTaken from the deal jacket and the title on file — nothing on this side is asserted by the agent.
Documents usedBuyer's order, datedAssigned title on fileLien contract and payoff
Why this clockIt is dealer-financed, so §215.144 runs 45 days rather than 30.
ActionApproveAmendSend to manager review
What the score decidesBelow the configured threshold the package picks up a manager read before the clerk.
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 delivered dealFrom the deal jacket
03Assembly
Assemble to the state's rule
Draw on the jacket, the rule set in force and the TxDMV matrix at rev. 17 Nov 2025, priced per vehicle.
01Approved path
The clerk signs, not the system
Complete, in-state deals arrive assembled, aged against the rule and evidenced.
02Human review
Temp tags are a federal matter now
Texas prices each misused tag at $1,000 and SDNY charged eleven defendants on 20 May 2026 — flagged tags reach the clerk first.
04Build an evidence trail
The document, the state rule it was read against and the clerk who signed stay on the deal.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
A blended on-time transfer rate can read as healthy while two states carry nearly all the late transfers, which Texas prices per vehicle. Nestack reports the late-transfer rate by slice, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Out-of-state retail deals
8.6%
3.7×
Review
Dealer-financed contracts
6.9%
2.9×
Review
Trade-ins with an open lien
4.3%
1.8×
Watch
In-state cash deliveries
1.5%
0.6×
Normal
Bar: late-transfer-rate lift vs. in-state cash baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
A late transfer becomes a test
A cycle closes when the late transfer is a case the next release has to catch. That suite is what the next package assembled is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Late-transfer rate rises in one state.
02Diagnose
The car delivered in March whose title moved in July is read back until the cause is one thing.
03Improve
The fix carries a version, and the deals that forced it travel alongside it.
04Verify
Nothing goes out until every touched title case has passed a second time.
05Learn
It is kept for good, and the state rules are amended in the same commit.
Learn → DetectThe return edge. The next detection runs against a suite one case longer than this one.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, titling workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Titling workflow discovery and boundary definition.
02DMS and title-system assessment.
03Per-state deadline and document rule-set mapping.
04Deal-jacket ingestion and normalisation.
05Package assembly and document binding.
06Confidence scoring and gap routing.
07Clerk approval workflow.
08DMS and title-system integration.
09Deadline and document cases.
10Guardrails and signing controls.
11Deal-trail instrumentation.
12Deployment, documentation 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 state, one storeProductionProduction title systemsAdvancedMultiple states / rooftops
Introduced at Pilot
Assembly to your deals and rules✓✓✓
Clerk approval✓✓✓
Package-completeness baseline✓✓✓
Introduced at Production
Reporting by state—✓✓
Approval workflow in your systems—✓✓
Approved write-back—✓✓
DMS and title-system integration—✓✓
Introduced at Advanced
Complex multi-state rules——✓
Multi-stage store approvals——✓
High deal volume——✓
Multi-state titling controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls 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 deal-jacket structure and document set→Deal-jacket ingestion and document mappingWeek 1
02Representative completed title packages→Assembly baseline, rule extraction and document bindingWeek 2
03Your state rule sets and deadline decisions→Deadline, document and automation-boundary mappingWeek 1
04Access to relevant APIs, feeds or exports→DMS and title-system assessment, then integration setupWeek 2
05Applications you would not want signed→Rejection cases and failure-mode testingWeek 4
06What no signature may rest on→Confidence scoring, gap routing, guardrails and approval controlsWeek 3
07Named title clerks to approve packages→Clerk approval workflow, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Each band is drawn over the weeks that phase genuinely takes, so the fifth carries two.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Titling workflow discovery, rule mapping and the automation boundaryW2Source integration and the assembly baselineW3Assembly workflow, confidence logic and approval controlsW4Evaluation suite, deadline checks and failure-mode testingW5Title-system integration, pilot states and targeted correctionsW6One month of deliveries worked under the title clerk, then Agent Care handover
Reading the bandEach bar covers the weeks its work is named in and no others. Week 5 genuinely carries two.
At the end of W6Validation closes on live deals, and Agent Care picks up monitoring.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Automotive AI agent
Build a titling agent around the clock your state actually runs.
Show us your deal jacket, your state rule sets and who signs. If your stores read intent to defraud as the test, then note it is the private standard at §32710(a), not the criminal one.
