Service · App development

Build a taxi app for your own transport company.

Your own rider app, a driver app and a dispatch back office that work hand in hand, custom built for your taxi operator, regional taxi organisation or patient transport company. Your own brand, your own pricing, your own customer base, integrated with your BCT (on-board taxi computer) and your invoicing. We design and build these apps natively or in Flutter, with a matching engine that survives both the quiet hours and the rush hour.

Rider + driver appDispatch back officeReal-time matchingBCT integrationKIWA / TX quality mark

A taxi app is not an Uber clone.

The search "build a taxi app" yields, in nine out of ten cases, a quote for an Uber clone from an offshore template factory. A nice screenshot, screen flows lifted from a marketplace, and a price that seems too good to be true. Three months later your licence holder is left with an app in which no trip registration flows to the Taxi On-board Computer, in which the driver can't see whether a trip falls under Wmo transport, and in which the dispatch system doesn't understand what a combined trip is. That is the problem we solve.

We build custom taxi apps for taxi operators in Amsterdam and Rotterdam, regional taxi companies with multiple ranks, patient transport providers who drive for Wmo and Valys, executive transport companies with fixed business contracts and courier transport that carries parcels as well as passengers. The technical building blocks are similar, but the reality of a driver doing a wheelchair trip for the CAK at half past six in the morning is different from that of a driver starting an airport run at half past one at night. An app that serves only the street segment well shuts out a serious part of the Dutch transport market, and an app that can only handle contracted transport shuts out the rush-hour peaks.

Our angle is different from that of a standard app developer: the complexity isn't in the UI of the rider app. That's done in a few sprints and looks much like what you're used to. The complexity lies in the combination of real-time matching between demand and supply, the fare engine that has to blend zone, distance and waiting-time rates with agreements that differ per client, and the integration with the Boordcomputer Taxi (BCT, the mandatory on-board computer in the Netherlands). That's where 80% of the project goes, and it's what determines whether your own taxi platform is still more profitable than a franchise formula a year after delivery.

What we build that sets it apart: a platform under your brand, with your pricing, your customers and your data, not a marketplace that gradually moves your drivers onto another marketplace. Native or cross-platform, integrated with exactly the systems you use, and with a dispatch workspace that works intuitively in the office, without your dispatcher needing a week's training first. We deliver the code, you own the IP, and you manage it yourself or with us. There's no per-ride licence and no revenue percentage that climbs as you become more successful.

Three types of taxi platform.

The right form depends on what you run and who your clients are. In the first conversation we'll work out together which one fits. You'll often start with the first two components and grow into fully dispatched transport.

Compact project · fixed sprint budget

Rider app with simple dispatch

A mobile app for customers to request a ride, either immediately or booked in advance, plus a lightweight dispatch workspace for your control room. Suited to regional taxi companies moving from phoning the control room to their own app for their existing customer base. Your own logo, your own pricing, payment via Mollie or Adyen or cash on settlement, and a short feedback loop between ride and star rating. No marketplace, no unknown drivers, no surge pricing, just your own fleet, easier to reach.

Ride requestMollie / AdyenRatingPDF ride statement
Mid-sized project · fixed sprint budget

Rider and driver app with matching engine

The same rider app plus a full driver app for your drivers, with a real-time matching engine that assigns ride requests based on distance, vehicle suitability (wheelchair, child seat, executive), availability and driver rating. The dispatch back office sees the whole fleet on a map, can make manual overrides, and has insight into what goes through automatic matching and what doesn't. Suited to taxi operators (TTOs) and regional taxi companies with their own fleet of anything from a handful to a few dozen vehicles combining street and contracted transport.

Matching engineReal-time websocketDispatch mapFare engine
Larger project · fixed sprint budget

Full platform with BCT, healthcare and B2B integrations

The full package: rider app, driver app, dispatch workstation, scheduling, a fare engine handling multiple clients side by side, integration with the Boordcomputer Taxi for mandatory ride registration, integration with patient transport portals (CAK / Wmo / Valys), invoicing integration per client, and management reporting on conversion, no-show rate and average waiting time. Suited to transport organisations that, alongside street work, also do substantial patient transport or contracted B2B transport and want to relieve their control room with automation that is genuinely automatic.

BCT integrationWmo / Valys portalMulti-clientReporting

What you get at the end.

