Work with me
on your robots.
I take on a small number of FANUC projects each year — the kind where getting it right matters more than getting it cheap.
Twenty years of programming, commissioning and rescuing cells, applied directly to your problem. Remote or on-site, a week or a quarter.
New cells built right the first time — architecture, motion, DCS, homing and PLC integration. ROBOGUIDE first, floor second.
Cell not hitting cycle time? Intermittent faults nobody can pin down? I've untangled a lot of programs I didn't write.
Socket messaging, vision bridges, data tooling, custom HMIs, CRX plugins — the work TP can't do.
A second set of eyes before you ship, or a programming standard your whole team can actually follow.
On-site or remote workshops built around your cells and your standards — not generic courseware.
Ongoing access for architecture decisions and hard problems, without adding a headcount.
No surprises, no change orders.
Every engagement starts with a scoped, fixed-price proposal. You know what you're getting and what it costs before any work begins.
Thirty minutes on what you're building or what's broken. If I'm not the right fit, I'll tell you — and often point you somewhere better.
Deliverables, timeline, assumptions and a fixed price. Clients tell me the scope doc alone is worth the call.
Regular check-ins and working demos as we go. You're never wondering where things stand.
Documented, commented code written to a standard your team can extend after I'm gone. No black boxes.
You've probably already read my work.
I've written 60+ articles on FANUC programming, published Robot Whispering — read by engineers at 600+ companies — and built the tools a lot of shops use daily.
That's not a credential for its own sake. It means when we talk, you're talking to the person who'll actually do the work, and you already know how I think.
Tell me about your project.
A short email is plenty to start — what you're building, what's stuck, and when you need it.