Launching a micro SaaS while living as a digital nomad in Europe means fighting through platform approvals, building payments, and posting daily content before the first sale arrives. That is exactly what a Brazilian developer documented in December 2024 while building Jesus in Chat, a WhatsApp chatbot, from Switzerland, Paris, and Portugal.
What Launching a Micro SaaS From Europe Actually Involved
Launching a micro SaaS in Europe, as documented in a December 2024 video by Brazilian developer André Elias, meant building a WhatsApp chatbot called Jesus in Chat while traveling through Switzerland, France, and Portugal as a digital nomad. The product answers messages on WhatsApp with conversational context, and the plan was simple: charge subscriptions, cover server and API costs, and pay personal bills.
The video is a day-in-the-life vlog rather than a tutorial, so its value is in the concrete hurdles and launch numbers it shows. Those numbers, posted by the creator in December 2024, include roughly 300 likes on LinkedIn with no sales, 80 likes on a Threads post, and three subscriptions driven by an organic post from his wife Carol on Threads.
The product idea sits in a niche the creator describes as religious chatbots on WhatsApp. He notes in the video that another developer he met through LinkedIn runs a Bible chatbot in the same space, and that person helped him through the approval process. That peer detail matters more than it looks: the fastest unblock in the whole story came from someone already operating in the same niche.
Why Meta and WhatsApp Approval Nearly Killed the Project
The hardest part of the build was not code. The creator started developing the WhatsApp chatbot during a live stream, then hit repeated rejections from Facebook (Meta) when applying for API access, and came close to abandoning the project entirely.
The root cause, as he explains it, was business verification rather than the app itself. He had to validate his domain and put a registered company name (razão social) on the website before Meta would approve the application. Once the domain was validated and the company details were in place, the approvals came through: Meta approved the app, and the WhatsApp Business number was cleared to send messages.
The sequence he followed after approval is a useful checklist for anyone integrating the WhatsApp Business Platform:
- Validate the domain used by the app.
- Display a legal company name on the site.
- Reapply for API access and wait for Meta's approval.
- Approve the WhatsApp Business number for messaging.
- Finish the app, then build the landing page, terms of use, and privacy policy before submitting the app for final review.
By the time of the launch, the bot already answered incoming messages with conversation context. What remained was monetization.
The Stack: a Next.js Template and Stripe
The remaining engineering task at launch time was adding payment processing. The creator chose Stripe, the payment platform for internet businesses, to handle recurring subscriptions. His stated motivation is candid: revenue has to cover the bot's running costs and his own living expenses, because that is the point of a SaaS.
For the application layer, he offers a Next.js SaaS template he built, published as the Crazystack Typescript template. The video itself does not walk through the code, so readers evaluating the stack should treat the template as the creator's own product rather than an independent endorsement of any architecture.
This split is typical of micro SaaS builders in this niche: a thin product layer on a general-purpose web framework, messaging delivered through a platform API owned by Meta, and billing outsourced to Stripe. None of those components are open source as a whole in the way the product runs, so claims about the stack should stay at the level of the tools named above.
Launch Results by Channel: Engagement Versus Sales
The most instructive part of the video is the launch scoreboard, three days after release. The creator posted on LinkedIn and Threads, and his wife Carol posted organically on Threads as well. The numbers he reports in the video, in December 2024, are first-hand and self-reported, not independently audited.
| Channel | Post author | Engagement | Sales attributed |
|---|---|---|---|
| Founder | Almost 300 likes | 0 | |
| Threads | Founder | 80 likes | 0 |
| Threads (later post) | Founder | 27 likes | not stated |
| Threads (organic) | Wife, Carol | 312 likes, many comments | drove 3 subscriptions |
His own diagnosis is audience mismatch: the people engaging on his LinkedIn are developers and peers, not the target users of a religious WhatsApp chatbot. Carol's post reached an audience closer to the product's actual buyers, and that is where the three subscriptions came from.
The planned next step, stated at the end of the video, is continuing organic content and experimenting with short-form video on TikTok. Three subscriptions is a validation signal, not a business, and the creator presents it that way.
The Nomad Context: Switzerland, Paris, Portugal
The launch happened mid-trip. At the start of the video the creator and his wife were in Switzerland; by the middle they were in Paris; three days after launching they were in Portugal. He films on an iPhone 15, records his screen with Screen Studio, uses an Elgato Wave 1 microphone, and works from a MacBook Pro.
He is explicit that he is testing the nomad lifestyle rather than selling it: the experience has pros and cons, he does not want to oversell it as perfect, and he says he will share whether it is worth it once the experiment concludes. For readers considering the same path, that framing is more honest than the usual highlight reel.
The practical takeaway is that a one-person SaaS with platform-delivered messaging and hosted payments can be operated from a laptop across borders, at least in its first weeks. What the video does not cover, and what any reader would need to research separately, is tax residency and business-registration implications of running a company from multiple countries.
What This Launch Teaches Other Indie Developers
Three lessons emerge from the video, and all three generalize beyond this specific product.
- Platform approval is a project risk, not a formality. Meta rejections over domain validation and company identity nearly ended the project. Budget weeks for this and prepare the legal entity and domain before writing much code.
- Engagement without audience fit produces no revenue. Almost 300 LinkedIn likes coexisted with zero sales; the converting channel was a post aimed at the product's actual audience.
- A small win is still a win. Three subscriptions within days of launch, driven by organic content with no ad spend, validates demand enough to justify continuing.
A fourth, quieter lesson comes from the peer who helped him: another builder in the same niche, running a Bible chatbot, unblocked the approval process. Niche communities of operators are often more useful than generic advice for passing platform reviews.
FAQ
- What is Jesus in Chat? It is a WhatsApp chatbot created by developer André Elias that answers users' messages with conversational context, launched in December 2024 and monetized through subscriptions via Stripe.
- Why did Meta initially reject the WhatsApp API application? According to the creator, the application failed until his domain was validated and a registered company name appeared on the site. Once those were fixed, Meta approved the app and the WhatsApp Business number.
- How many subscriptions did the launch produce? The creator reports three subscriptions in the first days, all connected to an organic Threads post by his wife Carol, which received 312 likes and many comments.
- Did LinkedIn engagement translate into sales? No. A LinkedIn post drew almost 300 likes but zero sales, which the creator attributes to his LinkedIn audience not matching the chatbot's target users.
- What tools were used to build and run the product? The video names Stripe for payments, the WhatsApp Business Platform for messaging, and the creator's own Next.js-based Crazystack Typescript template for the application layer.
Turn Your Own Build Log Into an Article
The lesson of this launch is that small, honest numbers tell a better story than polished hype: three subscriptions from the right audience beat 300 likes from the wrong one. If you document builds like this on video, that same story can work in text, where search engines and answer engines can actually find it.
Skala Blog turns a YouTube video into a structured written article: paste the video URL, get a transcription, and generate a publishable draft you can review and edit. Your launch logs, tutorials, and day-in-the-life dev content become searchable articles without writing them from scratch.
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