"Our flag 🇮🇳 does not fly because the wind moves it,
it flies with the last breath of each Soldier who died protecting it!"
Jai Hind Ki Sena 🇮🇳🦂
#IndianArmy#Deepotsav2025#Deepavali2025
My raja beta
Loved the festive season
And his Ma...
Loves the glow on his face
Celebrating victory of good over evil
Prayers for our braves to be safe 🙏
Away from home, at our borders
Shubh Narakachaturdasi to all 🙏
@Rahulsainlll@dev_Aditya07 is a really good choice. He created color picker extension having 1000 users. Also, built good projects.
Please checkout https://t.co/ipAB8Ty9Ss, multilingual portfolio
here's what we did to reduce churn:
(warning: I did many things that don't scale...)
1. doubled prices and attracted higher quality customers:
we doubled prices a few weeks ago after seeing that the people that churned were almost always using our launch code and didnt pay the full price - just don't sell to price sensitive people or to people that don't see your product as a "must have" for the pain they experience. a higher price turned out to be a great filter for this
2. obsession with onboarding and user activation + time to "aha-moment":
I watched A LOT of posthog sessions recordings and noticed a couple patterns among the people that ended up converting (we have a limited opt in free trial without cc for context).
those who ended up upgrading were always directly activated they "understood" the product right away and hit the limit of the trial within 1-2h.
after seeing that I made an email sequence to offer everybody that matched ICP criteria & signed up but didn't hit that "aha-moment" 1:1 onboarding to manually guide them to that moment + find out why they are getting lost.
we took these insights and rebuild the onboarding for a third time now: reduced time to "aha moment", more activation by guiding the user better to their first results and so on...
3. closely monitoring user activity + manual outreach to "idling users":
I set up a posthog dashboard with every user to see the last time they were active and what features they used. I reached out to everybody manually that wasn't active in the last 7 days to understand what was keeping them from using it daily (which is the best case for our product)
We got many insights from this which led to just many slight improvements that added up to a whole better UX I'd say
4. habit building:
Duolingo is king in user activation and retention. So I watched some podcasts of the founder and some product managers from Duolingo to understand how they approach this + everybody in the team started reading the book "hooked" by nir Eyal.
From Duolingo we took away that we need a higher incentive for people to show up --daily-- and not every other day when they feel like it (otherwise its hard to build a real habit around your product usage).
so we implemented a posting streak counting only posts published by postel. Duolingo found out in their data that every user hitting a 7 day streak experienced increased "loss aversion" making them use the product just not to loose the streak. we got the first users telling us the same... so its working :)
From the book "hooked" we got a way better framework to understand were our users are in the "habit building journey" - this changed a lot in how I communicate certain features and present them... I nudge our users to use certain features more because I saw in our data that those features where heavily used by our users with the highest ltv.
I can recommend having a closer look at your most loyal users and what they use exactly and then trying to understand why those features are "habit building"... then systemise the process to lead all sign ups down a path that will make them use the same "habit building features"...
Sadly its not in my best interest here to be more specific since one of our competitors is already in the middle copying a bunch our features and I cant give out all the sauce - just dm me if you want to know more about the last part which I think moved the needle the most
And also I have to apologise:
I made a mistake in my tiktok & post on here: we reduced churn by 50% since launch of which roughly 40% was this month alone. Sorry I didnt mean to inflate the numbers (I record this vids just before going to be when I'm already kinda done for the day...)
tldr:
just build a good product for 1 specific avatar bruh
Just funded our latest investment:
– Pre-seed
– Three technical founders
– SF-based
– AI-native jobs network
Reminder: we’re backing at least one new team every month with $100k to $1M checks.
DMs always open.
Deepinder Goyal – building India’s own gas turbines
Aman Singh – creating a sovereign healthcare LLM (Sanjeevani AI)
Sanket Jain – developing Dhruva Space for satellite tech
Wing Commander Vishal Mishra – powering military drone swarm tech (Vayulink)
Tanay Pant – building open-source Indian AI models
Tan90 team – designing rural-friendly thermal batteries
Kunaal Sood – automating drone production and logistics
Kumar Varun – building India’s semiconductor packaging infra
Agnikul and Skyroot teams – launching reusable rockets from Indian soil
Thank you for building India's future 🙏
A few months ago, Blinkit Ambulances started quietly in Gurugram with just 5 ambulances and a dream. What if emergency help could reach you in 10 minutes, just like groceries?
This is one of the hardest and the most resource intensive challenges we have ever taken up. But we are not backing down.
We started with 5 ambulances at the beginning of the year in Gurugram and currently, we have 12. From serving a small area around Golf Course Road, we have now extended the service to cover almost half of Gurugram.
Until today, we have responded to 594 calls, 50% of these critical emergencies. Today, our 12 ambulances across 6 depots reach patients within 10 minutes, 83% of the time.
But numbers only tell part of the story.
Behind every number, every case, is a human being and their family. Moments of fear and hope, desperation and relief.
We discovered how hesitant people still are to call an ambulance, even in critical moments. Many prefer personal cars or cabs, afraid help won’t arrive on time.
We learned how difficult it is to find and train paramedics who can deliver not just medical aid, but empathy when it matters most. Our team is now building an in-house paramedic training program to raise the bar of emergency care in India.
Blinkit Ambulances isn’t just a project. It’s a responsibility we carry close to our hearts. It’s tough, it’s emotional, and it’s still Day 1.
We’re learning. We’re committed. And we won’t stop until every single person trusts that life-saving help is only 10 minutes away.
Has Blinkit Ambulances helped you, or your near and dear ones? We would love to hear your story – will serve as fuel for us and the Ambulances team to keep going.
Cc @albinder
We saw Jason’s post. @Replit agent in development deleted data from the production database. Unacceptable and should never be possible.
- Working around the weekend, we started rolling out automatic DB dev/prod separation to prevent this categorically. Staging environments in the works, too. More tomorrow.
- Thankfully, we have backups. It's a one-click restore for your entire project state in case the Agent makes a mistake.
- The Agent didn’t have access to the proper internal docs -- rolling out a fix to force Docs search on Repit knowledge.
- And yes, we heard the “code freeze” pain loud and clear -- we’re actively working on a planning/chat-only mode so you can strategize without risking your codebase.
I reached out to Jason the moment I saw this on Friday morning to offer assistance. We'll refund him for the trouble and conduct a postmortem to determine exactly what happened and how we can better respond to it in the future.
We appreciate his feedback, as well as that of everyone else. We're moving quickly to enhance the safety and robustness of the Replit environment. Top priority.