Data Orchestration: Why the Future of Mobility Is Not About Vehicles, Fuel, or Payments

The Illusion of Scale

Mobility volumes are climbing, and transactions per fleet are multiplying. Despite this growth, industry players like fuel card issuers, leasecos, OilCo retail, and MaaS operators are seeing less profit per unit. Scale has stopped paying for itself. Value is migrating from the vehicle to the orchestration layer above it, a process known as data orchestration, which is already underway. This shift is why margins are compressing even in a rapidly growing industry.

The size of the prize remains real. Estimates for the global MaaS market by 2035 vary dramatically —from roughly $1.4 trillion (Precedence Research, Meticulous Research) to over $6.5 trillion (Future Market Insights), with CAGRs spanning 14–38% depending on whether vehicle leasing, energy, urban transit, micro-mobility, and payments are bundled into the definition. The spread itself tells the story: the addressable pool is being redrawn faster than methodologies can settle on it. Whatever the final number turns out to be, the direction is settled — value is migrating from the vehicle to the orchestration layer above it, and the migration is already underway.

Hypothesis: traditional mobility business models were built around siloed P&Ls — fuel here, insurance there, parking somewhere else. The modern customer journey was never siloed. Travellers and fleet users experience mobility as one continuous flow. PwC's mobility consumer research is consistent on this point — seamlessness ranks above features for most users. When the underlying architecture fails to mirror that reality, value leaks at every handover point.

The strategic question has shifted from how to scale to who controls the connective tissue when the customer moves, transacts, and recharges. One operating blueprint — engineered with unusual coherence — currently sets the bar for what that looks like.

Tesla charging stations representing a crucial component of the unified 'Musk Stack' ecosystem.

Data Orchestration in The Musk Stack: A Four-Layer Mental Model

To understand where mobility is heading, it helps to study the most audacious blueprint currently in operation. Tesla is the visible part of a deliberately interconnected portfolio. Read the Musk companies as a single stack and the strategic intent becomes plain: own the layers that compound, partner the layers that don't. As one IT architecture analysis on Medium puts it:

"Elon Musk isn't running five separate businesses. He is architecting a single, massive Ecosystem.

Hardware: The Physical Foundation

Tesla manufactures its own vehicles, battery cells, and increasingly its own silicon. The choice is strategic — a hardware platform purpose-built to run proprietary software gives Tesla cost control, fewer external dependencies, and a product iteration speed that competitors with diluted supply chains cannot match.

Software: The Invisible Engine

A Tesla is, at its core, a software-defined vehicle (SDV). Braking, climate, driver assistance, energy management — every system runs on code that can be updated remotely. The asset stops behaving like a depreciating car and starts behaving like a subscription product. New features appear overnight. Performance improves after purchase.

Energy: The Lock-In Layer

Superchargers function as a strategic moat. By owning the charging network, Tesla turns energy — the new fuel — into an ecosystem anchor. Drivers do not just choose a car; they opt into an energy relationship that is difficult to exit without friction.

Network: The Data Flywheel

Every Tesla on the road is a data node. Anonymised real-world telemetry feeds back into Tesla's systems, improving autonomy models and informing future product decisions. Individual users compound into collective intelligence — and the next generation of vehicles inherits the result.

Think of the four layers as interlocking gears. Remove one and the machine slows. Together they create a position that competitors cannot reach piecemeal, because the integration itself is the asset.

Tesla does not own everything. It buys silicon from Samsung and Intel and continues to source battery cells from Panasonic. The discipline is to own the layers where data and customer relationship compound, and partner where speed or capital efficiency wins. That is the line every mobility and payments incumbent now has to draw for themselves.

Memorable form: integrate the core, partner the edges, orchestrate everything in between.

Which raises an important question for any payments rail flowing through mobility today: if the vehicle is becoming a node in a wider system, what does that mean for the transactions that flow through it?

Mobility companies collect data from many sources, such as a parking meter, highlighting the integration of mobility and payment technology. In the unified mobility ecosystem, the question is: what data do you own?

Payments as Infrastructure, Not Plumbing

For most of the industry's history, payments have been treated as plumbing — necessary, invisible, forgettable. That model worked when the transaction was the end of the journey. It stops working when the transaction becomes a data event inside a continuous customer relationship.

Traditional payment processor	Ecosystem payment platform
Earns basis points per transaction	Earns on transaction + data + adjacent services
Competes on price and uptime	Competes on intelligence and customer lock-in
Treats data as a by-product	Treats data as the product
Scales through transaction volume	Scales through depth of customer relationship
Margin-thin utility	Margin-protected platform

The shift is mechanical. When the data layer is owned, adjacent revenue streams open up that demographic-only competitors cannot price.

The Insurance Disruption Blueprint

Tesla's insurance business shows the shift in numerical terms. By pricing risk on real-time driving telemetry rather than demographic proxies, Tesla Insurance was growing at roughly 20% per quarter as of late 2022 and had reached a 17% attach rate in states where it was available (Tesla Q4 2022 earnings call). Tesla's broader "Services and Other" segment — Supercharging, FSD subscriptions, insurance — reached $12.53 billion in full-year 2025, up 19% year-over-year, while the core automotive business posted Tesla's first annual revenue decline on record (Tesla Q4 2025 results).

