Skip to content
DT Nova
Custom CRM

Dealership CRM for sales and service, built around your stores

A dealership CRM that answers every lead quickly, follows each customer from first enquiry to test drive, trade-in and delivery, and keeps the relationship going through the service years until the next car. We build custom automotive CRM software for dealerships and dealer groups whose brands, rooftops, lead sources and service processes do not fit a standard product, connected to the dealer management system you already run. The code and the data are in your name, hosted in the EU.

  • You see the result before it goes live
  • Fixed price for the agreed scope, in writing before work starts
  • Source code, domain and accounts in your company's name

Request a quote

How a dealership wins and keeps a customer

Car sales start online and close in the showroom, and the profit over the life of a customer comes as much from service, parts and the next purchase as from the first deal. A dealership CRM has to cover both halves, and both halves have their own systems today.

StepTypical todayWith a custom CRM
LeadPortal, website and manufacturer leads in separate inboxesOne queue with vehicle of interest, source and target response time
Appointment and test driveDiary on paper or in a spreadsheetBooked against the salesperson and the vehicle, with confirmation
Trade-inAppraisal notes in the salesperson's folderAppraisal on the opportunity with photos and value
Offer and dealTyped into the DMS, followed up from memoryOffer status visible; deal created in the DMS through the integration
DeliveryChecklist on paperDelivery checklist and a follow-up after the first weeks
OwnershipService reminders from the DMS, sales not involvedService, lease end and equity signals shared between sales and service

What the custom CRM does

Service department CRM

The service department sees customers more often than sales does. A service CRM plans reminders from mileage and dates, follows recalls until the vehicle has been in, records work the customer declined and offers it again at the right time, and asks for feedback after the visit. It also tells sales when an owner whose lease ends soon is in the workshop today. Bookings and repair orders stay in the DMS; the CRM reads them through the integration. For dealer groups that also run rental or company fleets, see fleet management software.

Integrations

We connect the CRM to the dealer management system for stock, deals, customers and repair orders; to listing portals, the manufacturer's lead programme and the website for leads; to Microsoft 365 or Google Workspace for email and calendars; to SMS and telephony platforms where they offer an interface, so a conversation is logged on the customer; to e-signature for offers and orders; and to accounting where needed. Each integration is built against the system's own interface, described in API integration.

The rules a dealership CRM has to follow

Customer information security in the US. The FTC Safeguards Rule names, among its examples of financial institutions in 16 CFR 314.2(h)(2)(ii) (eCFR, read 12 November 2026), an automobile dealership that, as a usual part of its business, leases automobiles on a nonoperating basis for longer than 90 days, with respect to its leasing business. Whether other parts of your business are covered is a question for your counsel. Where the rule applies, 16 CFR 314.4 (read 12 November 2026) requires an information security program with a Qualified Individual, a written risk assessment, access limited to what each person needs, encryption of customer information in transit and at rest, multi-factor authentication, secure disposal no later than two years after the information was last used unless it must be kept, monitoring or testing, oversight of service providers, a written incident response plan, and notice to the FTC within 30 days of discovering a notification event involving at least 500 consumers. The CRM is built with role-based access, multi-factor login, encryption, logs and retention rules from the start.

Texts and automated messages. Under 47 CFR 64.1200 (eCFR, read 12 November 2026), telemarketing with an automatic dialing system or an artificial or prerecorded voice to mobile numbers needs prior express written consent; a person may revoke consent by any reasonable means, including replying "stop", and the revocation must be honoured within a reasonable time not exceeding ten business days; a request not to receive telemarketing is recorded and honoured for five years; numbers are checked against a version of the national registry of numbers that opted out of telemarketing obtained no more than 31 days earlier; and telephone solicitations to residential subscribers stay between 8 a.m. and 9 p.m. at the recipient's local time. The CRM applies each of these before a message goes out.

