What the pilot is
The pilot is a conversation before it is a product. We are defining the first group of airport-connected businesses who will help us decide which signals are worth sending, how early they need to arrive, and what a useful suggested action sounds like on a busy shift.
There is no software to install and nothing to pay for. At this stage we want to understand your operation well enough to build something you would actually open on a Tuesday morning.
Note
DwellTime is in active development. Airport coverage, delivery channels and pricing are still being defined. Everything shown elsewhere on this site, including sample scores and payloads, is illustrative rather than a live forecast.
Who we would like to hear from
We are most interested in teams who already feel disruption in their day: a cafe that empties and fills with the departures board, a transfer operator watching arrivals compress, a hotel that fields the calls when the last bank of flights goes. Platforms and operations teams who would embed signals in their own tools are equally welcome.
You do not need a data team. You do not need to know what an aviation weather report contains. If you can describe what changes on a disrupted day, that is the input we need.
What we ask of pilot participants
A short call to start, then occasional questions as the product takes shape. If early signals reach you, we will ask whether they matched what you saw on the floor. That feedback is the whole point of the pilot.
What you can read first
If you want to understand the product before getting in touch, the product overview explains the three scores, the use cases show how the same disruption reads differently by business type, and the glossary defines the vocabulary we use. Engineers may prefer the developer overview.