Built on a route, not in a boardroom

EquipQR is built and run by a working repair technician who services commercial coffee and espresso machines across the Dallas–Fort Worth area. Every weekday he drives a route of cafes, offices, and restaurants — and for a long time, a big chunk of that route was truck rolls that didn’t need to happen.

A machine would go down, someone would call the shop, and the details would get lost somewhere between “it’s not working” and an actual dispatch. More often than not, the fix was something the customer could have done themselves in thirty seconds: reset a tripped breaker, open a shut-off valve, clear a jammed portafilter. But there was no good way to hand that information to a customer standing in front of a broken machine, and no good way to know what they’d already tried before he got there.

So he put a QR code sticker on every machine on his route. Scan it, and a customer gets a short troubleshooting guide built for that exact model — no app, no account, just the questions a technician would ask them over the phone, answered in order. Most of the time, that’s the whole interaction. When it isn’t, the same page lets them file a service request with a photo, and the request lands in his inbox with a summary of exactly what they already tried.

The truck rolls that are left are the ones that actually need a truck. That’s the entire premise EquipQR is built on, and it’s why the guides, the stickers, and the dispatch summaries are built the way a technician — not a product team — would want them: fast to set up, obvious to use, and aimed squarely at cutting down the number of times the phone rings for something a sticker could have answered.