You've decided to launch a ride-hailing business. You've looked at a few platforms, sat through a couple of demos, and they all look more or less the same. Clean UI, GPS tracking, driver app, customer app. Fine.
But the platform you choose will shape every operational decision you make for the next three to five years. Switching mid-flight — after you've onboarded 80 drivers and 2,000 customers — is not something you want to do. So before you sign anything, here are five things that actually matter.
1. Who Owns the Infrastructure?
This is the first and most important question to ask. When you pay a setup fee and a monthly fee, what exactly are you paying for?
There are two very different models in the market:
- SaaS licensing: You get access to a shared platform. Your data lives on the vendor's servers. If you cancel, your data may be locked or deleted. You're renting a seat, not running a business.
- Managed service: The platform is hosted and managed by the vendor on cloud infrastructure. Your data is always exportable. If you ever leave, you can export your business data (customers, orders, financials) within a 30-day window.
Always ask: "If I cancel tomorrow, what happens to my driver data, my customer data, and my transaction history?" The answer will tell you a lot about who you're dealing with.
2. What Does the Dispatch Engine Actually Do?
Every platform will tell you they have "smart dispatch." Few will tell you what that means in practice.
At minimum, a serious dispatch system should support:
- Nearest available driver (basic)
- Zone-based dispatch (for airport queues, city zones)
- Least-busy driver rotation (to distribute earnings fairly)
- Manual override by dispatcher (for corporate accounts, special pickups)
If you're running a fleet in a dense city, the dispatch algorithm directly affects driver earnings and customer wait times. A few seconds of dispatch delay, multiplied across 500 rides a day, compounds into missed revenue and churn. Ask to see the dispatch logic in the admin panel — not just in a slide deck.
3. How Are App Updates Handled?
This is where most operators get caught out in year two.
Apple and Google both release iOS and Android updates multiple times a year. Each update can break existing apps if they're not updated to match new OS requirements. If your vendor charges per update, or if updates require a separate development engagement, you will find yourself negotiating costs at the worst possible time — when your app is broken and your drivers are calling you.
Ask explicitly: "Are security patches, OS compatibility updates, and app store compliance updates included in my monthly fee?"
A managed service model should include this by default. If it doesn't, budget for it — typically 10–15% of the original development cost annually for a custom-built app.
4. What Are the Real Ongoing Costs Beyond the Monthly Fee?
The monthly platform fee is rarely the only cost. Here's what you also need to account for:
- Maps and routing: Google Maps API charges $5–$10 per 1,000 map loads. For an active taxi fleet, this can easily reach $500–$2,000/month. Platforms that use open-source mapping (OpenStreetMap + OSRM) eliminate this cost entirely.
- SMS notifications: Driver/rider OTP, trip notifications. Typically $0.01–$0.06 per message depending on country. Budget $50–$300/month at modest scale.
- Payment processing: Stripe charges 2.9% + $0.30 per transaction. On 1,000 rides at an average $8 fare, that's ~$320/month just in payment fees.
- App store fees: $99/year for Apple Developer, $25 one-time for Google Play.
None of these are hidden — they're standard. But some platforms include maps in their fee (check if they use open-source routing), and some don't. Get a full picture of your monthly cost at 100 rides/day and at 500 rides/day before you commit.
5. What Happens When Something Breaks at 11pm on a Friday?
This will happen. A driver can't log in. The payment gateway throws an error. The app is crashing for customers on a specific Android version.
The platform's support model — not its feature list — is what determines whether you can run your business through that situation.
Questions to ask:
- What is the support response time in your plan? (Email-only 24hr vs chat 4hr vs phone 1hr are very different realities)
- Is there a direct contact — a person, not a ticketing system?
- Do they have an uptime SLA or monitoring commitment?
Insist on understanding the support tier in your contract, not just in the sales conversation. The demo call is not the moment when you'll need them most.
The Short Version
Before you commit to any platform, run through these five questions:
- Who owns the data and infrastructure if I cancel?
- What dispatch strategies does the system support — can I see them in the admin panel?
- Are app store compliance updates and security patches included in my monthly fee?
- What are my total monthly costs at 100 rides/day (maps, SMS, payment fees)?
- What is the support response time in my tier, and is there a real person I can reach?
A platform that answers all five clearly, in writing, is a platform you can build a business on.
All cost figures referenced are based on publicly published pricing from major cloud and API providers as of 2026. Individual costs will vary based on usage volume and region.
