I was eight years old the first time I typed a command into a Commodore 64 and watched it do exactly what I told it to. Later it was a 128. That moment never left me.
I didn’t come up through a computer science program. I came up through spreadsheets and databases in my first corporate job, teaching myself SQL, AWK, VB, VBA, JavaScript, and PL/SQL because the tools I needed didn’t exist yet, so I built them.
My first real integration project was with the USPS—automatically updating mailing lists when the National Change of Address system flagged undeliverable addresses. Nobody told me to build that. I noticed the problem and couldn’t leave it alone.
That’s basically been the whole career: notice the friction, build the fix, move to the next one.
Most of the friction inside companies isn’t people not working hard enough. It’s their systems refusing to talk to each other. Once you see that, you can’t unsee it. I started MindCloud as the answer: connect the systems so people can stop being the glue.
I don’t measure the impact only in revenue. I measure it in the people who got their lives back—the ones who used to spend every day babysitting broken workflows and chasing errors, and now don’t have to.
Building MindCloud wasn’t glamorous in year one. There was no team and, for a long stretch, no proof it would work—just a conviction that it should. Mentors who eventually believed in it waited for evidence first, not promise. That’s the right instinct: build with evidence, not ego. Earn the right to raise.
I run MindCloud on rhythm, not reaction. The founders who last aren’t the ones who feel less; they’re the ones who learn not to make big decisions while they’re feeling the most.
Today MindCloud is the connective layer for hundreds of companies that don’t want to dedicate their best people to maintaining the pipes between their own software. That’s the whole job: give people back the time and leverage broken systems were quietly taking from them.
Outside of that, I write and record music →