This is the second part of the story. You can also read the first part here: How do you make a School Project grow beyond School? 

Since my batch graduated from school, there have been a lot of changes to KHMD. The juniors who were in charge of taking KHMD forward unfortunately had to leave Kumarans after their 10th. The juniors who now wanted to run it were 4 years younger than us. Which meant that they could potentially run it for 4 years. That could be a good thing. It could also be a bad thing. Only time would tell.

These guys tried their best to give it a form that they would like to take forward (one of my suggestions to them was to transform KHMD into a thing that they felt comfortable taking forward). Their idea was to make it more inclusive by displaying how tech could be applied to whatever the interests of an individual may be. From what I hear, this approach never really caught on. During their first event, Ignite (notice the naming of all KHMD events), they made tons of mistakes while organizing due to inexperience(even though I and my batch mates had called out their mistakes in advance, they went ahead how they wanted to). This is when having 4 years to run something helps. But I liked their approach a lot. Fail fast, fail forward.

Fast forward one year, it was now March 2017. The juniors were able to actually get approval and funding for a makerspace on school premises. Big win.

Over the course of my first year in college, I was trying to figure out how to best take the same KHMD idea to other schools. KHMD had given us enormous belief in the power of students working together and building projects in a collaborative manner.

The idea we (the three co-founders of Hackio) came up with was this — to build a startup that works on IoT products for a smart India in a collaborative manner with school students. We wanted to become a platform for students to take their ideas to market.

On the advice of one of our mentors, We tried to get into a social venture fellowship that bred and supported social ventures. We tried to incorporate some social aspect to it but then we couldn’t convince the guys running the fellowship. So that didn’t happen.

Then we pivoted. We never really liked the idea of restricting ourselves to IoT so we scrapped that part. We retained the remaining parts while saying that we’d go to schools and do workshops that would bring them to a level where they could start prototyping their ideas. But we never really wanted to be a workshop company. So this too changed. Actually, ever since then, we’ve been pivoting our ideas.

Our ideas right now are very adaptive and we’re just taking Hackio forward as if it’s an experiment. Hopefully, some time in the near future, we’ll understand how to do it the right way. In conclusion, our current state of mind — confused. Clarity is boring.

If you’re interested in joining our collective or can add to the experience in any way, feel free to contact us at or the author at

To know about our projects, please visit

Happy Hacking!

This concludes the two part series.

The original post appeared on and has been reproduced with the permission of the author.