Technical consulting & advisory
I take on short, clearly bounded engagements where a founder, investor, board, or engineering leader needs an experienced systems view quickly. The goal is to diagnose, decide, de-risk, architect, or recover—and leave behind an executable path that the organization can continue to use.
If there is a fit, I propose a defined scope, explicit outputs, timeframe, and fee before work starts. Most engagements are designed to conclude with a decision, architecture, evidence plan, or recovery path—not an indefinite retainer.
Where I am useful
I am most useful where product intent, systems engineering, hardware, software, sensing, mechanics, manufacturing, regulation, suppliers, evidence, and organization are interacting—and the real failure is hiding between disciplines.
For a program that is slipping, failing integration, accumulating technical debt, or producing activity without decision-quality evidence.
For an ambitious concept that needs to become an executable technical system rather than a collection of promising subsystems.
For investors, founders, boards, or acquirers who need an independent technical read before committing money, time, or reputation.
For a prototype that works once, but may not yet be a repeatable, supportable, certifiable, manufacturable product.
For a negotiation, proposal, supplier discussion, or senior technical decision where you need experienced technical judgment on your side of the table.
Engagement shapes
The right format depends on the decision. I prefer the shortest engagement that can produce a defensible result.
Review the available material, pressure-test assumptions, talk through the system, and leave with a decision, missing-evidence list, or next-step memo.
A concentrated engagement producing a system view, risk register, verification path, and an executable recovery or realization plan.
For a bounded period when architecture, integration, vendors, engineering decisions, or a critical program need senior ownership before the permanent structure is in place.
About short transition work: I can step in temporarily as a hands-on systems or technical leader when that is the fastest way to stabilize a critical program. It remains explicitly scoped, with a defined purpose, authority, handoff, and endpoint.
What you get
I work from evidence toward decisions. Depending on scope, the output is a useful engineering artifact—not a generic slide deck—and should be usable by the people who continue the work.
Client perspective
“He has the kind of depth across disciplines that actually ships systems. When the problem is hard and it matters, I'd work with him again without hesitation.”Gennadiy Goldenshteyn ↗ · Managing Partner, First Principles, LLC · Founder & Managing Partner, Dinemic Ventures
Good fit
How we start
Use the calendar for a direct conversation, or email a short brief first if the context is sensitive or technically dense.
What is the system, what is stuck, what has already been tried, and what decision needs to become possible?
If I can help, I will propose a bounded scope, outputs, timing, and fee. If another specialist is the better answer, I will say so.
Book a conversation directly. You do not need a polished brief—just enough context for us to identify the real decision and whether I can materially improve it.