PipeTrace
A production system built around shared tablets, moving work, and unreliable connectivity on a pipe shop floor.
My roleProduct engineering
Available for select product collaborations
Product engineer · Software + hardware
I build the digital layer for the physical world.
I turn complicated operations into useful products—connecting the software, hardware, and real-world workflow instead of treating them like separate problems.
No buzzword fog. No made-up results. Just thoughtful systems and clear evidence of what is working now.
System study / 01Customer intent → physical production
Lead system / PATCH22 + PatchSight MK2
One customization problem. Two sides of the work.
PATCH22 helps the customer make a clear product. PatchSight explores what happens when that physical patch reaches production. I’m building the handoff between the two.
01 / Customization + commercePATCH22
A guided product designer that turns a customer’s idea into structured, order-ready patch decisions.
Read the case study 02 / Computer vision + manufacturing automationPatchSight MK2An operator-reviewed vision workflow that turns an embroidered contour into calibrated, laser-ready geometry.
Read the case studySelected work
Different surfaces. The same kind of problem.
I do my best work when the interface, the operation, and the physical constraint all have to make sense together.
Harold Robotics
A small companion-robot platform built from the display and firmware outward, with privacy and physical verification kept honest.
My roleProduct and embedded engineering
What I bring
One builder, fewer handoffs.
Product systems
I map the people, equipment, decisions, and failure points before deciding what the product should be.
Software + interfaces
I build the application, data model, and operator experience as one connected system.
Hardware + field integration
I work through the seam between code and the physical environment where the product has to hold up.
How I work
Observe.
Model.
Build.
Prove.
I’m not interested in making the process sound mysterious. I get close to the work, find the hard seam, build it, and pay attention to what the evidence says.
- 01
Observe
Get close to the work.
In PipeTrace, that means starting at the station tablet and the next job—not an office dashboard. - 02
Model
Make the whole system visible.
PATCH22 separates customer choices, product data, and the production handoff so the order stays understandable. - 03
Build
Put the riskiest seam on the bench.
PatchSight tests the exact point where camera pixels have to become calibrated, reviewable geometry. - 04
Prove
Record what actually happened.
Harold keeps compiled firmware, flashed hardware, and observed physical behavior as different evidence levels.
About
Oh, hi Mark.
I’m a product engineer with a bias toward the physical.
I’m most useful when a problem crosses disciplines—when the software, equipment, operator workflow, and business process all need to make sense together.
I like manufacturing systems, robotics, custom products, and the practical tools that help people do better work.
🍕Have a hard, physical-world problem?
Bring me the difficult part.
Tell me what you are trying to build, move, measure, or improve. The email starts with the useful questions so we can get to the point.
Start a conversation