A production-ready taxi platform with your own brand and your own data, plus everything needed to manage and extend it. We don't deliver a black box: you own the code, the customer list, the ride data, the release pipeline and the App Store account.

  • Rider app for iOS and AndroidNative (Swift, Kotlin) or cross-platform (Flutter, React Native), with ride requests, advance booking, price estimates, live tracking, payment, ratings and ride history.
  • Driver app for iOS and AndroidJob acceptance, navigation via Mapbox, HERE or Google, fare calculation during the ride, waiting-time buttons, final settlement, and an integration with the in-car taximeter (BCT).
  • Dispatch workspace as a single-page applicationFor your control room: a live map view of the fleet, ride assignment, ETAs, no-show detection, exception flows, and manual overrides for when the matching engine gets it wrong.
  • Matching engine and fare engineAssignment logic based on distance, suitability and scheduling, plus a pricing layer that combines zone and per-kilometre rates, waiting time, night rates and client-specific agreements. With automated tests, because this is where the commercial risk sits.
  • Payment and invoicing flowOnline payment via Mollie or Adyen for the street segment, plus a consolidated invoicing flow per client for contracted transport. See also our payment platform service.
  • Driver onboarding flowDocument upload (driver card, certificate of conduct (VOG), KIWA pass), a screening checklist, an integration with your HR system and an approval workflow for the planner. One place where the status of every driver lives.
  • Taximeter and patient transport integrationsIntegration with the on-board taxi computer (BCT) suppliers (CMT, Cabbie, EuroCabbie) and with the client portals of health insurers, municipalities and the CAK for Wmo and Valys transport.
  • Reporting and management dashboardKPIs for management: number of rides, average waiting time, no-show rate, margin per client, revenue per driver and utilisation per time slot. Exportable to your BI tool or accountant's file.
  • Codebase, documentation and ownershipFull source code, an architecture document, an incident runbook, and a clean ownership handover package. No lock-in, no revenue percentages.
  • Maintenance contract (optional)Monitoring, OS updates for iOS and Android, security patches, certificate renewals for the app stores and ongoing development. Fixed monthly price, four response-time levels.

Who we build taxi apps for.

Six patterns we see again and again in the Dutch transport market. If you recognise your organisation in one of them, we'd be happy to talk further, even if you don't yet know whether your own app is the best answer.

TTO

Licensed taxi organisations (TTOs)

TTOs in Amsterdam, Rotterdam and The Hague that serve the street segment and don't want to lose their drivers to an international marketplace. Your own app means you keep the customer relationship, set your own pricing and stay in control of your relationship with the municipality around TTO rules. An important prerequisite: integration with the on-board taxi computer (BCT) and with your TTO's pass system is not optional but a starting point.

Regional

Regional taxi companies

A regional taxi company with its own fleet of a few dozen cars, an established customer base and a mix of street rides, business transport and subscriptions. Until now, scheduling has run through phone calls to the control room, and the whole organisation can feel it no longer scales. Your own rider app with a dispatch integration replaces phone traffic for the repeat segment, freeing up the control room for the more complex bookings that really need attention. See also our transport software service page.

Patient transport

Wmo, Valys and seated patient transport

Carriers working for municipalities, the CAK, Valys or health insurers: seated patient transport to dialysis and rehabilitation, Wmo transport for people with an assessed need, or wheelchair transport for care institutions. Trips are imported from the client portal, combined into efficient routes and carried out by drivers with the right credentials. Reporting afterwards has to be accurate to the kilometre and the minute, leaving no room for manual correction.

Executive

Business and executive transport

Carriers working for law firms, head offices and hotels, with fixed contract clients, a professional driver pool and higher demands on vehicle segment and service level. Advance booking, sensitive cost-centre administration per client, periodic consolidated invoices and reporting that lets a director-owner or fleet manager see exactly what a department has spent on travel. Here the app is the carrier's calling card with the end user.

Courier

Passengers and parcels in one fleet

Carriers that, alongside passenger transport, also handle urgent parcel runs: laboratory samples, legal documents, spare parts for industry. The dispatch engine recognises which type of job it is and assigns it to the right driver, with the right vehicle, on the right route. Insurance and liability for goods transport are recorded separately, and the fare engine can calculate hybrid pricing.

Specialist

Specialist and international

Niche transport for schoolchildren with an assessed need, pupil transport for municipalities, asylum seeker centre (AZC) transport, or international taxi transport to Schiphol and Belgium. Here an app helps not only the operation but also the tender: a client who can follow the status of every trip in their own client portal will weigh that heavily when choosing a carrier. Your own platform gives you that as an award criterion.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

How a taxi app project works.

1

Introduction

