In their words.

Billing, complaint management, and location-tracked field operations for an electricity distributor.

Our office people and our field crews basically lived in different worlds. Most of the information moved around because somebody typed it in somewhere. Before they built anything, they actually came out with our crews. They spent a day watching how people worked instead of assuming they already knew. When we rolled everything out, I kept waiting for complaints... but there really weren't many. People just carried on with their jobs. If you've ever introduced new software into a large field-operations company, you'll know that's pretty rare.

Cloud platform for remote patient data across a growing network of clinics.

Healthcare people don't hand over patient systems lightly. We questioned everything, and honestly, we should have. What I appreciated was that security wasn't treated like another document to tick off. It came up in every discussion. We've expanded the platform into more clinics since then, and the rollout was... quiet. Doctors kept seeing patients. Nurses kept working. Nobody noticed we'd changed systems, which sounds boring, but in healthcare that's exactly what success looks like.

Enterprise single sign-on and identity federation across dozens of applications.

Identity platforms are one of those things nobody notices until they stop working. We were replacing a system everyone had been complaining about for years, so I was expecting at least a few rough days. Instead, people logged in Monday morning and just... carried on. No flood of support tickets. No late-night calls. No emergency rollback. It wasn't the flashiest project I've worked on, but it was one of the most disciplined.

Inventory and shipment tracking across distributed warehouses.

There was a time when finding stock meant calling three different warehouses and hoping someone answered. Warehouses aren't neat places. Things happen. Shipments arrive late, people move pallets around, priorities change every hour. What surprised me was that the software handled that mess instead of expecting everything to be perfect. My team didn't have to change how they worked. The system adapted to them.

A zero-downtime ERP modernization and cutover.

I've been through enough ERP migrations to know they're usually stressful. They planned the entire cutover with us weeks in advance, and every step had a backup plan. I came into the office on Monday expecting a long day. Nothing happened. People logged in, finance started processing invoices, operations carried on... That's probably the most successful migration I've ever been involved in.

A marketplace and payments platform for first-time online sellers and buyers.

A lot of our sellers weren't particularly comfortable with technology, and many of our customers were ordering online for the first time. We spent a lot of time talking about trust rather than features. I remember one designer saying, 'If someone's nervous about clicking Buy, we've already lost them.' That mindset showed up in the product. People figured it out without us explaining much, and that's exactly what we wanted.