An app for taxi fleets: drivers see their balance and payouts without calling a manager.
Half of the calls to a fleet are «how much did I earn», «why was this deducted», «when will the money arrive». A driver app answers these by itself: daily balance, fines with a photo of the notice, payout requests, car inspection at handover and return, maintenance booking.
For a taxi fleet, an app is first of all a self-service tool for drivers, not a showcase for passengers: drivers take orders in the aggregator's app. The fleet's own app shows what the aggregator does not: rent, deposit, fines, deductions, rent-to-own and payout history. When a driver sees a transparent balance, there are fewer disputes and fewer departures to another fleet.
The second task is the cars. Photo inspection at handover and return with damage marks, mileage, reminders for maintenance and oil changes, accident reports with photos and geolocation. This protects the fleet in damage disputes and reduces downtime.
For car-sharing, the app is the business itself: sign-up with licence verification, booking, unlocking the car via telematics, per-minute payment. We build natively (Swift, Kotlin) or with Flutter — the choice is made after assessing scenarios and budget.
What a taxi fleet app includes.
Daily credits and debits: aggregator revenue, commission, rent, fines, deposit. Each line comes with an explanation.
A withdrawal request in a couple of taps, payout status and history. Payout rules and limits are set by the fleet.
The notice with date, time and amount, linked to the driver's shift, a notification and the payment or deduction procedure.
Required angles at handover and return, damage marked on a diagram, mileage and fuel level — with time and geolocation.
Reminders for scheduled maintenance, booking at the fleet's service, accident reports with photos, geolocation and instructions.
Rent-to-own payment schedule, remaining balance, overdue payments, the contract and addenda in the app.
Push notifications about credits, fines, expiring insurance and changes in terms — cheaper than SMS and more reliable than a WhatsApp group.
A web admin for managers and mechanics: drivers, cars, payouts, fines, inspections, downtime reports.
App screens.
- Sign-in by phone number and SMS code
- Home: balance, next payment, payout status
- History of credits and deductions
- Payout request
- Fines with notices
- My car: details, documents, OGPO, maintenance
- Photo inspection at handover and return
- Report an accident
- Rent-to-own: schedule and remaining balance
- Support: chat with a manager
An app, a Telegram bot or a web account.
Up to 30–50 cars, an app usually does not pay back: balance and payouts are covered by a CRM and a Telegram bot that tells the driver «how much is credited» and «when is the payout». It is faster and cheaper.
From 50–100 cars, the load on managers grows and balance and damage disputes become routine — then an app with photo inspection and a transparent balance saves people and money. A middle option is a PWA driver account from ₸1,200,000: it runs in the phone browser without publishing to the stores.
Car-sharing and self-drive rental cannot work without an app: booking, unlocking and payment all happen in it. This is a project from ₸2,500,000 and usually more because of telematics.
Where the app gets its numbers.
A driver app shows what the accounting system has calculated, so the backend comes first: drivers, cars, contracts, credits, fines, payouts. Data sources:
- revenue and rides — the aggregator's partner API or regular import of exports;
- mileage and location — GPS tracking;
- fines — notices loaded by licence plate;
- payments — reconciliation of Kaspi receipts and payouts.
If accounting is still in Excel, we start with CRM and automation and connect the app to it as a second stage. This way the driver sees a correct balance from day one, not a copy of a spreadsheet.
How much an app for a taxi fleet costs.
A driver app for iOS and Android with a backend and admin panel starts from ₸2,500,000, from 8 weeks: balance, payouts, fines, photo inspection, notifications. A PWA driver account starts from ₸1,200,000. Car-sharing with booking, telematics and per-minute payment costs more; we estimate it after reviewing the scenarios.
The price depends on: number of screens and roles, integration with the aggregator and GPS, offline mode for photo inspection, payments. Details are on the mobile apps page.
The short version.
How much does an app for a taxi fleet cost?
A driver app for iOS and Android with a backend starts from ₸2,500,000, a PWA account from ₸1,200,000. An exact estimate follows a review of screens and integrations.
Can driver revenue be pulled from the aggregator?
Yes, if the fleet has access to the aggregator's partner API — shifts and transactions load automatically. Otherwise we import exports on a schedule.
How does the app help with damage disputes?
Photo inspection with required angles, time and geolocation at every handover and return. Damage that was not there at handover is visible immediately, and the dispute is settled by the photos.
What do you build apps with?
Natively in Swift and Kotlin or with Flutter. For a driver app without complex device features Flutter is often enough; for car-sharing with telematics and Bluetooth we usually choose native.
How long does development take?
From 8 weeks for a driver app with core scenarios. Car-sharing and complex integrations take longer; we name the timeline after the prototype.
Same service for other industries
Drivers call about every credit? Describe your fleet — we will suggest a format and estimate.
Tell us how many cars and drivers you have, where you keep records now, whether you work with aggregators via API and whether you need car-sharing. We will tell you what pays off better — a bot, a PWA or an app — within 1–2 business days.