Why the ROI Conversation for Frontline AI Is Backwards

Here’s how the frontline AI ROI conversation usually goes: someone shows the model, capabilities, accuracy, benchmark results. Someone else asks how much it costs. Then someone asks if it’s worth it. The whole frame is “how good is the model, and can we justify the price?”

Wrong question. Not even close.

The model isn’t where the value is. You can rent capable AI intelligence for cents and an API call. The benchmark differences between leading models matter at the margins. The expensive, scarce, hard part is getting a governed AI answer to the exact point where frontline work actually happens.

That’s the question that determines the ROI: what does it cost to reach every deskless worker with connection, knowledge, and action, and what do you save when you finally can?

Start with the cost side. The average frontline enterprise is already paying four standing taxes that almost never appear as line items: management time consumed by routing information every shift; a stack of single-purpose tools each with its own adoption push and integration burden; an IT footprint where every tool is its own identity and audit problem; and the daily cost of information arriving at the next shift instead of the moment someone needs it. These aren’t new costs AI creates. They exist right now, in every frontline operation, invisible because they’ve been there long enough to look like the cost of doing business.

Now the benefit side. When you get governed AI to the frontline, trained on company documents, gated by the right permissions, delivered through a channel people actually use, all four taxes start collapsing at once. At GAT, ramp crews have asked Shelbe nearly 3,000 questions, not just PTO stuff, but pushback procedures, wind limits, incident reporting. At 10 minutes of reclaimed time per question and 12% adoption, that’s ~500 hours returned. Real number. Also the smallest possible version of it, one tax, one customer, early adoption. Move to 30% adoption across thousands of workers at dozens of sites, then stack the other three taxes.

The ROI conversation was never about answer quality. It was about the cost of not having one, and what it takes to close that gap at scale, for a workforce the original enterprise software stack wasn’t built to reach.

Lead with one honest number. Show it’s the smallest of four, at the lowest adoption stage, at a single location. Then let the stacking do the work.