Consulting
Four ways to engage. Each starts with a fifteen-minute call, which is free and exists so we can both find out quickly whether this is a fit.
Engagements
Technical due diligence
An independent read on whether a technical premise holds, for an investor, a board, or an operator about to commit capital. I examine the architecture, the assumptions in the model, and the gap between what has been built and what has been claimed.
- You receive:
- a written assessment with the risks ranked and the ones I would not accept named explicitly.
- Typical duration:
- two to three weeks
- How it starts:
- a fifteen-minute call
Architecture review
For teams building at the intersection of physical systems and financial or data infrastructure, where the problems are usually at the boundaries rather than inside any one component. I work through the system with your engineers and return a position on what is structural and what is fixable.
- You receive:
- a review document and a sequenced remediation plan.
- Typical duration:
- two weeks
- How it starts:
- a fifteen-minute call
Fractional technology leadership
Ongoing. For companies that need someone accountable for technology decisions but not a full-time hire yet. Architecture, product direction, hiring input, and vendor decisions.
- You receive:
- a defined number of days per month and a named person who owns the outcome.
- Typical duration:
- six months minimum
- How it starts:
- a fifteen-minute call
Advisory
A standing relationship, low volume, for founders and teams who want a specific person to call when a decision is genuinely difficult.
- You receive:
- availability, and someone who has enough context to be useful without a briefing.
- Typical duration:
- ongoing, quarterly
- How it starts:
- a fifteen-minute call
Method
How I work
I take a position. If you want someone to lay out three options and let you choose, I'm the wrong person; you can get that anywhere. I will tell you what I would do and why, and I will tell you where I'm uncertain rather than smoothing it over.
Everything is written up. Verbal advice evaporates; a document can be argued with, which is the point.
Boundaries
What I decline
Work where the conclusion has already been decided and the engagement exists to document it. Projects with no named person accountable on your side. Anything requiring me to endorse a technical position I don't hold.
Financial systems engagements as standalone work, for the moment. I publish on the domain and I build the rails inside energy platforms; I'm not selling into banking.