I like taking things
from zero to working.
I'm the person who'd rather build the thing than argue about it in a doc.
I came up as an engineer, but I was always more interested in why we were building something than which framework we used. Three years at TelioLabs pulled me toward the customer side of the table, sitting in on their problems, shaping what got built. Now I'm at Masters' Union adding the strategy layer, because I want to own that decision, not just execute it.
Who’s asking?
I've owned initiatives end to end at TelioLabs across three concurrent workstreams, turning ambiguous problems into structured outcomes, driving ~35% efficiency gains, and shipping features used by 30+ enterprise clients. Built for a Founder's Office: sharp strategy, cross-functional delivery, and a stakeholder cadence you don't have to chase. I close the gap between "someone should build this" and "it's live."
Highlights
How I think
Skills, with receipts
Named exactly as they appear on the resume and LinkedIn — not paraphrased.
Lighter, faster, weirder
See all experiments →Built, sold, and organized between classes
See all MU Unscripted →Off the clock
Trekking, bungee jumping, parasailing, and snorkeling — chasing a different kind of adrenaline off the clock.











