The Daimler internal systems that dealer groups depend on for sales data are not built for programmatic access. 2FA requirements, CSV-only exports, and periodic authentication changes mean that any automated data pipeline you build can break overnight. When it does, the fallback is manual.
This isn't a criticism of the OEM. Their systems are built for compliance and vehicle operations, not for the cross-location analytics a group at your scale needs. The gap has to be bridged somewhere. Right now, for most groups, it's bridged by people.
What small fixes actually look like in practice
The instinct when you hear "data infrastructure" is to picture a six-month project, a new system, and a budget that needs board approval. That's not the only way this works.
The most effective starting point is usually the highest-friction weekly task. For most dealer groups that's the sales reporting cycle: pulling data from the OEM portal, cleaning it, pushing it into a BI tool, distributing it. That specific workflow can be automated without replacing your DMS or your reporting tool.
One Nordic dealership group reduced their weekly reporting time by a factor of 10. The change was a scheduled data job that pulls from the OEM system, cleans the relevant fields, and feeds directly into their existing Power BI environment. No new dashboards. No new systems. The reports they already had, running without anyone touching them.
From there, the next layer is offer statistics: a lightweight interface where sales agents upload their weekly quote data, which rolls up automatically into group-level dashboards. No full CRM replacement. A single integration point that removes one manual process.
The principle is that you don't have to rebuild everything to stop losing the week. Find the workflow that costs the most time. Fix that first. Then the next one.