A tourism transport operator's whole operation, in one system.
Bookings, fleet, routes, drivers and fares stop living in WhatsApp and spreadsheets. Custom software for transfer, shuttle and private transport companies, and the website that brings the bookings in.
The booking comes in on WhatsApp. After that, everything is manual.
That is how most tourism transport operators in the region run, and it works until they grow. Then bookings collide, drivers leave without a clear route and the fare is worked out by eye.
- Bookings duplicated or lost between chats and spreadsheets.
- Drivers assigned by hand, without a view of the whole fleet.
- Fares worked out from memory; every quote is a conversation.
- No real reporting on trips, revenue or occupancy.
The modules that run the company.
Each module is built around how the operation works, not the other way round. The system stores and organises; the team decides.
Reservations engine
Online bookings with origin, destination, date, passengers and luggage. Every request lands in the team's panel and in their inbox, ready to review.
Fleet and route management
Vehicles, capacity and frequent routes in one place, with the data the agency already keeps.
Driver dispatch
Trip assignment with route, pickup time and passenger details. The assignment email goes to the driver from the system itself, service by service. Nothing to install.
Fares by route
Prices by route and zone, loaded with the data the agency already quotes with. The team quotes with its own judgement, from one place.
Reporting and control
Every request and every service is recorded. Reports of services by route or by driver, exportable whenever the team needs them.
The website for the niche
Sites designed for tourism transport operators: routes, fleet, integrated bookings and the traveller's language. It is what brings the request the system then organises.
For those who move people.
Running a fleet with drivers has its own logic and deserves its own software. The operators Starknot works with:
- Airport transfersPickups with tracked flights, fares by destination, confirmation to the traveller.
- Shared shuttlesFixed routes with schedules, seats and occupancy per departure.
- Private and executive transportHourly or per-trip services, assigned drivers, invoicing to companies.
- Chauffeured fleets for agenciesOperators serving agencies and other businesses, with per-client reporting.
Five steps.
A system refined with real operators and a team that specialises in this niche.
- 01
Diagnosis
One session to understand the operation as it runs today: bookings, fleet, drivers, fares. The result is the recipe for the system.
- 02
System design
Modules, flows and screens agreed in writing before building. That document is the scope.
- 03
Build
Module by module, starting with the one that hurts most. Weekly deliveries and access from week one.
- 04
Go-live
Migration of the data now in spreadsheets, training for the team and the drivers, a supported start.
- 05
Support
Adjustments on real operating data and the monthly maintenance plan that keeps the system current.
Everything that comes with the system.
No payments, collections or accounting: the system organises the operation; the money stays in the same hands as always.
- The team's panel with every request and service.
- The assignment email to each driver, sent per service from the system itself.
- Routes and fares loaded exactly as the agency keeps them.
- Exportable reports by route and by driver.
- Training for the team to use the system from day one.
- Monthly maintenance plan and the code handed over once it is fulfilled.
What operators ask before starting.
Does everything have to change at once?
No. It starts with one module, usually bookings or dispatch, and the rest connect once the team already works with the first one.
What about the data currently in spreadsheets?
It is migrated. Routes, fares, frequent customers and the fleet go into the system before go-live, so the whole operation is there on day one.
Do drivers need an app?
No. Each assignment reaches them by email, sent from the system: route, pickup time and passenger details. Nothing to install.
Who owns the system?
The operator. Same as with the websites: once the maintenance plan is fulfilled, the code, the infrastructure and the documentation are handed over.
Start by understanding the operation.
A diagnosis session with the person who builds the system. The result is the recipe, whether it is built with Starknot or not.
Book a diagnosis