Travel OS by Great Times

Your travel business.
Your brand. One platform.

The software a working Nairobi agency runs on every day, being opened up to other agencies — under their own name.
  • Your own domain
  • Your branding on every document
  • Pilot places, not a sign-up
yourbrand.co.ke/admin/enquiries
RefCustomerProductValueStage
7ASYVHSample Customer AMara — 3 nightsKES 184,000Quoted
8OU8CXSample Customer BNBO–DXB returnKES 41,970Ticketed
9XHII3Sample Customer CSchengen visaKES 12,500Documents in
7LFP8JSample Customer DDiani — 5 nightsKES 96,400Deposit paid
7E7PJFSample Customer EDubai — 4 nightsKES 212,300New

Sample data, to show the layout.

Ten systems, or one.

Most agencies run on a shared inbox, a folder of quote templates, a payments spreadsheet and somebody's memory. Here is the same work, in one place.
  1. 01

    Enquiry

    Arrives in a shared queue, against a customer.

  2. 02

    Quotation

    Priced and sent as your own document.

  3. 03

    Deposit

    Instalments recorded, balance on screen.

  4. 04

    Ticket

    Issued, or read in from the GDS file.

  5. 05

    Your ledger

    Credited to the consultant who sold it.

One record the whole way through, which is why the numbers at the end agree with the ones at the start.

Quotations

Your name on it. Not ours.

A customer who opens your quotation should see your agency. The platform behind it is ours to run and keep working.
  • Your logo, colours and company details on every quotation, invoice, receipt and itinerary.
  • Saved products and itinerary templates, so the fifth Mara quote does not start from a blank page.
  • Sent as a document, with the acceptance or decline recorded against the quote instead of buried in a reply.
SW

Safari World Travel

Your logo. Your colours. Your name.

Quotation
  • Flights NBO–JRO return, 2 adults84,000
  • Serengeti lodge, 3 nights, full board196,400
  • Game drives and park fees62,800
  • Airport transfers9,200
TotalKES 352,400

Sample data, to show the layout.

Money

Every shilling, accounted for.

The question “has this one been paid for?” should take one look, not three phone calls.
  • Payment plans with instalments, each payment recorded against the booking it belongs to.
  • The outstanding balance on a screen, not reconstructed from a bank statement at month end.
  • Deposits, part-payments and refunds all on the same record as the sale.

Payment plan

Sample Customer A · Mara — 3 nights

  • ✓DepositPaid 14 Sep120,000
  • ✓Second instalmentPaid 12 Oct120,000
  • !BalanceDue 28 Nov112,400
OutstandingKES 112,400

Sample data, to show the layout.

Your team

Who sold what, without asking.

Commission arguments are usually a record-keeping problem wearing a management hat.
  • Every sale attributed to the consultant who made it, from the moment it is recorded.
  • Each consultant sees their own numbers, rather than waiting for a spreadsheet from management.
  • Roles decide what each person can see — net fares and commission are a narrower audience than the people selling.

Sales by consultant

This month

  • Consultant A42 sold · KES 2,410,000
  • Consultant B31 sold · KES 1,880,000
  • Consultant C24 sold · KES 1,245,000
  • Consultant D11 sold · KES 604,000

Sample data, to show the layout.

Ticketing — optional

Ticket files that read themselves.

For agencies that issue their own tickets. If you do not, you never see this module.
  • Galileo (MIR) and Amadeus (AIR) files read into the ticket ledger automatically.
  • Credited to the consultant whose sign-on issued the ticket.
  • Voids reverse the sale they undo, instead of being filed as a duplicate and counted as revenue.

AIR00412.AIR

AIR-BLK207;7A;;207;0000000000;1A1469862

K-USD111.00;14495;;;;;;;;;;;32960;130.57

T-1419496686949

read automatically
1419496686949issued
Fare
KES 32,960
Credited to
Consultant A
Rate applied
130.5725

Sample data, to show the layout.

Three steps to a demonstration.

No automated onboarding, because moving an agency's records is not a sign-up flow.
  1. 01

    Tell us what you sell

    Five minutes on the form. Which modules matter, and how big the team is.

  2. 02

    See it running

    A walkthrough of the parts you would actually use, with your questions in front of us.

  3. 03

    Get it in writing

    Which modules, what the setup involves, the cost and the timeline — before you pay anything.

Add the parts you sell.

A visa consultancy should not pay for airline ticket reconciliation. Everything here works today in the agency that built it. See what each one does.
  • Packages & itineraries

    Your holiday products, and the itineraries that sell them.

  • Hotels

    Hotel products, rates and enquiries.

  • Visa cases

    Applications, documents and where each one has got to.

  • Suppliers & procurement

    Who you buy from, and what you agreed.

  • Transfers, drivers & vehicles

    Airport pickups and tour transport, assigned and tracked.

  • Resellers & sub-agents

    Sub-agents selling your products under their own markup.

  • GDS ticket ingestion

    Galileo and Amadeus files read into your sales ledger.

Where this is up to

Honest about the unfinished part.

Travel OS is not a new product looking for its first user. It runs Great Times' own agency — the ticket ledger, the quotes, the payment plans and the consultants' sales numbers are all live in it.

What is still being built is the part that lets a second agency run alongside the first with its own branding and its own completely separate records. That work is underway, and it is why places are limited and why the honest next step is a conversation rather than a sign-up button.

We would rather tell you that now than discover it together after you have moved your customer list.

See it running, with your own questions in front of you

A walkthrough of the modules you would actually use, and a straight answer on what it would take to get your agency onto it.