Technical consulting
An experienced second opinion on architecture, technology choices, estimates, and vendors — before the decision gets expensive.
Questions I help answer
- Should we build this, buy it, or connect existing tools?
- Is this architecture right for where the product is going?
- Is the estimate we were given realistic?
- Why is delivery slow, and what would actually speed it up?
- Where could AI help in our business, and where would it be a waste?
Formats
- A single session — one to two hours on a specific question, with written notes afterwards.
- A review — I read the code, the architecture, or a vendor proposal and give you a short report: what is sound, what is risky, what to do first.
- Ongoing advice — a few hours a month as a technical counterpart for a founder or a team without a senior engineer.
What to expect
Plain language, a clear recommendation, and the reasoning behind it. If the honest answer is "do not build this", that is the answer you will get.