“CRM Is Broken!” Why Static Workflows Kill Deals (And How to Engage with Shoppers In Real Time) | Matt Leone, CEO of DriveCentric

“Static workflows” refers to rigid, pre-defined processes that don’t adapt when a user gets stuck. In CRM and dealership operations, that rigidity can slow down responses and cause missed opportunities, because shoppers and dealers need timely, situation-specific help.

This is the episode’s core theme: the hosts argue that CRM workflows are failing dealers because they’re too static and not designed for real-time, cross-team customer engagement.

Salesforce is a widely used CRM platform, referenced here as an example of how CRM tools are configured for specific teams. The episode criticizes the idea that CRM usage should be limited to sales while other dealership roles are actively speaking with customers.

F&I stands for Finance and Insurance, and the F&I manager typically handles financing, warranties, and insurance products during the sales process. The episode highlights that the F&I manager is often one of the dealership’s best closers, so they should be included in CRM-based customer conversations rather than working in isolation.

BDC stands for Business Development Center, commonly a team that contacts leads and schedules appointments for the dealership. The episode includes BDC in the list of groups talking to customers, arguing they should also be represented in the CRM workflow.

DriveCentric is a dealership-focused technology company discussed in the episode. The host frames it as part of the solution to how dealers manage customer conversations and CRM workflows.

Real-time customer engagement means responding to shoppers immediately and keeping customer communication current as the conversation evolves. The episode contrasts this with rigid task management, arguing that dealers need faster, more coordinated responses to protect margins and improve deal outcomes.

Rigid task management refers to CRM processes that rely on predetermined steps and scheduled follow-ups rather than adapting to the customer’s current needs. The episode argues this approach breaks down in modern dealership environments where multiple roles interact with customers and timing matters.

This concept means reducing tool sprawl (multiple disconnected systems and channels) so the dealership communicates consistently across teams. The episode ties it to protecting margins by ensuring customers get coordinated, timely messaging instead of conflicting or delayed responses.

“CDG Circle of communities” appears to be a dealer-focused community or network where companies are discussed and mentioned. The hosts use it as a proxy for industry visibility and sentiment around DriveCentric.

CDG Circle is referenced as a community space where companies receive mentions and where sentiment can be observed. It’s used in the episode as an indicator of industry traction for DriveCentric.

A Rolodex is a mechanical card file used to store contact information on physical cards. The host uses it as a metaphor for how early CRM systems digitized the same idea—keeping lead and customer contact details organized.

Microsoft is referenced as a company that released CRM-related software in the late 1980s/early 1990s era. The point is historical: CRM began as digitizing contact management and then expanded into workflow and communication.

SAP is an enterprise software company known for large-scale business systems. In the transcript, SAP is mentioned as an early CRM-related offering that focused on process, workflow, and accountability rather than industry-specific dealership needs.

Lead management is the process of capturing, tracking, and nurturing potential buyers through the sales funnel. In CRM terms, it often includes assigning leads, setting follow-up tasks, and measuring rep responsiveness to improve conversion.

CDK is a well-known automotive dealership software provider. The transcript places it in the evolution of CRM/lead systems in the auto tech vertical, alongside other dealership-focused lead tools.

Reynolds is mentioned as part of the dealership software/lead-management evolution in automotive tech. The transcript doesn’t specify which Reynolds product or company, but it’s clearly treated as an auto-industry software player.

A reporting layer is the analytics and dashboards built on top of operational systems so managers can see activity and performance. In dealership CRM terms, it’s what turns raw lead/task data into visibility for leadership.

Tech bolt-ons are add-on products layered onto an existing platform to patch gaps or add features without redesigning the core system. The speaker argues that in auto tech, these bolt-ons proliferate while the underlying CRM approach stays static.

A digital retailing widget is an embeddable tool (often on a dealer website or messaging flow) that helps shoppers complete parts of the buying process online—like selecting vehicles, estimating payments, or configuring options. The speaker lists it as one of many “bolt-ons” that get added around a static CRM.

The speaker describes a fragmented tech stack where many vendors each handle different pieces of the shopper experience (video, phone, chat, digital retailing). Even with all these additions, the CRM category can remain unchanged if the core workflow and data strategy don’t evolve.

A “mobile-friendly application” is software designed to work well on phones, where many shoppers will interact first. The speaker ties this to higher engagement by making the CRM experience easy to use on mobile.

“Native video” means video features built directly into the platform (rather than relying on external tools). In a dealership CRM context, it can help reps communicate more effectively—like sending personalized walkarounds—without adding extra steps.

“AI bolt-ons” refers to adding AI features as separate add-ons to an existing CRM stack. The speaker suggests that if you simplify the core platform, you may not need as many extra AI modules to achieve better engagement outcomes.

