I design and build software for industries still stuck on spreadsheets.

Junctions

• Systems thinkingIn freight, almost nothing happens in isolation. An expired registration, a weigh station pull-in and a toll bill can all trace back to the same truck. So before I design a screen, I map how the pieces connect and find what everything hangs off of. At Fleetworthy, that was the vehicle. Unifying four products around it meant one record, one set of permissions, and one place to see what needed attention, while each product kept its own backend.Fleetworthy
• Initiative & ownershipI like early, ambiguous problems where nobody has told me what to build yet. I use the latest tools to get from idea to working code fast, and I know when to move fast and when to slow down. I solo-built an entire native mobile application, Diezl, that currently helps over 400 owner operators make better decisions.Fleetworthy · Diezl · Trochi
• Love the ProblemSolutions, no matter how elegant, fall flat when they solve the wrong problem. That's why I dive into understanding how people actually work before deciding what to build. At Triumph, six 90-minute sessions shadowing support agents showed they were jumping between customer profiles just to find basic information. We built one search that pulled it all together, and chat handle time dropped 49%.Fleetworthy · Triumph Financial · Diezl
• Sweating the detailsI care a lot about craft, especially in enterprise tools where people stare at dense data all day. A screen can be beautiful but difficult to parse, and getting that balance right is most of the work. In Trochi, every surface leads with a plain-language takeaway and the number a broker actually needs, the rate, is always the biggest thing on the screen.Triumph Financial · Fleetworthy · Diezl · Trochi