What is Mobility-as-a-Service and why MaaS matters for your mobility business?

What is Mobility-as-a-Service and why MaaS matters for your mobility business?

What is Mobility-as-a-Service and why MaaS matters for your mobility business?

MaaS is short for Mobility-as-a-Servive, and simply put, it combines various mobility options into a single unified mobility app for a city or region.

Today, we have more options for getting from point A to point B than ever before. Vehicle-sharing, ride-hailing, and all sorts of rental services for all types of transports have grown deeply ingrained in our day-to-day lives, fundamentally changing how we choose to move and commute through cities. 

But, as we all know, quantity doesn't necessarily equal quality. Just because there are many more options for transportation, doesn't mean that they're the most effective for getting where you want to go: 

  • Crossing an entire city on a scooter will quickly become costly and exhausting. 
  • Renting a car may still have you stuck in traffic.
  • Commuting with a rental moped may be less environmentally friendly than potential alternatives, e.g. public transportation. 
  • Managing half-a-dozen applications to find the best deals also gets tiresome.

That's where MaaS comes in. 

In what follows, we'll take a closer look at what is Mobility-as-a-Service, explore some examples of MaaS implementations, and how MaaS may impact your own mobility business. 

Mobility-as-a-Service definition

MaaS solutions integrate various forms of transport services into a single multimodal mobility service accessible on demand. These different transport forms include public transport, as well as ride, car-sharing, and bike-sharing, and others. 

Multimodal simply means that users can combine various types of mobility when planning their journeys, e.g. taking a bus for the first leg of the trip and then hopping on a scooter for the last mile. 

MaaS has been the talk of the mobility industry for years now and the Mobility-as-a-Service market size is projected to grow explosively over the coming years, especially in the Asia Pacific region. 

What are the benefits of Mobility-as-a-Service? 

Multimodality is one of the main ones for end-users. Others include a single payment system and general ease-of-use made possible by having multiple mobility services under one roof. 

Typically, there are different payment plans available – a monthly subscription model with a fixed monthly fee or “pay-as-you-go” model, where each booked trip is priced separately.

But MaaS is not JUST a mobility service aggregator for city dwellers. 

The primary client of a MaaS solution is the municipality. A MaaS solution is first and foremost intended as a way for a city to modernize and gain control over its mobility networks and data. 

MaaS lets the local government offer a convenient mobility solution, while equipping the city with insight on transit data, movement flows, and mobility preferences. It also empowers the city to nudge desirable traveler behavior, i.e. promote certain modes of mobility. 

For example, the city might subsidize discounts for an integrated bike rental solution during the summer to encourage people to choose cycling over other types of transportation. 

MaaS brings together both public and private players – MaaS platform developers, mobility service providers, public transport authorities, and others – and project ownership typically lies with a public institution, hence it may be inaccurate to speak of a general Mobility-as-a-Service business model. 

While individual mobility providers may profit from integration as it allows them to reach a broader audience, the MaaS project as a whole will usually operate at a loss. After all, at its core lies public transportation and its core purpose is to improve quality of urban life, not make profit. 

Still, MaaS comes in all shapes and sizes, so what are the models of Mobility-as-a-Service? Let's explore this through some examples. 

Mobility-as-a-Service examples

One textbook example of a MaaS solution is Berlin's Jelbi. Created by Trafi and Berlin's public transport authority BVG, it brings together every kind of public and shared mobility – ready to be booked in a moment’s notice right from the app. 

With Jelbi, Berliners can easily plan multimodal journeys, buy public transport tickets, and pay for services with all the most popular payment methods. With public transport as the backbone, Berlin has built mobility hubs – physical stations across the city, where people can switch from public transport to shared mobility – to facilitate convenient multimodal transport and encourage people to leave their cars at home. 

Trafi was also behind yumuv in Switzerland, which was one of the first that trialed a regional MaaS solution with subscriptions connecting the three cities of Zurich, Bern, and Basel. Though it was only a research project, its ambitious scope spells the potential future of MaaS – a country-wide mobility solution accessible from a single app.

In fact, such a solution has already seen the light of day – glimble. Created by another major player in the MaaS development scene, Moovit, glimble enables easy travel within the Netherlands, offering most of the same benefits as Jelbi, but on a national scale. 

A MaaS solution done differently

Technically, if we look at MaaS as a unified multimodal mobility app, then Google Maps also qualifies as a MaaS solution, though it stands out for its global scope and not being tied to any particular city. 

Google has proactively partnered with micro mobility partners in various regions, has integrated public transport timetables, and done more to offer a convenient route planning solution. However, the lack of payment integrations and minimal adaptation to local markets makes Google Maps more of a map application with some MaaS capabilities, rather than a full fledged MaaS solution. By the way, are you aware that ATOM Mobility customers can easily showcase their vehicles on Google Maps for free?

