A micro SaaS does not usually die because the idea is wrong; it dies because the product is presented to the wrong audience. This case study shows how one indie developer fixed positioning, ran paid ads, and grew recurring revenue within weeks.
What Is Jesus in Chat and Who Built It?
Jesus in Chat is a WhatsApp chatbot that answers questions using only the Bible and sends occasional Vercel, built by Brazilian indie developer André Elias in early 2025. The stated goal was to help Christians get quick, accessible answers about scripture. Elias describes himself as an indie hacker: someone who builds internet products without outside investment and grows them gradually.
The project came out of a working trip to Switzerland, where Elias and his wife were recording live videos and building the product at the same time. His wife also wrote the daily devotionals later used in the product's community. Elias had previously failed at a SaaS in 2023 because, in his own account, he feared selling, and he credits a mindset shift toward learning sales for his later progress.
By the time of this video, published in February 2025, Elias had left his job to work on his own products full time. He reports having been invited to record a course on the subject and reaching 10,000 subscribers on his YouTube channel, André Elias | Dev. Those claims are self-reported and were not independently verified for this article.
Why Was the WhatsApp Integration So Hard?
The hardest technical and operational hurdle was Meta's approval process for the official WhatsApp Business API. Elias reports repeated highs and lows while getting his application approved, and he came close to abandoning the project during this stage.
The turning point came from a viewer named Emerson, who had watched one of the live streams and offered tips on the approval process. With that help, the app was approved and the team could finally use the official API. The practical lesson is that WhatsApp integration is not just a coding task: it involves Meta's business verification and app review, which can stall a small team with no prior experience.
For developers planning something similar, the official requirements live in Meta's WhatsApp Business Platform documentation, which describes the business verification and app review steps the transcript refers to indirectly.
What Went Wrong at Launch?
The launch produced attention but not retention. The team promoted the product on TikTok, Instagram, and LinkedIn, and the LinkedIn post performed extremely well. Many people praised it, but others criticized the framing of a chatbot speaking as Jesus in the first person and worried it might replace prayer.
Elias says the site itself stated the product was a support tool for the Bible and did not aim to replace anything. The criticism still stung. More damaging was the retention data: people tried the chatbot a few times and left. The team considered shutting the project down again, and it sat idle for about a month.
The explanation he later identified was an audience mismatch. Most users came from LinkedIn, which was not the persona who would use a Bible chatbot day to day. Praise from the wrong audience looked like traction and masked the real problem.
Which Repositioning Strategy Turned It Around?
The recovery started with a case study Elias saw on Twitter (now X) about a Christian app in the United States that grew fast with a simple strategy. He decided to test the same approach on his own product rather than quit.
The changes were concrete and small enough to copy:
- Reworked how the product was communicated, with clearer and more direct messaging
- Reinforced the positioning as a Bible support tool, not a replacement for prayer
- Ran paid advertisements aimed at the actual target persona rather than whichever channel happened to bring traffic
Retention improved gradually and subscriptions began to grow. The insight was not a growth hack in the technical sense; it was correcting who the product was shown to. The table below summarizes how each channel performed against the product's real audience.
| Channel | Audience fit | Reported result |
|---|---|---|
| Poor fit for daily use | Viral post, low retention | |
| TikTok and Instagram | Closer to target persona | Part of the revised mix |
| Paid ads on the right persona | Direct fit | Retention and subscriptions grew |
How Did the WhatsApp Community Grow?
Alongside the product, the team created a WhatsApp community to share daily devotionals written by Elias's wife. The first group hit WhatsApp's 2,000-member limit quickly, so they created more groups, which also filled fast.
Elias says the team is still deciding how to manage community at this scale, describing WhatsApp as limiting for this purpose. They want to keep members connected around the Bible while also reinforcing the product's brand and credibility. No migration to another platform has been announced; the constraint is stated as an open problem, not a solved one.
What Are the Actual Revenue Numbers?
After 22 days of the new strategy, Elias reports that Jesus in Chat had earned R$3,132 in total, of which R$845 was monthly recurring revenue (MRR). He also reports one to three new subscribers per day, depending on the day.
Two arithmetic checks are worth making. First, R$845 of MRR out of R$3,132 total means roughly R$2,287 came from payments that were not part of recurring subscriptions, such as annual plans or one-time charges; the transcript does not break this down. Second, his projection of reaching R$3,000 in MRR within three months assumes the current subscriber pace continues. That would require roughly 3.5 times the current MRR, and Elias himself notes it does not account for churn, which he says always happens. The projection is the creator's own forecast, not a verified outcome.
All figures are self-reported by the creator in the February 2025 video and were measured in his own dashboard. They are presented here as vendor-reported numbers, consistent with how he frames them himself.
What Lessons Apply to Your Own Project?
The core lesson Elias draws is that the problem is sometimes presentation and execution rather than the idea. A product that looked like a failure under one distribution strategy improved once it reached the right people with clearer positioning.
The transferable steps, in the order they happened:
- Ship the product even when setup fights you; the WhatsApp approval delay nearly killed the project before launch
2. Watch retention, not applause, because a viral post on the wrong channel mimics success
3. Change the message and the audience before changing the product
4. Test a strategy that worked for a comparable product instead of assuming your case is unique
5. Give the fix enough time to produce data; 22 days was enough to see the direction here
One caution: this is a single product in a niche with a motivated audience and a community layer. The numbers show a promising start, not a proven playbook for every micro SaaS.
FAQ
- What is Jesus in Chat? It is a WhatsApp chatbot that answers questions based on the Bible and sends occasional Vercel. Its creator positions it as a support tool for Bible reading, not a replacement for prayer.
- Who created Jesus in Chat? André Elias, a Brazilian indie hacker and YouTuber, built it in early 2025 with help from his wife, who writes the community devotionals, and a viewer named Emerson who helped with API approval.
- How much revenue does Jesus in Chat make? The creator reported R$3,132 in total revenue after 22 days of the revised strategy, including R$845 in monthly recurring revenue. These are self-reported figures from February 2025.
- Why did the product almost fail? Low retention and public criticism of its first-person Jesus framing nearly led to abandonment. The creator later identified the real problem: most early users came from LinkedIn, which did not match the product's actual daily-use persona.
- What fixed the retention problem? A repositioning effort: clearer, more direct messaging, reinforced positioning as a Bible support tool, and paid ads aimed at the real target audience. Retention and subscriptions then grew.
Turn Your Own Video Into an Article
This story existed first as a six-minute video, and its most useful parts, the numbers, the pivot, and the channel-mismatch insight, are exactly what a written article preserves and makes searchable. If you have lessons like these sitting in your own uploads, you can put them to work as text.
With Skala Blog, you paste a YouTube URL, the video is transcribed, and you get a structured article draft you can review and publish. A project worth not giving up on is also worth documenting; if this case study helped you, your own might help someone else.
Fork this article
Start a new branch from the same video, shaped your way. You keep the credit; the original keeps the attribution.
A fork in another language is filed as a translation of this article, so the two pages point at each other. You can unlink it later from the editor.
0/240
You are creating
- Format
- For
- Language
- Source
- Your angle
You will be asked to sign in before it is generated.
Buy credits