Eklavya Hire

Musician, Social entrepreneur, Startup, Student, Writer/Editor

I’m a builder and problem-solver from Nashik who turns real-world chaos into clear data. I’ve led projects including "Kumbh Seva", "Routly", and more — using technology to help cities, businesses, and people move smarter and safer. My work focuses on making invisible patterns visible so communities can make better decisions, faster.

*What I'm Passionate About* I’m passionate about making invisible problems visible before they hurt people. Most of the time, cities and organizations don’t fail because people don’t care. They fail because they can’t see what’s coming. A queue that turns into a stampede. A factory floor that gets congested and causes an accident. A bus stand that overflows because no one knew 500 people would show up at 6pm. I’ve spent years building technology that helps us see that. Through projects like "Kumbh Seva", "Routly", and others, I’ve worked on systems that understand how people move, where crowds build up, and where systems are about to break. What drives me is this: data should serve people, not the other way around. I’m not interested in tracking who you are. I’m interested in understanding _how_ we move together. How many people are in a space. How fast it’s filling. Where the bottleneck is going to be 20 minutes from now. That’s it. Anonymous, real-time, useful. Why does this matter to me? Because I grew up seeing how much stress, money, and safety we lose to "reactive" decisions. We wait for traffic to jam, then send police. We wait for a line to get too long, then open another counter. We wait for an incident, then do an inquiry. I believe we can flip that. We can build systems that feel pressure the way our bodies do — and adjust before it becomes pain. I’m passionate about 3 things inside this: *1. Safety without surveillance* You shouldn’t have to give up privacy to be safe in public spaces. The tech I build doesn’t care about names or faces. It cares about flow. "This hall is 80% full." "This lane is slowing down." That’s enough to prevent 90% of crowd-related problems. Safety should be the default, not an afterthought. *2. Dignity in everyday life* Waiting in line for 2 hours isn’t just inconvenient. It’s exhausting. It steals time from parents, students, workers. If a temple, hospital, or transit hub could predict demand and adjust staff, gates, or buses in advance, we give people back hours of their life. That’s what technology should do — give time back. *3. Building from tier-2 cities* I’m from Nashik. And I’m passionate about proving that big ideas don’t only come from Mumbai, Bangalore, or Silicon Valley. Some of the hardest problems — crowds, logistics, public systems — are right here. If we can solve them here, with fewer resources, we can solve them anywhere. I want to build products in Nashik that get used in 100 other cities. Through "Kumbh Seva", I learned how to design for scale and chaos — millions of people, limited time, zero room for error. Through "Routly", I learned how to turn movement data into decisions that save fuel, time, and frustration. And through every other project, I’ve learned that the best technology disappears. People don’t notice it. They just notice that things work better. At the core, I’m passionate about this belief: *Cities, companies, and communities deserve a nervous system.* Right now we build roads, buildings, and apps. But we don’t give them the ability to feel. To know "I’m getting crowded" or "I’m about to break". If we can give infrastructure that sense, we prevent problems instead of managing them. That’s what gets me out of bed. Not the tech itself. The outcome. Fewer accidents. Shorter queues. Calmer events. Factories that run smoother. Parents who get home 30 minutes earlier. I want to live in a world where systems are designed around how humans actually behave — not how we wish they would behave. A world where we stop asking "who caused this" after something goes wrong, and start asking "what did we miss" before it does. If I can spend my career building that one layer — the layer that helps the world _feel_ itself — then I’ll know I did something worth doing. Because the future shouldn’t just be smarter. It should be kinder, safer, and less stressful to live in. And that starts by paying attention.

