42 Days In — Built India's AI Astrology Startup, ₹744 Revenue, 6 Customers
What I'm building
KundliAI — India's first AI Vedic Astrology platform.
Free Vedic birth chart (kundli) in 30 seconds using AI +
Swiss Ephemeris calculations. Hindi + English both.
Why astrology?
- India's astrology market: $12 billion+
- 80% Indians consult astrologers regularly
- Zero good AI-powered solutions existed
- Hindi content = massive SEO opportunity
42-day numbers
| Metric | Value |
|--------|-------|
| Revenue | ₹744 ($9) |
| Paying customers | 6 |
| Daily users | 20-60 |
| Indexed pages | 427 |
| External backlinks | 37 |
| Email subscribers | 9 |
| Push subscribers | 35 |
What's working
1. AI Assistant traffic (48%)
ChatGPT, Claude, Gemini recommend KundliAI
when people ask about free kundli. This is
organic and growing.
2. Hindi SEO blogs
77+ blogs published. Low competition in Hindi
astrology content. Getting impressions fast.
3. Free tool as lead magnet
Free kundli → paid report (₹149) funnel
is converting at ~1%.
What's not working
❌ Social media — almost zero traffic
❌ Email list — only 9 subscribers
❌ Retention — returning users very low
Biggest challenge
Getting people to come back.
Kundli is a one-time thing for most people.
Working on daily rashifal, push notifications
and Sawan campaign to fix this.
Revenue model
- Full Kundli Report — ₹149
- Kundli Matching Report — ₹149
- Ask Pandit AI (30 days) — ₹149
- Sampurna Pack — ₹399 (launching soon)
This month's goal
₹3,000 revenue by June 30.
Sawan (Hindu holy month) starts July 11 —
that's the big revenue opportunity.
Ask
- Anyone built for Indian vernacular markets?
- How did you solve retention for one-time use tools?
- Any Hindi SEO tips?
Happy to share more details! 🙏
I'd be careful treating this primarily as a retention problem.
The interesting question may not be how to bring users back.
It may be what behavior actually deserves to be repeated in the first place.
Those sound similar, but they can lead to very different product decisions.
I wouldn't make that call casually from the current signals.
That's a really important distinction — thank you for pushing on this.
You're right, I was framing it as "how do I bring people back"
when the real question is "what's worth coming back for?"
Right now, the core action is generating a kundli — which is
inherently a one-time event for most people. There's no natural
reason to repeat it.
So if I take your framing seriously, the question becomes:
what behavior is actually repeatable and valuable?
A few candidates I can think of:
(genuinely changes, so revisiting makes sense)
(career decision, relationship doubt) — not a fixed schedule,
but recurring need
(travel, purchases, ceremonies)
These feel different from "come back to see your kundli again" —
they're tied to genuinely recurring needs, not artificial engagement loops.
I think my mistake was treating "retention" as a metric to optimize
rather than asking whether the product has a recurring use case
at all in its current form.
Appreciate you flagging this — going to sit with it rather than
rush a "retention feature."
Possibly.
The reason I'd still be careful is that I don't think the interesting part is which recurring use case gets chosen.
I think it's the decision sitting underneath that choice.
That's one of those decisions that can quietly shape what future feedback looks like, which signals feel validating, and what the product eventually becomes.
I wouldn't try to unpack that properly in a thread.
If you're curious, drop your email and I'll put together the tighter version.