15+ years building software. Not managing it — actually building it. I've been the person on the other end of a panicked founder's message at midnight, three days before a launch. I've rescued SaaS products that other agencies left half-finished, rebuilt platforms that no-code tools couldn't handle anymore, and shipped products like Zapbook from broken prototype to live, paying customers. I started SociiLabs because founders deserve a technical partner who treats their product like it's their own — not a ticket in a queue. If you're talking to me, you're talking to the person who will actually be accountable for what we ship.

I'm the person who makes sure what we promise actually gets delivered. My job sits at the intersection of engineering and operations — making sure the right systems, processes, and people are in place so projects don't fall apart between the kickoff call and the launch. I work across the full stack and across the business, which means I see problems before they become your problem. When we say AI-native, that's not a marketing line. It's how we actually build — and my job is making sure it stays that way at every project we take on.

23 years in software is long enough to have seen every shortcut that looked smart at the time — and watched it fail two years later. My background is enterprise architecture, which means I think about systems at a level most development teams never reach. I've worked across PHP, modern full-stack, and more recently, production-grade generative AI — not experimenting with it, actually shipping it inside real products for real businesses. What I bring to SociiLabs is the kind of technical judgment that only comes from having built things at scale, watched them break, and fixed them. When we make an architectural decision on your project, it's not a guess. It's a call backed by two decades of knowing what holds and what doesn't.