Why does MaaS matter to your shared mobility business? 

If you're a micro mobility service provider and your city is mulling over launching a MaaS solution, it may be wise to get your foot in the door. Having your service integrated within the city mobility app confers various benefits. 

For one, it enables you to reach more people. Being on the city's MaaS app will expose your service to commuters that might otherwise elect to choose other modes of transportation. It also helps overcome a critical adoption barrier – people will be able to conveniently use and pay for your solution, without having to download and sign-up on your individual app. 

Secondly and continuing the previous point, it's potentially free advertising. Cities are invested in maximizing their MaaS solution's adoption and spend significant resources in popularizing it. As a result, partnering service providers can piggyback on the marketing efforts of the public transport authority. 

Thirdly, it embeds your business with an additional layer of legitimacy. Namely, your solution being chosen by the city gives it an air of “official”ness, especially if your competitors aren't on it. Once again, this may help attract more users. 

MaaS – an evolution in urban mobility

MaaS lets cities and their citizens take control over a rapidly evolving mobility landscape. With so many different types of transportation and dozens of companies competing over customers, it can all get a bit hectic. 

At the end of the day, finding the best way – be it quickest, cheapest, or environmentally friendliest – is in the interests of both cities and travelers and that's exactly what MaaS tries to offer. 

Whether MaaS will become a standard across cities is yet to be seen, as MaaS companies, much like other large-scale mobility businesses, continue to struggle to reach profitability with Finnish startup MaaS Global recently filing for bankruptcy. Still, the technology behind it was snatched up soonafter by Dutch MaaS company umob, signalling faith in the MaaS project at large. 

So, if you're a mobility service provider, MaaS is something that you shouldn't ignore. 

Interested in launching your own mobility platform?

Click below to learn more or request a demo.

Related posts

More case studies

View allView all case studies
Blog
Unmet demand heatmap: Turn missed searches into measurable revenue growth
Unmet demand heatmap: Turn missed searches into measurable revenue growth

📉 Every unmet search is lost revenue. The unmet demand heatmap shows where users actively searched for vehicles but none were available - giving operators clear, search-based demand signals to rebalance fleets 🚚, improve conversions 📈, and grow smarter 🧠.

Read post

Fleet operators don’t lose revenue because of lack of demand - they lose it because demand appears in the wrong place at the wrong time. That’s exactly the problem the Unmet demand heatmap solves.

This new analytics layer from ATOM Mobility shows where users actively searched for vehicles but couldn’t find any within reach. Not guesses. Not assumptions. Real, proven demand currently left on the table.

What is the unmet demand heatmap?

The unmet demand heatmap highlights locations where:

  • A user opened the app
  • Actively searched for available vehicles
  • No vehicle was found within the defined search radius

In other words: high-intent users who wanted to ride, but couldn’t. Unlike generic “app open” data, unmet demand is recorded only when a real vehicle search happens, making this one of the most actionable datasets for operators.

Why unmet demand is more valuable than app opens

Many analytics tools track where users open the app (ATOM Mobility provides this data too). That’s useful - but incomplete. Unmet demand answers a much stronger question:
Where did users try to ride and failed?
That difference matters.

Unmet demand data is:

✅ Intent-driven (search-based, not passive)

✅ Directly tied to lost revenue

✅ Immediately actionable for rebalancing and expansion

✅ Credible for discussions with cities and partners

How it works

Here’s how the logic is implemented under the hood:

1. Search-based trigger. Unmet demand is recorded only when a user performs a vehicle search. No search = no data point.

2. Distance threshold. If no vehicle is available within 1,000 meters, unmet demand is logged.

  • The radius can be customized per operator
  • Adaptable for dense cities vs. suburban or rural areas

3. Shared + private fleet support. The feature tracks unmet demand for:

  • Shared fleets
  • Private / restricted fleets (e.g. corporate, residential, campus)

This gives operators a full picture across all use cases.

4. GPS validation. Data is collected only when:

  • GPS is enabled
  • Location data is successfully received

This ensures accuracy and avoids noise.

Smart data optimization (no inflated demand)

To prevent multiple searches from the same user artificially inflating demand, the system applies intelligent filtering:

- After a location is stored, a 30-minute cooldown is activated
- If the same user searches again within 30 minutes And within 100 meters of the previous location → the record is skipped
- After 30 minutes, a new record is stored - even if the location is unchanged

Result: clean, realistic demand signals, not spammy heatmaps.

Why this matters for operators
📈 Increase revenue

Unmet demand shows exactly where vehicles are missing allowing you to:

  • Rebalance fleets faster
  • Expand into proven demand zones
  • Reduce failed searches and lost rides

🚚 Smarter rebalancing

Instead of guessing where to move vehicles, teams can prioritize:

  • High-intent demand hotspots
  • Time-based demand patterns
  • Areas with repeated unmet searches