A conversation in which we learn what kind of transport you run, how your dispatch centre works today, which BCT supplier is installed in your vehicles and which client portals are involved. We also look at your fare structure, because a lot of hidden complexity sits there: zone prices, per-km prices, waiting time, surcharges, night and weekend rates, plus deviating agreements per business contract. The clearer the picture at the start, the less we have to correct along the way. A fare engine that has to be rebuilt halfway through is expensive.

2

Planning and user research

A workshop with your dispatchers and interviews with three to five drivers. We ride along, sit in on the control room and watch the current BCT (dispatch system). The reality of a driver in gloves, in a cold car at five in the morning, having to accept a job is different from what seemed logical in a Figma flow in the office. At the end: a concrete scope, a well-thought-out split between automatic matching and manual dispatch, and clear agreements on what is and isn't included in phase one.

3

Building in sprints

Every two weeks, a working build of the rider, driver and dispatch apps on a staging environment. We first build the happy flow from trip request to payment, then add the fare engine, then matching, then the BCT integration and finally the client portals. You test along, your dispatchers test along, and a driver or two take test trips. The fare engine and matching engine get extra automated tests, because a calculation error on one trip multiplies with trip volume: a few cents per trip across thousands of trips a month is real money.

4

Pilot and rollout

First a pilot with one segment, often the street segment of one taxi rank or one client contract, and then a phased expansion. Short training for your dispatchers and drivers, plus an open hour where a driver can practise with the app without pressure. After that we move on one target group per week. After rollout, many clients schedule a second release cycle for whatever comes up in actual use: an app that really runs will by definition produce new ideas that nobody ever came up with on a whiteboard.

5

Further development

A taxi platform isn't a project that stands still after go-live. Apple and Google roll out new OS versions every autumn in which background permissions and location rights work slightly differently again, clients place new demands on their reporting, and BCT legislation shifts along with the Ministry of Infrastructure and Water Management. We provide ongoing maintenance for clients who don't want to set up their own dev team, or we hand over knowledge so that an in-house developer or another agency can take over.

Frequently asked questions.

What clients usually want to know before we start on their taxi platform.