Title: What if Cities Could Feel How Crowded They Are?* *The Idea:* We build cities to hold people. But we build them blind. Right now, a city has no nervous system. A mall doesn’t know it’s about to be overcrowded until the queue is 200 people long. A factory doesn’t know a zone is dangerous until there’s an accident. A road doesn’t know it’s jammed until you’re already stuck in it. What if cities could _feel_? My idea is simple: give cities a sense of touch through real-time crowd and movement intelligence. Not surveillance. Not tracking names. Just understanding: how many people, where, how fast, and where is it about to break. I’ve spent the last few years building this. Through projects like "Kumbh Seva" and "Routly", I learned one thing — the biggest problems don’t happen because we don’t care. They happen because we don’t _see_ them coming. We react to stampedes. We react to traffic. We react to factory shutdowns. But we never prevent them, because we’re missing the most basic data: how people are moving, right now. *Why this matters:* 1. *Safety*: 80% of crowd disasters are predictable 30 minutes before they happen. If a temple, station, or event knew "Zone 3 is at 90% capacity and growing", they could open another gate. No panic. No headlines. 2. *Efficiency*: MIDC factories lose crores because machines wait for parts and workers wait for space. If a floor manager could see "Assembly Line B is congested", they could reroute in real time. That’s money saved, not people policed. 3. *Dignity*: People don’t want to stand in 2-hour queues for prasad or wait 40 minutes for a bus. If systems could feel demand, they could adjust. Fewer crowds. Less frustration. *How it works without being creepy:* This isn’t about facial recognition or "who" you are. It’s about "how many" and "how fast". Anonymous sensors, thermal cameras, and movement patterns. The output isn’t a person’s name. The output is: "This area is full. Open gate 2." Think of it like a weather forecast, but for crowds. You don’t need to know who the rain drops are. You just need to know it’s going to rain. *What changes if we do this:* Imagine a city dashboard that shows stress points like we show weather. Red zones for congestion. Green for clear. Event organizers get alerts before, not after. Factory managers prevent bottlenecks. Hospitals know when ER will spike. We already do this for traffic with Google Maps. We already do this for weather. The next step is to do it for people. *The bigger point:* For 100 years we designed cities for cars, then for data, now for AI. But we forgot to design them for humans in motion. Technology has given us satellites to see forests burn and sensors to feel earthquakes. It’s time we built the same for human movement — the most common, most dangerous, and most ignored force in our cities. If we can make cities that feel, we can make cities that care. Cities that don’t wait for disaster to act. Cities that give people space, time, and safety by default. That’s the idea worth spreading: *Don’t just build bigger cities. Build cities that can feel.*

"Reroute Staff", "Send Another Bus". Systems people will actually use at 2am., 1. Crowd & Movement Intelligence Building systems that understand how people flow through spaces in real-time. Anonymous crowd counting, actionable data. 3. Operational Efficiency for Factories & Enterprises Using movement and flow data to reduce downtime, and congestion for businesses and public services. 5. Product Development in Resource-Constrained Environments Shipping and scaling technology from tier-2 cities like Nashik. Expertise in building simple, and events prevent problems before they happen. Focus: turning invisible pressure points into visible, and live alerts for safety and efficiency. Projects: "Kumbh Seva" and others. 2. Urban Systems & Public Safety Tech Designing technology that helps cities, and optimize space in MIDC and manufacturing environments. Turning shop-floor chaos into clear decisions. 4. Logistics & Routing Optimization Building tools like "Routly" that use real-world movement patterns to reduce wait times, bottleneck prediction, density mapping, fuel costs, improve safety, rugged, temples, transit hubs, usable products that work without heavy infrastructure or big teams. 6. Translating Complex Data into Simple Action My core skill is taking complex sensor + AI data and turning it into one clear instruction: "Open Gate 2"

