Build what endures
Ryan Roberts, founder of The Saunter Group
Behind the method

Why I build systems, not just strategies.

Ryan "Gus" Roberts. Founder, The Saunter Group. Twenty years modeling failure for the Department of Defense. Then built and sold a defense firm. Same discipline, different arena.

Connect on LinkedIn

I started my career as a fighter pilot and senior strategy officer in the United States Air Force. That world demanded clarity under pressure, disciplined systems, and leadership in environments where mistakes were not recoverable.

Most of my career was spent leading teams that modeled and assessed systems risk for the Department of Defense, working alongside large defense contractors and weapons manufacturers to synthesize failure-mode data across complex systems and produce real-world risk-level assessments.

That work taught me how risk actually behaves: how to quantify it, how to model it, and how to engineer around it before it could cascade. It also taught me something I didn't expect to find useful later. The difference between systems that hold and systems that fail is rarely the people inside them. It's the architecture they were given to work in.

"At this level, ambition without architecture doesn't create freedom. It creates exposure."

From the cockpit to the cabin.

When I left the service, I built and sold a defense contracting firm while living aboard a sailboat in the Caribbean. Different arena, same laws of reality.

At one point, revenue was outpacing structure. The demand was real, but the system underneath wasn't ready to absorb it. What looked like progress was structural debt forming underneath. Visibility narrowed. Decision latency went up. The margin for error collapsed in slow motion, and I was the last to see it.

That was the moment it stopped being theoretical for me. The same systems-engineering discipline I'd applied to cascading failure in defense systems applied directly to business architecture under growth load. The variables changed. The math didn't.

Why this practice exists.

Since then I've watched the same pattern repeat across operators and executive teams. Growth doesn't break what's strong. It exposes what was always weak, and amplifies whatever's underneath.

People are rarely the real problem. Their architecture is.

The Saunter Group exists to fix that with evidence rather than opinion, before it becomes irreversible. We diagnose the system. We diagnose the leaders inside it. We prescribe the structure that holds under load, and we stay long enough to make sure it actually holds. Two instruments and one method, for operators who've moved past survival mode and are quietly struggling under the weight of their own growth.

Three arenas, one discipline

The same systems-engineering discipline, applied across three arenas.

USAF · 20+ years

Fighter pilot. Strategy officer.

Two decades flying combat aircraft and serving as a senior strategy officer. Where the cost of a wrong decision is measured in lives, not P&L.

DoD systems risk

Failure-mode modeling at scale.

Led teams synthesizing failure-mode data across complex defense systems with large contractors and weapons manufacturers. Turned cascade prevention into a discipline.

Operator · founder

Built & sold a defense firm.

Founded, scaled, and exited a defense technology company while sailing the Caribbean. Same systems. Different arena. Compounding consequences either way.

What it taught me

The patterns that repeat across companies.

Growth doesn't break what's strong. It exposes what was always weak.

What worked at $50K/month breaks at $200K. Not because the team got worse. Because the architecture wasn't built for the load you just added to it.

Pressure shows you which leaders actually carry weight.

Calm reveals very little about a leadership team. Crisis reveals who's been compensating for whom, and which decision-making rhythms fall apart the moment they're tested.

The cracks were always there. The growth just made them visible.

Most "sudden" failures aren't sudden. They're structural debt accumulating quietly for six to eighteen months until a growth wave finally surfaces the bill.

Architecture compounds. So does the lack of it.

What you don't structure accumulates as exposure. The fix is almost never heroic. It's structural, and it's usually less work than the patch you've been running.

A note from Ryan

The point of evidence isn't to call anyone out. It's to make the invisible decisions visible, so the team can actually choose. Nobody wakes up wanting to scale chaos. Most of the time they just can't see it yet.

That's the whole job. Diagnose what's actually there. Tell the truth about it. Then build the architecture the next stage needs, and stay long enough to make sure it holds.

— Ryan "Gus" Roberts
FOUNDER · THE SAUNTER GROUP
Start the conversation

If you're scaling, the next conversation should be about evidence.

Most people start with the LDNA. It's free, takes about six minutes, and tells you something useful about how you actually lead. If you're already considering BAIC for the company, the Fit Assessment is the qualifier.