I spent 25 years leading teams across military, education, freight, logistics, coaching, recruiting, and fulfillment operations. Now I help people build AI systems that hold up outside the demo.
I did not come up through the tech industry. I spent 25 years leading teams across military, education, freight, logistics, coaching, recruiting, and fulfillment operations.
One pattern kept showing up across every role: the organizations that win treat technology as infrastructure and data as a decision-making asset, not a reporting afterthought.
That observation pulled me into AI strategy, and it is why operators looking for an AI strategy consultant would rather hire a practitioner than a vendor.
The full background lives on the About page. The short version is this: I lead high-volume automated fulfillment operations, manage teams inside complex operational environments, and build my own local AI stack, agent workflows, RAG pipelines, and living wiki.
I do not stop at theory. I build systems that hold up when things get chaotic.
This is an early-stage practice built alongside my full-time operations role, graduate work, writing, and system-building. I am not trying to take every project. I am trying to find the right few.
This page is for people trying to figure out whether I can help them solve a specific problem.
Where I Can Help
Why Work With an AI Strategy Consultant
I help individuals, operators, and small teams think through what to build, how to make it work reliably, and what to avoid.
No hype. No vendor-shopping theater. No strategy deck that dies in implementation.
This is practical implementation grounded in systems I have personally built, run, broken, fixed, and maintained.
If you want to build AI capability without becoming dependent on a vendor, this is the kind of work an AI strategy consultant should be doing for you. The goal is not to look innovative. The goal is to make the work better.
“The goal is not to look innovative. The goal is to make the work better.”
Knowledge System Design
Most knowledge systems collect information. Good ones compound it.
I designed and built my living wiki from scratch using a multi-domain architecture, federated indexing, AI-assisted knowledge development, and human enrichment as the primary knowledge event.
That system is not just a place where I store notes. It is the context layer behind how I think, write, build, retrieve, connect ideas, and work with AI.
I can help you design a knowledge system that compounds over time instead of one that just collects and stalls. This is system design, not productivity tips.
RAG, Agents, and Workflow Architecture
There is a wide gap between an AI demo and an AI system that works reliably.
Most people only see the demo. They do not see the context problems, retrieval failures, brittle prompts, bad handoffs, missing review steps, cost creep, governance gaps, and workflow confusion underneath. That is where implementation starts.
I work with people who are past the novelty phase and are trying to build something more durable: retrieval systems, agent workflows, automations, and decision-support tools that fit the way they work. That means thinking through:
- What context the system needs
- Where that context lives
- How it gets retrieved
- How agents or workflows use it
- Where humans stay in the loop
- What failure looks like
- How the system is maintained
- What should never be automated
My own stack includes local AI infrastructure, agent workflows, RAG pipelines, automation tools, and a living knowledge system that I use every day.
For a deeper technical grounding in how retrieval-augmented generation works, Anthropic’s research on contextual retrieval is one of the better breakdowns available.
“I am not the person to sell you a magic box. I am the person to help you think through the system.”
Leadership and Organizational Advisory
Twenty-five years of leading teams across military, education, freight, logistics, recruiting, coaching, and fulfillment operations taught me one thing over and over: tools do not fix weak systems, technology does not replace trust, and change does not stick just because leadership announced it.
The lens is always the same: how do you build people and systems that hold up when conditions change?
I work with people carrying the responsibility of leading, not people looking for leadership theater.
I learned servant leadership from a mentor at Gap who asked questions that changed how I lead. He never told me the answers. He just kept asking until I found the right path. That is still how I think about developing people.
I learned to coach from kids who did not care about my title. You cannot manage a fourteen-year-old into running a sprint. You earn it or you do not. That lesson transfers further than most leadership books do.
I learned systems thinking from environments where failure had consequences. In the infantry, a bad decision does not stay on a slide deck. It lands on a person. That changes how you think about process design, redundancy, and what “good enough” actually means.
Speaking and Guest Contributions
I am available for podcasts, panels, interviews, and written contributions when the conversation is serious and the overlap is clear.
The conversations where I am most useful sit at the intersection of practical agentic AI, knowledge systems, AI governance, leadership, operations, and execution. I talk about what I have personally built, tested, used, and learned from, not what the industry says everyone should be excited about.
No canned keynotes. No trend-chasing. Conversations worth having.
Content Collaboration
If you are a creator, practitioner, or writer working at the intersection of AI, operations, PKM, knowledge systems, or leadership, we should talk when the overlap is clear.
I do not collaborate for reach. I collaborate when the work is better together.
Who I Work Best With
I work best with leaders, operators, builders, creators, and practitioners who are trying to solve specific problems.
That usually means people who are tired of generic advice, allergic to hype, and serious about building systems that hold up outside the demo. If you are looking for an AI strategy consultant, I work well with people who value directness over diplomacy, substance over style, and execution over theater.
The best fit is usually someone who says:
“I know AI matters, but I do not want to chase tools.”
Or: “We have knowledge everywhere, but no usable system.”
Or: “We are trying to use AI, but the workflow breaks down once people touch it.”
Or: “I need someone who understands both the technology and the operational environment.”
If you have a specific problem, a serious commitment to solving it, and a budget that matches the importance of the work, we will probably get along fine.
Who I Do Not Work With
If you want a consultant who tells you what you already believe, I am not your guy.
If you need a slide deck more than you need a solution, look elsewhere.
If you are shopping for a vendor and want someone to validate a decision you already made, I will say so directly.
If you want to talk about AI but have no interest in changing the way work gets done, I am not the right fit.
I am not selling bloated packages, vague advisory relationships, or open-ended engagements where the incentive is to stretch the work instead of solving the problem.
This is not rudeness. It is a filter. The right people appreciate it.
“This is not rudeness. It is a filter. The right people appreciate it.”
What It Looks Like
We start with a conversation. Not a discovery call built around a sales framework.
A direct conversation about what you are trying to do, what has not worked, what constraints matter, and what success actually looks like.
If it is a fit, I will tell you. If it is not, I will tell you that too. When possible, I will point you toward a better path.
Projects are scoped when we agree to work together. We define the problem, the deliverable, the timeline, and the end state.
I do not bill by the hour to think out loud. I build, advise, teach, and leave you with something that works after I am gone.
“If it is a fit, I will tell you. If it is not, I will tell you that too.”
Before You Reach Out
The best messages are specific.
Tell me what you are working on. Tell me what is not working. Tell me what you have already tried. Tell me whether you are ready to build, trying to make a decision, or still figuring out the shape of the problem.
You do not need to have the whole answer. But the problem should be specific enough to discuss.
Let’s Talk
I read every message myself. I respond when the problem is clear, serious, and specific. Either way, you get a direct answer.