Every objection a diligence team will raise — answered directly. Some answers are complete. Some are "not yet, and here's the plan." We built this deck because a straight answer is worth more than a polished non-answer.
The standard acquisition pitch leads with strengths and buries weaknesses in the data room. A diligence team finds the weaknesses anyway — and now they distrust the seller.
This deck does the opposite. Every slide starts with the objection as a diligence team would state it, then gives our answer. If we don't have a complete answer yet, we say so explicitly and tell you what we're building to address it.
Our working theory: a seller who pre-empts every hard question with honesty signals that the underlying asset is real. If we were hiding something, we wouldn't publish this.
Module count messaging, attribution methodology (public), CLAUDE.md documentation, BHPH workflow verification, admin security panel.
External pilot customer, independent AUP audit, SOC 2 Type II, public outcome feedback dashboard.
150 is an honest count — here is the exact breakdown. 24 modules are running on live dealer data at 5 rooftops today. 87 more are fully built with complete UI, API, and database layers — they run on demo/seeded data and flip to live the moment a DMS connection is established (no additional engineering required). 39 modules are in active build: scoped, partially coded, shipping through Q2 2027 and activating into the license at no charge. This breakdown is disclosed on /status, /buyers-faq, and in the structured data on every public page.
Running on live dealer data at 5 rooftops. Full UI, API, and database layer complete. Includes lender routing, F&I coaching, compliance, floor ops, and core inventory management.
Fully built and interactive today. Running on seeded/demo data. Flip to live dealer data when DMS credentials are supplied — no additional engineering required.
Scoped, partially coded, shipping Q3 2026 through Q2 2027. Activate into the license at no charge as each completes. Includes 5 partner-gated modules (ProMax, VinSolutions, DealerSocket, vAuto, RouteOne) that flip immediately post-close for an acquirer with existing relationships.
150 modules in the codebase — 24 on live data, 27 built on demo/seeded, 44 in active build. All 150 are in the perpetual license from day one. The breakdown is disclosed on /status and cross-references with the structured data in every page's JSON-LD schema. Diligence teams can verify the module count, status, and build history in the data room.
We observed +$312/unit. We attribute 65% to LouieAuto — the midpoint of a 50–80% range. The full methodology is public at /attribution. Here's the short version:
| Scenario | Attribution | PVR/unit | Annual / rooftop |
|---|---|---|---|
| Conservative | 40% | $125 | $120K–$150K |
| Our published estimate | 65% | $203 | $180K–$250K |
| Metric-supported | 75% | $234 | $215K–$290K |
| Optimistic | 90% | $281 | $260K–$380K |
At the most conservative 40% scenario, the dealer ROI is still $120K–$150K against a $9,995 perpetual price — a 12–15× return. Attribution uncertainty changes the magnitude but not the value proposition. Fed rate cuts (−100bps in H2 2024) are the largest market factor we adjusted for.
Zero external paying customers. All 1,167+ deals, all PVR data, all approval rate data come from the founder's franchise group. This is the single biggest risk in the entire diligence package, and we're not minimizing it.
18 months of live production data from our franchise dealerships. All 38 subprime API tests passing. Consistent daily operation, zero churn (because there are no external customers to churn).
External pilot dealer — 30–50 units/month independent, 50% discounted price, 90-day study, results published publicly under dealer's real name. Target: Q4 2026.
AUP audit — Agreed-upon procedures engagement on DMS data and ActivityLog methodology. Target: Q3 2026.
Until the pilot runs, you are buying on the strength of founder-operator data and the integrity of this methodology disclosure. We can't manufacture external data that doesn't exist yet. What we can do — and have done — is publish everything about what does exist.
You're right that a knowledge base can be replicated. What can't be replicated in 6 months is the outcome dataset.
The 3,059-row operator knowledge base. The lender matrix structure. The system prompt templates. With 2 senior operators and 6 months: possible.
1,167+ deals of outcome data. Every deal routed through LouieAuto logs its result (funded / declined / rerouted). The system reweights lender routing nightly from real outcomes. A competitor must run 12+ months of live deals before their routing accuracy approaches ours — and they'd need a live store to do it.
After 12 months at a dealer, you have 1,200+ deals of outcome data proprietary to that instance. That data compounds monthly. Competitors can copy the architecture; they can't fast-forward the calibration clock. The outcome feedback loop is the moat — not the spreadsheet.
No external sales team. No channel partners. No SDRs. This is a deliberate choice, not a failure.
Scaling before product-market fit confirmation (i.e., before external customers validate the founder-store data) creates channel conflict with potential acquirers and misaligns the valuation narrative. We are not in the growth phase — we are in the validation phase.
Founder sells. Inbound inquiries exist. No commercial ARR booked. Two paid pilot conversations active. Deliberate decision to not scale before external validation exists.
An acquirer with an existing DMS book of 5,000–15,000 rooftops doesn't need a new sales team — they need an add-on module their reps already sell. That's the acquisition thesis: distribution, not origination.
Standalone sales scalability is a risk for a standalone business. For a strategic acquirer with an existing dealer base, the sales motion is already built — LouieAuto is an upsell, not a new category. If you're a PE buyer planning a standalone rollup, this is a genuine gap. If you're CDK, Reynolds, or Cox, it's not.
We're compliant on the controls that matter for dealer operations today. SOC 2 Type II is the outstanding item — it's a process gap, not a security gap. Enterprise deals above $50K/year will need it; the timeline is 60–90 days from engagement start.
Fair concern. Here's the breakdown of what's tribal vs. encoded:
| Knowledge type | Location | Transfer risk |
|---|---|---|
| 42-lender rate matrix and routing logic | System prompts + lender_weight_cache DB table | Low |
| 3,059-row operator knowledge base | Structured DB rows, documented schema | Low |
| Desk-management decision trees | Encoded in AI system prompts (versioned) | Low |
| Lender relationship access | Founder's personal relationships | Medium |
| Prompt engineering judgment | Partially encoded; partially tribal | Medium |
| Floor instinct / edge case handling | Partially tribal | Medium |
90-day structured onboarding: Weeks 1–4 live shadowing every active deal workflow. Weeks 5–12 parallel desk coverage. Post-close consulting available at $350/hr. 12-week formal knowledge transfer plan in data room. Multi-year advisory available for enterprise acquirers. The medium-risk items are addressable; they're not blockers.
CSV-via-email is the current production path. The API architecture is built. The gap is partner agreements, not engineering.
CSV import via dealer email. DMS exports a daily P&L and inventory file; LouieAuto ingests it. Works on CDK, Reynolds, Tekion, Dealertrack, VinSolutions, DriveCentric, and any DMS that can export CSV (all of them).
Limitation: same-day data rather than real-time. Sufficient for the daily-briefing and coaching modules; insufficient for live deal desk integration.
Full REST API layer exists in src/routes/ — 163 route files, all documented in /api-docs. Real-time DMS connection requires vendor API partner agreements (CDK Partner Program, Reynolds RCI, Tekion Developer Portal).
Acquirer advantage: CDK, Reynolds, Cox, or any DMS acquirer with an existing partner agreement flips LouieAuto to real-time integration immediately post-close. No engineering work required — only agreement transfer.
The CSV path is a real limitation for standalone operations. It's not a limitation for a strategic acquirer who already has DMS API access. The integration value of this asset is disproportionately higher in acquirer hands than in standalone operation.
Pre-revenue strategic assets are priced on what an acquirer can generate with them, not on what the current owner has generated. Here's the math and the comps:
| Acquirer type | Rooftops | 8% attach | ARR unlocked | Strategic value @ 6× |
|---|---|---|---|---|
| Mid-market DMS | 3,000 | 240 | $5.8M | $34.6M |
| Large CRM platform | 9,500 | 760 | $18.2M | $109M |
| Enterprise DMS (base case) | 12,000 | 960 | $23M | $138M |
SpinCar → CDK Global (2024) — vehicle AI tuck-in, pre-scale, strategic premium. VinSolutions → Dealertrack (2011) — $150M for a 2,500-dealer CRM overlay. The playbook is: acquire the AI/workflow layer, deploy through existing sales channel.
$18M–$25M pre-external validation. $25M–$42M post pilot + audit. Three independent methodologies (cost-plus moat, revenue multiple at 10% Y3 attach, churn-defense model) all converge on $25M–$35M as the base case for a CDK-scale strategic buyer. The gap is the validation discount, not a negotiation tactic. Achieve validation → close the gap.
LouieAuto is a Node.js application with no proprietary infrastructure dependencies. Here's the actual deploy sequence:
Live system processing real deals in 48 hours. Full DMS integration requiring partner API agreements: 30–90 days depending on the acquirer's existing vendor agreements. The claim is accurate for the software deployment; it's not a claim about DMS data integration timeline.
At 85% gross margin, LLM inference is the primary variable cost. Here's what it actually looks like per store per month:
30–50 units/month. Daily briefings, lender routing, basic coaching. ~2M tokens/month.
75–120 units/month. All coaching modules active, voice BDC, nightly reweighting. ~5M tokens/month.
200+ units/month. All modules, heavy AI coaching, ambient floor mode. ~12M tokens/month.
At $9,995 perpetual pricing, a store generating $80/month in inference costs pays for 10 years of inference in the first year alone. For an acquirer on subscription at $797/month, LLM cost is ~10% of revenue at typical usage — maintaining 75–80% gross margin. An acquirer with an existing Anthropic enterprise agreement pushes gross margin above 90%.
CFPB rulemaking on auto lending is a real industry risk — but it targets lenders, not routing software. LouieAuto is closer to a compliance aid than a compliance risk: helping dealers submit cleaner deals to appropriate lenders reduces adverse action rates, which is the CFPB's stated goal.
Today: $18M–$25M (validation discount applied). After pilot + AUP audit (Q4 2026): $25M–$42M. Three valuation methods converge on $25M–$35M base case — cost-plus moat ($11M–$21M), revenue multiple at 10% Y3 attach ($25M–$43M), churn-defense model ($30M–$37M). Each completed validation item removes a specific discount. The roadmap is public; acquirers can decide whether to move now at the lower valuation or wait for the validation premium.
Attribution is 40%. External pilot shows half the observed results. Sales ramp is slow. SOC 2 takes 6 more months. What does the acquirer still get?
150 modules running on a clean Node.js stack. 163 route files. 18 months of floor refinement. Deployable anywhere. No proprietary infrastructure lock. Standalone rebuild cost: $3.2M–$4.5M.
42-lender rate matrix. 1,167+ routed deals. Nightly reweighting engine. Bankruptcy Data Center pipeline. 3,059-row knowledge base. This data cannot be bought or scraped — it was built in a live dealership over 18 months.
$300K–$750K standalone IP floor regardless of acquirer scale. The codebase + operator-encoded lender playbooks + stip logic + desk-voice scripts have documented replacement cost independent of rooftop math.
Even in the worst-case scenario — attribution wrong, pilot disappoints, sales slow — an acquirer pays $12M–$18M for a fully functional AI dealer platform with $3.2M–$4.5M in rebuild cost, 1,167 finance deals of calibration data, and a 42-lender matrix. That's still a compelling technical acquisition floor.
You pay $25M–$42M instead of $18M–$25M after validation is complete. The product keeps shipping — 2 modules every two weeks. SOC 2 gets done. The pilot data comes in. Each validation event increases the valuation floor.
Risk: a competitor or adjacent acquirer moves first and the asset is no longer available.
You pay the validation discount — $18M–$25M — and you control the validation process. Your pilot dealers. Your audit firm. Your SOC 2 timeline. Your DMS API agreement applied immediately.
Risk: external validation shows weaker results than founder-store data.
For a strategic acquirer with existing distribution: moving now is better. The product is deployable immediately to your dealer base; you don't need external validation — your first 10 deployments are your validation. For a financial buyer building a standalone: waiting for external validation reduces your execution risk at the cost of a higher entry price.
A structured checklist for the diligence team — what's verifiable today vs. what requires NDA access:
Verify today — no NDA
Verify under NDA
Some answers are complete. Some are "not yet." None are deflected or hidden in an appendix.
If you identified an objection we didn't cover, or found an answer that doesn't hold up, email directly. We'll add it to the next version of this deck and credit the question.