Hi, I am Ryon.
An entrepreneur, developer, product builder and strategist, and the founder of Sitepact Group.
I've always been drawn to figuring out how things work, and more usefully, how they could work better.
That turned into businesses, software products, and a habit of building things myself rather than waiting for somebody else to make them.
I sit somewhere between business and engineering.
I've never been interested in choosing between being technical and being business-minded. The interesting work happens when you understand both.
I can spend half a day on positioning, pricing or unit economics, and the other half inside APIs, databases, payment flows or server configuration.
I don't see technology as separate from the business. Usually it's the strategy.
Constraints are where the opportunities are.
Building outside the largest markets comes with a particular set of constraints. Infrastructure, banking, payments, logistics and access to global platforms are rarely as straightforward as the documentation assumes.
I've learned to read those constraints as signals rather than obstacles. A process that is unnecessarily hard usually means nobody has built the thing that would make it easy.
Difficult problems create room for useful companies.
The products I build now are designed for a global market from the first line of code, rather than for one region with expansion bolted on later.
How I work.
Straightforward, and it has not changed much.
Understand the problem deeply.
Build the simplest version that solves it.
Put it in front of real people.
Learn what breaks.
Improve it.
I'm comfortable in the detail. That might be writing code, configuring infrastructure, designing an operational process, working out why a payment failed, or deciding the business model was wrong.
I care far more about whether something works than whether the work fits a job description.
What I'm building.
This list keeps changing. Curiosity tends to do that.
Beyond the polished version.
A personal site turns into a list of accomplishments with the mess removed very easily. I'd rather this one didn't.
The Journal and the Lab carry the actual process. Experiments, technical problems, things I'm still learning, and fixes that took far longer than they should have.
The process is usually more interesting than the finished product.