Email. 16 CFR 316.5 (read 12 November 2026) bars charging a fee or asking for anything beyond the email address and preferences, or any step beyond a reply email or a single web page, to opt out of commercial email. In the EU, Article 13 of the ePrivacy Directive, Directive 2002/58/EC as amended (consolidated text read 12 November 2026), requires prior consent for email marketing to individuals, with a narrow exception for existing customers and similar products, and the GDPR requires a lawful basis for every contact under Article 6, consent that can be withdrawn as easily as given under Article 7, and an end to direct marketing when a person objects under Article 21.

Ready-made dealership CRM or custom?

Automotive CRMs such as VinSolutions, DealerSocket and the CRM modules of DMS providers such as CDK, as well as general platforms like Salesforce, HubSpot or Pipedrive, serve many dealerships well, and for a single-brand store on a standard process one of them is often the right choice. A custom CRM pays off for groups with several brands and systems, for dealers with their own lead routing or service retention model, and for dealerships that want customer data in their own account.

SituationReady-made dealership CRMCustom CRM
One rooftop, one brand, standard processUsually a good fitRarely worth building
Group with several brands and DMSsOne configuration per storeOne CRM over each system you run
Sales and service in one viewDepends on the productShared customer and vehicle record
Your own routing and retention rulesConfigurable up to a pointYour rules, as written
Pricing modelPer rooftop or per user subscriptionFixed price for the agreed scope, then maintenance
Data location and ownershipThe vendor's platform and regionsYour account, EU data region

How we build it

  1. Walk the process. Leads, showroom, business office, delivery and service, mapped with the people who run them.
  2. Scope and fixed price in writing. Lead sources, routing, integrations, consent rules and what the first phase leaves out, with a fixed price for that agreed scope.
  3. A test version on your real data. Last month's leads and your customer and vehicle data imported, so managers see their own pipeline.
  4. Pilot and acceptance. One rooftop goes first, and the phase is accepted against the written scope.
  5. Roll out and measure. Lead response time, show rate and service retention, compared with the numbers recorded at the start.
  6. Maintenance. Updates, monitoring and rule changes on a monthly plan you can cancel with one month's notice.

You own it

As a standard term, the source code sits in a repository in your company's own account, the database and hosting are in your name in an EU data region, and the customer data stays in your control. The general side of the build is on our custom CRM system page, and other industries are listed under custom CRM, including insurance agency CRM. See prices.

Questions we get

What does a dealership CRM do?

It runs the customer side of a dealership: leads from the website, listing portals and the showroom, test drives, trade-in appraisals, offers and follow-up, delivery, and then the ownership years with service reminders and the next purchase. The dealer management system remains the record for stock, deals and accounting.

How is automotive CRM different from a general CRM?

Automotive CRM is built around vehicles as well as people: the car a customer drives, its age and mileage, the lease or finance end date, the service history and the trade-in value. A general CRM can hold some of this in custom fields; a dealership CRM uses it to decide who to contact and when.

Can it connect to our DMS and listing portals?

Yes, where they offer an interface or a data feed. We connect the dealer management system for stock, deals and service, listing portals and the manufacturer's lead programme for leads, the website, email and calendars, and SMS and telephony platforms. Integrations are agreed in the written scope.

Can the service department use the same CRM?

Yes, and it should. Service reminders, recalls, declined work and the customer's next purchase are all part of the same relationship. Service advisors see the vehicle and its history; sales sees when an owner is in the workshop.

Does a car dealership CRM handle consent for texts and email?

It records consent and opt-outs per channel, applies them before every send, and honours an opt-out across all rooftops and departments. The rules for your markets are agreed with your compliance lead and configured in the system.

Does it work for groups with several rooftops and brands?

Yes. Leads are routed per rooftop and brand, customers are shared where your policy allows, and management sees results per site and in total.

Who owns the system?

Your dealership or group. The source code sits in a repository in your own account, and the database and hosting are in your name in an EU data region.

Get a written quote

Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.

See every price · Contact details

Request a quote