What should a dealership prepare before a DMS demo?

Pick the scenarios in advance

One routine transaction, one exception the store handles weekly, and one month-end or reporting task. Send them to the provider ahead of time and require them to be shown.

Bring the right people

The departments that will use it, not only management. The accounting office and the service drive routinely surface issues nobody else sees.

Score during, not after

Use a written scorecard with agreed weights and score in the room. Recollection after three demos favours the most recent and the most polished.

Record what is native

Note for each capability whether it is native, configured, partner-delivered or roadmap. That distinction is usually invisible in the flow of a demo and decisive afterwards.

Preparing your data

Assemble sample records that reflect how your store works: a deal with a trade and a lien payoff, a warranty repair with split billing, a parts return and a month-end close. Remove personal information where necessary. Provide these to the vendor in advance so the presenter can configure the demonstration to your scenarios rather than improvising.

Running the day

Set a schedule that gives each department time on its own tasks. Ask the presenter to hand over the controls for at least part of each scenario so that your staff can try the steps.

Take notes on unanswered questions and agree who at the vendor will reply, and by when. Keep the scorecard visible so weights are respected.

After the demo

Consolidate scores the same day, list follow-up items and send them to each vendor in writing. Compare answers when they arrive.

Contact references before narrowing the list. If a vendor could not perform a scenario, record that as a finding and ask whether it is a limitation or a preparation gap before scoring.

Roles for the demo day

Assign a lead to keep to the schedule, a note-taker per department, a scorer for each criterion and someone to ask the integration questions. Agree beforehand which questions will be asked of every vendor.

Brief the team on the difference between demonstrated and described. Prepared observers catch more than a large, unstructured audience.

Follow-up requests to send

After the demo, send a list of items not shown, questions unanswered and documents requested, such as sample contracts, integration lists and security reports. Ask for replies by a set date and note who did not respond. Slow answers before a sale are informative about service after it.