I have been building systems people actually use since fifth grade, when my friends and I rigged a camcorder to hold perfectly still so things could appear and disappear in our school movies. The assignment ended. The rig didn't. We kept making movies with it for years, and I kept building things.
By 2010 I was building an iPad sign-in and intake system for a physical therapy clinic, before front-desk tablets were a thing anyone had. On paper it saved them twelve thousand dollars a year in printing. In practice it saved them nothing, because one employee kept printing every form back out and scanning it into her Dropbox. I could have written that off as her failure. It wasn't. It was mine.
Software does not fail on servers. It fails at the front desk.
I have built everything since for the person actually standing at it.
Then I went inside a PE backed operating platform and got to solve the same problem many different ways, at scale, for years. I built the program, built the team, built the tech stack that carried the company through its holding period. My first day there opened with a malware attack. Ten days later the whole business was standing again; it never fully went down. I learned what I actually believe in those years: that companies waste money on inefficiencies they keep because they have always done it that way, and starve the one thing that was keeping them alive, which is culture. You can over-engineer every process in a building and still kill its spirit. The dying is the optional part.
So when Megan showed me what she was building, I did not need a deck. The output speaks. You cannot pick up a rock around this tool without finding a return under it. I came to put real bones under something I believe in, with someone whose passion I trust. My first question when she brings me a wild idea is always the same: what part can I play in this chaos?

