Here’s an honest thing to say about 14 years of building frontline software: most of the work is invisible.
The visible part is the app. The messaging feed. The broadcast that hits everyone on the night shift. The AI assistant that answers a safety question in six seconds. Those are real and they matter. They’re also the easy part.
The hard part, the part that took 14 years and can’t be replicated in a procurement cycle, is everything that has to be true before any of that works. The model. The rail.
Think about what it actually takes to get the right message, document, or answer to a specific frontline worker, with the right permissions, in the right language, at the exact moment they need it. You have to know who that person is without an email address or directory entry, by badge number, clock-in ID, or role. You have to know what they’re allowed to see and do, and that answer has to stay current automatically as their role or location shifts. You have to understand how authority flows through a real working shift, because the org chart isn’t accurate and the shift lead acting for the absent manager isn’t captured anywhere official.
And you have to hold all of that true, at scale, while people are hired, transferred, cross-trained, terminated, and rehired every single day.
That’s not a feature list. That’s an architecture you arrive at slowly, by living in the problem. Customer by customer, industry by industry, learning how frontline identity, access, change, and delegation actually behave in the wild versus how they look on a whiteboard. The gap between those two things is enormous, and it only shows up over time.
We made mistakes. We had assumptions that turned out to be wrong. We built things we had to tear down and rebuild. Edge cases in year three broke assumptions we’d built on in year one. Every one of those experiences is in the architecture now, not as a patch, but as a design choice that accounts for reality.
The result is a rail. Infrastructure. The thing that carries everything else. Like all good infrastructure, it’s designed to be invisible, you shouldn’t notice it any more than you think about what’s under the road while you’re driving.
But when you’re evaluating who to trust with your frontline communication, and especially as you think about getting AI to your workforce, the question worth asking is: what’s underneath? Any vendor can put a messaging screen in front of you and say the word AI. The question is whether anything underneath it can actually deliver accurate, permissioned, governed answers to a workforce that never stops moving.
That’s what the 14 years built. Not the screen. The substrate the screen runs on.
It’s the least visible part of everything we do. And it’s the entire moat.