My hackathon journey didn't start with winning.
It started with losing.
My first hackathon was BlueHacks 2025. We spent almost all of our time building and very little time understanding the business side of our project. When it came time to pitch, we struggled to explain why our solution mattered. That experience taught me an important lesson:
A great product means nothing if people don't understand its value.
Next came GCash's invite-only hackathon.
We didn't win, but I walked away with something more valuable than a trophy. I learned more about product thinking, working with data, and met someone named Neo, who would later become a key part of my hackathon journey.
Then came the YSES Hackathon.
Once again, we fell short.
We believed we had built a strong solution, but we made the same mistake. We focused too much on the technology and too little on market validation, business models, and the value our product created.
Everything changed during Based Space Batch 002.
It was
Discussion
Leave the first comment
Be the first to leave a mark on this discussion.