Indian EdTech Companies @BYJUS, @Unacademy, @PhysicsWallahAP, @upgrad, @VedantuLearn, @LEADSchool, @ClassplusApps, @TeachmintApp, @Doubtnut, @Toppr, @Cuemath, @CollegeDekho, @GreatLearning, @Simplilearn, @Scaler_official, @MasaiSchool, @NewtonSchool, @GeeksforGeeks,

doubtnut chutiya tha thoda sa but very helpful

Toppr best lga mujhe & doubtnut occasionally

doubtnut aur brainly pe kya din hua karte the

omg meritnation and doubtnut 😭

bring back the meritnation,doubtnut,brainly,toppers days🥀

Starting Sherlocks was probably the worst financial decision I ever made. Or so it seemed at the time. When I decided to start my third company, I had genuinely lucrative options on the table. Good money, interesting work, and none of the uncertainty that comes with building from scratch. I chose to start anyway. Those options were very good, although after doing this three times, I've come to understand something about myself. I default to being a large part of a small system, not a small part of a large one. After Doubtnut was acquired, I found myself inside a bigger company that was comfortable, stable, well-resourced, and completely wrong for how I'm wired. The entrepreneurial default is hard to switch off. You take ownership, you want to move fast, you want the problem you're solving to actually matter to you. Being one function inside a large machine doesn't scratch that itch, no matter how good the compensation is. So I left and started Sherlocks, accepting the financial stress of not knowing how long the runway is or when the next funding round closes. I knew the problem I wanted to solve. I knew AI was ready to do something real in reliability. That was enough to make the "stupidity" feel worth it. Has there been a moment when you chose the harder path, knowing it made no financial sense?

You know that feeling when an incident fires and 6 people join the call, and somehow, 20 minutes later, nobody agrees on what's actually broken? The problem is that everyone starts with different information. At Doubtnut, the actual fix would often take 20 minutes. Getting everyone aligned on what we were even looking at took 40. One person had last week's dashboard open. Another was scrolling through Slack. Someone else pulled up a runbook that was three months out of date. Five people on the call, five different theories, and no shared starting point between any of them. I used to think the answer was better runbooks. Write more of them, keep them updated, and make sure everyone knows where they are. The runbooks weren't the problem. The gap between the alert firing and everyone having the same picture is where the time went. That's the problem we built Sherlocks around. Before anyone opens their laptop, it's already correlating your logs, metrics, recent deploys, and similar past incidents into one working hypothesis. Your team walks into the incident with a shared starting point instead of building one from scratch while the clock is running.

For years, I was the person my team called at 2 am. And I've never fully made peace with why. I was CTO at Doubtnut, scaling to tens of millions of users. Uptime was my responsibility, and we didn't have the budget to have people on-call 24/7. When the on-call problem first came up, I couldn't believe how much it was affecting the team. So I stepped in, and I'd take it myself. Then I just kept doing it. Not because there was no other way. Not because the team wasn't capable. But because I cared too much about people, and thought that if I could take this one thing off their plate, it would help. It would've been easy to say, "I'll sort the process later. For now I'll just hold it together." But that wasn't solving anything. I realised that being nice to the team doesn't always help. Some problems need a process, a budget, clear responsibilities, and people held accountable, not a leader quietly absorbing everything alone. So I kept taking the pain myself. Deep down, I believed protecting them was the same as helping them. That experience never left me. It's a big part of why I built Sherlocks. Because I knew there were hundreds of CTOs and engineering leaders doing exactly what I did. The real fix isn't a rota. It isn't hiring more people to share the misery. It's building a system that handles the routine so your engineers don't have to.

The trick I used to watch Doubtnut videos or Brainly answers when the login screen covers everything.

i feel kids with ai nowadays will never come across the grueling hours we used to spend on meritnation, doubtnut, sarthak econnect, brainly, toppr the struggle to click the screenshot in 1sec when the answer was shown before the login prompt would come

– Meet Tanushree Nagori & Aditya Shankar – Co-founders of Doubtnut – Started in 2016, before the AI hype wave – When “AI tutor” wasn’t a buzzword – Solved math doubts using image recognition short video explanations – Built for students beyond metro cities – Worked in low-bandwidth environments – Focused on CBSE, ICSE & state boards – Became a daily homework companion for lakhs of high school students – In the pre-ChatGPT era – When doubts meant tuition or waiting till next day – You could just click a photo and get a solution in seconds – Quietly scaled across India – Eventually acquired by Allen While the world was still figuring out online education… They were building one of India’s earliest AI-powered doubt-solving platforms. For many of us, Doubtnut wasn’t just an app, It was our after school lifesaver

i remember the time when my tuition teacher found out about "Doubtnut" and oh boy his world changed that day 😭

I remember not being able to view the answers because I wasn’t signed up. I don’t know. I was the somehow very lazy to sign up doubtnut to see a stupid answer?? I mean its shocking how far we hv come today😭 I want to go backkk where things were found by google search not by gpt or gemini😭😭

Doubtnut disappeared like it never existed. I remember using it quite often during my JEE days.

Vo bhi kya zamana tha vedantu doubtnut brainly

Doubtnut 🥸

thats what I was wondering lol it gave me doubtnut vibe for a moment there... there solutions used to be vague sometimes!!

Dubai → Gurgaon Everyone said I was crazy. 6 years ago today, on Diwali, I proved them right. And wrong. I left Dubai. Left the comfortable life. Moved to Gurgaon. To join Doubtnut as CTO. My family thought I was crazy. My friends asked, "Why leave Dubai?" I didn't have a great answer. I just knew I had to. What followed was a blur: → Scaling from 15 to 50 million users → Navigating COVID crisis while running infrastructure → Explosive growth that broke everything → 3am alerts that woke up my family → Midnight releases that never ended → Incidents we couldn't contain because changes were too rapid I was exhausted. My team was exhausted. Our families paid the price. Every 3am alert was research. Every broken release was a lesson. Every incident was data. Akshat and I lived the problem so deeply that we couldn't unsee it. That pain became Sherlocks. ✔️ The AI SRE that helps teams recover from incidents faster. ✔️ The system that prevents families from being woken at 3am. ✔️ The solution we wish we had at Doubtnut. Steve Jobs was right: You can only connect the dots looking backward. 6 years ago on Diwali, I made a decision that felt impossible. Today, on Diwali 2025, I'm building the solution to the problem that decision revealed. The toughest decisions don't make sense when you make them. They make sense when you look back and realize: That was the door. And you walked through it. Happy Diwali to everyone celebrating. 🪔

🧵In order to grow a software/app product you need 3 things: 1. Acquisition 2. Engagement & Retention 3. Monetization Doubtnut had really good acquisition(mostly driven by organic Google search) & retention part(instantly getting the Aha moment of the habit forming loop)......