Aviapros

Every request, from a refuel to cleaning, was tracked between people by phone and email. Requests got lost, duplicated or delayed because they sat in someone's inbox, not somewhere everyone could see.

Our project manager, a former ground handler, brought the project to us. The goal was a new tool that kept handlers, operators and admin teams aligned on flights and requests, without the calls and email threads.

I looked at existing FBO and ground handling tools. Most covered one narrow task, not the whole coordination workflow. To fill the gap, I held structured conversations with our project manager. His time as a handler showed me how requests, approvals and payments really moved between people day to day.

That surfaced three groups, each needing something different from the same flight data.

We chose one dashboard built from customisable widgets, not a separate tool for each role. The layout stays the same, but what's on it depends on the job. A handler sees a calendar and their tasks, an operator sees incoming requests and finance sees what's due for payment. It keeps the product simple to maintain and still feels tailored to each role.

It also covered crew rostering. Teams could see the roster and create new ones for their staff.

Handlers and operators are rarely at a desk, so it had to work on a phone on the tarmac as well as on a desktop. That shaped the smaller decisions: no crowded screens, nothing important hidden, and navigation rethought for mobile. The sidebar on desktop becomes a bottom bar on mobile, with the icons people use most.

Midway through, admin and finance became a full user group, not just people receiving requests. We went back into research and reworked existing flows to support a third role properly, instead of bolting it on.

Aviapros hasn't launched yet and has a waiting list. We designed it around a real handling company that manages about 8 flights a day, in and out. That set how much could sit on one screen before it turned into noise.