Why build your own taxi app when Uber, Bolt and Free Now already exist?
Three reasons. One: on a marketplace you pay a commission per ride (typically somewhere between 15 and 30 per cent) that structurally lowers your margin. At your own volumes, that quickly adds up to more than the build and maintenance costs of your own platform combined. Two: your customer base belongs to the marketplace, not to you. Stopping or switching means losing your repeat customers. Three: a marketplace serves a single workflow, a ride from A to B. Healthcare transport with a Wmo assessment, school transport with a pick-up protocol, business transport with cost-centre coding, or contract transport with a monthly consolidated invoice isn't part of their product. If you also do contracted or healthcare transport alongside the street segment, you can't really do without your own platform.
Does your app work with the Taxi On-Board Computer (BCT)?
Yes, an integration with the BCT is non-negotiable for Dutch taxi operators, as it is a legal requirement for registering assignments, rides and breaks. We integrate with the existing BCT suppliers (CMT, Cabbie, EuroCabbie and their variants) via their API or via a data logger in the vehicle. The driver app automatically starts a ride in the BCT on job acceptance and closes it at final settlement, so the driver doesn't have to operate two screens at once. Ride data is cross-checked against the data in the control centre, and discrepancies are flagged for manual review. If you don't have a BCT yet, we advise which supplier best suits your fleet, and there is real experience behind that advice.
What about KIWA, the TX-Keurmerk and the Wp2000?
The Passenger Transport Act 2000 (Wp2000) and the resulting requirements for the driver card, BCT registration and the TTO rules in large cities form the legal basis. For healthcare transport, the CAK quality framework applies as well, plus requirements around wheelchair transport and, where relevant, medical assistance. Our app supports document management for the driver pass, VOG (certificate of conduct) and, where applicable, the TX-Keurmerk within the driver onboarding flow, with automatic alerts when a document is about to expire. Legal responsibility remains with the operator, but you get a workspace in which you can see the status of every driver and every vehicle in one place.
How does the matching engine work?
At its core, the matching engine combines an ETA calculation (which driver can reach the pick-up in how many minutes), a suitability filter (does this vehicle have a wheelchair ramp, a child seat, an executive-class specification) and a priority layer (which driver has been idle longer, which is rated higher, which has priority under the client contract). For street transport it is mainly ETA-driven, for healthcare transport suitability becomes decisive, and for business transport a specific driver may be assigned per customer. For more complex scenarios, we combine it with an AI development layer that learns from historical ride data when a ride should be dispatched manually rather than automatically, typically where manual overrides show the same patterns again and again.
Which technology do you use?
For the mobile apps, we typically work with Flutter for cross-platform (one codebase for iOS and Android, which reduces maintenance), or go native with Swift and Kotlin if the performance requirements around background tracking and battery impact justify it. For the driver app we often prefer native, because continuous location tracking and background operations are more sensitive there. For the dispatch workstation we build an SPA in React or Vue with a real-time WebSocket connection to the matching engine. For mapping we use Mapbox, HERE or Google Maps Platform; the choice depends on where you operate and what the licence costs do at your volume. The backend runs on Node.js or Go in a container environment (GCP, AWS or Azure), with Postgres as the primary datastore and Redis for real-time state.
How do you handle payments?
For the street segment, we integrate with Mollie or Adyen as standard, offering iDEAL, credit card, Apple Pay and Google Pay as payment methods in the rider app. For business and contracted transport, we work with consolidated invoices per month or per contract period, generated from the trip records and linked to your invoicing system (Exact, Twinfield, Yuki, AFAS or a custom API). For healthcare transport, claims go through the client portal of the health insurer, the CAK or the municipality — we build the export or the direct integration, depending on what the portal offers. Combinations are common: an operator might get paid for a street trip in cash or via Mollie, and at the end of the month also send a consolidated Wmo (Social Support Act) invoice to the municipality.
What about GDPR and data protection?
A taxi platform processes sensitive data: pickup and drop-off addresses (often medically traceable in patient transport), location history per driver, payment details and, in healthcare transport, eligibility data. As standard, we carry out a DPIA at the start, supply a data processing agreement template for your clients, and set up retention periods in line with the GDPR and the additional requirements health insurers impose. Encryption at rest and in transit goes without saying, an audit log on sensitive actions is built into the dispatch workspace as standard, and retention periods are enforced in code, not in a manual procedure.
Can you build just the dispatch system?
Yes. For some clients the rider and driver app is the priority, while for others the pain is in the control room, which runs entirely on separate Excel files. We can also build the dispatch system as a standalone SPA that connects to your existing rider or driver environment, or work in phases: first a solid dispatch system, then connect the driver app, and only then bring the rider app to market. We decide together how to split the project into phases, based on where you lose the most today.
Do you have experience with healthcare transport specifically?
Yes, healthcare transport is an important segment in our portfolio. Wmo via municipalities and the SVB, Valys via Transvision, seated patient transport via health insurers — each has its own portal formats, its own tariff structures and its own reporting rules. The combination of eligibility checks (is this customer actually allowed to be transported under this contract), own-contribution administration, and the strict rules on shared rides (which customers may travel together in one vehicle) is not part of standard taxi software. We typically build custom solutions for this.
Who owns the code and the data?
You do. We deliver the complete source code, database schemas, build pipelines, deploy scripts and the App Store and Google Play accounts in your name. The data lives in your cloud or with a hosting partner of your choice. If you later want to continue with another agency, or take things over in-house, you can — no technical lock-in, no revenue percentage per trip, no licence fees that grow as you grow. We earn from good work that lasts, not from clients who are locked in.
What determines the cost of a project like this?
The biggest cost drivers are: the complexity of the fare engine (a single tariff versus multiple clients with different price lists), the number of integrations (BCT, invoicing, healthcare transport portals, payment providers), the degree to which you need matching automation versus manual dispatch, and whether multiple target groups with different flows need to be supported (street only versus street plus healthcare plus business). We work in sprints with a fixed sprint budget, so you won't face any surprises and can steer the scope sprint by sprint. An initial conversation about scope will give you a good idea of the range for your specific case.
How long until we can go live?
A first pilot with a rider app and lightweight dispatch for a single segment can be up and running within a few sprints. For a full platform with a driver app, matching engine, BCT integration and multi-client invoicing, we plan a project of several sprints. We often roll out in phases so that part of your fleet can start while we keep building. This gives the control room time to get used to the system and gives us feedback that we feed straight into the next target group. Many large operators deliberately choose a slower rollout to avoid operational disruption.

Talk to us about your taxi platform.

A half-hour introductory meeting, with no obligation. Tell us what your transport looks like now. We'll think along with you, give direction, and be honest about whether a platform of your own is the right answer or an existing package will do just fine. Sometimes the right first step is a better dispatch workstation on top of your current BCT; sometimes it really is a complete rider and driver app of your own. We'll also tell you if we think you're better off with an off-the-shelf package that we don't build. You can also email directly at fabian.vandijk@appfront.nl, or take a look at our other app development service pages for related mobile solutions.

Edit content