Not a demo asset. An operator's tool.
LouieAuto is used every business day in the operator's own stores — built by a car guy who ran it where he works before ever offering it to anyone else. This page documents the structural facts an acquirer can verify.
Before / After — Founder's Pilot Group
Structural facts.
Each number below is structurally verifiable. Where a live endpoint exists we link it.
Footnote: "operator deployment" refers to the operator's dealer group. This is not a third-party paying customer reference — it is a working product with an in-house reference site. For M&A purposes this is the equivalent of a design-partner deployment with a four-quarter operating history.
What an operator-built product means for the price.
Most vertical AI startups at this stage are pre-deployment. LouieAuto is post-deployment. The delta is material to an acquirer's diligence risk and should be priced in.
| Dimension | Pre-deployment startup | LouieAuto |
|---|---|---|
| Product-market fit risk | Unknown — theoretical | Tested across the operator's group, 4+ quarters |
| Integration risk | Hypothetical | DMS-agnostic overlay proven in live workflow |
| Operator knowledge in system | Training-data approximation | Encoded directly by the operator (12 tables, 3,059 rows) |
| Deal-desk accuracy | Unmeasured | Validated daily by the operator writing deals |
| Required retention window | 24–36 months to de-risk | 24 months with milestone-based earnout aligns to integration |
The /api/moat/public endpoint pulls from commodity sources — FRED, EIA, UMich,
OEM program feeds. The moat is not the data. The moat is the operator-encoded system prompts,
lender playbooks, stip logic, and desk-voice scripts that sit between those inputs and the dealer.
"A competitor can call the same APIs. They cannot replicate 30 years of floor experience compressed into prompt engineering — without hiring an operator and spending 18–24 months encoding the institutional knowledge. That encoding is what ships with the asset."
The moat compounds. Beyond the encoded knowledge, every deal that flows through Louie gets logged with its outcome — funded or declined, trade auction price vs. estimate, structure that held vs. structure that got recut. After 12 months of production use, the system has a store-specific outcome record that no acquirer can replicate by buying the software alone; it accrues only with time in operation. An acquirer isn’t pricing a static asset. They’re pricing a continuously self-improving dataset trained on real dealership outcomes at real current-market conditions.
Your deal data never trains a public AI model. LouieAuto uses Anthropic's Claude API with zero-data-retention settings — deal records are passed as context, not stored by the model provider. Your outcome history compounds on your instance only.
- ✓ Dealer data stored in self-contained SQLite on your server — no shared cloud database
- ✓ Full data portability — your outcome dataset exports as JSONL on request, usable with any AI stack
- ✓ One-page Data Processing Agreement available — CDK and Reynolds do not offer equivalent dealer-favorable DPAs
- ✓ FTC Safeguards Rule compliant at the control level — access log, encryption at rest, breach notification workflow all documented
Founder's pilot group — what moved.
Operator-controlled pre/post study across a multi-store franchise dealer group — a mix of domestic and import franchises. Before/after metrics below are rolling 12-month trailing vs. the 12-month trailing window before LouieAuto was deployed across the group. Store names are withheld from public write-up; full detail available to acquirers under NDA.
Method: metrics pulled from the group's DMS monthly P&L rollups and internal ActivityLog event tables. Trailing-12 windows compared: pre-deployment (Feb 2024–Jan 2025) vs. current (Mar 2025–Feb 2026). No store was excluded. Group benefits from a mature operator team independent of LouieAuto — the uplift is LouieAuto's contribution on top of an already-competent operating baseline, not a greenfield turnaround.
Why this matters for an acquirer
The metrics above are the reason the $150K–$274K/rooftop/year uplift claim on /acquire is not a marketing number. It's the pilot group's own result, broken down by the specific module that drove it, across a controlled multi-store operating window. An acquirer plugging LouieAuto into their own dealer-customer base should expect a range around this band, subject to their customers' starting PVR and inventory discipline.
What is not claimed here.
LouieAuto does not claim paying third-party customers. Pricing is live and inbound inquiries exist but no commercial ARR has been booked. This is a deliberate positioning — the product is being sold, not scaled, and avoiding channel conflict with acquirers. The strategic-tuck-in model on /acquire and the value math on /facts assume zero current ARR.
Everything on this page is either structurally verifiable (store count, years in production, module count, DB rows) or live-endpoint-auditable (moat refresh, uptime).
Ready to go deeper?
Data room includes: DMS P&L rollup exports, ActivityLog methodology workbook, architecture diagram, lender agreement list, and IP assignment framework. Released under NDA to qualified acquirers.
brian@louieauto.com · Typical NDA turnaround: same business day