A general ledger is the core accounting record that organizes financial transactions for reporting and compliance. The segment uses it to explain that financial systems should be separate from customer management systems like CRM.

Oracle is mentioned as an example of enterprise software used in the auto tech ecosystem, alongside Microsoft and SAP. In this context, it’s part of the broader “financial/compliance/general ledger” tooling that should be accurate and clean as a source record.

DMS usually means a Dealer Management System—software that handles dealer operations like inventory, service/repair workflows, and often parts of financial reporting. In the segment, the host contrasts DMS with CRM to argue they should be separate systems with different jobs.

CRM stands for customer relationship management, meaning it should help a dealership manage interactions with customers across the whole journey. In this segment, the host argues that many CRMs are implemented as sales-team task tools instead of a true system for managing the customer experience in real time.

CDP typically means Customer Data Platform, software that collects and unifies customer data from multiple sources. In this segment, the host lists CDP alongside CRM and other tools, arguing that the CRM should evolve into the system that manages the customer rather than forcing data and workflows into separate silos.

A service advisor is the front-line communicator in a dealership’s service department who interviews the customer, writes up the work order, and coordinates with technicians. This segment frames service advisors as part of the same real-time customer engagement flow as sales and BDC, rather than siloed behind separate processes.

“One voice” refers to consistent, unified messaging across channels and teams so the customer experiences a coherent conversation. The segment argues that multiple disconnected AI systems or tools can produce conflicting responses, and that the dealership needs a single integrated engagement layer.

“gentek AI” is referenced as an example of where AI-driven customer engagement is headed. The segment uses it to support the idea that AI responses should be unified and integrated rather than fragmented across multiple systems.

Lotlinks is the sponsor and the company behind “Lot GPT,” which is positioned as an AI tool for car dealers. The pitch emphasizes inventory and pricing guidance based on VIN-level data and shopper behavior.

Lot GPT is described as an AI-powered inventory strategist for car dealers. It’s marketed to analyze inventory, pricing, market conditions, and real shopper behavior, then recommend actions for specific vehicles.

VIN-level data means using the vehicle identification number to analyze information at the individual car level, not just by model or trim. For dealers, this enables more accurate targeting—like identifying which specific units are at risk or where demand exists.

NADA refers to the National Automobile Dealers Association, which hosts an annual convention where automotive retail technology and strategies are often announced. Mentioning NADA signals that the product update is aimed at mainstream dealer operations rather than a niche audience.

A “service engagement hub” is a centralized way to manage customer communication for the service department (repairs, maintenance, scheduling, updates). The concept matters because static or siloed workflows can cause delays and inconsistent messaging, while a hub supports more coordinated, real-time engagement.

F&I stands for Finance and Insurance, the department responsible for things like loans, warranties, and insurance products. An “F&I engagement hub” implies a centralized system to coordinate how that department interacts with customers, ideally in real time and across channels.

A “sales engagement hub” is a centralized platform for coordinating how the sales team interacts with shoppers. The underlying idea is to unify communication across departments so customers get consistent responses, regardless of whether they contact the dealership via phone, video, or other channels.

“Magentaic AI agents” refers to AI-driven agents used to handle or assist customer conversations within the engagement platform. In this context, they’re positioned as enabling the system to talk to customers across multiple channels (reception, voice, BDC, video) more efficiently than manual, static processes.

In this context, “pods” are dedicated support teams assigned to an account for its lifetime. They’re described as virtual but still capable of providing direct, human answers to dealership questions through the platform.

The segment contrasts static workflows with “real time” human support. The idea is that when dealers hit a question (like how a feature works), immediate answers reduce friction and keep the process moving, which helps deals progress.

“Virtual” onboarding/setup means configuring and training users remotely rather than on-site. For dealerships, this changes how quickly teams can adopt tools like CRM and how effectively vendors can transfer process knowledge.

“Instantaneous support” implies near-real-time help for users—often through a platform connecting dealers to an account manager or support person. In dealership operations, faster support can reduce downtime and improve lead handling.

“Remote customer experience” refers to how well a dealership (or vendor) supports shoppers and staff when interactions happen off-site—like via app, phone, or video. The point here is that if support and onboarding are remote, communication quality becomes a make-or-break part of the experience.

A “forcing function” is a design or process constraint that compels a desired behavior. In this context, remote installation/onboarding forces the company to build strong communication and support practices because there’s no in-person fallback.

Installation and onboarding are the steps required to deploy a system and get users (dealers, sales teams, support staff) using it effectively. In CRM and dealership tech, poor onboarding can make even good tools feel “broken” because reps don’t adopt the workflow or don’t use it consistently.

A “virtual launch” means rolling out a program or platform to dealerships remotely (without in-person onboarding events). In this context, it’s being used to show that onboarding and training can be done digitally while still achieving strong results.

