🚀 Creo Bot: From Hackathon Idea to a Production-Ready Internal Tool
Share this article
An internal hackathon journey that started with doubt, evolved through collaboration, and resulted in a real-world AI-powered automation bot.
🧠 Background: HnH Internal Hackathon
This project was built during an HnH internal hackathon, where participants were required to propose and build solutions aligned with predefined themes. One of the core themes was Artificial Intelligence, and the expectation was not just innovation—but practical relevance to the company.
💡 Ideation: Where It All Started
Initially, my idea revolved around an AI-powered Student Learner Hub.
🎓 Student Learner Hub (Initial Idea)
The vision was to create a system that:
Understands a student’s experience level
Adapts learning material based on expectations
Builds a personalized knowledge base
Helps students navigate learning paths efficiently using AI
From a technical and conceptual standpoint, the idea was strong.
However, during discussions with the organizers, I received crucial feedback:
“The idea is good, but to score higher, it should directly relate to company use cases — something that can integrate into workflows, tools, or internal systems.”
That feedback changed everything.
🔄 The Turning Point: Relevance Over Novelty
At this stage, I was honestly close to dropping out.
Most ideas felt repetitive, and time was running out (the hackathon deadline was 15 February).
Around the same time, I had already raised a PR to Tapas sir, but due to parallel priorities, the follow-up didn’t happen immediately — and I also missed pushing it further.
Instead of quitting, I decided to rethink the problem from a company-first lens.
🗣️ The Spark: A Simple Question That Changed Direction
During a casual discussion, I asked:
“Don’t you think we should have a bot to manage repetitive tasks ?”
That question led to a deeper discussion — and suddenly, a clear plan emerged.
