Dealership CRM Implementation Plan

Software goes live in a week. The habits take a quarter. Plan for the second one and the first takes care of itself.

Ask any dealer who has changed CRM twice what went wrong the first time and you will not hear about a missing feature. You will hear that the sales floor never really moved over, that half the team kept texting from personal phones, that the reporting was never trusted because the data was incomplete, and that eighteen months later the store was shopping again.

That outcome is predictable and preventable, and it is decided in the first thirty days. A CRM is not a tool that people use when convenient. It is the record of what your store did, which means partial adoption is worse than no adoption, because a report built on sixty percent of activity is a report that misleads confidently.

So the plan below is weighted the way the risk actually is. Configuration and data get a couple of weeks. Adoption gets a quarter of sustained management attention. If you read this and conclude that the hard part is your managers rather than your vendor, you have understood it correctly.

One structural note before the phases. Decide up front whether this is a change project with an owner and a deadline or a software purchase that someone will get around to. Implementations that are treated as projects finish. Implementations that are treated as purchases drift until the enthusiasm runs out, usually around week five.

Write the success criteria first, in numbers, and get your general manager to agree to them in the same conversation. Without this you have no way to tell the difference between a working implementation and a busy one.

Useful criteria look like this. Every inbound lead from every source lands in the system within a defined number of minutes and is assigned to a named person. Median time to first response is under a target you set, measured in minutes. Every salesperson conducts customer communication inside the platform, with an explicit rule about personal phones. A defined follow up cadence is loaded and running rather than existing as a document. Managers are pulling their weekly numbers from the system rather than from a spreadsheet someone maintains by hand.

Notice that none of those are about features. They are about behavior, which is what you are actually buying. A store that hits all five will get value from almost any competent CRM. A store that hits none of them will churn through three vendors and blame all of them.

Also decide what you are not doing in phase one. Ambition is the enemy here. Stores that try to launch lead management, desking, campaigns, service follow up and reporting simultaneously usually launch none of them properly. Our requirements checklist helps separate what you need on day one from what can wait until month three.

Five roles have to be filled. They can be five people or two people wearing multiple hats, but every one of them needs a name attached before the project starts.

The executive sponsor. A dealer principal or general manager who will personally say, in a sales meeting, that this is how the store now works. Implementations without visible ownership at this level are optional in the eyes of the floor, and optional means dead.

The system administrator. One person who owns configuration, users, permissions and the settings that change over time. Not a committee. Committees produce inconsistent setups that nobody can explain six months later.

Department champions. One respected person in each area: the floor, the BDC, finance. Not necessarily the manager, and ideally the person others already ask for help. They learn first and they answer the small questions that otherwise become excuses.

The data owner. Whoever is accountable for what comes across from the old system, what gets cleaned, and what gets left behind. This is a real job with real hours, not something to hand to whoever is least busy.

The vendor contact. Your named person on our side, with a way to reach them that is not a general support queue.

Write the five names on the same page as the success criteria. That single page is the plan; everything else is scheduling.

Some configuration is trivial to change later. Some of it hardens as soon as data starts flowing through it. Spend your attention on the second kind.

The hard to reverse decisions are lead sources, distribution rules and permissions. Lead sources determine whether your attribution reporting will ever be meaningful, and renaming or merging sources after twelve months of history is genuinely painful. Set up feeds and custom source feeds with names you can live with, and be more granular than feels necessary, because merging sources later is easy and splitting them retroactively is not.

Distribution rules decide who receives what and in which order, with escalation when nobody responds. Decide the rules before the first lead lands rather than after the first argument about it. Global lead distribution supports rules plus distribution lists for the cases that do not fit a rule, and global lead history records where every lead went, which is what settles the inevitable dispute about whether a lead was received.

Permissions and roles are the third. Decide your model before you migrate, not after. Retrofitting roles onto a live system with sixty users is far more painful than designing it once. Work out what a salesperson sees versus a manager, whether gross is visible, and who can export.

The easy to reverse things, which are templates, drip content, calendar preferences and dashboard layouts, can be rough on day one and refined in week six. Do not let a debate about text message wording delay a go live date.

This phase is where timelines slip, and it slips for the same reason every time: nobody looked at the data until it was time to move it.

Get your export from the outgoing system early, before you give notice, and open the file. Ask what you can export, in what format, whether notes and communication history are included, and what it costs. Our data export checklist covers the questions and CRM data migration covers the mechanics.

Then clean before you load, not after. Duplicate customer records, phone numbers stored in six different formats, dead email addresses and opt out status that lives in someone's memory are all cheaper to fix in a spreadsheet than in a live system. Two tools help here more than dealers expect. A phone validator checks numbers before your team spends an afternoon dialing disconnects, and an email validator protects your sending reputation before the first campaign goes out. Bringing a dirty list into a new system and immediately emailing it is one of the more expensive mistakes available to you.

Opt outs and the blacklist come across first, before anything else. A customer who unsubscribed from the old system and then receives a message from the new one is a compliance problem, not an inconvenience.