I’m passionate about problems you can’t see until it’s too late. A few years ago I started building technology to understand crowds. Not to watch people. To _feel_ them. To know when a space was getting full, when a line was about to break, when a system was about to fail. My first big test was a project called *"Kumbh Seva"*. The goal was simple: can we count how many people are in a city at any given time, without tracking who they are, and use that to keep everyone safer? We built the system. It worked. But then came the part I didn’t expect. The local authorities said no. That "no" hit hard. I thought I was building something to help. But I realized something else that day: big problems don’t get solved just because the tech works. They get solved when people trust it, understand it, and are ready to use it. So I had a choice. Quit, or rebuild the idea somewhere else. I chose to rebuild. That’s how *"Routly"* was born, and a bunch of other projects after it. Instead of starting with the biggest, hardest event, I started with places that said yes. MIDC factories that needed to know if a floor was too crowded. Malls that wanted to reduce queue times. Event organizers who were tired of reacting to problems after they happened. And here’s what I learned: the problem was never unique to Kumbh. Every hospital has an ER that overflows. Every station has a platform that gets dangerous at 6pm. Every factory has a bottleneck that costs lakhs but no one sees until the month-end report. We’re all running systems blind. The moment that changed me was in a factory in Nashik. The manager pulled up my dashboard and said, "This red zone here? That’s where we had 2 accidents last year. We never knew why. Now I do." He didn’t care about AI. He didn’t care about sensors. He cared that for the first time, he could _see_ the pressure building before it burst. That’s when it clicked for me. We don’t need smarter cities. We need cities that can feel. Right now we build roads, buildings, apps — but we don’t give them a nervous system. We don’t give them the ability to say "I’m getting full" or "I’m about to break." So we wait. We wait for the jam, the stampede, the shutdown, and then we react. I’m building the layer that comes before the reaction. Through "Kumbh Seva" I learned to design for scale and chaos. Through "Routly" I learned to turn movement into decisions. Through every "no" I learned that the best technology isn’t the most complex. It’s the one people actually use. My story isn’t about crowd counting. It’s about attention. We pay attention to weather with forecasts. We pay attention to traffic with Google Maps. But we don’t pay attention to people in motion — the most common force in any city. If we did, we could prevent instead of respond. We could give people back time stuck in queues. We could make spaces safer without making them feel watched. I’m from Nashik. And I’m proof that you don’t need to be in a metro or a big company to work on big problems. Some of the messiest, most human problems are right here. And if we can solve them here, we can solve them anywhere. The idea I’m chasing is simple: *What if the world around us could feel, so we don’t have to suffer?* What if a temple could open another gate before the crowd panics? What if a bus stand could send another bus before the line forms? What if a factory could reroute work before someone gets hurt? That’s the future I’m building toward. One sensor, one dashboard, one "yes" at a time. Because technology should do one thing above all else: It should make life less stressful, less dangerous, and more human. And that starts by paying attention — before it’s too late.

People see me as the "crowd tech" guy. The one who builds "Kumbh Seva", "Routly", and systems that count people. What they don’t see is what actually makes those projects work. *I’m good at translating chaos into a system.* Most people look at a crowded street, a jammed factory floor, or a 2-hour queue and feel stress. I feel a pattern. Give me 10 minutes in any messy environment and I can start mapping it: where people enter, where they stall, where pressure builds, where the whole thing will break in 30 minutes. It’s not magic. It’s just that I’ve trained myself to see flow instead of objects. That’s why my tech works. Because before I write a single line of code, I’ve already lived in the problem for a while. I stand in the queue. I walk the factory. I watch the gate. People don’t know I’m good at that — sitting in discomfort long enough to understand it. *I’m good at building with "no".* After Kumbh authorities said no, most people would have dropped it. I didn’t. I took the same engine and rebuilt it for factories, malls, and events — places that could say yes in 30 days instead of 3 years. People think I’m good at AI. What I’m actually good at is repackaging. Taking one core idea and reshaping it so a new person can say "oh, this solves _my_ problem". That’s sales, but it’s also empathy. You have to hear what keeps another person up at night, and then show them your tool is the answer to that — not to yours. *I’m good at making complex things feel simple to the person using it.* The dashboards I build look boring on purpose. No 50 graphs. No "AI model accuracy 97.3%". Just: "Zone 3 is 80% full. Open Gate 2." Because the person on the ground doesn’t care how smart the model is. They care: what do I do in the next 5 minutes? People don’t know I spend 70% of my time deleting features, not adding them. The best system is the one a 22-year-old supervisor can use at 2am without training. *I’m good at building in tier-2.* Mumbai and Bangalore get all the funding, the mentors, the press. Nashik doesn’t. But I’m good at finding advantages here. Cheaper pilots. Faster access to decision makers. Real problems that aren’t already solved 10 times over. I can walk into a MIDC factory and talk to the owner directly. No 6 layers of procurement. That speed is a superpower people in big cities don’t have. People don’t know I’m good at turning "disadvantage" into leverage. *I’m good at patience.* This work is slow. You don’t get viral growth. You get one factory, then one more. One event that goes well, then another asks for a demo. I’m good at doing that for years without needing applause. Because I’m not building for the headline. I’m building for the day a manager tells me "we avoided an accident because of your alert." That’s the metric no one sees. --- So if you strip away "crowd counting" and "Kumbh Seva" and "Routly", here’s what’s left: I’m good at seeing what others ignore. I’m good at turning a "no" into a new door. I’m good at making hard things usable. I’m good at building where no one is looking. I’m good at staying long enough for it to matter. That’s what I bring to any room, any project, any TED stage. Not just tech. The ability to feel a system, and then fix it before it breaks.