I’ve spent my career operating in environments where the system didn’t exist yet.

Everything I’ve done has been deliberate preparation for operating in complex, real-world systems.

I’ve consistently paired structured learning with direct application:

Formal education (MBA) to build financial and strategic foundations
Self-directed study across business, psychology, and systems thinking
Hands-on technical upskilling across software, AI workflows, and system design
Real-world execution through operating roles and consulting engagements

Not as separate tracks, but as a single loop:

Learn → Apply → Break → Rebuild → Scale

That loop has played out across every stage of my career:

Building and running systems inside operating businesses
Designing and implementing them as a consultant
and now, translating them into AI-enabled products

The goal has never been knowledge accumulation. It’s been capability:

To enter complex environments, understand how they actually work, and build systems that improve how decisions get made.

Across industries: HVAC, logistics, distribution, eCommerce, and now AI, the pattern has been the same:
- Enter ambiguous, unstructured environments
- Identify where decisions break down
- Design systems that align data, operations, and execution
- Translate complexity into something teams can actually use
That pattern has scaled from:
Individual trades work → to multi-state operations → to global supply chains → to AI-enabled systems
I actively invest in expanding both business and technical capability, with a focus on areas that directly impact system design:
- AI system design and retrieval-based architectures
- Workflow and automation design across business systems
- Product thinking applied to operational environments
This work is applied directly through:
- Pendel.ai (AI diagnostic system in development)
- Active consulting engagements
- Internal system builds across prior operating roles
That progression led naturally to where I am now.
Most organizations today have:
- More data than ever
- Increasing access to AI
- But no system for turning either into decisions
The gap isn’t technology.
It’s translation.
- Business understands the problem
- Engineering understands the tools
- But the connection between the two is missing
That’s the layer I operate in.
Today, I focus on:
- Designing AI-enabled decision systems
- Translating business problems into technical architectures
- Building Pendel.ai, a platform that turns fragmented operational data into structured, decision-grade outputs
I’m actively deepening my technical understanding of:
- AI system architecture
- Retrieval and context systems
- Performance, cost, and scalability tradeoffs
Not to become a pure engineer but to become more precise in designing systems that actually work in production environments.