The Career Was Working

Let me be clear about what I left behind:

Over $100M in delivered programs across aerospace, aviation, AI, and enterprise technology
100% on-time delivery record
Experience across four continents with Fortune 500 aerospace, enterprise technology, and international aviation companies

I wasn't stuck. I wasn't frustrated with my employers. The organizations I worked for were filled with talented, dedicated people doing meaningful work.

I left because I saw something I couldn't unsee.

The Gap

Across every organization I worked in — different companies, different countries, different program types — I kept observing the same disconnect:

The people were exceptional. The problems they solved were genuinely hard.
The tools they relied on were a generation behind the complexity they were managing.

I saw brilliant people spending hours synthesizing information that could have been at their fingertips. I saw hard-won context gradually fade as teams evolved. I saw people managing staggering complexity with approaches that hadn't changed in decades.

Every time I raised this observation, the response was a knowing nod — an acknowledgment that the gap was real, but not something anyone expected to change anytime soon.

That acceptance stopped being enough for me.

The Decision

The transition from "I see a problem" to "I'm going to build the solution" didn't happen overnight.

The final push came from a simple realization: I could spend the next decade working within existing systems, doing good work, advancing my career. Or I could take everything I'd learned and try to build something the industry actually needs.

Not something incremental. Something that addresses the root cause of the gap I kept seeing.

That carried real risk. Walking away from a proven career path. Trading predictability for uncertainty. Trading a track record for a blank page.

I did it anyway. I started TelosFlow in late 2025.

What I Brought With Me

I didn't start this company because I'm a technologist. I started it because I lived inside the problem for nearly a decade — managing complex programs from the inside, not studying them from the outside.

Many technology companies in this space are founded by talented engineers and developers who learn program management and project management through research, conferences, and customer interviews. That's a valid path.

My path was different — I lived it first. I sat in program reviews. I managed supplier relationships. I navigated compliance requirements. I felt the weight of decisions that affect safety, contracts, and careers.

That gives me a different starting point — one grounded in what it actually feels like to manage these programs.

What I've Learned About Starting Something New

Building a company is different from managing a program. A few things have surprised me:

The loneliness is real. In aerospace, you're surrounded by teams and stakeholders. As a solo founder, some days the only conversation about your work is the one in your head.

The aerospace network is incredibly generous. When I reached out to former colleagues to validate what we're building, I got genuine engagement — detailed feedback, honest criticism, introductions. Over 20 aerospace leaders took time to share their perspectives.

Speed and quality aren't opposites. The startup world pushes speed. Aerospace demands rigor. The real discipline is knowing which decisions need rigor and which need velocity.

The imposter syndrome is constant. I've delivered $100M+ in programs. I've led teams across four continents. And I still wake up some mornings wondering if I'm the right person to build this. That feeling doesn't go away — you just learn to build alongside it.

What Drives This

Let me be honest about what sparked this.

As a program manager, I was constantly fighting my own tools:

Excel spreadsheets that needed manual updates
MS Project files that required constant maintenance
JIRA boards that tracked tasks but missed the business context
PowerPoint decks rebuilt from scratch for every review

I wasn't using tools. I was serving them.

When I talked to other program managers — across companies, countries, and industries — I realized it wasn't just me.

The same frustrations came up everywhere:

First hour of every day just getting caught up on overnight changes
Rebuilding context after a key team member moves on
Sitting in a review and realizing the biggest risk wasn't on anyone's slide
Teams repeating avoidable mistakes because lessons learned live in forgotten SharePoint folders
Preparing for stakeholder meetings with data scattered across five systems that don't align

These aren't edge cases. This is daily reality.

And it hasn't changed in decades — even as programs have grown more complex.

Two questions started forming:

Why hasn't anyone built something that keeps up with program management?
What if the person who builds it should be someone who's actually lived it?

That's what I'm building at TelosFlow.

Not another tracking tool. Something built from the inside out — by someone who knows what this work actually demands.

Everything we build will be measured by whether it makes work better. Not easier — better.

What's Next

We're building. When we have something worth showing, we'll show it.

If you're in aerospace and the gap I've described resonates with your experience, I'd love to hear from you. Not a sales conversation — a real one.

Because that's how trust starts. One conversation at a time.