I don't just sell infrastructure.
I run the system that wins it.
Twenty years in federal and defense taught me that the deal is never decided by the datasheet. It's decided by the conversations, the quote, the relationships — and, increasingly, by who wields AI with the most discipline. This is how I operate.
Tools that catch what humans forget.
I build the tooling I wish I'd had. This Data Center Network Designer turns a customer's requirements into a complete, validated design — and surfaces the options engineers routinely miss under deadline pressure: breakout cabling, multi-pod scaling, oversubscription tiers, rack and power layout. Fewer surprises at build time. More trust at quote time.
Why it wins deals: the design that accounts for the breakout cable and the second pod on day one is the design that survives the customer's architecture review — and the competitor's teardown.
I don't sell products. I run conversations.
The smartest person in the room rarely wins it. The most trusted one does. Every motion below is something I run deliberately, not by instinct.
Builders who trust what they can see running.
Leaders who buy the narrative and the roadmap.
Teams who only believe their own keyboard.
The deal lives or dies here. Earn it, or route around it.
Arm them. They sell when I'm not in the room.
Acknowledge, don't overspend energy. Watch for escalation.
Intel and reach. They tell me what's really happening.
The BOM is where trust is won or lost.
Better SKU choices keep a quote competitive and build trust at the same time. I treat the bill of materials as an engineering problem: same outcome, fewer wasted dollars, no features the mission doesn't need.
Same capacity. Fewer modules, lower cost, room to grow — if the workload profile allows it.
Dropping an expensive feature the customer will never enable keeps the quote sharp and honest.
Everyone can use AI. The edge is how you orchestrate it.
A single chat window is table stakes. What I actually run is a self-hosted orchestration platform: one orchestrator that plans the work and routes each task across a five-tier model fleet — flat-rate cloud, local on-device, free vision, and two gated pay-per-call tiers — grounded by retrieval over my own notes and gated by human approval on anything metered. Privacy, cost control, and resilience by design.
Cool at the top, hot at the bottom — orchestration logic down to the silicon that burns the watts.
Engineers become PM/PO
The job shifts from writing every line to specifying intent, reviewing output, and owning the outcome.
Token cost is the moat
Two engineers reach the same result; the one who got there for a fraction of the tokens stays competitive.
Guard against bloat
Code bloat saturates context and quality collapses. I monitor for it and keep the agent honest.
Security & MCP validation
In cleared environments, validating every tool and MCP server an agent can reach is part of the job, not an afterthought.
Proof, not theory.
These designs were produced by augmenting my own work with Claude Code — the same artifacts that used to take days, iterated in minutes and handed off build-ready.