What building HackInverse 1.0 taught me
The honest story of running HackInverse 1.0: dates moving, sponsors going quiet, losing a day to Mahalaya, and the decision not to cancel.
The best decision I made this season was to not cancel HackInverse 1.0. Building it taught me more than any class. Here is the honest story.
It almost didn't happen. The date moved three times, a festival took away our first day, and the sponsors went quiet. So why did I keep going?
Here is what nobody tells you about running your first hackathon: the plan will break. What matters is what you do next. When a festival takes a day from your two day hackathon, you run it anyway. Here is how.
The plan
HackInverse 1.0 was supposed to be big. A 24 hour, two day offline hackathon, 300+ participants, the flagship event of Magistics, our builder community in Kolkata. I wanted it to be the first thing people think of when they think of student hackathons in this city.
The hurdles
The dates kept moving. 29 August, then 12 September, then 10 October. Every slip cost us momentum and a bit of trust from people who had already blocked their calendars.
Sponsors didn't close. Sponsorship is slow. Deals take weeks, and we were running out of weeks. A few conversations that looked close fell through late. I kept working the list anyway.
Another hackathon landed a week before ours. Same city, same students, same sponsor pool, same attention. They had the safer name. We were the newer one.
The scale we promised was not the scale we could run. 2,703 people applied. 169 were approved. That gap tells the whole story of what we wanted versus what we could actually handle.
How a hackathon became a hackday
The decision came down to one date. Our 24 hour plan ran on 10 and 11 October. Mahalaya fell on the 10th. Day one was gone.
So the two day hackathon became a single day. A 12 hour window on 11 October, with 6 hours of hacking on site. Smaller, tighter, and a very different event from what we had pitched.
The call I'm proud of
At the worst point, cancelling was the easy option. Dates slipping, sponsors going quiet, another event pulling attention away from us.
I didn't do it. That is the decision I'm proudest of from this whole season.
I also couldn't have done it alone. Without my father, this event wouldn't exist. He backed it more than anyone, financially, and he did it without making me feel the weight of it. I'm grateful, and I won't forget it.
The team
Saptorsi led sponsorship, and to me he was the most reliable person on this team. He ran things alongside me, supported me through the whole event, and handled everything with me when it got heavy.
Samyamay led events. He was also part of the design team, and he worked next to me like a brother.
The whole core team, along with our judges and mentors, gave their time to make the day run.
Event day
It was not smooth. The venue needed cleaning before we could start. The auditorium and rooms needed rearranging. Small issues kept showing up, and we delayed a few things as we fixed them.
Participants stayed through all of it. Teams built, submitted, and presented. The response afterward was strong, which is the part I did not expect to feel this good about.
What I'd redo
Timing. My team and I put in a huge amount of effort, but we read the situation too late. If we had understood it earlier, this could have stayed a hackathon and not become a hackday.
What I'm taking forward
- Check the calendar before you lock the venue.
- Sponsors need weeks. Start earlier than feels necessary.
- Don't cancel while a smaller version of the event can still run.
HackInverse will be back. Format and date come later.