This describes rapid dealership onboarding—getting many stores up and running quickly. It’s a process/operations concept relevant to how dealer-facing software or services scale, and why “static workflows” may fail when speed and responsiveness matter.

“Extended hours” refers to offering support beyond normal business times so dealers can get help when they need it. In a dealership engagement context, this supports real-time responsiveness rather than waiting for the next business day.

A “touch point” is a specific moment of interaction with a shopper during their buying journey (e.g., follow-up, outreach, or assistance). The host is arguing that dealers need ongoing touch points to guide shoppers in real time rather than relying on fixed, one-time workflows.

“Pod numbers” appears to be a dealership/marketing tracking label used to categorize or reference specific campaigns, locations, or content modules. The speaker notes they “reference them as pod numbers,” suggesting it’s an internal way to measure which virtual launch or engagement is driving results.

“Real time engagement” refers to interacting with shoppers as they move through the buying journey—on the lot, in the showroom, or during delivery—rather than waiting for a desktop-based workflow. The idea is to meet customers where they are and respond quickly to their questions or actions.

Using a mobile device for dealership workflows enables faster access to leads, appointments, and customer communication compared with desktop-only systems. This segment argues that being “where people wanted to be” (on mobile) improves adoption and responsiveness.

A voice assistant lets users perform actions by speaking instead of typing through an app. In dealership CRM workflows, this can speed up common tasks like checking appointments, marking availability, and reassigning leads between reps.

Siri is Apple’s voice assistant, used here as an example of “genius voice assist” functionality. The point is that voice commands can reduce friction for dealership reps when managing tasks like appointments and lead transfers.

A “hot lead” is a shopper who shows strong, immediate buying intent—often by taking an action like submitting a form, requesting info, or actively browsing. The segment ties “hot lead” to the dashboard question of who you need to engage with right now.

The discussion focuses on what “signals” a dealer should track and how to weight them when measuring engagement. The goal is maximizing conversion by identifying which shopper behaviors (like active website use and messaging) indicate buying intent.

The segment argues that video content drives higher response rates and adoption because it gives shoppers a richer way to interact. It also stresses that the value comes from tracking engagement (views and depth) rather than just sending video links. That engagement then informs how the dealership prioritizes outreach.

Engagement tracking means measuring how shoppers interact with content—such as whether they viewed a video and how deeply they engaged. The segment emphasizes using these signals to judge lead quality and effectiveness of outreach. This turns marketing activity into actionable CRM triggers.

A visitor ID is a unique identifier used to recognize a website visitor across sessions or interactions. In dealership marketing, it helps connect on-site behavior (like video views) to a specific lead record so outreach can be personalized and timely. This is part of “connecting dots” between digital activity and CRM follow-up.

“Triangulation” here means combining multiple data points about a shopper (website activity, video views, and engagement level) to form a clearer picture of intent. The segment uses it to justify prioritizing outreach—placing highly engaged visitors at the top of the list. It’s essentially a lead-scoring/intent-modeling idea applied to digital behavior.

“Genius” is described as an AI component built into the product to catch relevant signals and support the dealership’s workflow. The segment implies it helps interpret engagement data and respond appropriately, rather than relying on fixed steps. This is presented as part of making CRM more responsive to shopper behavior.

An engagement gap is the time between a customer’s interaction and the dealership’s next response. The segment frames this as a measurable KPI (minutes/seconds) that can be visualized in dashboards to help managers and teams act faster.

Dashboards and filters are used to visualize lead/customer activity and highlight issues like long engagement gaps. Here, the host describes showing managers and the whole team which customers are actively engaging and where follow-up is lagging.

P&L stands for profit and loss, a financial statement that shows revenue, costs, and overall profitability. The discussion ties CRM/lead-handling performance to dealership economics—how process failures can show up as lost revenue or higher costs.

“Average sales per sales person” is a dealership productivity metric that measures how many vehicles each salesperson sells over a period. The host notes it hasn’t improved much despite increased spending on technology, implying the tools aren’t translating into better conversion or efficiency.

The segment describes using AI to generate a performance review for dealership leadership (general manager or sales manager). It’s meant to evaluate each salesperson’s strengths, weaknesses, and how they compare to peers, then suggest coaching adjustments.

“Sentiment of the customer” refers to measuring the tone or attitude behind customer messages—e.g., whether they sound enthusiastic, skeptical, or frustrated. In sales coaching, sentiment helps identify what specific communication tactics lead to better outcomes, even if activity volume (like video count) is lower.

The host argues that training should be informed by the best available data—specifically, data from the salesperson or team member interacting with the most shoppers. That approach ties coaching to real performance signals rather than generic assumptions.

The segment contrasts real-time reporting with historical look-backs. Real-time data helps teams respond to shopper behavior as it happens, while historical reports mainly show what already occurred, which can slow down coaching and process changes.

