Brevmont Labs
Research archive
Dealer execution research
Original essays on dealer CRM execution, rep workflow, context-grounded AI, and bounded autonomy. The archive is organized as a monthly research spine, not a content feed.
01
Execution layer
The gap between what the CRM records and what the floor actually does.
02
Context discipline
How useful follow-ups depend on visible context, routing, and refusal rules.
Reading path
Two essays define the thesis.
Research standard
Field notes, product evidence, and thesis stay separate.
Brevmont Labs publishes company research from dealership workflow observation, internal product QA, and category analysis. No anonymous quotes. No invented benchmarks. When a claim needs public proof, the essay should say where the proof comes from.
Archive
All research
Newest first · 18 essays
No. 18
More leads are not always the answer
Small service businesses often ask for more leads, but the larger leak can be execution after acquisition: slow response, weak follow-up, buried proof, and missing next steps.
No. 17
The execution gap was not a dealership problem
The dealership floor exposed a pattern: sales systems can record activity without improving the behavior inside the conversation. As Brevmont tests outside automotive, similar moments keep appearing on different surfaces.
No. 16
The proof is already in the camera roll
Contractors often already have the proof they need to close trust gaps. The bottleneck is retrieval, organization, and deployment at the moment a prospect asks to see work.
No. 15
Context is the product in dealer AI
Useful dealer AI is not mainly a writing problem. It is a context problem: what the system can see, what it refuses to infer, and how every generation is verified.
No. 14
The rep-execution layer is the missing system
The CRM stores the record. The missing system is the rep-execution layer that turns what the rep knows into a generation, a note, and a manager-visible receipt.
No. 13
What Your Dashboard Cannot See
Dealer CRM dashboards measure activity, not behavior. The gap between what reps type and what reps do has widened for a decade. A diagnosis of the visibility problem on the modern sales floor.
No. 12
When the API Doesn't Exist, the DOM Is the Answer
When a dealer CRM API cannot support the workflow, the integration layer often has to live in the browser surface the rep already uses. The architectural decision shapes whether the tool gets used.
No. 11
Why Dealer Software Hasn't Had a Linear, Stripe, or Figma
Linear, Stripe, and Figma redefined their categories in the last decade. Dealer software produced no comparable vendor. The reasons are structural and the conditions are now changing. The category opens for the first time in twenty years.
No. 10
Activity Versus Behavior in the Floor's Data
Activity and behavior are two different things measured as one inside the dealer CRM. The dashboard reports activity counts as a proxy for behavior. The proxy is broken. The next layer captures behavior at the conversation rather than at the typing.
No. 09
The OEM Mandate Stack
The OEM mandate stack is the layer of dealer software the dealer principal pays for but did not choose. The factory uses certification leverage to enroll dealers in vendor relationships the dealer would not select on his own. The cost is structural and the workflow duplication is consistent across the category.
No. 08
The Integration Tax Across the Dealer Stack
Dealer software vendors publish integration directories with hundreds of partners. Two to four are wired live at any given rooftop. The integration tax is paid in admin labor, dashboard inaccuracy, and decision drift across the dealer principal's most important calls.
No. 07
Visibility Without Execution
The dealer software category built fifteen years of visibility tooling without shipping the execution layer underneath. Dashboards multiplied. Throughput on the floor did not. The principal who watches better dashboards is still watching the same gap.
No. 06
The Bilingual Pipeline No CRM Surfaces
Hispanic buyers represent twenty to thirty percent of new vehicle volume in many U.S. submarkets and convert at above-average rates. The CRM has no language field. The category has built one-language software into a multi-language market and the principal is paying for the gap.
No. 05
The Sub-Prime Re-Engagement Window
Sub-prime buyers who walk at the payment quote return on a 30 to 90 day re-engagement window once the down stack rebuilds. The CRM marks them lost the day they walk. The dealer principal who has been pricing this segment as one-and-done has been pricing it wrong for fifteen years.
No. 04
The Click Tax in Dealer CRM
Fully logging a customer interaction in a modern dealer CRM costs 30 to 50 clicks. At rooftop scale, full compliance is impossible. The dealer principal pays full price for a CRM that is structurally half empty.
No. 03
Lead Source Conversion at the Group Level
Lead source mix at a franchise dealer group is inverted from what most dashboards optimize for. The highest volume sources convert at the lowest rates. Group-level data routinely shows 60 to 70 percent of gross profit coming from 30 to 40 percent of lead volume.
No. 02
The Stack a Franchise Dealer Group Actually Pays For
Franchise dealer groups run 8 to 14 software contracts per rooftop. The integration story is theoretical. The tax is paid in compounding fees and in floor attention. The next layer absorbs the stack, not another vendor in it.
No. 01
The Category That Sold Itself the Same Product Twice
The dealer CRM category has commoditized. M&A collapsed the vendor count while feature parity converged. Pricing power disappeared a decade ago. The next wave of value moves to a layer the incumbents cannot build.