Software buyer checklist
How to evaluate taxi booking software before you buy
Test taxi booking software with one real booking and one problem case. Follow both through the customer app, driver app and dispatch panel. Then compare pricing, contract terms and launch time. Use the checklist below in every demo.
By Hoppvia · Updated
Taxi booking software checklist at a glance
- Customer app: book a ride, see the fare, track the driver live and pay by card.
- Driver app: receive and accept ride offers, verify the pickup and see earnings.
- Dispatch panel: bookings, driver availability, live map and trip history.
- Booking types: on-demand, scheduled and airport bookings, and corporate accounts if you need them.
- Pricing model: per trip, per vehicle, revenue share or flat price, compared over 12 to 36 months.
- Launch: who publishes the apps, and how long until they are submitted to the stores.
- Ownership: who owns the app store, payment and maps accounts, and how you export your data.
- Support: channels, hours and response times in writing.
Define the operation you need the software to support
Write down your area, number of drivers, booking channels, ride types, fares, payment methods and staff roles. Split must-haves from nice-to-haves.
List any special needs, such as advance bookings, airport pickups, hourly hire or company billing. A general taxi app may not cover them. For each one, ask to see it in a demo and get in writing whether it's included, a setting or extra work.
Follow one booking across passenger, driver and operator
These are questions to ask. No product includes every item. Ask to see live connections, not just sample screens.
| Stage | Questions to ask | Evidence to record |
|---|---|---|
| Passenger booking | Can the passenger choose pickup, destination and the correct vehicle category? How is the fare explained? | A request with the expected route, vehicle category and fare rules. |
| Driver assignment | Is assignment manual or automated? What happens if the offer is declined or no driver is available? | The driver's offer and the operator's view of acceptance or an unassigned booking. |
| Pickup | How do passenger and driver identify each other? How are delays, wrong pickups or cancellations handled? | The agreed check process and the records available to support staff. |
| Active trip | Which location and status updates are live? What happens if connectivity is interrupted? | Updates in the connected environment and a defined recovery or support process. |
| Payment | Which payment methods work in your market? Who handles failed payments, refunds and reconciliation? | The agreed payment flow, relevant statuses and the responsible party. |
| Completed trip | Can passenger, driver and authorized staff find the records they need? | Receipt, trip history, driver earnings and the agreed operator record. |
| Staff access | Which roles can view, assign, change or resolve a booking? | Access rules and the operations surface included in the quote. |
Test an exception, then agree how it will be resolved
Pick a problem your team really faces: an unanswered request, a changed pickup, a cancellation, a lost signal or a failed payment. Ask who sees the problem, who can act and what each person sees afterwards.
Record the expected outcome and compare it with the demo. Hoppvia includes live GPS tracking and card payments as standard. Other integrations are quoted on the Enterprise plan. A nice screen doesn't prove the whole system is connected.
Confirm licence rights and who does what
Ask what the licence covers. Confirm who owns the accounts, what data you can export and who handles backups and updates. With Hoppvia, hosting and updates are included and the platform is licensed for your brand without source code. You own your payment, maps and developer accounts.
Every Hoppvia plan includes the customer and driver apps, dispatch panel, brand setup, hosting and app store submission. See the white-label scope summary and pricing overview before your demo.
Compare the full quote and your acceptance conditions
Compare the licence, setup, integration work, provider fees, maintenance, developer account fees and taxes. Hoppvia plans include hosting, and the pricing page lists what each plan includes. Compare the same requirements across suppliers. Our taxi app cost guide explains the budget categories to include in a written quote.
| Field | What to write down |
|---|---|
| Requirement | The booking or operating outcome your team needs. |
| Scope | Included, configurable, separately quoted or excluded. |
| Demonstration | The environment and the steps actually shown; identify any sample data. |
| Responsibility | Who supplies each account, integration, release step and ongoing service. |
| Acceptance condition | What your team must be able to observe before accepting that part of the launch. |
Before launch, run your checks again on the live system. Give every open item an owner and a next step.
Prepare for a Hoppvia demo
Start with the passenger and driver product walkthrough, then review the operator console and driver-offer walkthrough. The public previews use sample trips.
Then send your market, driver count and booking example to Hoppvia. Ask to follow a booking from request to driver offer, pickup, drop-off and records. Then agree the tools and outside services for your launch.
Frequently asked questions
What should I bring to a taxi software demo?
Bring your service area, number of drivers, payment methods, one normal booking and one problem case. Mark which needs are must-haves for launch.
How has Hoppvia been implemented at scale?
Hoppvia runs with 5,000 drivers and 20,000 customers at peak traffic. Tell us your expected volume and we'll plan for it.
How should I compare two software quotes?
Use the same needs and tests for each. Then compare the licence, setup work, provider fees, yearly costs and who does what.
What features should taxi booking software have?
You need three parts. A customer app for booking, live tracking and card payments. A driver app for ride offers and pickup checks. And a dispatch panel for bookings, driver availability and trip history. Private hire and chauffeur firms also need scheduled bookings and corporate accounts.
How long does it take to launch taxi booking software?
With a white-label platform, branded apps can reach the app stores in days or weeks. Hoppvia usually submits them in about a week. A custom build usually takes months.
