About

Orion Leap was built from experience most consultants don’t have — and most companies need.

The Short Version

I spent twenty years inside technology organizations — from helpdesk to senior leadership, from frontend code to board-level strategy. I ran technology for a small manufacturing company where no budget existed for “innovation,” but the systems had to work anyway. I built teams across three continents, managed crisis responses, and learned what it actually costs when technology strategy and business strategy aren’t speaking the same language.

Orion Leap is the consulting practice that grew out of those years. It exists for one reason: small and mid-size businesses deserve access to senior technology leadership, not just vendors selling them the next thing.

The Longer Version

I started where most technology careers start: helpdesk tickets, graphic design requests, HTML that needed to work yesterday, and printers that still won’t cooperate. Over twenty years, I worked through frontend and backend development, systems and network administration, software QA, cybersecurity incident response, project management, vendor management, and digital marketing — every layer of what a technology organization actually does.

The second decade brought senior leadership — the small-business version where “senior leadership” and “senior individual contributor” are the same person depending on the time of day. I built teams across the US, Turkey, and Bulgaria. I managed budgets where the margin for error was zero. I learned what actually works when the agency recommendations don’t fit the reality of a limited budget.

That experience — being inside both the technology and the business decisions — is what Orion Leap is built on. Not theory. Not templates. Twenty years of finding answers that work within real constraints.

I’m currently an MBA candidate at LSU Shreveport, AACSB-accredited, focused on accounting and financial analysis. I bring that lens to every engagement — because technology spending isn’t a technical problem. It’s a financial one.


How I Think — and How Orion Leap Works
Start with the model. Before any recommendation, I need to understand the structure — the mechanism that drives the numbers. Not what the dashboard says, but why. This means mapping real architecture, real spend, real dependencies — not assuming based on org charts.
Prefer artifacts over opinions. Every engagement produces something tangible: a spend model, a comparison framework, a roadmap with cost implications. Vague guidance isn’t useful. You should see the logic behind every recommendation and be able to use it after the engagement ends.
Optimize for clarity. If a technology problem can’t be explained in language a non-technical decision-maker can act on, it’s not understood well enough yet. I translate complexity into choices.
Learn by building. I prototype before committing. Small simulations, comparative analyses, proof-of-concept work — because the fastest way to find the right answer is to test it, not debate it.

This framework applies whether I’m optimizing a cloud bill, recovering from an incident, or planning next year’s technology roadmap.


A Note on Perspective

Most technology consultants learned their trade inside large organizations with large budgets. I didn’t.

The most valuable lessons I learned came from years of delivering enterprise-grade outcomes with a small team, a finite budget, and no room for failure. When the agency pitch doesn’t fit your reality, you need someone who’s been on your side of the table. That’s the perspective Orion Leap brings to every engagement.

See How I Work

See how this applies to your situation.

If you recognize your business in any of this, let’s have a conversation.

Let’s Talk