Thirteen years before anyone called it internal tooling.
A phone call that took two days to answer
Air ambulance is a business of urgent questions with slow answers. A hospital calls. They need a patient moved from one country to another, with medical staff, at a specific level of care. What does it cost, and when can you fly?
Answering that meant checking aircraft availability, working out routing and fuel stops, confirming crew, checking permits, and calculating a price. Every one of those steps lived with a different person. The quote arrived two days later, by which point the hospital had often called someone else.
Nobody thought of this as a software problem. It was just how the work was done.
What I built
Two things that turned out to be one thing.
A routing and quote calculator. Feed in origin, destination and care level, get a viable flight chain and a price. Not a replacement for the people who checked it, but a starting point that took minutes instead of a day.
An operations dashboard. Time to first response, time to quote, conversion. Numbers that had existed only as impressions before, put where management could see them.
The second one changed behaviour more than the first. Once time to quote was visible, it started falling on its own.
Why this is on the page
Because it establishes that the pattern is not new. In 2013 there was no Vercel, no Supabase, no language model. What existed was a slow process and somebody willing to look at it directly.
The tools got better. The move did not change.