This is the actual output AX produces from a 1-hour discovery call with a logistics company. Click through the tabs to see how a raw transcript becomes a structured spec.
[Discovery call — Acme Logistics, Tuesday 10:32 AM] Sarah (Operations Lead): Right now our dispatchers are pulling from three different systems just to assign a driver to a route. They've got the load board open, the driver roster in a Google Sheet, and the truck maintenance log in our old fleet system. By the time they've cross-referenced everything the customer is already calling to ask where their pickup is. Mike (CTO): The Google Sheet alone has eaten us alive. Last month a dispatcher assigned a route to a driver who was already on a 14-hour rest break — DOT violation, the driver got a citation, we paid it. The fleet system doesn't know who's available, the load board doesn't know who's certified for hazmat, and nobody knows who's nearest to the pickup. Sarah: We need one screen. Show me available drivers, sorted by proximity to the pickup, with their certifications and hours-of-service status visible. And it has to flag the rest break thing automatically — we cannot rely on dispatchers remembering FMCSA rules at 6 PM on a Friday. Mike: We have about 240 active drivers across four terminals. Peak dispatch is around 200 assignments a day. Anything slower than 2 seconds to load the driver list and dispatch starts complaining. And it needs to work on the dispatchers' existing Windows machines — no Macs, no iPads. Sarah: Oh, and integration with our TMS — McLeod — is non-negotiable. If a load doesn't show up in McLeod within 30 seconds of being dispatched, the billing team's downstream report breaks.
Free plan gets you 3 runs. Pro trial gets you 100 / month for 7 days. No credit card.