Pilot-readyMature product foundation

Taxi operators, transfer companies and destination transport teams

Taxi & Transfer Operating System

A controlled operating system for transfer enquiries, route and per-kilometre pricing, vehicle choice, quotes, assignment and dispatch states, with optional Hotel and Tour handoffs.

Available for scoped implementation and controlled pilots.

Mature product foundation

Available through a scoped, owner-controlled pilot.

Open synthetic Taxi demo

Operating problem

A specialist foundation shaped around the operating workflow.

Transfer enquiries, route prices, vehicle availability and driver handoffs are often handled through calls and chat without one reliable state. Quotes are slow to reproduce and dispatch context becomes difficult to audit.

Two sides of the system

Clear for customers. Controlled for operators.

The public journey and the private operating workspace have separate responsibilities and access boundaries.

Public / customer

What the buyer or traveller can do

  • Request a point-to-point or return transfer
  • Choose a vehicle class using passenger and luggage capacity
  • Receive an indicative route match where the rate matrix supports it
  • Provide travel references and consent separately from the booking request
Operator / admin

What the operating team can control

  • Manage vehicle classes, fleet and driver records
  • Configure point-to-point rates with a per-kilometre fallback
  • Record waiting and day-allowance rules
  • Move requests through quoted, accepted, assigned and dispatch states

Isolation and integration

Tenant boundaries stay explicit.

Tenant-scoped records, operator sessions and server-side signed service requests keep business boundaries separate. Driver assignment and customer contact context are available only to authorised operator roles.

Hotel / Tour → Taxi handoff

Approved Hotel and Tour tenants can prepare signed transfer requests for a mapped Taxi tenant. The Taxi operator keeps control of pricing, acceptance, assignment and dispatch. Service credentials stay server-side, and every tenant link is an explicit configuration step.

Review the synthetic live preview

Controlled pilot

Included in a scoped pilot

  • One agreed operator, fleet and service area
  • Vehicle, driver and rate-matrix intake
  • Branded public transfer-request route
  • Least-privilege operator handoff
  • Quote, assignment and dispatch QA

After a request

No tenant is created automatically.

  1. 01

    Mesh Creation reviews the operator, fleet, rate model, service area and desired start date.

  2. 02

    The owner prepares a proposal with scope, responsibilities and pilot terms.

  3. 03

    After explicit acceptance, the owner opens a pilot dossier and schedules data, access and QA handoff.

  4. 04

    Tenant creation, service links and launch remain separate, explicit owner actions.

Commercial termsProposal / pilot based

Taxi pilot, setup and subscription terms are proposal based. No unverified public numeric price is shown.

Request a pilot review

Start with the real constraint

What needs to work better?

Share the product, platform or workflow that needs to be built, modernised or made easier to operate.