A white label solution or building your own software - what to choose for your vehicle sharing business?
May 21, 2021
min. read
Software is an essential part of your vehicle-sharing business. And it doesn't matter what vehicles your customers are going to share. They will do it through the mobile app. So here is the decision to make – are you going to create the vehicle-sharing software from scratch or choose one of the existing solutions on the market. Hopefully, this article will help you with this decision.
Which one of these two options should you choose? There is no one correct answer and there are advantages as well as weaknesses to both of them.
Imagine that this is your first vehicle-sharing business and you have decided to do everything on your own. You are full of enthusiasm and you approach your CTO or IT partner and promise to come up with the brief. The task doesn't seem too complicated for the software you need. However, the vehicle-sharing business is the one that makes creating the brief so complicated. There are many small details to consider.
First step - long and costly research
If you really have decided to start to develop software from scratch, you should take one step back. Your CTO or IT partner must start with the investigation on what functions you might need and how one thing might lead to another. This might take a lot of time and money. In addition, sometimes you can get an impression of what clients need only by operating in the market. For example, ATOM is operating in 23 countries. Their software that is also a white label solution for vehicle-sharing businesses already includes over 100 different features and settings that users might need. And those features are a collection of suggestions from users made over the course of several years in those markets.
However, the aim of the research is to understand what the vehicle-sharing software might look like. If the investigation is done, you can start to prepare the brief and documentation for developers. Here is a list of some other things that you should consider before starting work on a technical solution:
- backend, as well as frontend of the solution - both should be developed and supported so your team can manage operations;
- there should be two versions of the mobile app - one for users that has a device operating on iOS. Other - for the owners of devices that run on Android;
- whenever Apple or Android updates their operating systems or other 3rd party makes an update, you should be ready to check if everything works on your apps;
- apps should be compatible with smart locks in the case of bikes or IoT solutions in the case of scooters, mopeds, cars that are used on the vehicle;
- the IT solution must be properly tested and debugged - the industry average shows that testing the app takes approximately two-three months;
- if your vehicle fleet has over 100 vehicles, most likely you will have a service team. The most convenient way for the service team to operate is by using the phone app. This means that there should be one more app for the service team. And your team members might also have iOS as well as Android operating systems on their devices. So again – there are two more apps for you to build;
- additionally, you must have an invoicing option and also the option to create reports, see statistics, analyze routes, distribute promotions, launch referral programs, etc. And this list can go on and on.
The software development usually costs from EUR 100,000-400,000 depending on the complexity and features that you might want to include. In addition, you have to keep in mind that nothing ends with development. The software requires testing, private launch, debugging and support. And only then will the software be ready for the public launch. However, more bug fixing should probably be done.
One year and you are ready to go!
This whole process mentioned above takes approximately one year. Of course, fingers crossed that the solution as well as the integration with smart locks or IoT solutions works. There is just one problem - the vehicle-sharing industry is changing very rapidly - new players are coming in, others are expanding, new means of transportation are used for vehicle-sharing. And there are a lot of things that might happen and change in a year. It might be hard to catch up.
Furthermore, competitors are constantly offering and creating new features that were not in the market previously such as subscriptions, which is currently a new trend. For example, ATOM Mobility has created a white label solution for the vehicle-sharing market that constantly collects knowledge from their clients and adds new features. Later those features are integrated into solutions offered to other clients so everyone is up to date. In the case of a custom-made solution, everything is on you - it might take additional time and money.
One more thing that speaks in favor of the white label solution - let's imagine that your business is very successful. You have developed a vehicle-sharing software for the one-vehicle type and you would like to grow by adding other vehicle types. Sorry, not possible. You will have to make significant changes to the existing software or develop the new one. So probably you will have to start over again.
The same problem might apply to extending the fleet. If your business becomes scalable, the software might not be appropriate for a fleet with 20 000 vehicles. White label solution providers are usually ready for such success of their customers as they have already supported thousands of vehicles for some time.
When it is worthwhile developing a custom solution?
However, there are times that it is worth considering developing a custom solution - your own software for your vehicle-sharing business. It is worth doing this, if:
1) You already know that you might need some very specific features, but the company offering white-label solutions can't provide them to you. For example, you want your car sharing software to run on the blockchain. Or you want to create a decentralized sharing service. However, it is only worth investing in such a specific solution if it is a real game-changer for you and you have the data to proof it;
2) You have EUR 500,000 or more available in funding and you have a very strong team of developers that you would like to keep working for your company. You consider them to be your asset. Then, if you are lucky, after some time, someone might be interested in buying your company just because of the team and, of course, the solution you have developed;
3) The co-founder of the company is a very good CTO with high-level technical skills and the ability to lead the team. Then it is probably worth building a team. However, most likely you will build a technological and not a vehicle-sharing company in the end and spent more on development than actually on vehicles.
4) For some reason one of the requirements is to have a source code. Companies offering white label solutions won't be able to help you with that.
There is a power in sharing and this doesn't just apply to vehicle-sharing. You always get access to a strong network when you are working hand in hand with the industry leaders. That's what we at ATOM emphasize in collaboration with our clients. We are ready to share as much as we can because we do really care about our clients’ business. It is important for us that they grow and constantly have access to the latest achievements within the industry.
Interested in launching your own mobility platform?
Click below to learn more or request a demo.
Blog
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 🧠.
February 17, 2026
min. read
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
🚕 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.
February 9, 2026
min. read
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
Driver App demo credentials - Email: test@atom.com, Password: driver