🏙 Stronger city conversations

Unmet demand heatmaps are powerful evidence for:

  • Permit negotiations
  • Zone expansions
  • Infrastructure requests
  • Data-backed urban planning discussions

📊 Higher conversion rates

Placing vehicles where users actually search improves:

  • Search → ride conversion
  • User satisfaction
  • Retention over time
Built for real operational use

The new unmet demand heatmap is designed to work alongside other analytics layers, including:

- Popular routes heatmap
- Open app heatmap
- Start & end locations heatmap

Operators can also:

  • Toggle zone visibility across heatmaps
  • Adjust time periods (performance-optimized)
  • Combine insights for strategic fleet planning
From missed demand to competitive advantage

Every unmet search is a signal. Every signal is a potential ride. Every ride is revenue. With the unmet demand heatmap, operators stop guessing and start placing vehicles exactly where demand already exists.

👉 If you want to see how unmet demand can unlock growth for your fleet, book a demo with ATOM Mobility and explore how advanced heatmaps turn data into decisions.

Blog
🚀 New feature alert: Web-booker for ride-hailing and taxi operations
🚀 New feature alert: Web-booker for ride-hailing and taxi operations

🚕 Web-booker is a lightweight ride-hail widget that lets users book rides directly from a website or mobile browser - no app install required. It reduces booking friction, supports hotel and partner demand, and keeps every ride fully synced with the taxi operator’s app and dashboard.

Read post

What if ordering a taxi was as easy as booking a room or clicking “Reserve table” on a website?

Meet Web-booker - a lightweight ride-hail booking widget that lets users request a cab directly from a website, without installing or opening the mobile app.
Perfect for hotels, business centers, event venues, airports, and corporate partners.

👉 Live demo: https://app.atommobility.com/taxi-widget

What is Web-booker?

Web-booker is a browser-based ride-hail widget that operators can embed or link to from any website.
The booking happens on the web, but the ride is fully synchronized with the mobile app and operator dashboard.

How it works (simple by design)


No redirects. No app-store friction. No lost users.

  • Client places a button or link on their website
  • Clicking it opens a new window with the ride-hail widget
  • The widget is branded, localized, and connected directly to the operator’s system
  • Booking instantly appears in the dashboard and mobile app
Key capabilities operators care about
🎨 Branded & consistent
  • Widget color automatically matches the client’s app branding
  • Feels like a natural extension of the operator’s ecosystem
  • Fully responsive and optimized for mobile browsers, so users can book a ride directly from their phone without installing the app
📱 App growth built in
  • QR code and App Store / Google Play links shown directly in the widget
  • Smooth upgrade path from web → app
⏱️ Booking flexibility
  • Users can request a ride immediately or schedule a ride for a future date and time
  • Works the same way across web, mobile browser, and app
  • Scheduled bookings are fully synchronized with the operator dashboard and mobile app
🔄 Fully synced ecosystem
  • Country code auto-selected based on user location
  • Book via web → see the ride in the app (same user credentials)
  • Dashboard receives booking data instantly
  • Every booking is tagged with Source:
    - App
    - Web (dashboard bookings)
    - Booker (website widget)
    - API
🔐 Clean & secure session handling
  • User is logged out automatically when leaving the page
  • No persistent browser sessions
💵 Payments logic
  • New users: cash only
  • Existing users: can choose saved payment methods
  • If cash is not enabled → clear message prompts booking via the app

This keeps fraud low while preserving conversion.

✅ Default rollout
  • Enabled by default for all ride-hail merchants
  • No extra setup required
  • Operators decide where and how to use it (hotel partners, landing pages, QR posters, etc.)
Why this matters in practice

Web-booker addresses one of the most common friction points in ride-hailing: users who need a ride now but are not willing to download an app first. By allowing bookings directly from a website, operators can capture high-intent demand at the exact moment it occurs - whether that is on a hotel website, an event page, or a partner landing page.

At the same time, Web-booker makes partnerships with hotels and venues significantly easier. Instead of complex integrations or manual ordering flows, partners can simply place a button or link and immediately enable ride ordering for their guests. Importantly, this approach does not block long-term app growth. The booking flow still promotes the mobile app through QR codes and store links, allowing operators to convert web users into app users over time - without forcing the install upfront.

Web-booker is not designed to replace the mobile app. It extends the acquisition funnel by adding a low-friction entry point, while keeping all bookings fully synchronized with the operator’s app and dashboard.

👉 Try the demo
https://app.atommobility.com/taxi-widget

Want to explore a ride-hail or taxi solution for your business - or migrate to a more flexible platform? Visit: https://www.atommobility.com/products/ride-hailing

Launch your mobility platform in 20 days!

Multi-vehicle. Scalable. Proven.