Industrial & Manufacturing
›
Automotive
›
Dealership Technology & Operations
Dealer Management Systems
High-stakes purchases and complex multi-party buying decisions across consumer and commercial segments.
Example organizations in this space:
CDK Global
Reynolds & Reynolds
Dealertrack (Cox)
DealerSocket
This interactive experience is the shipped product itself — the same application code customers run in production, mounted read-only in your browser over a real sample journey. Not a video, not a mockup: because the demo and the product are one codebase, it can never drift from the real thing.
Inside this journey
-
Pre-Sales
Qualify and diagnose the dealer group's requirements before investing in formal proof and scoping.
-
Qualification
Confirm budget range, decision-makers, timeline, and procurement constraints before investing in a full discovery and proof cycle.
Qualification Questions
Budget
- Is there an allocated budget range for a DMS replacement or upgrade?
- Will the budget need to cover implementation, data migration, and training in addition to software licensing?
Decision-makers
- Who will sign the final contract and which roles will materially influence the decision?
Timeline
- What is your target go-live window for a new DMS?
- What is the primary business driver for that timing (for example OEM requirement, lease/ownership change, financial planning, or operational risk)?
Procurement and constraints
- Do you expect formal procurement requirements we should know about (RFP, approved vendor list, required OEM approvals, or specific legal terms)?
- Are there any non negotiable commercial or contractual constraints that would prevent proceeding (minimum contract length, insurance limits, data residency, SLA thresholds)? If yes, please list.
-
Dealer Network Discovery
Map current DMS workflows, integrations, data ownership, migration risks, and measurable success signals across single- and multi-store operations.
Discovery Questions
Getting Oriented: Your Dealer Footprint
- How many rooftops and service locations are in your group today?
- Which roles on your team will be directly involved in evaluating a new DMS?
- Describe your primary revenue mix across new vehicle, used vehicle, service, parts, and F&I.
- In a typical month, how many total sales and service transactions cross your DMS?
- Who in your organization currently signs off on major vendor selection decisions at the group level?
Where Your DMS Really Touches the Business
- Name one transaction or report failure in your operation that would force you to escalate to the CFO immediately.
- How often do reconciliation or OEM reporting mismatches occur across your sites?
- Tell me which modules in your DMS, for example accounting, F&I, parts, or service, cause the most operational interruptions.
- Share the last incident at your dealership where a parts or service workflow needed a manual workaround, what happened, and what fixed it?
- What is the average time your team spends resolving a critical accounting or OEM reporting issue?
When Migration Has Gone Wrong, What Happens Next
- Walk me through the last time a data migration caused measurable business disruption at any one of your sites.
- For those incidents in your environment, which data domains were the root cause, for example customer records, vehicle history, inventory cost, or GL mappings?
- Rate the cleanliness of your master records, considering duplicate customers, missing VINs, and incorrect cost basis.
- If a migration missed parity at a single rooftop, would your team pause the rollout, remediate and continue, or continue while fixing in parallel?
The Other Paths You Might Take
- Who are the other vendors or internal paths you are seriously comparing this solution against?
- List any internal initiatives your organization has to build or extend its own DMS capability instead of buying third party.
- Under which circumstances would your group choose to remain on the incumbent system rather than replace it?
- Estimate the relative influence of references from similarly sized dealer groups on your final decision.
- Has any stakeholder on your team advocated for an internal build instead of partnering with an outside vendor?
Practical Readiness: Who, What, and When Must Be Ready
- What single internal blocker would stop a migration from starting on your target date?
- Identify the day to day owner in your organization for data extraction, transformation, and migration sign offs.
- Do you have dedicated IT or integration resources available for the pilot and full rollout?
- List the third party systems used in your operations that must be integrated, and mark whether APIs or vendor supported connectors are available.
- Describe how accessible production data is for exports and test loads in your environment, including any read only windows or approvals required.
- If an API or connector required for your integrations was unavailable, would your preference be to delay, fund a custom connector, or accept a phased workaround?
Success Signals and Acceptance Criteria
- Name the single pilot result that would allow your leadership to approve an immediate contract.
- Provide three measurable acceptance criteria you would require for pilot success and initial go live.
- Identify the roles and level in your organization at which final sign off is required for a rooftop and for the group.
- Specify the exact parity metrics you will use in your evaluation for revenue, parts, and service transactions, for example percentage match and allowable variance thresholds.
- Faced with a pilot that meets your acceptance criteria except for one OEM integration, would your team accept a remediation window or require full compliance before go live?
Next Steps and Decision Triggers
- Assuming the pilot demonstrates the expected benefits, who in your organization must approve the budget and what timeline do they require?
- Which procurement or legal steps in your process typically add the most time to final signature?
- Please name the teams in your organization that must be engaged to prepare environments, licensing, and staff training for the pilot.
- By your target go live date, what fallback or rollback conditions in your view would force a delay?
- Realistically, when could your team assemble the pilot participants and data extract owners to start work?
-
-
Solution Evaluation
Run a hands-on proof against the buyer's acceptance criteria — sample data migration, integration smoke-tests, and OEM-compliance checks to validate risk and fit.
- current_state
- decision_readiness
- success_criteria
- desired_state
- gaps
- stakeholders
- gaps
- stakeholders
- desired_state
- success_criteria
- decision_readiness
- current_state
- gaps
- current_state
- desired_state
- success_criteria
- stakeholders
- decision_readiness
- decision_readiness
- decision_readiness
- decision_readiness
- decision_readiness
-
Solution Scope
Define modules, migration boundaries, integration responsibilities, roles, and measurable acceptance criteria for the rollout.
Scope Configuration
- Migrate Sales, Service, Parts, and Accounting Records
- Configure Vehicle Inventory and VIN-Level Tracking
- Deploy Sales Desking and Deal Structuring
- Configure F&I Menu Selling and e-Contracting
- Import Parts Catalog and Enable Purchasing/POs
- Deploy Service Scheduling and Repair Order Management
- Set Up General Ledger and Accounting Posting
- Configure Payroll Processing and Employee Payroll Data
- Integrate OEM Factory Communications with Certified Connectors
- Integrate Source CRM and Lead Sync
- Activate Digital Retailing and Online Inventory Feed
- Integrate Lender Decision Engines and Funding Interfaces
- Configure Role-Based Access and Multi-Store Permissions
- Execute Live Cutover and Transaction Switch to Platform
Scope Questions
Migrate Sales, Service, Parts, and Accounting Records
- Which transaction domains must be migrated as active records versus archived historical exports (Sales deals, Service repair orders, Parts transactions, General ledger entries)?
- How many records exist by domain that you expect to move at cutover (approximate counts for deals, RO numbers, parts SKUs, journal lines)?
- What is your required migration completeness threshold for go-live expressed as a percentage of historical transactional records (for example 90% of sales deals, 99% of active inventory)?
- List the critical transactional fields that must validate 1:1 after migration (for example VIN, sale price, lender ID, tax code, RO labor hours).
- Who on your team will provide source extracts and own field-level validation for sales, service, parts, and accounting exports?
- Are there OEM, lender, tax authority, or audit retention rules that limit how far back transactions can be migrated or exposed in the new system?
Configure Vehicle Inventory and VIN-Level Tracking
- Which inventory locations and rooftops must be provisioned for VIN-level tracking at go-live?
- How do you currently identify vehicle lifecycle events to preserve (acquisition, PDI, wholesales, retail sale, title in/out)?
- Specify the VIN-level attributes that must be migrated and searchable (for example VIN, trim, mileage, service history, OEM recall flags).
- Which barcode or scanner hardware models and in-lane processes must the platform support for lot movement and PDI scanning?
- Do you require parity reporting on inventory valuation at cutover (parity by VIN and book value per rooftop)?
- Identify any third-party feed or marketplace endpoints that must receive your online inventory (VIN, images, DOM) at go-live.
Deploy Sales Desking and Deal Structuring
- Which deal types must the desking engine support at launch (retail, lease, loan, dealer trade, wholesale)?
- Provide the existing pricing rules, incentives, or manufacturer programs that must be encoded in deal calculations (cash incentives, dealer cash, APR buy-downs).
- Do you require lender-rate lookup integration during desking or will rates be entered manually during deal build?
- Which F&I products or appetites must appear in the menu flow (for example extended warranties, GAP, service contracts) and which require carrier-specific contract templates?
- Who will own final approval of pricing and deal structures per rooftop (General Manager, Sales Manager, Finance Manager)?
- Do you require audit logging for every price or term change tied back to a user ID for compliance or internal control?
Configure F&I Menu Selling and e-Contracting
- Which F&I product providers and contract templates must be available in the menu at go-live (list carriers or provide template IDs)?
- How should e-contract artifacts be stored and indexed (PDF per deal, XML per contract, signed timestamp and signer ID)?
- What e-signature flow is required for customers and co-signers (in-lane tablet, remote email signing, integrated lender signature)?
- Which compliance checks must run during F&I menu presentation (ODD disclosure, state-specific forms, OEM-required disclaimers)?
- Who provides the legal-approved F&I menu wording and state-specific contract clauses for configuration?
- Do you require end-to-end integration of e-contracts to lender funding files and reporting for each funded deal?
Import Parts Catalog and Enable Purchasing/POs
- Which parts price book or catalog formats will you supply for import (OEM parts CSV, aftermarket CSV, vendor EDI)?
- How many unique SKUs and manufacturer part numbers must be ingested at go-live?
- Which purchase order workflows must be supported (PO approval thresholds, automatic reorder, blanket POs)?
- Specify required integrations to parts vendors or distributors for real-time price and availability (for example vendor EDI endpoints or FTP feeds).
- Do you require parts cost and margin parity checks between legacy system and new platform at cutover?
- Who will provide SKU-level mapping between your catalog and platform product codes during import?
Deploy Service Scheduling and Repair Order Management
- Which appointment types and bay configurations must be modeled (express lane, multi-tech RO, sublet work)?
- What service processes must be enforced on every RO (RO open/close checklist, warranty flags, customer authorization capture)?
- Which technician skill codes and flat-rate manuals must be imported for labor scheduling and estimating?
- Do you require integration with OEM service bulletins and recall feeds to flag affected VINs at scheduling?
- Who owns confirmation and appointment reminder templates (SMS, email) and do you require configurable templates by rooftop?
- Which KPIs must be reconciled on day 1 of cutover for service (RO count, labor hours, parts cost, technician productivity)?
Set Up General Ledger and Accounting Posting
- Which chart of accounts will be used at go-live (provide your GL file or mapping requirements)?
- How should transactional posting map to GL accounts for sales, COGS, payroll liabilities, and parts inventory adjustments?
- What reconciliation tolerance will you accept between legacy GL balances and platform postings at first close (for example $ variance or percentage)?
- Which external accounting exports are required (batch journal export, per-transaction API, payroll liability files) and in what format?
- Who signs off on accounting mapping and initial reconciliation (Controller, CFO, external CPA)?
- Do you require automated month-end close tasks and configurable posting periods for multiple rooftops?
Configure Payroll Processing and Employee Payroll Data
- Which payroll elements must be imported (employee master, tax IDs, pay rates, deductions, commission schedules)?
- How many active employees and payroll entities will be managed across storefronts at launch?
- Which payroll frequency and tax jurisdictions do you operate in that affect tax calculations at go-live?
- Who will provide year-to-date earnings and tax filings to seed into the platform for current fiscal year continuity?
- Do you require integration to a payroll provider for direct deposit and tax filing or will payroll remain an external process?
- Are there union, state, or local compliance rules (for example tip reporting, certified payroll) that must be configured per rooftop?
Integrate OEM Factory Communications with Certified Connectors
- Which OEM factory feeds must be active at launch (for example parts warranty claims, dealer stock reporting, recall notifications)?
- Do you require certified connector coverage for specific OEMs and can you supply OEM IDs or dealer codes for connector validation?
- What test criteria will you accept to validate OEM connector functionality (example: successful VIN-level recall lookup, dealer stock file processed within 15 minutes)?
- Who will coordinate OEM-side testing and approvals (dealer OEM admin, manufacturer rep, platform connector team)?
- Are there OEM-approved compliance items (audit trails, field mappings) that must be included in scope and documented before cutover?
Integrate Source CRM and Lead Sync
- Which CRM objects must sync to the platform (leads, opportunities, contacts, activities) and in which direction (one-way, two-way)?
- How frequently should lead sync occur at go-live (real-time webhooks, near-real-time every 5-15 minutes, nightly batch)?
- Provide the CRM record volume (leads/month, active contacts) to size sync throughput and error handling expectations.
- Which field mappings are non-negotiable between the source CRM and DMS (lead source, lead owner, vehicle interest VIN)?
- Who will own ongoing duplicate resolution and lead routing rules after sync is enabled?
- Do you require delivery receipts or SLA reporting on lead handoff to measure lead-to-contact latency?
Activate Digital Retailing and Online Inventory Feed
- Which elements of digital retailing must be enabled at launch (payoff estimates, trade valuation, online deal builder, payment calculator)?
-
Mutual Commit
Finalize commercial terms, multi-year commitments, OEM compliance obligations, and mutual responsibilities for cutover and support.
Agreement Modules
- Subscription Agreement
- Order Form
- Master Services Agreement (MSA)
- Statement of Work (SOW)
- Service Level Agreement (SLA)
- OEM Compliance Addendum
- Data Processing Agreement (DPA)
- Cutover & Support Responsibility Schedule
-
Deployment
Operationalize rollout with readiness checks, execution, and outcome validation.
-
Pre-Deployment Readiness
Confirm concrete readiness facts — owners, migration windows, data access, environments, and rollback/contingency plans before execution.
Pre-Deployment Questions
Environment and site access
- Is the buyer's production environment allocated and available for the planned cutover window (so we can confirm scheduling)?
- If not fully reserved above, what target cutover date or date range should we plan for? (so we can draft the deployment calendar)
Data and configuration
- Which source system categories are in scope for migration or live integration? (we will collect system identifiers in DeploymentConfig)
- Has a named data owner agreed to provide extraction access and approve migrated data for acceptance?
- If a named data owner exists, provide full name and role of the person who will approve extracts and sign off test migrations (so we know who to schedule for approvals).
People and ownership
- Which buyer-side owners are already assigned to the deployment workstreams? Select all that apply.
- Provide the primary deployment lead's full name, role, and preferred contact (email or phone) — this person will approve cutover and be the escalation owner.
Timing and constraints
- Are there blackout windows, required OEM reporting dates, or other calendar constraints we must avoid for cutover?
- If there are blackout windows or recurring constraints, list the specific dates or recurring periods (e.g., month‑end, OEM reporting cycles) so we can schedule around them.
- Is there an agreed rollback/contingency plan and a named decision owner who will authorize rollback if required?
-
Integration & Configuration
Lock exact configuration values the deployment team will use — API credentials, field mappings, integration endpoints, and role/permission settings.
Configuration Details
Environments & Endpoints
- Production instance identifier to use in the deployment (enter the exact instance name the build will reference; example: 'store-nyc-prod')
- Production API base URL the integration will call (format: https://... — enter exact base URL, e.g. 'https://api.example.com/')
- Integration endpoint hosting region (Default: us-east-1) — select the single region where the endpoint is hosted
Authentication & Credential Handling
- Preferred integration authentication method (Default: OAuth2 client credentials) — select the single auth method the connector will use
- Integration client identifier or non-secret credential name (enter identifier only; DO NOT paste secrets; example: 'crm-connector-client-id-123')
- Credential owner and planned secret-exchange channel (Default: Buyer's secrets manager) — choose where the secret will be uploaded at kickoff (we will not accept secrets in this form)
Field & Role Mappings
- Primary customer identifier field name in the source system (enter exact field name the migration will use; example: 'customer_id' or 'account_number')
- Sales transaction status code mapping approach (select one; Default: Seller standard canonical mapping)
- Role-to-permission mapping approach for production (Default: Centralized roles) — choose one strategy the deployment will implement
Operational Settings & Limits
- Daily migration batch size limit (number of source records per day; Default: 10000) — enter numeric value only
- Timezone for scheduled jobs and cutover windows (Default: America/New_York — enter IANA timezone name, e.g., 'America/New_York')
- Enable transactional parity verification run after deployment? (Default: Yes — this triggers the reconciliation job that compares source vs. target transactions)
-
Deployment
Execute the migration, integrations, training, and phased cutover with clear owners, milestones, and escalation paths.
-
Go-Live Acceptance
Verify site- and transaction-level acceptance criteria — transaction parity, accounting reconciliation, OEM reporting, and named sign-offs before declaring production go-live.
Checklist items
- Obtain written go-live authorization from buyer's designated approver(s)
- Collect per-site production acceptance sign-offs
- Complete transaction parity validation and obtain sign-off
- Deliver accounting reconciliation report and obtain finance sign-off
- Execute production integration smoke-tests and capture acceptance
- Validate OEM reporting transmission and receipt
- Create and verify final production backup and rollback point
- Complete cutover runbook checklist and document contingencies
- Confirm monitoring, alerting, and escalation ownership
- Agree post-go-live support plan and shared ticket channel
-
-
Operational Success
Track adoption, SLA performance, open issues, and prioritized enhancements with recurring reviews and a shared ticket channel.
Success Reviews
- Go-Live Health Check (weeks 1-4)
- First Measurement Review (weeks 4-10)
- 90-Day Realization Review (around day 90)
- Quarterly Operational Review
Issues & Enhancements
- Implement or tune monitoring alerts for integration endpoints to proactively detect uptime degradation.
- Execute targeted fixes for the highest-impact integration errors and monitor their effect on the ticket burn-down.
- Restate the numeric targets recorded in Solution Scope
- Verify progress on month-end close cycle time and data migration completeness against Solution Scope targets.
- Agree a time-bound remediation plan for any remaining gaps and set the BAU transition date.
- Confirm operational SLAs and runbooks are in place to sustain outcomes post-hypercare.
- Produce a 90-day outcomes report mapping each metric to the Solution Scope targets and outstanding remediation tasks.
- Schedule remediation sprints for unresolved defects with explicit completion dates.
- Publish updated runbooks and SLA definitions for BAU support ahead of the hypercare transition.
- SLA and incident trend review
- Confirm that integration uptime and user adoption / role-based proficiency rate meet or are trending toward Solution Scope targets.
- Agree the next quarter's prioritized enhancement items and their expected delivery windows.
- Ensure the open ticket queue is being actively resolved and escalation paths are functioning.
- Publish the quarterly operational summary including SLA performance, adoption trends, and updated backlog priorities.
- Schedule targeted role-based training sessions to address identified proficiency gaps.
- Reconfirm success criteria and owners
- Confirm deployment completion and that no critical production defects remain unresolved.
- Agree immediate remediation actions, short-term timelines, and owners for all critical hypercare tickets.
- Verify incumbent system wind-down status and closure steps are documented.
- Publish a go-live health summary that lists open critical tickets, remediation tasks, and timelines.
- Schedule migration retries or reconciliation jobs for any failed records uncovered during validation.
- Establish a daily hypercare stand-up until critical ticket count is reduced to an agreed operational level.
- Present first measurement data against Solution Scope targets
- Determine whether adoption and hypercare ticket burn-down are on track to meet Solution Scope targets.
- Identify root causes for metric shortfalls and agree specific corrective actions with deadlines.
- Confirm the updated timeline toward the milestone recorded in Solution Scope.
- Publish the first-measurement dashboard and a short remediation plan tying each metric gap to specific tasks.
- Schedule role-based refresher training sessions to address proficiency gaps uncovered in the data.
- Present outcome data against each metric
- Adoption and proficiency review
- Deployment and migration validation
- Diagnose root causes for any gaps
- Review persistent defects and enhancement backlog
- Early adoption signals and usage patterns
- Prioritized enhancement backlog and release planning
- Review unresolved integration and data exceptions
- Incumbent system wind-down check
- Agree corrective actions and timeline to reach Solution Scope milestones
- Open ticket channel and escalation path review
- Agree residual remediation plan and BAU transition criteria
- Open issues and immediate remediation actions
- Confirm SLAs and operational runbooks for steady-state
- Quarterly closure and next steps