The short answer
Most of the time between a charter request and a quote is spent re-keying and checking facts that already exist somewhere else: the aircraft’s availability, positioning, crew legality and the price build-up.
The fix is not a faster pricing calculator. It is one trip record that the request, quote, crew, release and invoice all share, so each fact is entered once.
Software can read a request and draft a priced, feasible quote. A person with the authority to commit the aircraft should still send it.
Where the time actually goes
Watch a charter desk work a request and the pricing itself takes a few minutes. The rest of the hour goes on questions the operation already knows the answer to, spread across systems that don’t talk to each other.
- Reading the request. It arrives as an email, a marketplace RFQ or a phone call, each in a different shape, and someone types it into the quoting tool.
- Checking the aircraft. Is the tail available, where will it be before the trip, and is there maintenance due that the scheduler doesn’t know about?
- Checking the crew. Who is current, who is legal for the duty day this trip creates, and what does that do to tomorrow?
- Building the price. Positioning legs, overnights, crew expenses, fees and taxes, from the aircraft’s own costs rather than a generic table.
- Chasing a signature. The quote goes out, the client replies, and the booking is re-entered into scheduling by hand.
None of these steps is hard. Each one is a chance to be wrong, and each one waits for a person who is doing something else.
Why the obvious fixes don’t work
A faster quoting tool shortens the step that was already short. A shared spreadsheet adds a fifth place for the truth to live. And a new all-in-one platform usually asks the operation to give up the maintenance tracker or scheduling system it already trusts, which is a year-long project with a trip desk still running beside it.
One trip, one record
The approach that works treats the trip as a single live record from the moment the request arrives. The request becomes a structured trip. Pricing reads the tail’s real configuration and position. Crew are assigned to legs on the same record, so recency and duty are counted from what was actually flown. The release is gated on the things that must be true. The invoice inherits the trip’s own numbers. The existing tracker and accounting stay where they are, connected rather than replaced.
Nothing in that list is exotic. The gain comes from never typing the same tail number twice.
Where AI fits
Reading an unstructured request is exactly the kind of task current language models do well: pull out the city pairs, dates, passenger count and special requests, and show which line of the email each fact came from so a person can check it in seconds. From there the system can draft a priced quote that already respects the aircraft’s availability and the crew’s legality.
What it should not do is send the quote. Committing an aircraft is a commercial and operational decision. The software prepares it; the person who owns that call approves it.
How to measure it
Before changing anything, take a month of real requests, exactly as they arrived, and record three numbers for each: time from request to quote, how many systems were touched, and whether the quote needed correcting later. That is your baseline, and it is the only honest way to tell whether any tool — ours or anyone else’s — made a difference.