
Build Files
The dispatcher's web app and the crew's phone, talking to each other.
Build Files
The dispatcher's web app and the crew's phone, talking to each other.
Build Files came to us with a simple-sounding ask: build a tool that lets dispatchers and field crews work like one team. Anyone who's tried to ship that kind of paired system knows it is anything but simple.
The brief
Build Files is a field service management platform for construction crews. We designed and built two paired surfaces: a dispatcher web app and a crew-facing mobile app. Live map tracking, job check-ins, material orders, and invoicing all work across both surfaces, with information flowing both ways in real time.
What we solved
Field service tools either over-serve the dispatcher and frustrate the crew, or over-serve the crew and leave dispatch flying blind. The crew lives on a phone with gloves on, in noisy environments, with patchy reception. Dispatch lives on a laptop with three tabs open. Both need different things from the same data, and any latency between them causes real money to be lost.
How we got there
We started by following dispatchers and crews in the field. The crew app got designed for one-handed operation with gloves on: large tap targets, no typing where it could be avoided, and aggressive offline support. The dispatcher web app got designed around a single view: where every crew is, what they're working on, and what's blocking them. Both surfaces share a single source of truth.
What we shipped
The crew app surfaces today's jobs, current dispatch instructions, and a single button to check in or out of a site. Material orders are voice-input optional. The dispatcher web app shows live crew positions on a Mapbox layer with job statuses overlaid. SMS-based crew alerts keep even outdated phones in the loop.
What changed for the client
Dispatchers are running their workflows three times faster than the legacy system Build Files replaced. Forty contractors onboarded in the first six months, and crew adoption hit ninety percent within the first two weeks of rollout, which is unheard of in this category.
Frequently asked.
Questions that come up most often when companies reach out about projects like this.
Yes. We've shipped multiple paired-surface products including Build Files, Global Hair, Washouse, and Social Bites. The trick is designing the shared data model up front and making sure both surfaces agree on what's authoritative.
Big tap targets, generous spacing, voice-input where possible, and aggressive offline support. We watch real users on real sites before we draw a single screen, because what looks good in Figma usually doesn't survive a construction site.
Yes. SMS comes up in any product that touches non-app users. We've used it for crew alerts, customer notifications, and OTP flows on Build Files, Global Hair, and Washouse.
Paired builds depend on offline support requirements and how much logic is shared between surfaces. Faster shipping is possible when one surface is essentially a viewer and the other is the source of truth. AXI Launch is the right shape for the initial build.
Want something like this for your team?
Book a Call →AXI Studio
Subscription1 active slot at a time. Pause, scale, or cancel any time.
AXI Launch
Fixed PriceOne project, one price. Scoped to your needs and delivered fast.
Starting atAXI Automate
AI WorkflowsAI agents and automations that replace manual workflows.
Starting at