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.