Map Your Substrate.

This work is most useful for teams operating at the boundary where Web3 meets traditional infrastructure — and where the substrate underneath matters as much as the application on top.

— Founders building decentralized infrastructure (DePIN protocols, NTN/satellite networks, decentralized identity, decentralized energy)

— Operators bridging Web3 and traditional enterprise or telecoms

— Investors evaluating substrate-aware, DePIN, or Web3-infrastructure portfolios

If your work touches the boundary between physical infrastructure, decentralized protocols, and intelligent network coordination — that boundary is what I think about.

A one-time engagement that maps your current infrastructure, protocol stack, or strategic position against the substrate-aware framework. Identifies where substrate awareness is already implicit in your architecture, where it could be made explicit, and where multi-substrate operation creates strategic or commercial leverage. Deliverable: a written assessment and follow-up conversation.

Typical scope: 2–3 weeks.

A multi-month retainer engagement for organizations actively building or integrating decentralized infrastructure. Includes scheduled strategy calls, ad-hoc consultation, framework guidance, and review of internal documents (architecture, capability statements, pitch material, federal applications). Best fit when you have an active workstream that benefits from a regular outside perspective.

Typical scope: 3–6 months.

Keynotes, workshops, panel participation, or advisory board facilitation on substrate-aware networks, the DePIN operating stack, Web3-to-enterprise translation, or decentralized identity infrastructure. Available for organization-internal sessions or industry events.

Typical scope: One-off.

— Operating depth: I run live multi-protocol decentralized physical infrastructure in a rural deployment environment — Wingbits aircraft tracking, Geodnet RTK GPS, Starlink NTN connectivity. This means ground-truth understanding of how DePIN networks actually operate day-to-day, not just how they're described in white papers.

— Substrate-aware framework: I work from a framework for thinking about networks as compositions of substrates — physical, computational, network, identity, governance, memory — and the coordination problems that emerge when they have to operate together intelligently. The framework crosses Web3 and traditional infrastructure vocabularies and is designed for organizations operating in both worlds simultaneously.

— Cross-domain perspective: My focus spans telecommunications (NTN, AI-RAN, 5G/6G, satellite spectrum), Web3 (DePIN, DID, DAOs, vCons), and decentralized energy infrastructure. Most strategic operators specialize in one substrate; my work sits in the operating layer that bridges several.

The first conversation is no-cost and exploratory. Bring your questions, your current systems, and a sense of where you're heading. I'll bring honest observations about what I see, what I think might fit, and whether I'm the right person to help.

If we both think there's a fit, we'll scope from there.