Why Anchor exists
Anchor exists because good people leave for reasons nobody catches.
Built by someone who watched it happen for twenty years, and got tired of not seeing it coming.
The reason
The tool didn't exist, so it got built.
The same thing kept happening, year after year. A good one would come apart slowly, quietly, and by the time it showed up anywhere a manager could see it, they were already gone. The signals you’d catch one-on-one at the crew level turned into statistics in a roll-up. Nobody was watching the one place the loss actually started: one person, one manager, before the breakdown.
Anchor is the tool that should have existed for that. Not a dashboard for HR. Not a survey nobody acts on. A clear, honest read on one person, written for the manager who can actually do something about it, while there’s still time to do it.
The record
Built from inside the work.
James Little spent twenty years inside energy services and petrochemical operations, leading specialty-services teams through the boom-and-bust cycles that define Gulf Coast heavy industry. Anchor is the retention tool he wished existed during that career.
He started as a field-level technician, running the work and learning the trades from the bottom up. From there the ladder went team lead, field manager, project manager, operations manager, area manager. Each step added more people, more sites, more accountability, until more than two hundred people reported up to him directly and indirectly. Every promotion taught the same thing: the higher you go, the harder it gets to see when a good one is coming apart.
The turn
One phone call made it a system.
I’d been building my own retention toolkit for years. Burnout videos, hard-won field lessons, whatever I could pull together to read my teams better. None of it ever became a system.
The shift came on a long phone call with a close friend who worked emergency-room shifts at a high-volume hospital. There were hours where she didn’t have words for what was happening to her, just sobbing on her drive home. I’d watched the same unraveling move through good people on my own crews, quieter and slower, the same pattern. Hearing it in real time, next to my own years running turnarounds, locked in what every previous attempt had missed. The person who needs the tool isn’t HR, and isn’t the employee. It’s the manager, before the breakdown, with intelligence specific enough to act on.
That recognition was ten years ago. Anchor is what I’ve been building toward since.
Home ground
Why we're starting in Houston.
I grew up in Southeast Texas, eighty miles from Houston. Houston was where you went, for school shopping, Astros games, anything that mattered. It’s my spiritual home, and the career that followed kept me close to it. A career of specialty services, turnarounds, and petrochem across Beaumont, Lake Charles, Baton Rouge, New Orleans, Port Arthur, and the greater Houston area. A network across the Gulf Coast that converges in Houston.
The layoffs. The survivors quietly looking. The retention bonuses for specialists everyone’s afraid to lose. Those are my people. That’s why we’re starting in Houston, and that’s why we’re starting now.
In plain terms
A few things I'm not.
I’m not a clinical psychologist. I’m not an HR executive. I’m not a software engineer in a prior career. I don’t have an MBA. And I’m definitely not a venture-backed founder. Anchor is bootstrapped, built by someone who watched the problem from inside the work and knows what it’s like to lose a good one and not see it coming.
See what Anchor became.
The product is the proof. The fastest way to understand Anchor is to read one finished analysis the way your managers would, first page to final script.