ONEflight International Case Study

My role: Research, product design & front end
Timeline: 3 months
Product: BAJops · Shipped

Problem

Five aircraft meant five separate entries.

About 100 charter companies quoted trips through BAJops, and operators could submit only one aircraft quote at a time. If five aircraft could service a trip, they had to complete five separate entries.

Research

What operators kept telling us.

I talked with operators, clients, and internal stakeholders before changing the flow. Operators who quoted more than one aircraft often left the same comment in our feedback form: they hated signing back in just to submit another quote. The MVP was to add a multiquote button to the existing interface. I went against the grain and stepped back to ask what operators were actually trying to do. Quoting a trip is its own process. It should have as few friction points as possible, and it should give us something to build from. So I designed bulk entry around the trip, with submitted quotes available to find, reuse, and compare.

Multiquote MVP: Add Multiple Quotes button added to the original stacked layout and multi-leg itinerary — **MVP approach.** Add a multiquote button to the existing interface. Try the MVP approach

Direction · Shipped

Five aircraft. One bulk submission.

My redesign let operators add multiple aircraft quotes and submit them together. I designed the workflow and built the React front end for backend engineers to integrate.

Before

Seven steps and four emails, repeated for every aircraft.

After

Four steps and one email, for any number of aircraft.

Dashed steps happen in the operator’s inbox, outside BAJops.

The pushback was timeline.

The team wanted to ship quickly, so the plan was the legacy route: a multiquote button on the existing flow. I had already built the entire front end for the redesign, and it only needed binding to the backend. That changed the math, and they rolled out the redesign instead.

How the redesigned workflow works

1 / 3

Full operator workspace with the itinerary, previously submitted aircraft and trip or leg quote actions — 01
Start with the trip.
Keep the itinerary and submitted quotes together. Add a whole-trip or individual-leg quote from the same workspace.

Quote entry form beside the complete multi-leg itinerary — 02
Build one bulk submission.
Add each aircraft’s price and documents, then submit the quotes together. The itinerary stays in view.

Active flight requests beside ranked competing aircraft quotes — 03
Manage what comes back.
Find pending requests and compare submitted aircraft, rank, and price differences without switching context.

Interactive demo

Illustrative data

Try the operator workflow

Further exploration · Prototypes

From more quotes to a clearer choice.

The two sides were tightly linked. Every quote an operator placed in BAJops showed up in the traveler marketplace with ONEflight’s markup applied. Say an operator already has a plane heading back to the same airport. They can quote lower and land in first place in BAJops, and the traveler sees a better aircraft for less. Knowing the marketplace was next, I built the quoting work as a foundation, with reusable components and animations we could carry straight into the marketplace build. I also explored how operators could quote from a phone.