Fixed quote after a free call

Dealership CRM automation that keeps every lead and customer moving

Dealer leads arrive from the website, third-party marketplaces, OEM programs, Facebook, phone calls and walk-ins, and too many sit in the CRM without a next step. We connect every source to your dealership CRM through ADF feeds and APIs, match leads to stock and existing customers in the DMS, automate tasks and follow-up cadences, and report on which sources and salespeople turn leads into appointments and deals. For independent repair shops we do the same around the shop management system. A typical build costs $1,000 to $2,500 per workflow and takes about four weeks.

The problem

Why dealership CRMs fill up with dead leads

Dealership CRM systems such as VinSolutions, DealerSocket, Elead or DriveCentric are powerful, but only as good as the data and habits around them. Leads from a new marketplace arrive by email instead of ADF, phone-ups never get logged, and duplicate customers pile up when the CRM and DMS disagree.

Managers then cannot trust the reports: which sources produce shows and sales, how quickly each salesperson responds, and how many sold customers came back for service. Independent garages have the same problem on a smaller scale, with customers spread across the shop system, a booking tool and a spreadsheet.

What we build

What our dealership CRM automation includes

Every lead source in ADF

Website, marketplace, OEM, Facebook and chat leads normalised into ADF XML or the CRM's API, with source and vehicle of interest recorded.

Phone-ups and walk-ins logged

Call tracking and a quick walk-in form create CRM records instead of notes on paper.

Stock and customer matching

Leads matched to inventory and existing DMS customers, so salespeople see trade-in history and service visits.

Follow-up cadences and tasks

Tasks and reminders by stage, with escalation to the sales manager when a lead goes untouched.

Sold-to-service hand-off

Sold customers enrolled into first-service and review workflows automatically.

Source and salesperson reports

Leads, response times, appointments, shows and deals by source and salesperson, emailed weekly.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Lead arrives

    A web, marketplace, phone or walk-in lead creates or updates the CRM record.

  2. 02 Automated

    Matched

    The lead is matched to stock and any existing customer in the DMS.

  3. 03 Automated

    Tasks created

    Follow-up tasks and cadences start; untouched leads escalate.

  4. 04 Advisor review

    Salesperson works lead

    The salesperson calls, books the appointment and records the outcome.

  5. 05 Advisor or manager decides

    Deal decisions

    Vehicle price, trade-in value and finance are decided by authorised staff, never by the CRM.

How it behaves

How the dealership CRM pipeline behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the customer sees

  • A fast reply about the car they asked about
  • A salesperson who already knows their history
  • Follow-up that stops once they buy or say no

What staff see

  • Leads with stock and customer history attached
  • Clear tasks and escalations
  • Weekly source and response reports

What the automation does

  • Normalises leads into ADF or the CRM API
  • Matches stock and customers
  • Runs cadences with stop rules and consent checks

Edge cases and fallbacks

Same customer from two marketplaces
Merged on phone, email and vehicle of interest; both sources kept.
Vehicle already sold
The salesperson is told and similar stock suggested for them to offer.
Lead without consent to text
Email follow-up only and a call task.
DMS or CRM API outage
Leads are queued and retried, and the BDC manager is alerted.

Architecture

A dealership CRM pipeline at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Website leads Forms, chat Marketplaces ADF lead feeds Phone-ups Call tracking n8n Normalise, match Dealer CRM Pipeline, tasks DMS Stock, customers Salesperson Calls, visits Weekly report Source, staff
  • Input
  • Logic and services
  • Data
  • People
  • Output

How it flows

  1. 1 Leads arrive from the website, marketplaces and phone calls.
  2. 2 n8n normalises each lead, matches it to stock and existing customers, and updates the CRM.
  3. 3 Salespeople get tasks with full context; untouched leads escalate to the manager.
  4. 4 A weekly report shows response time, appointments and deals by source and salesperson.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Dealership & automotive CRM automation project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Lead sources, CRM and DMS, current cadences and reporting needs.

  2. 02

    Design

    2 to 3 days

    ADF mapping, matching rules, cadences, escalation and consent fields.

  3. 03

    Build

    1 to 2 weeks

    Source normalisation, matching, tasks, sold-to-service hand-off and reports.

  4. 04

    Shadow run

    About 1 week

    Leads processed in parallel with the current setup, and we compare.

  5. 05

    Launch

    1 to 2 days

    Switch over and train sales and BDC staff.

  6. 06

    Support

    Ongoing

    New lead sources, cadence changes and reporting tweaks.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n ADF XML lead feeds CDK Fortellis APIs or Keyloop partner APIs VinSolutions, DealerSocket, Elead or HubSpot Call tracking Twilio SMS and email

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Sources, ADF mapping, matching and cadences.

    $200 – $400

  • Build

    Normalisation, matching, tasks and reports.

    $500 – $1,300

  • Integrations

    CRM, DMS, call tracking and messaging.

    $150 – $400

  • Testing and shadow run

    Parallel run with your current setup.

    $100 – $250

  • Launch and training

    Switch-over and team training.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. DMS API access (such as Fortellis consumption fees), CRM subscriptions, messaging and n8n are billed to you directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • DMS API access: Billed by the DMS vendor; CDK prices Fortellis APIs by consumption rather than per dealer.
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
  • Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees (Twilio's published US pricing).

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US: dealers and the Safeguards Rule

Dealers that arrange financing are financial institutions under the FTC Safeguards Rule, which requires a written information security program and oversight of service providers.

Source: www.law.cornell.edu

US: texts and calls need consent

Telemarketing texts and calls using automated systems need prior express written consent; purchased leads do not carry consent for your dealership.

Source: www.law.cornell.edu

UK: marketing by text and email

PECR requires consent, or the soft opt-in conditions, for marketing by electronic mail, with a way to refuse in every message.

Source: www.legislation.gov.uk

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Dealership & automotive CRM automation questions, answered.

Software that tracks every sales lead and customer from first enquiry to sale and beyond, with tasks, cadences and reporting. It works alongside the DMS, which holds deals, stock, parts and service.

VinSolutions, DealerSocket, Elead, DriveCentric and general CRMs such as HubSpot, through ADF lead feeds and the API routes each vendor offers. We confirm the route for your CRM before quoting.

CDK offers APIs through its Fortellis marketplace, and Keyloop has a partner programme with approved integration points. Access usually needs vendor approval and may carry fees, which we scope up front.

Many shops are well served by the customer tools in their shop management system, such as Tekmetric or Shopmonkey, plus automation around them. A separate CRM makes sense for multi-location groups or fleet sales.

It prevents new duplicates by matching on phone, email and VIN, and flags existing ones for staff to merge in the DMS.

Response time, appointment set rate, show rate, close rate by source, untouched leads and sold customers returning for first service.

Free 20-minute call

Want this for your automotive?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call