On integrations, list every source that currently posts leads: website forms, third party providers, chat, phone, marketplace listings. Each one gets repointed and each one gets tested with a real submission that you watch land. Because no dealer management system access or inventory feed is required to operate, the integration list here is shorter than it is for a full system conversion, which is deliberate.

The instinct is to switch everyone on a Monday. The better approach is to run a pilot, and it costs you two weeks rather than a quarter.

Pick a team rather than a store if you are a single rooftop: the BDC is usually ideal, because they are already working leads systematically and they will surface process gaps quickly. If you are a group, pick one mid sized store with a cooperative manager rather than your best or your worst performer. Run them fully for two to three weeks while everything else stays put, with real lead flow rather than test records.

Measure three things against the old system over the same period. Median time to first response. Touches per lead before the trail goes cold. Appointments set. Those three tell you more than any demo does, and they give you internal evidence rather than vendor claims when you take it to the rest of the team.

Expect the pilot to expose process problems rather than software problems, and expect most of them to be about who is responsible for what. Fix those before you roll out, because rolling an unresolved ownership question out to sixty people multiplies it by sixty.

Month to month pricing is what makes this possible. A vendor that requires a multi year commitment before you can evaluate is asking you to carry a risk they are not willing to carry themselves. See the pricing page for how the plans are structured.

Go live is not the finish line. It is the start of the only phase that determines whether this worked.

Set one rule and enforce it without exception: customer communication happens inside the platform. No personal cell phone texting, no side email, no exceptions for the top producer. That last clause is the one that gets tested in week two, and the answer your managers give will decide the outcome. If the highest earner is allowed to work outside the system, everyone else learns that the rule is a suggestion.

Make the system faster than the alternative, because that is the real argument. Click to call with a VoIP softphone means dialing from the record is quicker than picking up a cell. Text templates mean sending is quicker than typing. Voicemail drop means leaving a prepared message takes three seconds instead of forty. When the compliant path is also the fast path, adoption stops being a discipline problem.

Run a short daily stand up for the first two weeks. Five minutes, looking at yesterday's response times and untouched leads, by name. Not to punish, but because attention is what makes something real. Coaching gets far cheaper here than it used to be: call recording with transcription lets a manager read four calls in the time it once took to listen to one.

Load the follow up cadence in the first week rather than the second month. A system with no cadence running is just a database, and databases do not create habits. Our page on follow-up cadence covers what to build.

Put three dates in the calendar during week one, with the same people in the room each time. Implementations that get reviewed on a schedule keep improving. Implementations that get reviewed when someone complains slowly revert.

Day thirty: adoption. Are all users logging in, and is anyone still working outside the system? Is every lead source landing correctly? Compare your response time and touch depth against the success criteria you wrote at the start. Fix people problems now, while the change is still recent enough to talk about openly.

Day sixty: process. Are the follow up cadences actually running, or were they switched off by someone who found them noisy? Are appointments being confirmed and no shows being recovered? This is the right point to turn on what you deliberately deferred in phase one, whether that is desking, campaigns or the customer facing deal pages. The desking tool is a common phase two addition.

Day ninety: outcomes. Now the numbers are worth reading. Appointments set and shown, contact rates by source, and cost per lead by source with real attribution behind it. Ninety days is also long enough to have an honest conversation about whether the vendor has earned the next quarter.

We cannot guarantee results, and any vendor promising a specific improvement inside ninety days is describing your market, which they have never seen. What a plan like this does is remove the variables that are entirely within your control, which turns out to be most of them. If you want help building your version of this plan, contact us and we will work through it with your managers rather than sending you a template.

How long does a dealership CRM implementation take?

Two to four weeks to configured and live, then a full quarter to genuinely adopted. The software timeline is short. The habit timeline is what determines whether the project succeeded.

What is the difference between this and an onboarding checklist?

This page is the project plan: phases, owners, decisions and review dates. The onboarding checklist is the task level list of settings, imports, users and training to work through inside each phase. Use both together.

Which configuration decisions are hardest to change later?

Lead source naming, distribution rules and the permission model. All three harden as history accumulates. Templates, drip content and calendar preferences can be rough at launch and refined later without cost.

Should we pilot or switch everyone at once?

Pilot. Run one team, usually the BDC, on real lead flow for two to three weeks. Measure response time, touches per lead and appointments set against the old system, then roll out with your own evidence rather than vendor claims.

How do we stop salespeople using their personal phones?

Set the rule, enforce it on the top producer first, and make the in system path faster than the alternative with click to call, text templates and voicemail drop. Adoption fails when the compliant path is the slower one.

Do we need a dealer management system integration to go live?

No. Neither system access nor an inventory feed is required to operate, which shortens the integration phase considerably. If you do have a feed, it can be ingested and published separately.

We will work through the phases with your managers, name the owners, and set the review dates. Month to month, so the plan is judged on results rather than a contract.