In December 2025 my team built STROT, a system-driven platform aimed at tackling generational poverty through what we called "BAL. BUDDHI. VIDYA." We didn't win the hackathon. We walked out with something more useful: a specific, painful lesson about pitching.
The problem wasn't the system
We had a product, a story and a vision. What we didn't have was a way to explain a system that takes hours to understand in the two minutes the stage gave us. Judges scored the pitch they heard, not the system we'd actually built — and they were right to.
Three lessons I still use
- Clarity matters more than depth. A judge who doesn't understand the core loop in thirty seconds won't score the rest of the pitch fairly, no matter how good it is.
- Storytelling matters as much as systems. The most technically impressive project I've built is not automatically the one that communicates best under a countdown timer.
- Every stage builds you for the next one. The pitch skills from Product Genesis and BYTEBATTLE didn't transfer perfectly to a two-minute format, and that gap was worth learning before it cost me something bigger.
We didn't take the trophy, but we took the product forward — because an idea like STROT deserves more than a scoreboard.