Put AI to work on your hardware engineering, with checks that keep it honest
I use AI every day in my own engineering work, for design review, firmware and test tools, and documentation. Used well, it lets a small team move like a larger one. Used carelessly, it produces confident mistakes that end up in copper. I help teams get the first without the second.
What I do
Where you are now
A short review of how your team uses AI today and where it would save the most time.
AI-assisted design review
Schematic and layout review where AI flags issues and an engineer signs off, with a record of what was checked and what couldn't be.
Software and tools
AI coding tools such as Claude Code for firmware, test scripts and internal tools, with review rules your team can live with.
A pilot on one real board
The workflow proven on one design before it's rolled out, with the time saved measured.
Team training
Hands-on sessions built around your tools and your designs, not generic examples.
How it starts
-
1
A 20-minute call
You tell me what you're building and where you're stuck. No cost.
-
2
A small, fixed-scope start
One defined problem at a fixed fee, so you can judge the work before committing to more.
-
3
Build, with clear gates
Larger work runs in phases. You see progress at every gate and decide whether to continue.
Have a board in progress? A $4,500 design risk snapshot is a quick way to see AI-assisted review on your own design.
Questions founders ask
- Is our design data safe?
- We agree up front which tools may see your files. For sensitive work, I can set up a workflow that keeps design data on your own systems.
- Will AI replace our engineers?
- No. It speeds up the work around their judgment. Every workflow I set up keeps a named engineer signing off on anything that goes to fabrication.
- Where should a small team start?
- Usually with design review or test tooling, where the payoff is quick and the risk is low.
Start a conversation
Tell me what you're building. I reply within one business day.