The lesson for fuel card issuers, leasecos, and TMCs is direct. Telematics + transaction data + policy management + wallet services, run as one platform, change the customer proposition from "process my fuel spend" to "manage my total mobility spend." Different addressable market. Different pricing power. Different defensibility.

Which raises an uncomfortable question for any payments platform operating in mobility today: if the transaction is increasingly commoditised, what exactly do you own — and is it defensible?

The Ownership Question: What Do You Actually Own?

Before any organisation designs its own stack, the harder question to answer is what it genuinely owns that competitors cannot replicate within an 18-month window. Apply the VRIO test (Valuable, Rare, Inimitable, Organised) to three categories — and answer honestly.

Data ownership

Most fuel card issuers, leasecos, and OilCos are data-rich and insight-poor. The raw transactional feed is valuable. The behavioural data layered on top of it — route patterns, dwell times, vehicle health, fueling-vs-charging mix, policy-vs-actual variance — is the asset that compounds. The questions worth asking yourself:

• Does your data capture route preferences, dwell times, and payment behaviour as connected events, or as separate tables that never meet?

• Is it structured in a way your organisation can act on within a quarter, rather than within a multi-year transformation programme?

• Could a competitor replicate it within 18 months, given the same regulatory and customer access?

Tesla's instructive move: every vehicle with driver-assist also functions as a data-collection engine, continuously training the next generation of systems. That is owning the map at scale.

Customer relationships

Relying on third-party APIs for critical customer touchpoints is a strategic trade — the relationship, and the loyalty, end up belonging to whoever runs the interface. In a MaaS world, whoever controls the interface controls the customer. Questions to test yourself against:

• Do you operate direct customer accounts, or do you reach customers only through aggregator data and intermediary funnels?

• Do you control notification and engagement rights outright, or does a partner platform sit in the middle?

• Can you personalise offers without a third party taking margin or shaping the user experience?

Infrastructure and the utility layer

Owning charging infrastructure, route or pricing data with genuine network effects, or embedded payment rails creates switching costs that no competitor can dissolve with a feature release. Test it with three questions:

• Do you operate physical or digital infrastructure where network effects compound as usage grows?

• Do third parties depend on your proprietary integrations for parts of their own product?

• Do you carry recurring service contracts anchored to your platform rather than to the underlying asset?

Understanding precisely which of those three categories holds your real moat is the prerequisite for everything that follows.

Owning charging infrastructure, route or pricing data with genuine network effects, or embedded payment rails creates switching costs that no competitor can dissolve with a feature release.

Four Strategic Imperatives for Mobility Incumbents

Recommendation, not forecast. Based on current regulatory direction (AFIR, PSD3) and observable competitive moves by OEM captives, EV-native CPOs, and fintech challengers, four moves close the largest gaps for fuel card issuers, OilCos, leasecos, and TMCs.

1. Collapse the silos. Energy, financial services, and mobility need to operate as one P&L view of the customer — not three. Customers do not experience your org chart; they experience friction. Integrating EV charging, payments, journey planning, and reporting into one interface removes that friction and raises switching costs in the same motion.

   
   

2. Open the platform, keep the customer. A partner API ecosystem expands capability without surrendering the user relationship. The discipline is open enough to attract, structured enough to retain control. Telematics is the sharpest current test case — deep integration or ownership, never loose third-party plug-in.

   
   

3. Move revenue mix toward recurring. Asset-heavy growth is a treadmill. Subscription services, usage-based insurance, and bundled energy contracts generate predictable revenue without the balance sheet weight. The shift also improves valuation multiples, which matters in a sector currently re-rating.

   
   

4. Build for the software-defined fleet now. Robotaxi and autonomous-fleet economics will reward operators who already run dynamic pricing, real-time fleet optimisation, and SDV orchestration. Hardware-margin operators will find themselves structurally excluded from those economics.

Key takeaway: the ecosystem you build today determines whose platform you operate on tomorrow — your own, or someone else's. The whole playbook condenses to eleven words: integrate the core, partner the edges, orchestrate everything in between.

The Ecosystem Decade

Mobility is a utility. Vehicles, fuel, and payments are pipes, not water. The organisations assembling owned ecosystems today will define how people and freight move by 2035. The ones that defend the existing product will compete on the margins Tesla was happy to leave behind.

Two regulatory clocks are running. AFIR (in force since April 2024) requires ad-hoc payment options and open data APIs at public EV chargers above 50 kW — turning proprietary lock-in into a compliance problem and turning multi-network acceptance into a structural advantage for issuers already built for it. PSD3 and the accompanying Payment Services Regulation, with final texts agreed in 2026 and applicability targeted around Q2/Q3 2028, will accelerate data portability, open-banking access, and customer control over payment data. Both regulations penalise incumbents that treat data and payment access as defensive. Both reward incumbents that treat them as a distribution surface.

So the question worth sitting with is operational, not philosophical:

When your customer charges, parks, refuels, or pays in 2030, whose ecosystem are they inside — and what does your share of that transaction look like?

Key Data Orchestration Takeaways

• Why the Future of Mobility Is Not About Vehicles, Fuel, or Payments

• Open the platform, keep the customer.

• Move revenue mix toward recurring.

• Build for the software-defined fleet now.