about

I'm an M.S. Information Systems student at the University of Cincinnati, and I've figured out that I care more about the product than the code. I try to start from a real user and a real problem, build the thing, and then go figure out how to actually get it in front of people. A product nobody uses isn't worth much, no matter how well it's built.

I've built a real system around AI, not just a pile of prompts, and that's how I get to own the whole thing solo: finding the problem, building it, and getting it used. Five products solo so far (four live, one in App Review), and honestly I've learned something a little different from each one. I'm endlessly curious, and I'd rather be a beginner at something new than coast on what I already know. That's how I went from sales and consulting to shipping real products with real users in about a year.

how i build

I go from idea to shipped fast, but not by just prompting an AI and hoping. I've built a real system around it: subagents that check each other's work, loops that run on their own, a memory layer so context doesn't get lost between sessions, and routing that sends each task to the right model. That system is what lets me run the whole thing myself, like a team of one: finding a real problem, building it, and putting it in front of people to see if it actually lands.

Building the thing turned out to be the easy half. The part I care about more the longer I do this, and the part I'm honestly still figuring out, is who a product is really for and how it reaches them. With my earlier stuff I bolted that on at the end. Now I try to think about it a lot sooner, though I'm still learning as I go.

I don't just use AI tools, I build the machine around them. I've assembled 50+ custom Claude Code skills, MCP servers, subagents, and hooks into a system that runs my whole operation: research, content, code review, outbound, and deployment. A few favorites:

off the clock