Building Products People Love
What I've learned about product development from co-founding two startups and building platforms used by thousands.
It Starts with a Real Problem
The best products I've built didn't start with a brilliant idea. They started with a real person, facing a real problem, wishing something better existed.
When we built SenangPrint, it wasn't because we had a grand vision for the future of printing. It was because Kelvin's customers were calling him on WhatsApp, sending specs in voice notes, and tracking orders on spreadsheets. The product practically designed itself — we just had to listen.
Build Less, Learn More
Early on, I made the classic mistake of over-building. I'd spend weeks perfecting a feature, only to discover that users didn't care about it at all. With Artmeet, we learned to ship fast and iterate.
Our design competition feature? Started as a simple form. Users loved it, so we added judging systems, discussion boards, and scoring rubrics — but only after we knew people wanted it.
The Intersection That Matters
My strength has always been at the intersection of engineering and product thinking. Understanding both sides means I can:
- Translate ambiguity — Turn vague business needs into concrete technical plans
- Make trade-offs — Know when "good enough" ships faster than "perfect"
- Stay user-focused — Never lose sight of who we're building for, even deep in architecture
Metrics That Matter
After years of building, I've learned to focus on the metrics that actually indicate value:
- Are users coming back?
- Are they completing the core action?
- Are they telling others about it?
Everything else is vanity.
What's Next
I'm still chasing the same feeling I had when I saw our first Artmeet user land a design job through the platform. That moment when technology creates real value for real people — that's why I build.