PDL Engagement · CRM Strategy

CRM Strategy
Crestline Auto Group

Independent Used Car Dealer Akron/Canton Metro April 2026 14 Employees · $6.8M Revenue
SPDR Score
52.2/100
Developing
PDL Approach

CRM exists for one reason: to capture what you need to know about your customers and prospects so that relationships are built on information, not memory. Who they are, what they're looking for, where they are in the buying process, and whether they've done business with you before. That data is what lets you move deals through a pipeline with intention, keep in touch across the full customer lifecycle, and build the kind of marketing and follow-up that works because it's relevant. The tool is infrastructure. The capability is what matters.

That's why PDL offers tool selection as a service. We evaluate what you may already have, what your process actually needs, and what the realistic switching costs look like before recommending anything. Sometimes the best answer is a standalone CRM. Sometimes it's already sitting inside the system you're paying for and not using. PDL also offers CRM rescue services for when things go wrong.

What CRM Actually Does
CRM is less about software and more about capabilities. A functioning CRM gives you four things a growing business can't afford to leave to memory and instinct.
01
Lead Capture
Every inquiry (phone, web form, walk-in, marketplace) lands in one place with a timestamp. Nothing enters the business and quietly disappears.
02
Pipeline Visibility
At any moment, you can see where every active lead stands. Not in someone's head. Not in a spreadsheet. In a shared system with a defined stage for every deal.
03
Follow-Up Consistency
Follow-up happens on a schedule, not on instinct. The right message goes to the right person at the right time, without requiring someone to remember to do it.
04
Post-Sale Relationship
The relationship doesn't end at delivery. Post-sale touchpoints (satisfaction check-ins, service reminders, repeat buyer outreach) are systematized, not sporadic.
Systems Fit
Where CRM Sits in the SPDR System
CRM touches all four systems and connects them.
S
Strategy
Enables
CRM is where the business strategy becomes operational. Crestline's winning aspiration (most trusted dealer for working families, built on repeat buyers) only works if there's a system capturing who those families are, what they drove away in, and when to reach back out. Without it, the strategy depends on memory, disconnected notes, and spreadsheets that don't talk to each other.
P
Processes
Primary
CRM is the process system for the sales side of the business. Lead capture, pipeline stages, follow-up cadence, and post-sale touchpoints are process failures before they're CRM failures. Getting the workflow right in IDMS is the Phase 1 deliverable.
D
Data
Generates
A functioning CRM creates the data that doesn't currently exist: source attribution, lead conversion rates, time-to-close, repeat buyer frequency. This is what feeds marketing decisions and eventually the AI buying filter. CRM is the upstream source.
R
Resources
Reinforcing
CRM and the people using it make each other more effective. The system replaces scattered spreadsheets, notes, and individual inboxes with a single point of truth. The people bring the judgment, relationships, and context the system can't replicate. Together they support the repeat buyer strategy in a way neither can alone.
For Crestline: Why IDMS CRM
Already owned, already integrated. DealerSocket IDMS is the operational core of the business. Activating the CRM module adds capability without adding a new system. No data migration, no integration work, no parallel logins.
Lower learning curve. The team is already in IDMS for inventory and deal management. CRM in the same system means one workflow, one login, and habits that build on what's already familiar.
Floorplan exposure makes speed matter. Every day a lead goes unworked is a day a vehicle is sitting on floorplan. CRM activation reduces that gap and it's already paid for.
Foundation for AI and marketing. The data a functioning CRM generates (source attribution, conversion rates, follow-up cadence) feeds directly into the AI thought partner and marketing channels already in the roadmap.
The honest caveat: IDMS CRM is the right starting point for Crestline. DealerSocket's parent company announced a significant AI investment in early 2026 (including AI-assisted call capture and automated CRM logging) but those features are not yet confirmed live. Phase 1 proceeds with IDMS CRM as configured today, with PDL evaluating AI feature availability during the engagement. At the Phase 1 review: if adoption is strong, stay the course. If adoption struggled and the AI features still aren't available, migration to a purpose-built platform becomes the recommendation. With a functioning process already running, that transition is significantly easier than starting from scratch.
All data in this assessment is synthetic, developed from real-world patterns and industry research to illustrate how PDL engagements work. All real client data is private and confidential.
Phase 1 · Foundation
Activate IDMS CRM — Lead Capture Through Post-Sale
Weeks 4–12 · Concurrent with Business Strategy Phase 1 and AI Pilot
Initiative 4
Activate IDMS CRM — Lead Capture and Pipeline
Weeks 4–10
Crestline's current lead-handling lives across phone logs, Gmail threads, and individual memory. The goal of Initiative 4 is to get every lead from every channel into a single structured pipeline with defined stages, timestamps, and an owner. This is the foundation everything else depends on. Nothing in Phase 2 is possible without a working pipeline.
Owner: Lead Coordinator + PDL
System: DealerSocket IDMS CRM
Timing: Weeks 4–10
01
Define contact and deal fields. Before anything else is configured, decide what information Crestline actually needs to capture. Contact fields come first: who the buyer is, how many drivers in the household, what they currently drive, budget range, and how they heard about Crestline. Deal fields follow: vehicle of interest, acquisition source, stage, and expected close. Getting this right at the start prevents the most common CRM problem: a system full of incomplete records that can't be used for anything.
02
Evaluate lead scoring capability. Lead scoring — prioritizing leads based on engagement signals, vehicle match, budget fit, and buying timeline — is a meaningful capability for a business handling volume across multiple channels. If IDMS supports it natively, configure it. If not, AI can fill that gap: a simple scoring model built on the fields defined in step 01 can surface which leads deserve immediate attention without requiring a purpose-built feature.
03
Configure pipeline stages. Define and build deal stages inside IDMS CRM that reflect how Crestline actually sells, from first inquiry through delivered. Stages should be specific enough to be actionable, not so granular they become a burden to maintain.
04
Map and connect all lead sources. AutoTrader, Facebook Marketplace, dealer website, walk-in, and inbound phone all need a defined path into the CRM. Every source gets a capture method and a default stage entry point.
05
Establish lead ownership and response protocol. Who owns a new lead the moment it enters the system. What the first response looks like. How quickly it needs to happen. These are process decisions, not technology decisions. IDMS enforces them once they're defined.
06
Train the team on daily CRM use. Training focuses on the daily workflow, not a feature tour. What does using the CRM look like from the time you arrive to the time you leave.
Initiative 5
Configure Follow-Up and Post-Sale Workflows
Weeks 8–12
A pipeline without follow-up is a list. Initiative 5 builds the workflows that make CRM a relationship system, not just a tracking tool. Automated follow-up cadences for active leads, post-sale touchpoints for delivered customers, and re-engagement sequences for past buyers are all configured inside IDMS and connected to the repeat buyer strategy.
Owner: Lead Coordinator + PDL
System: DealerSocket IDMS CRM
Timing: Weeks 8–12
01
Build active lead follow-up sequences. Define the cadence (when, how, and what message) for leads at each pipeline stage. Channels include SMS, email, and phone. Frequency and tone should reflect Crestline's voice, not a generic dealership template.
02
Configure post-sale touchpoints. Satisfaction check-in at day 7. Service reminder at 90 days. Repeat buyer outreach at 18–24 months. These aren't marketing campaigns. They're relationship maintenance that compounds over time and directly supports the repeat buyer strategy.
03
Build a re-engagement sequence for past customers. Crestline has years of buyers in the market. A structured re-engagement workflow triggered by time since purchase and aligned to typical vehicle replacement cycles turns past customers into a pipeline asset rather than a dormant list.
Phase 1 Evaluation · AI-Assisted Call Capture
The most common objection to CRM adoption in sales isn't resistance to the tool. It's a legitimate tension: "Do you want me to sell or take notes?" That trade-off is real and it's why CRM adoption fails more often than CRM configuration does. If AI can eliminate the documentation burden without adding friction, it changes the starting position for adoption entirely.
During Phase 1, PDL evaluates which path is viable for Crestline. DealerSocket has announced AI-assisted call capture on its roadmap, but availability in Crestline's tier is unconfirmed. If native features aren't live, a lightweight API-connected workflow can solve the same problem now. A transcription tool captures the call, an AI layer extracts the relevant fields, and an automation layer pushes the record directly into IDMS. Tools like Whisper for transcription and n8n or Zapier for automation are illustrative examples of what that workflow can look like. The salesperson sells. The system handles the rest.
A →
Wait for DealerSocket native AI. If the features ship during Phase 1 and are available in Crestline's tier, activate within IDMS. Lowest integration complexity.
B →
Build a lightweight API workflow. Transcription + AI extraction + automation layer connected to IDMS via API. Available now, independent of DealerSocket's roadmap.
C →
Factor into tool selection. If AI-assisted capture is critical to adoption success and neither path above is viable, this becomes a deciding factor in whether to stay on IDMS or migrate to a platform where it's already live, such as HubSpot.
PDL Deliverables
📋
Strategy
CRM Strategy Document
Documented approach covering objectives, tool rationale, pipeline design, and how CRM connects to the business strategy and repeat buyer goal.
⚙️
Governance
CRM Governance Guidelines
Defines data standards, field requirements, ownership rules, and what good CRM hygiene looks like on a daily and weekly basis.
✅
Process
Best Practices & SOPs
Step-by-step documentation for how to use the CRM across the key workflows: lead intake, follow-up, post-sale, and re-engagement.
📊
Metrics
Key Metrics & KPI Framework
Defined metrics tied to outcomes, not just activity. Lead response time, pipeline conversion rate, repeat buyer rate, and follow-up completion with context for what each number means for the business.
🎓
Training
Training Documentation
Role-specific training materials for daily CRM use. Designed to onboard new team members and reinforce habits for existing ones.
🔗
Connected
NotebookLM Integration
CRM documentation, SOPs, and best practices loaded into the shared NotebookLM hub alongside AI engagement materials. One reference point for the full team.
All data in this assessment is synthetic, developed from real-world patterns and industry research to illustrate how PDL engagements work. All real client data is private and confidential.
After Phase 1
What Phase 1 Answers
CRM Phase 1 has one job: prove that the capability is real and being used. Everything else follows from that.
Phase 1 Working
Every lead channel has a path into the pipeline. Nothing is entering the business and disappearing.
The team is logging activity consistently without being reminded. The habit has formed.
Follow-up is happening on schedule, not on instinct. Response time has measurably improved.
Post-sale touchpoints are running. Past customers are being contacted systematically for the first time.
Source attribution data exists. Crestline knows where buyers are coming from.
Phase 1 Struggling
Leads are still being tracked outside the CRM. Gmail threads and spreadsheets haven't disappeared.
Activity logging is inconsistent. Some team members are using it, others aren't.
Follow-up is still driven by whoever remembers. The workflow isn't running without prompting.
The pipeline data doesn't reflect what's actually happening in the business.
The Real Variable: Adoption
McKinsey, IBM, and Harvard Business Review all cite failure rates for change initiatives in the range of 60–70%. The specific numbers are debated. The research behind them is largely practitioner observation, not controlled studies. But the underlying pattern is consistent across two decades of data: most technology implementations fail not because the tool doesn't work, but because the people using it don't change how they work. CRM has one of the worst adoption records in enterprise software. The reason is almost always the same: it was configured for leaders and handed to teams.
The most reliable finding across independent research isn't a methodology. It's an ownership gap. Studies consistently show that leaders believe they're involving their teams in change decisions far more than team members actually experience. People adopt what they helped build. They comply with what was decided for them, and compliance isn't adoption. This is why PDL's approach to both CRM and AI involves the team deliberately, from tool selection through workflow design. It's not a philosophy. It's what the data says works. That said, change management is mitigation, not prevention. PDL can improve the conditions for adoption significantly. It can't guarantee it. No one can.
Where AI changes the equation: if call capture and CRM logging happen automatically through a transcription workflow or native AI features, the documentation burden that drives the classic sales objection disappears before adoption even has a chance to fail. That's not a feature consideration. It's a change management strategy built into the infrastructure from the start.
System Connections
What a Working CRM Unlocks Across the System
AI
The AI thought partner pilot runs concurrent with CRM Phase 1. A functioning CRM is what gives the AI pilot something real to work with: customer data, lead patterns, and follow-up history. As the CRM matures, AI moves from general thought partner to a tool that can interpret pipeline trends, flag stalled deals, and inform buying decisions. The two engagements reinforce each other. A struggling CRM limits what the AI pilot can do. A strong CRM accelerates it.
Marketing
The marketing strategy identified email and SMS as retention channels. Retention marketing only works if you know who to reach, when, and with what. CRM is the source of that data. Source attribution from the CRM tells Crestline which channels are producing buyers worth retaining. Post-sale workflows in the CRM feed directly into the marketing cadences. Without CRM, marketing is broadcasting. With it, marketing is targeted.
Data
CRM is the single point of truth for customer data. IDMS handles inventory and deals. QuickBooks handles accounting. None of them talk to each other by default, and that's exactly where CRM will surface its own ceiling. As lead data, marketing attribution, and financial performance accumulate across separate systems, the appetite to connect them grows. The Data engagement starts with an audit: what does IDMS reporting actually cover, where are the gaps, and what would a centralized data system make possible. Forecasting, bidirectional marketing sync, and financial and sales analysis all require connecting sources no single platform can see on its own. The audit determines the scope. The CRM makes the case.
Phase 2 · Amplification
Phase 2 Only Proceeds If the Foundation Is There
You only get out of CRM what you put in. Phase 2 is not a calendar decision.
Phase 2 Triggers
What Has to Be True Before Phase 2 Begins
→
The pipeline is live and being used consistently by the full team, not just the people who were already bought in.
→
Source attribution data exists and is reliable. Crestline knows where leads are coming from and which sources are converting.
→
Follow-up workflows are running without manual prompting. The process is systematic, not person-dependent.
→
At least one post-sale touchpoint sequence has completed a full cycle and produced measurable repeat buyer or referral activity.
The Question PDL Asks at the End of Phase 1
Did CRM actually help Crestline? And if the answer is yes, what does Phase 2 look like?
If the answer is yes, the next conversation is about amplification: deeper AI integration, Lindy voice agent, and marketing attribution. If the answer is no, the conversation is about what got in the way, whether it was the tool, the process, or the people. That review happens before anything else moves forward.
All data in this assessment is synthetic, developed from real-world patterns and industry research to illustrate how PDL engagements work. All real client data is private and confidential.