About Thomas Advisory
I've seen what breaks companies. Usually before they do.
Not because I'm clairvoyant. Because I've been in the room when it happened, and I've spent the better part of two decades learning to read the signals most founders don't know to look for.
I started my career in the U.S. Air Force working in wireless communications and satellite ground stations. Systems where failure isn't an option and "we'll fix it later" isn't a philosophy. That environment shaped how I think about reliability, process, and what it actually means to build something that holds under pressure.
From there I spent years working across some of the most demanding technical environments in software: Atlassian, where engineering standards are a competitive advantage. Best Egg, where financial infrastructure has to be right the first time. Net Health, navigating the complexity of healthcare compliance. Clear Measure, advising CTOs and founders directly on the decisions that determine whether their technology accelerates the business or holds it back. And Grover Gaming, where I contributed to the technical foundation that supported a $1.05 billion exit.
That breadth is not accidental. Every engagement taught me something different about where systems break, where teams break, and where founders get blindsided by decisions they didn't know they were making.
What that career arc gave me isn't just a list of companies. It's perspective on how decisions age.
Think of technical debt as a business loan. You take it out deliberately, borrowing against your future engineering capacity to move faster now. That's not reckless, it's rational. Every company does it. The question isn't whether to take on the debt. It's whether you know what you owe, and whether you're paying attention to the interest rate.
Because unlike a bank loan, technical debt doesn't send you a statement. The bill shows up when you need to move fast and can't. When a competitor pivots and your architecture won't let you follow. When you need to change your business model and pricing structure but can’t capture the metrics to charge customers. When a customer asks for something reasonable and your team says it'll take six months. When the engineering team you hired to accelerate growth is spending most of its time dealing with emergencies. That's the moment founders realize the debt was larger than they thought, and the interest has been compounding.
I've seen that moment coming from a long way off. I've been inside enterprises tracing their current constraints back to decisions made when the company was a fraction of its current size. I know what today's compromises look like three years from now, at every stage from early startup through scale-up to mature enterprise. That's not something you learn from a playbook. It's something you learn from being in the room when it happens, more than once, across more than one kind of company.
The through line across all of it is the same: I've been close enough to the decisions that matter to know which ones actually matter. And I've watched enough companies stumble over the same avoidable mistakes to stop being surprised by them.
What I actually do
I work with post-funding B2B SaaS founders who know something is wrong but can't name it yet, or who are about to make a technical decision with consequences they can't fully see. I'm not here to write code or manage sprints. I'm here to be the person in the room who has already seen the outcomes of the choices you're about to make and can help you avoid the expensive ones.
That looks different depending on where you are. Sometimes it's a board advisory relationship, a structured monthly engagement where I stay close to your decisions and flag what I'm seeing. Sometimes it's fractional CTO work where I step in with more hands-on technical leadership while you focus on sales or implementation. Sometimes it starts with a single conversation about a single decision.
What stays consistent is the approach. I ask the questions nobody else is asking. I tell you what I see, not what you want to hear. And I stay in my lane, strategy and leadership, not execution and implementation.
If something here resonated, that's not an accident. Let’s talk about it. Turn engineering from a bottleneck into a catalyst.