“Real time information” means live updates as events happen, rather than waiting for scheduled reporting. In a sales context, it can show who’s responding to leads, who’s converting, and why certain reps are performing better. The episode contrasts this with static workflows that only reveal results after the fact.

A leaderboard is a gamified performance display that ranks reps based on measurable outcomes. In dealership CRM usage, it can help managers quickly identify top performers and investigate what behaviors drive results. The segment implies the “why” behind ranking matters, not just the rank itself.

This refers to the traditional funnel where the customer’s main progress happens only after arriving at the dealership. Modern retail strategies try to move more of the decision-making earlier—through messaging, quotes, and scheduling—while still keeping the in-person experience.

“Agent dashboards” are software interfaces that help dealership sales teams manage leads, conversations, and next steps in one place. The idea is to reduce manual work and make it easier for agents to respond quickly and consistently.

The speaker is describing “shopping friction,” where customers must contact or visit many dealerships to compare options, pricing, and availability. Reducing this friction is a key goal in modern CRM and lead-management systems.

The segment frames customer-facing AI as a “personal assistant,” meaning it should understand intent and respond naturally rather than forcing users through fixed menus. For dealerships, this matters because shoppers want answers that feel like a real person at the store, not a rigid chatbot.

Large language models (LLMs) are AI systems trained on huge amounts of text to understand and generate human-like language. The host notes that if you have many different “agents” trained in different ways, you can’t expect them to talk to customers with the same tone and effectiveness.

Conversational AI is software that can hold a back-and-forth dialogue with a person, often via chat or voice. In the segment, it’s discussed as something dealers may use, but the host questions whether it’s the right approach without a broader engagement platform and proper integration.

Integrations are connections between different dealership systems (like CRM, chat/voice tools, and inventory or scheduling software) so data and conversations flow between them. The discussion suggests dealers want simpler workflows, which often depends on how well these integrations work.

Centralized experiences means consolidating customer-facing tools and data into fewer systems so the shopper journey is consistent. In dealership tech, this can reduce handoffs and make it easier to manage conversations and follow-up.

A customer engagement platform is software used to interact with shoppers across channels (chat, voice, SMS, web) and guide them toward next steps like scheduling or buying. The episode frames DriveCentric as such a platform rather than just a tool for internal dealership operations.

The “desking tower” refers to the sales desk/office area where deals are structured—pricing, trade details, and deal terms are typically finalized. The segment uses it as an example of a step where the process can become fragmented if systems aren’t integrated.

The cashier step is where the transaction is finalized—payments, paperwork processing, and closing the deal. In the segment, it’s used to illustrate how multiple departments (sales → desking → F&I → cashier) can create a fragmented customer journey without integrated systems.

An integrated system is software that connects different dealership departments so the same customer record and deal data follow the shopper through each step. The segment argues that integration reduces “leakage” during handoffs and improves the customer experience.

Darwin is referenced as a system the speaker uses alongside other tools (e.g., a desking system). The context suggests it’s part of the dealership’s software stack, and the problem is that these tools aren’t integrated, leading to fragmented workflows.

The host is referring to “service of sales” as a workflow area in dealerships—how leads and shoppers move through sales operations. In practice, it’s about coordinating sales outreach, follow-up, and handoffs so shoppers don’t fall through gaps between teams.

“Leakage” describes lost opportunities when shoppers or leads fall between departments—commonly between service and sales. The idea is that static, siloed workflows cause delays or missed follow-ups, so shoppers disengage before a deal is closed.

“One platform” refers to consolidating dealership tools into a unified system to manage the full customer journey. The goal is to reduce handoff friction and close leakage by keeping data and actions connected across sales and service.

Telephony here likely means the phone system integration used for calls and call routing in the dealership workflow. When paired with customer engagement tools, telephony helps ensure calls are handled quickly and tied to the right shopper record.

An “AI widget” is an embedded software component (often on a website or app) that uses AI to assist with customer interactions. In this segment, it’s part of a broader integration strategy to engage shoppers through multiple channels rather than relying on static workflows.

A “partner hub” is a centralized integration marketplace or management layer where third-party partners connect to a platform. The host describes it as growing rapidly with many integration requests, implying a scalable ecosystem for dealership tooling.

“API connect” refers to using application programming interfaces (APIs) so different software systems can communicate automatically. In dealership terms, APIs enable integrations that keep customer data and actions synchronized across platforms, which supports real-time engagement and reduces dropped leads.

The hosts reference “direct competitors” in the context of the industry landscape and how dealerships compare tools or approaches. This is more about business strategy than a specific automotive technology.

This describes the problem of using overlapping tools that capture the same customer data without proper synchronization. If two systems both store lead/customer details, the dealership can end up with duplicates and a fragmented view of the shopper.