At some point, every automotive leader has the same uneasy thought:
We are swimming in data. So why does it still feel like we are flying blind?
Recent market research estimates the automotive data monetization market at around $7–8 billion in 2024, set to more than triple by the early 2030s as connected vehicles grow from a few hundred million to well over 400 million. The value is there. The question is who will be structurally ready to capture it.
That tension brought OEM and Tier 1 leaders to Munich for Cars.Code.Cashflow event. Not for another glossy showcase, but for a blunt conversation about what breaks next if the industry keeps treating data as exhaust, not product.
Hardware cycles still run on years. Software and data cycles run on weeks. If that mismatch continues, the industry risks a Symbian moment: technically capable, widely deployed, and still overtaken by players who reorganize faster.
This is not a recap. It's the story of what leaders in the room were forced to confront, the shifts they agreed cannot wait another 6–12 months, and what it will take to avoid becoming the next Symbian of mobility.
Why Symbian, and Why Now
We didn't host Cars.Code.Cashflow to announce a grand vision. We hosted it to answer a narrower, harder question:
How do you monetize vehicle and mobility data without magical thinking or ten parallel transformation programs that never land?
It was a test for us at DataArt too: could we add something useful beyond frameworks and slides, and talk with OEM and Tier 1 leaders about constraints like supply chains, compliance, internal politics, and legacy platforms nobody wants to touch?
The Symbian metaphor was our way into a technically advanced platform that lost not on ideas, but on cadence, developer experience, and ecosystem.
The question we posed:
What is the Symbian risk for your organization today?
By the end of the evening, most participants had an answer.
Across two panels and a keynote, we saw 29 questions from the audience, active exchanges during Q&A, and spontaneous discussions in the breaks, which was a clear signal that the topic hit a nerve.
What Leaders Realized
The first uncomfortable insight was not technical. It was behavioral.
Most executives still default to risk hedging instead of path setting. They spread small bets across pilots and PoCs while avoiding the one decision that changes outcomes:
Data has to be treated as a core product, not a compliance artifact.
That affects who makes decisions, how budgets are allocated, and how teams are measured.
As Dr. Rodrigo Biurrun, Partner Development & Technology at Porsche Consulting, put it:
"We have the data. What we don't have is trust and operational clarity."
Dashboards, lakes, and telemetry – they exist. What's missing is a shared, governed way to turn data into products that product managers, engineers, and business owners can rely on.
Andrey Levitin, Manager, Development & Technology at Porsche Consulting GmbH, was blunter:
"We are still working in silos. Real change means stepping out of that box."
It's one thing to say "agility beats pedigree." It's another to admit your operating model makes agility almost impossible.
The Real Bottleneck Isn't Tech
One message cut across every discussion:
Organizational agility, not technology, is the bottleneck.
The industry has talent, cloud platforms, streaming infrastructure, and maturing SDV toolchains. But structural issues keep repeating:
- Hardware-driven planning that locks software into multi-year commitments
- Fragmented ownership of vehicle, cloud, and mobility data
- Compliance teams pulled in late, forced to veto instead of co-design
- Supplier contracts optimized for cost, not cadence or data access.
You cannot just 'do software' on top of hardware practices.
Trying to build SDVs and data products on top of yesterday's governance and supplier models is how you end up with a platform that looks modern on paper but cannot move at software speed.
Supply Chains, Not Slideware, Shape What You Can Ship
One quote from Roger Atkins, LinkedIn Storyteller, Top Voice for EV, MC, drew a lot of nods:
"Form does not follow function. It follows supply chains."
Procurement frameworks freeze key platform choices for years. Contracts make it expensive to swap or co-engineer. Integrations depend on a single niche vendor.
If your supply chain is optimized only for cost and risk transfer, your SDV strategy is already constrained.
The pragmatic view in Munich was simple:
- Vertical integration is romantic.
- Strategic partnerships are realistic.
That means deciding where you truly differentiate and where you co-engineer with partners who can move at software speed and still respect automotive delivery, safety, and regulation.
As Roger Atkins argued, SDV-ready teams must be able to adjust software mid-crisis to match supply constraints.
That's not a tooling question. It's an operating model question.
The SDV Readiness Shift Map
By the end of the event, three shifts kept resurfacing. Together they form a simple diagnostic: the SDV Readiness Shift Map – three moves that separate organizations performing readiness on slides from those actually shipping.
1. From Data Exhaust → Data Products
Stop treating vehicle and mobility data as a byproduct.
- Define a small set of data products (for example, fleet health, usage profiles, OTA performance).
- Give them real product owners and P&L-relevant KPIs (recovery time, new service revenue, warranty cost, retention).
2. From Hardware Cadence → Software Cadence
Design for the tension between multi-year hardware cycles and weekly software releases.
- Make one leader accountable for software cadence across vehicle, edge, and cloud.
- Create safe integration points where fast software can coexist with slow hardware.
- Bring compliance and safety into design, not just into sign-off.
3. From Closed Control → Collaborative Ecosystems
Real monetization rarely comes from acting alone.
- Map where partners need real-time access to your data products (insurers, fleets, energy, mobility platforms).
- Stabilize interfaces and contracts so they can build on top of you with confidence.
- Use governance and lineage to keep risk in check without freezing experimentation.
Where Trust and Governance Still Hurt
The hardest discussion of the evening was about trust.
Trust in the data. Between business and engineering. Between OEMs and suppliers.
Leaders admitted that impressive-looking platforms still fail basic tests:
- Can we explain where this number came from, end to end?
- Can we prove the model or rule complies with current regulations?
- Can we change it without a six-month internal battle?
In many organizations, governance is still seen as a brake. But the alternative isn't freedom; it's paralysis.
We shared an example where our team helped an automotive client enable data lineage and compliance for a critical analytics pipeline in three weeks. We didn't build a new platform. We removed months of legal and political friction blocking a high-value use case.
The lesson:
Governance embedded in how you build and ship data products creates speed.
Governance bolted on at the end creates drag.
How We Show Up
We didn't use Cars.Code.Cashflow to put DataArt at the center. The challenges are bigger than any one partner.
What participants asked for, however, was partners who can:
- Move at software speed without breaking compliance or delivery trust
- Co-engineer with internal teams instead of dropping decks and disappearing
- Respect legacy systems and supply chains while still pushing for progress
That's how we choose to work: close to the constraints, not just the ambition. With teams that blend SDV, cloud, and data engineering, and that are comfortable inside regulated environments and complex supplier networks.
And we stay long enough to see whether the beautiful architecture survives first contact with production.
What Breaks Next Is Up to You
The Symbian analogy resonated because everyone recognized the pattern: strong engineering and solid funding are not enough if the organization cannot evolve around data and software.
If you want to stress-test your SDV and data strategy or unblock a technically complex use case, let's talk. In our working sessions with teams rewriting how automotive and mobility software is actually developed, we typically focus on one or two high-value challenges, ranging from cross-company data exchange and warranty cost reduction to aligning release cadences across vehicle, edge, and cloud. Together, we identify where data is stuck, where delivery slows down, and what it takes to move critical streams from slides into production.
We won't promise to change the world, but we will help you avoid becoming its next Symbian.
