One agency owner willing to pay R$249 a month was the entire foundation of this micro SaaS launch. Instead of hunting for a market, André Elias built LeadYuu, a WhatsApp bot that qualifies leads, around the daily grind of a real customer who answered the same questions over and over.
How the LeadYuu Micro SaaS Launch Started
LeadYuu is a WhatsApp chatbot that qualifies sales leads, schedules meetings and can pause atendimento automatically. Brazilian developer André Elias launched it in March 2025 and documented the whole micro SaaS launch on his YouTube channel, including the goal of reaching R$15,000 in monthly recurring revenue within one year.
The name has no deep meaning. André had a previous product ending in "yuu" and liked that suffix because domains ending that way are easy to find. The product itself is simply "lead" plus that ending, pointing at what it does: handle leads, which are potential customers for a business.
The launch plan rested on a deliberately small target. Five paying clients per month, acquired over twelve months, would reach the R$15,000 MRR goal. That arithmetic made an ambitious-sounding number feel achievable for a solo developer, and it set the customer profile for all marketing that followed: agencies that handle many client conversations per day.
Where Did the Product Idea Come From?
The idea arrived through a client, not through brainstorming. André had previously built a WhatsApp chatbot that helps Christians study the Bible, and that project made noise on LinkedIn. Guilherme, who runs an agency called Italiane focused on Italian citizenship processes, saw the post and asked for something similar for his own operation.
Guilherme's pain was concrete. He spent hours each day on WhatsApp answering the same onboarding questions for citizenship clients: the ancestor's name, whether the client had the required documents, whether they already knew the process. At the end of every conversation he shared a link so the client could book a meeting. A bot that automated that exact sequence would save him real time.
The commercial terms were negotiated openly in the video's retelling: Guilherme could pay up to R$200 per month considering AI costs, and André proposed R$249 per month with AI costs covered by him. The deal became the first revenue of the micro SaaS launch, and a beta tester came bundled with the contract. This pattern, where a builder's existing work attracts a buyer with a specific pain, is common in the Brazilian micro-SaaS creator scene; creators such as Gustavo Dev Doido, who runs the Bootcamp do Dev Doido, teach a similar client-first approach, and André himself sells a Next.js SaaS starter called Crazystack Typescript for developers who want a head start on this kind of build.
André's closing lesson follows directly from this origin story. If you struggle to find SaaS ideas, he argues, you are probably not building enough. Once you start shipping, ideas begin to arrive on their own, and your first product may be the one that opens the door to the next one.
Which Features Got Cut Before Development?
The original scope was a complete platform: a fully customizable bot screen with action buttons, integration with the Google Calendar API for scheduling, and the long Meta app approval process for WhatsApp, plus Google's own approval flow. André estimates that scope would have cost months of development, so he forced himself out of what he calls the perfectionist developer mindset.
The question he asked was narrow: what is the simplest version Guilherme could start using tomorrow? The answer produced two cuts that shrank the timeline to roughly three weeks of building and testing, and both cuts are visible in the shipped product.
The cuts mattered because each one removed either engineering work or an external approval dependency. The table below shows the two decisions side by side:
| Planned feature | What shipped instead | Why it worked |
|---|---|---|
| Fully customizable bot with action buttons | Three fixed flow steps: collect questions, schedule meeting, pause atendimento | Covered the client's actual daily workflow |
| Deep Google Calendar API integration | A shareable Google Calendar appointment link sent at the right conversation step | The link behaves like a Calendly page with zero integration code |
| Custom scheduling logic | Client books directly on the shared Google Calendar link | Removed development time and approval surface |
This is the core of the micro SaaS launch method in the video: identify the smallest paid outcome, deliver it, and let everything else arrive later. The three flow steps were not a compromise in the client's eyes; they were his process, encoded.
What Does the LeadYuu Product Actually Do?
The finished application is a WhatsApp-attached dashboard organized around a configurable three-step flow and a set of business settings. Reviewing each area answers a different question a potential buyer would have, and the areas were all shown on screen in the March 2025 video.
Conversations inbox
The main tab lists every conversation between the business and its clients. The operator can read messages and reply directly from the dashboard, so the bot and the human share one place to handle atendimento.
Flow configuration
Each of the three steps can be switched on or off. The qualification step lets the owner add the questions the bot should ask. The scheduling step holds the Google Calendar link plus an optional custom prompt for personalization. The final step controls whether atendimento pauses once the flow completes.
Playground, templates and settings
A playground lets the owner test the current flow and see how the bot responds before clients ever touch it. A templates area exists only to satisfy Meta's app review requirements and was not in active use at launch. The settings area holds the company name, a business description for the assistant's context, the bot's personality, and a lead scoring factor, which is a probability-of-closing score assigned to each client. WhatsApp profile fields such as status, address, email and website are configurable, multiple phone numbers are supported, and the product also offers web chat channels, each behaving as a separate environment with its own playground, flow, settings and conversations.
How Did Meta Approval and Beta Testing Work?
Meta approval was the riskiest external dependency in the launch. While waiting, André added Guilherme as a beta tester of the product inside the Facebook developer configuration, which let him use the app before public approval. Meta's developer platform, documented at the WhatsApp Business Platform docs, requires app review before an app can message real users at scale, and André has complained on his channel before about how slow that process feels.
Handing the product to a real client before approval produced the moment André describes with dread: Guilherme immediately wanted to send it to his own clients, and small problems appeared. Nothing damaged the end experience, and the team kept fixing and iterating until the flow held up under real traffic.
Approval came shortly after the beta period. The sequence is worth noting for anyone planning a similar launch: build, onboard the paying client as a beta tester, iterate on real usage, then clear the platform review. The Meta app review process is a hard gate for WhatsApp products, and planning the beta around it is part of the schedule, not an afterthought.
How Were Payments and the Public Launch Handled?
Once Meta approved the app, three things remained: a payment button inside the product, a landing page, and the announcement. André added payments using Stripe, the internet payment processing platform, which handled the R$249 monthly subscription that Guilherme paid through a payment link.
With billing in place, the product was live, and the video ends with the launch moment itself. The public go-live completed the micro SaaS launch sequence: client pain, contract, three-week build, beta iteration, platform approval, billing, landing page, release. Each step was small; the sequence was the point.
The positioning also stayed narrow. The target customer is an agency that attends many clients per day on WhatsApp and repeats the same onboarding questions. That specificity is what allowed the product to be simple enough to ship in three weeks while still being worth R$249 a month to its first buyer.
Is R$15,000 MRR in One Year a Realistic Goal?
The math only requires five new paying clients per month at roughly R$249 each, compounded across twelve months. André states the goal openly in the video and admits it sounds crazy, but frames it as a customer-acquisition cadence rather than a technical challenge. His confidence rests on the product's fit for a well-defined profile: agencies drowning in repetitive WhatsApp atendimento.
Whether the target was reached is unknowable from the video alone, which was published in March 2025 and reports events as they happened. What the video does prove is the method: one paying client funded the build, the client's real workflow defined the scope, and the remaining features were cut without negotiation. For a solo developer, that ordering, contract first and platform second, is the practical lesson of the launch.
Frequently Asked Questions
- What is LeadYuu? LeadYuu is a WhatsApp chatbot for qualifying sales leads, scheduling meetings and pausing atendimento. Brazilian developer André Elias built and launched it in March 2025.
- How long did the LeadYuu build take? About three weeks of development and testing. The timeline was made possible by cutting a customizable bot UI and direct Google Calendar API integration.
- How much does LeadYuu cost? The first client, an Italian citizenship agency, paid R$249 per month with AI costs covered by the developer, after negotiating up from the client's stated R$200 budget.
- Where did the LeadYuu idea come from? A client named Guilherme saw André's Bible-study WhatsApp chatbot on LinkedIn and asked for a similar bot to automate his agency's repetitive client conversations.
- Why was Meta approval a bottleneck? WhatsApp Business products require app review from Meta before real users can be messaged at scale. André managed this by running his paying client as a beta tester while the review was pending.
- What replaced the Google Calendar API integration? A shareable Google Calendar appointment link, similar to a Calendly page, sent to clients at the right point in the conversation. It required no custom integration code.
- What is lead scoring in LeadYuu? It is a score assigned to each client based on the probability of closing a deal, configured in the product settings alongside the bot's personality and business description.
- What is the revenue goal for LeadYuu? R$15,000 in monthly recurring revenue within one year, which requires about five new paying clients per month at the launch price.
- Does André sell a template for this kind of SaaS? Yes. He offers Crazystack Typescript, a Next.js SaaS starter template, at crazystack.com.br for developers who want to skip boilerplate on similar builds.
Turn Your Own Build Story Into an Article
The most useful part of this launch story is not the product; it is the sequence of decisions a solo developer made in three weeks. If you have recorded a video walking through your own build, launch or lesson learned, that same narrative can work as a written article that reaches people who search instead of scroll.
With Skala Blog, you paste a YouTube URL, the video gets transcribed, and the transcript becomes a structured article you can review and publish. Your build story, like André's, already exists on camera; the written version is just one paste away.
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