Mobility as a Service: One App to Rule Them All?
The pitch for Mobility as a Service is elegant: open a single app, input your destination, and receive a seamless journey combining metro, bus, e-bike, and ride-hail — planned, ticketed, and paid in one transaction. It’s the kind of vision that plays well in pitch decks and smart city conferences. The reality, as our team at Güil Mobility Ventures has observed across markets, is considerably more nuanced.
Helsinki’s Whim: The Cautionary Tale
No discussion of MaaS is complete without Helsinki’s Whim, launched by MaaS Global in 2016 as the world’s most ambitious multimodal platform. At its peak, Whim offered monthly subscription plans bundling public transit, taxis, car rentals, and e-scooters. The concept attracted global attention and significant venture funding.
By 2023, MaaS Global had filed for restructuring. The core problem wasn’t technology — it was margin. Aggregating other operators’ services into a subscription meant Whim absorbed the price risk. When taxi costs exceeded subscription revenue, the model bled cash. The lesson: a pure aggregation play without control over supply-side economics is structurally fragile.
What’s Actually Working
Despite Whim’s struggles, elements of the MaaS vision are succeeding — just not as a single unified product. Several models are gaining traction:
- Transit agency-led integration — agencies like Berlin’s BVG and Singapore’s LTA are embedding bike-share, scooter access, and ride-hail into their own apps. The transit operator controls the platform, and third-party modes complement rather than compete with public transit.
- Employer mobility budgets — companies like Betterway (France) and MOIA (Germany) provide employees with monthly mobility allowances that work across multiple modes. The employer is the customer, removing the consumer acquisition cost challenge.
- Regional bundled passes — Switzerland’s national transport pass, which covers trains, buses, boats, and cable cars, is arguably the oldest and most successful MaaS product, even though nobody calls it that.
The Data Integration Challenge
The technical backbone of MaaS — real-time data exchange between operators — remains its greatest obstacle. Transit agencies, scooter companies, and ride-hail platforms use different data formats, API standards, and update frequencies. The General Transit Feed Specification (GTFS) provides a common language for public transit data, but extending it to on-demand and shared modes is an ongoing effort.
Privacy adds another layer of complexity. A truly integrated mobility platform knows where users go, when, and how often. European GDPR requirements and growing consumer awareness of data practices mean MaaS providers must architect their systems for data minimization from the start — not as an afterthought.
Where We See Opportunity
Our investment perspective on MaaS has evolved. We’re skeptical of consumer-facing “super apps” that try to aggregate every mode. Instead, we see value in:
- Infrastructure-layer integration — the APIs, payment rails, and data standards that enable interoperability between modes, regardless of which front-end app the user prefers
- B2B mobility management — platforms that help employers, universities, and property developers offer integrated transport to their populations
- AI-driven journey optimization — systems that learn user preferences and dynamically route across modes based on real-time conditions, price sensitivity, and carbon impact
MaaS isn’t dead — but the monolithic “one app” vision probably is. The future looks more like an ecosystem of interoperable services than a single platform to rule them all.
Resources
- MaaS Alliance Framework — industry body working on MaaS standards and interoperability
- UITP MaaS Report — global assessment of MaaS implementations
- GTFS Realtime Specification — the data standard underpinning transit integration