Xcelerate Web and Mobile Applications

Xcelerate is Teamfront's enterprise field service management platform for property restoration and construction contractors, the businesses that handle water damage mitigation, fire and smoke restoration, mold remediation, biohazard cleanup, asbestos abatement, and reconstruction. It runs the full job lifecycle in one place: lead intake, estimation, production, scheduling, time tracking, invoicing, payment collection, and closeout. Its users are restoration project managers, technicians, dispatchers, office administrators, sales reps, and owners working inside multi-location organizations with role-based permissions at enterprise scale, and it syncs with the accounting and field tools those companies already run, including QuickBooks, NetSuite, Encircle, Xactimate, and CompanyCam.

The platform had two faces, and both needed work. The web application is the operational command center where the business is planned, financed, and reported on. The mobile application is what technicians carry to every job site, the workspace where restoration work is actually executed and recorded. Both had grown feature by feature over years, and neither had a shared design language to grow into.

Xcelerate was capable but aging. Each area had evolved independently, and the product had accumulated the classic failures of a legacy enterprise tool that no longer matched how modern restoration businesses work. The same problems recurred across web and mobile:

Mobile carried its own version of these problems, sharpened by where the work happens. Critical workflows like job detail management sat under multiple layers of navigation, so a technician standing in an active water loss needed too many taps to reach customer contacts, insurance details, work authorizations, and job progress. The home screen failed to surface the next job, pending tasks, or the day's schedule at a glance. Clock in and out, switching between jobs, marking arrival, and taking breaks carried unnecessary friction for workers doing it many times a day. The CRM module lacked modern patterns for lead management and pipeline visualization. And financial work, creating invoices, managing estimates, and processing payments, required switching to desktop, so the field could not close the loop it had just opened.

The approach was to rebuild Xcelerate as one product on one system rather than as a set of modules improved individually. Align UI became the shared foundation across both applications, so every screen drew on the same typography hierarchy, spacing rhythm, component patterns, and interaction behaviors. On web that meant a shared top navigation and collapsible sidebar tying six independently evolved modules together. On mobile it meant a consistent vocabulary of cards, bottom sheets, inputs, and navigation across more than fourteen modules. Consistency was the precondition for everything else. Once the vocabulary was shared, a user could move through the lead-to-cash lifecycle without relearning the interface, and each module could be judged on the specific problem it removes rather than on its existing feature list.

On that foundation, the web application was reorganized around what managers and administrators need to see and decide. The Dashboard became a genuine command center, trading a wall of raw metrics for focused KPIs with trend and target context, and it set the visual standard the other modules inherited. Jobs became the list-level operational hub, holding the table of record alongside lead intake, guided job creation, tasks, time tracking, scheduling, integrations, and an AI-powered AR Agent that scores receivables by risk. Job Detail became a single-job workspace anchored by a Summary view, with the deep restoration-specific sub-modules separated cleanly beneath it. Reports became a flexible BI layer over 200 plus reports, giving them the information architecture, builder, and scheduling they had never had. Settings consolidated fifteen plus scattered admin areas into one panel built for enterprise scale, and added a native Marketing Campaign module. Two-Way Texting became the communication backbone, pulling customer SMS, team chat, e-signature, and document sending into one place.

Designing the same product for the office and for the job site taught me that consistency and parity are not the same thing. The temptation with a web and mobile pair is to make them mirror each other, but the technician standing in an active water loss and the manager reviewing receivables have opposite needs. Sharing the design system while letting the information architecture diverge gave both what they needed. The visual language stayed unified, the depth did not.

Working across six web areas and more than fourteen mobile modules made it obvious that the highest-leverage work happens before any individual screen. Getting the shared foundation right, then designing the Dashboard as the reference implementation of the new visual standard, meant every module after it inherited decisions rather than relitigating them. In a redesign of this size, that compounding is what makes the scope survivable.