Operating region and scenario
State the intended city or region and whether the project is ride-hailing, taxi, intercity passenger service, Robotaxi, vehicle operations, logistics or enterprise travel.
START FROM THE BUSINESS OBJECTIVE
Project enquiry,
grounded in the operating model
Tell us what you plan to operate, the current stage of your systems and the intended launch date. We will use that context to assess standard product, integration, private deployment and custom implementation.
PROJECT BRIEF
Prepare these five points
The brief does not need to be complete. Clear context reduces repeated discovery and helps define product and delivery boundaries sooner.
Users and fleet model
Describe passenger or enterprise users, vehicle types, drivers or capacity providers and the intended operating model.
Current systems and interfaces
List existing apps, mini programs, payment, maps, vehicles, regulatory or third-party systems and the data that must be retained.
Priority operating problem
Explain the largest current constraint, such as booking, acquisition, dispatch, fulfilment, compliance, settlement or vehicle management.
Target launch date
Share the intended pilot and production dates so standard product, integration and custom work can be assessed.
FROM BRIEF TO PLAN
From the first conversation
to an executable plan
Version, scope, timing, pricing and data use are confirmed in the project solution, contract and compliance review.
Confirm context
Align on region, operating model, participants, current systems and launch objective.
Diagnose the workflow
Map users, drivers, vehicles, orders, dispatch, settlement and external interfaces.
Define solution and boundary
Confirm standard capability, integration, custom scope, data, deployment and responsibilities.
Build the delivery plan
Plan configuration, implementation, migration, integration testing, training and launch support.
PROJECT ENQUIRY