Key takeaways
- Every win came from a smaller problem than the teams we beat, executed completely. The loss came from building more and explaining less.
- Serve the user other teams skip: farmers who cannot type, small shops with no marketing budget, food that goes to waste at midnight.
- The demo path is the product. Freeze code early, seed the data, rehearse on the presenting laptop.
- Three people with three roles was the shape of every winning team.
- A win is a story you tell for years; a loss is a lesson you use for years. Collect both.
What did winning three hackathons actually teach?
That the prize goes to the team that solves a small problem completely and shows it working, not to the team with the biggest idea. Changethon 2025 at IIT Roorkee, Product Genesis at Vividhotsava 2025 at CSJMU Kanpur, and BYTEBATTLE by MeetKats were three different rooms, three different problems and three first prizes with the same shape: a named user, one flow demonstrated end to end, a rehearsed pitch, a team of three. The fourth room, STROT, taught the same lesson from the other side.
Also asked as: hackathon experience · what i learned from hackathons · hackathon lessons learned · hackathon success story · hackathon winner story · hackathon journey student · lessons from winning a hackathon · hackathon reflections
These stories exist in longer form on the portfolio, one per event [1][2][3][4]. This page is the version I tell when a college club asks what actually mattered, with the highlight reel removed.
I have won with less code than the teams I beat, and lost with more. The code was never the variable. Pranjul Rathour
Changethon 2025, IIT Roorkee: KrishGyan
The problem statement was social impact; the audience we chose was farmers who do not read or type. KrishGyan let a farmer send a voice note on WhatsApp in their own language and get spoken advice back on pests, crop health and weather, drawing on AI-powered agricultural data. It won first prize at the National Social Summit's hackathon because the demo was a voice note in and a voice note out, which any judge could follow, and because nobody else in the room had designed for a user who cannot read [1].
Also asked as: changethon iit roorkee · national social summit hackathon · krishgyan · krishi gyan ai · farming advice ai whatsapp · voice first ai for farmers · iit roorkee hackathon winner · agritech hackathon project
The lesson: find the constraint the other teams will ignore, and design for it. The constraint was literacy and it decided the architecture, voice on WhatsApp, before we wrote a line.
Product Genesis, Vividhotsava 2025, CSJMU Kanpur: BrandHive
A product-building competition rather than a pure code sprint. BrandHive was a platform for small businesses and emerging influencers to grow their organic presence without a marketing budget, bringing three components together in one loop. It won because we showed the whole loop live rather than a slide listing features, and because we pitched to the shopkeeper in the room, not to the judges [2].
Also asked as: product genesis csjmu · vividhotsava 2025 · brandhive · csjmu kanpur hackathon · product building competition college · kanpur hackathon winner · small business marketing platform student project
The lesson: judges cannot score a feature list. They can score a loop they watched close. Every pitch since has been built around one complete loop.
BYTEBATTLE, MeetKats: Annapurna
Surplus food coordination: hotels and events with leftover meals, NGOs that distribute, volunteers who carry, and a verification layer so impact is real. Four roles, one flow. Annapurna won first prize because a judge could watch one meal move from a kitchen to a shelter through four clear hands, and because roles made the demo legible. It later became a tool people actually used, and its code is public [3][6][7].
Also asked as: bytebattle meetkats · annapurna hackathon · food donation platform hackathon · surplus food app · ngo coordination platform · hackathon project to real product · meetkats hackathon winner
The lesson: clear roles win twice, once in the demo, where each role is a step a judge can follow, and once afterwards, when the same roles become the product's structure. The story of turning it into a real tool is separate [6].
STROT: the one we did not win
We built more than any team in the room and explained less. The demo depended on a live API call over venue Wi-Fi, and it failed in front of the judges. The team that won had a simpler product, a seeded demo that ran without a network, and a pitch rehearsed to the second. They deserved it. I have quoted that loss in more talks than any of the wins, because it is where the rules on this page come from [4][8].
Also asked as: strot hackathon · losing a hackathon · hackathon loss lessons · what to do after losing a hackathon · hackathon failure story · demo failed at hackathon · how to handle losing a competition
I also placed top three at a hackathon at IIT Kanpur, and there are other rooms where we did not win first that taught smaller versions of the same lessons [5].
What do the wins have in common?
A named user with a real friction. One flow demonstrated end to end, in under three minutes. A constraint honoured that others ignored: literacy, budget, timing. A team of three with three roles: builder, interface and data, pitch and problem. Scope cut early, so the last hours went to rehearsal. None of these is about talent, and all of them are decisions a first-year can make at hour one.
Also asked as: how to win hackathons consistently · what winning hackathon teams have in common · hackathon winning formula · hackathon strategy that works · secrets of winning hackathons · hackathon tips from winners
What did the loss teach that the wins could not?
How to lose usefully. Congratulate the winners specifically, ask the judges one question about what would have changed the score, write the answer down, and use it at the next event. Post about the loss the same week; students remember honest posts longer than trophy posts. The loss also taught the operational rules I now hand every team I mentor: seed the data, freeze early, rehearse on the presenting machine, keep a backup video. None of the wins would have taught those, because nothing had gone wrong.
Also asked as: how to lose a hackathon gracefully · learning from failure hackathon · hackathon feedback from judges · growth mindset hackathon · what losing teaches · dealing with failure as a student
How did hackathons change what I build and how I judge?
Every production system I have shipped since carries the hackathon habits: name the user first, build the demo path end to end before features, cut scope, rehearse the release. As a judge, I score the demo I saw and the answers I heard, I brief panels on the four criteria that decided these rooms, and I give each team one specific sentence, because that is what I wished a judge had told us at STROT. As a mentor, the first thing I ask any team is what they will cut.
Also asked as: how hackathons shaped my career · hackathon to production engineer · from hackathon participant to judge · hackathon lessons for real projects · hackathon mindset in engineering · hackathon habits
What would I tell a team before their first hackathon?
Pick the user before the idea. Cut until the demo fits in three minutes. Decide roles tonight. Build the demo path first and the features never, if the path is not done. Freeze two hours before. Rehearse three times where you will present. Then, win or lose, write the story down the same week, because the story is what you keep. The four rooms above are mine; yours start with the next registration.
Also asked as: advice for first hackathon · first hackathon tips · what to expect at your first hackathon · hackathon advice for beginners · hackathon tips for students · hackathon preparation advice
Want these lessons for your team?
I run pre-hackathon sessions on scoping, demos and pitching, and I judge and mentor at college events and internal Smart India Hackathon rounds, free for student communities. Email pranjulrathour41@gmail.com or use pranjulrathour.scult.in/invite.
Sources
- Changethon 2025 at IIT Roorkee: KrishGyan, Pranjul Rathourpranjulrathour.scult.in
- Product Genesis at CSJMU Kanpur: BrandHive, Pranjul Rathourpranjulrathour.scult.in
- BYTEBATTLE by MeetKats: Annapurna, first prize, Pranjul Rathourpranjulrathour.scult.in
- STROT: the hackathon I did not win, Pranjul Rathourpranjulrathour.scult.in
- Three times I did not win first, Pranjul Rathourpranjulrathour.scult.in
- Annapurna: from hackathon to real tool, Pranjul Rathourpranjulrathour.scult.in
- Annapurna source codegithub.com
- Losing a hackathon gracefully, Pranjul Rathourpranjulrathour.scult.in
GenAI engineer and AI product builder with 2+ years shipping production-grade AI systems: RAG pipelines, fine-tuned LLMs, hybrid retrieval and multi-modal apps across vision, speech and OCR, architected end to end from ingestion to deployment. Leads engineering for SCULT INDIA's 14-member team, founded the 500+ member TechVerse Enclave community and has mentored 200+ students. Three hackathon first prizes: Changethon 2025 (IIT Roorkee), Product Genesis at Vividhotsava 2025 (CSJMU Kanpur) and BYTEBATTLE (MeetKats).
Open to GenAI roles, hackathon judging, mentorship sessions and guest talks at colleges. Email pranjulrathour41@gmail.com.
