Mobility as a Service: The Platform Wars

The vision of Mobility as a Service — a world where individuals subscribe to a single platform that seamlessly combines transit, ride-hailing, bike-share, e-scooters, car-share, and eventually autonomous vehicles into a single integrated experience — has been the organizing principle of transportation technology investment for nearly a decade. The vision has proven stubbornly difficult to execute. But in 2024, the conditions are finally aligning for MaaS to emerge as a real platform category, and the competition to own the space is intensifying.

What MaaS Actually Is (and Is Not)

Mobility as a Service is a concept that has been defined differently by different stakeholders, which has contributed to significant confusion in both the investment community and among city planners. The most useful definition focuses on the user experience: MaaS is a transportation subscription or on-demand service that provides access to multiple transportation modes through a single interface, a single payment system, and a single account — eliminating the need for users to manage separate accounts, payment methods, and interfaces for each transportation mode they use.

The MaaS vision is not simply multimodal trip planning — that is a feature that Google Maps and Apple Maps have offered for years. True MaaS involves a commercial relationship with the user (subscription or pay-per-use) and actual integration of service delivery: a single booking confirmation that covers the subway trip, the connecting bike-share ride, and the final-mile e-scooter — with real-time adjustments when any leg of the journey is disrupted. This level of integration requires commercial partnerships with all participating transportation providers, operational integration with their booking systems and vehicle fleets, and a payment infrastructure that can settle with multiple providers in real time.

Building this infrastructure is genuinely hard. It requires negotiating commercial terms with transportation providers who are often competitors of each other, integrating with disparate technical systems that were not designed for interoperability, and creating a user experience that is genuinely superior to the existing alternative of managing each mode separately. These challenges explain why pure-play MaaS companies have struggled, and why the most successful MaaS deployments to date have been either city-funded public systems or heavily government-subsidized private platforms.

The European Experiment: Lessons from MaaS Global and Others

The most extensive real-world testing of the MaaS concept has occurred in Europe, where a combination of superior public transit infrastructure, higher urban density, stronger car-alternative culture, and favorable regulatory environments have created conditions more hospitable to MaaS than most US cities. MaaS Global, the Finnish company behind the Whim application, ran the most ambitious experiment in commercial MaaS in Helsinki, Antwerp, Birmingham, and other European cities from 2017 to 2022.

The Whim experience — which ended in business failure in 2022 — is instructive for understanding the MaaS challenge. Whim successfully demonstrated that users would use and value a multimodal MaaS subscription when they had access to good underlying transit infrastructure and a sufficient density of mobility options. User satisfaction among active Whim subscribers was high; many reported meaningfully reduced car ownership interest after using the platform. The business model challenge was not user value — it was economics. Whim was paying retail rates to transportation providers while offering subscriptions priced to drive adoption, creating a structural deficit that the company could not close at the scale it achieved before it ran out of capital.

The Whim lesson is not that MaaS is impossible — it is that MaaS is impossible as a standalone intermediary without either regulatory support (subsidies, mandated data sharing, preferential access to public transit inventory) or captive supply (owning or directly operating the mobility services rather than reselling them at retail rates). Successful MaaS requires either being a city or having the leverage to negotiate supply costs that make the economics work.

The US Landscape: Different Constraints, Different Opportunities

The US MaaS landscape faces challenges that are in some ways more severe than Europe and in others less so. The more severe challenges are structural: US cities are dramatically less dense than European cities, public transit infrastructure is weak outside a handful of major metros, and car culture is deeply embedded in the built environment and consumer psychology of most of the country. A MaaS platform that works in Helsinki — where 75% of residents do not own a car — faces a fundamentally different user acquisition challenge in Phoenix or Dallas.

The less severe challenges relate to mobility supply diversity. The US has the world's largest and most competitive ride-hailing market (Uber and Lyft), a rapidly growing e-scooter and bike-share ecosystem, and the most advanced autonomous vehicle deployment in the world. The raw material for a compelling multimodal experience exists in more US cities than anywhere else globally.

The most interesting MaaS opportunities in the US are not city-wide platforms attempting to replace car ownership for the general population — that market is too car-dependent to reach at commercially viable customer acquisition costs in the near term. Rather, the opportunities lie in specific high-density corridors and use cases: corporate campuses and technology parks where employers are motivated to reduce employee car commuting, major transit hubs where first-mile and last-mile connections are the primary pain point, and dense urban neighborhoods where the combination of good transit access and diverse mobility supply creates the conditions for genuine MaaS utility.

The Platform Architecture Question

One of the most important strategic questions in MaaS is the platform architecture: should the winning MaaS platform be a marketplace that aggregates third-party mobility services, or a vertically integrated operator that controls its own supply? The marketplace model offers faster scaling and lower capital requirements but depends on maintaining favorable commercial terms with transportation providers who may become competitors. The vertically integrated model offers better economics and user experience control but requires enormous capital to build out owned supply.

The evidence from analogous platform businesses in other sectors suggests that the successful model will be a hybrid: a platform layer that provides the user interface, payment integration, and subscription management, combined with some level of owned or preferentially contracted supply in the most important service categories. Uber's evolution from a pure marketplace to a platform that owns its own e-bike and e-scooter fleets (Jump) while also integrating third-party transit and car-share options illustrates this hybrid approach. Lyft's integration of Citi Bike and other bike-share systems into its core platform is another example.

For seed investors, the MaaS architecture question has important investment implications. We are more interested in the enabling infrastructure — the API integration layer that allows any MaaS platform to connect to mobility service providers, the payment infrastructure that enables real-time settlement across multiple mobility partners, and the data platform that powers the demand forecasting and real-time optimization that makes multimodal routing genuinely useful — than in pure-play MaaS consumer applications that are dependent on a supply-side commercial model that is not yet clearly viable.

Cities as Partners, Not Just Markets

The most important insight about successful MaaS platforms is that cities are not just markets for them — they are essential partners. Cities control the curb space that mobility services operate from, the permits that allow shared mobility operations, the data that enables effective multimodal routing, and the procurement processes that can direct public transit subsidies to private mobility platforms. A MaaS company that has a genuine partnership with its city government has a structural advantage over one that is operating in an adversarial or indifferent relationship with city hall.

Building genuine city partnerships requires capabilities that are unusual for venture-backed technology companies: regulatory affairs expertise, government relations capacity, willingness to share data with city authorities on terms that protect user privacy while enabling public planning, and patience for procurement timelines that operate on municipal budget cycles rather than startup schedules. Companies that have built these capabilities — and that treat city governments as partners in the mobility infrastructure challenge rather than obstacles to be circumvented — are the ones we see building the most durable positions in the MaaS ecosystem.