Builder, photographer, author.

My story

Most businesses don’t have a technology problem. They have a process that grew by accident: a spreadsheet here, an email thread there, a critical step that lives in one person’s head. I got into software because I couldn’t stop noticing this, and because I learned early that the fix is rarely more software. It’s the right software, built around the way the work already happens.

That’s what I make: custom tools shaped to a business, instead of a business bent to fit a product designed for everyone. Most clients arrive knowing exactly what hurts and nothing about what the solution should look like, and that’s where I like to start. I watch how the work gets done, cut what doesn’t need to exist, and build what’s left until people reach for it without thinking. Take AlirKonek, for example: it brings many everyday functions into one application.

Photography and writing taught me the rest. Photography trained my eye to decide what belongs in the frame and what gets left out. Writing taught me that an idea you can’t explain simply isn’t finished. Both shape every screen and workflow I design.

What I’m after is software that disappears into the work. The people using it shouldn’t have to learn it, think about it, or work around it. They should get their time and attention back, and spend it on what they’re good at.