Booking and operations platform

One system replaced the inbox and the spreadsheet

Customers book flights, upload health documents and pay online. The operator's team approves, schedules and invoices from one back office, and ground staff run each flight from their own dashboard.

One booking, five peopleCustomerOperationsGround teamFinanceAdminsees and edits every booking1234567
5user roles, each seeing only its own screens
8 weeksfrom order to first delivered version
1system instead of email, sheets and paper
How it works

One booking, five people.

A simplified view of how one booking moves through a system like this one. Each role sees only its own part of the same record.

Booking #2041Acme Freight, Chicago to LA
Requested
Customer
Books
Uploads documents
Pays online
Operations
Approves
Checks documents
Schedules
Ground team
Runs the day
Finance
Sends the invoice
Matches payment
Admin
Sees and edits every booking, price, route and user, with a record of who changed what
Step 1 of 7

The customer books

The customer books through the portal. Nothing is emailed, nothing is re-typed.

Customer
  1. The customer books through the portal. Nothing is emailed, nothing is re-typed.

The situation

Bookings arrived by email and lived in spreadsheets. Every flight meant chasing paperwork, re-typing details and answering 'where is my booking' by hand.

What we built

  • A public front page with a live route map and an enquiry form
  • A client portal: book a flight, track it, upload health documents, see invoices
  • A back office: review bookings, manage flights, routes, pricing, clients, contracts and payments
  • A separate dashboard for the ground team on the day of a flight
  • Card payments, private document storage and automatic email notifications

The result

  • Delivered as a working system in about eight weeks: ordered in May 2026, first version delivered in July 2026