You want to quit your dev job and build your own products, but you only have a few months of savings and no proven product. That was exactly the mistake André Elias made with his first project, Mais Vendas: three months of runway, a 3,000 recurring revenue target, and no result. His advice now is simple and direct.
Why a Developer Chose to Quit His Dev Job for Micro SaaS
A developer quits a stable dev job for micro SaaS when the limits of employment outweigh the security of a salary. In this case, workplace friction and a mentorship commitment collided with the goal of building independent products, a trade-off common among solo builders discussed on sites like Indie Hackers and MicroConf.
André Elias left his full-time remote job at a foreign company in November 2024 because two pressures converged: he had already planned to leave in January, and the relationship with management at the company had deteriorated. In a short, unedited video he described feeling worn down at work and no longer aligned with the team's direction, so both sides agreed to end the contract.
He was earning what he calls a decent salary and living comfortably, but employment limited the freedom he values. Working full time means being present every day, doing what you are paid to do, with little room to pursue your own projects. His decision to quit his dev job for micro SaaS work was therefore a mix of push and pull: workplace friction pushed him out, while his own products, his content creation, and a preference for independence pulled him forward.
It is worth naming the entities involved. A micro SaaS is a small software product, usually run by one person or a tiny team, that targets a narrow audience and aims for recurring revenue. Rocketseat is a large Brazilian education platform focused on training developers, and the mentorship deal he signed with them was one of the factors that consumed his remaining free time and accelerated the exit.
What His First Failed Product Taught Him About Runway
His first product, called Mais Vendas, failed, and he is explicit about why. He bet everything on it with only three months of income saved, promising himself he would reach 3,000 in recurring revenue by the end of that window. It did not happen. He had to look for a job again, which delayed his plans and cost him momentum.
The lesson he draws is procedural, not motivational. Arrange your employment situation first, build the product in your free time, and if the product works, use your salary to amplify what is already proving itself. Only then go all in. The failed attempt served as a warning he now repeats to anyone considering the same move: do not hand in your notice before something solid exists in your projects.
This matches a pattern many solo builders describe: a short runway creates pressure to ship fast and monetize fast, which pushes product decisions toward desperation. A salary that funds development for a year or more changes the psychology of every decision you make about the product.
How the Rocketseat Mentorship Changed His Timeline
A partnership with Rocketseat accelerated his exit. He closed a deal to give mentorships on their platform, focused on SaaS topics alongside other well-known people in the Brazilian market, and committed to being closely involved with them for the following months. That commitment consumed the free time he had left after his job, his products, and his content creation.
The arithmetic is easy to follow. A full-time remote job plus a mentorship program plus a YouTube channel plus building products is more than one person's week. Rather than drop the mentorship or slow the channel, he treated the conflict as confirmation that the planned January exit should happen sooner. The link to the mentorship was left in the video description for viewers who wanted to follow the program.
For readers mapping their own exit, the transferable point is that external commitments can be either the reason you stay or the reason you go. He chose to let a paid, structured commitment outside employment justify leaving employment, because the mentorship aligned directly with where he wanted his career to go.
The Seed-Planting Mindset for Building Products
The seed-planting mindset means treating each SaaS product as one of many seeds: you launch several, expect most to fail, and give the survivors time to grow before they bear fruit. It is a strategy of volume and patience, not a bet on a single winner, which lowers the pressure on any one launch.
The mental model he adopted is agricultural: building SaaS products is like planting seeds. You throw a seed and sometimes the soil is bad or the climate is wrong for that variety, and nothing grows. When a seed does take, there is a growth period before it bears fruit, so you give it time and you plant many of them, because the chance that at least one succeeds is higher when you plant several.
He connects this to a well-known parable of the sower from the Bible, where Jesus describes the word of God as seed that falls on different grounds: birds take some, some falls on rock, some falls among thorns and grows but is suffocated. He is a Christian and says he applies the parallel directly to his work life. Asked what he does now, his answer is a one-liner: I plant seeds.
Practically, this means he continues publishing content, keeps improving his existing products, and starts new ones, accepting that most will not take off. This overlaps with ideas like building in public and the portfolio thinking behind many indie SaaS businesses, where creators run several small bets instead of one big one. His channel had declined somewhat after an early boom, and he expects another viral video on TikTok could lift it again, but he treats the channel as one seed among several rather than the whole strategy.
His Straight Advice to Developers Who Want to Do the Same
His recommendation is a short ordered path, and it is deliberately unromantic:
- Keep your job and work on your product in your free time.
- Ship the product and watch whether it earns real recurring revenue.
- If it works, use your salary to amplify what is already working.
- Only after something solid exists, go all in.
He also warns that working a job and building at the same time is very hard and very draining. He does not soften that. The honest picture he presents includes the tension he feels now that all responsibility sits on his own shoulders, alongside the relief of being free. He frames the uncertainty in religious terms, saying he trusts that things are under God's control.
The overall shape of the advice matches what the video itself demonstrates: a failed first attempt caused by jumping too early, and a successful exit that only happened once multiple commitments and products were already in Notion. The sequence matters more than the leap.
What He Is Working On After Leaving Employment
At the time of the video, published in November 2024, his focus splits across four fronts. He runs a micro SaaS for couples, maintains a Next.js template for SaaS builders aimed at people who want a ready starting point for their own products, records content for his channel, and delivers the Rocketseat mentorship. He was also live streaming the creation of a new product from zero as the video went out.
His equipment list, shared in the video description, is modest: a MacBook Air M1, an Elgato Wave 1 microphone, and an iPhone 15 for recording. The point for readers is not the gear but the cost structure. Nothing in his setup assumes funding or a team; the whole operation is designed to run on one person's output and low overhead, which is what makes a micro SaaS path viable before revenue is stable.
FAQ
- Why did André Elias leave his job at a foreign company? He had already planned to leave in January 2025, but friction with management made the situation increasingly draining. Both sides agreed to end the contract early, in November 2024, and he committed fully to his own products and content.
- What was his first product and why did it fail? His first project was called Mais Vendas. He gave it three months of saved income with a target of 3,000 in recurring revenue, missed the target, and had to look for a job again. The lesson he draws is to build while employed and only quit once the product proves itself.
- What is the seed-planting mindset? It is the idea of launching several small products, accepting that many will fail, and giving the ones that grow time to bear fruit. He borrows the image from a biblical parable about seed falling on different kinds of ground.
- Should you quit your dev job before building a product? His answer is no. Work on the product in your free time, confirm it generates real recurring revenue, and only then leave. He warns that combining a job with building is exhausting, but that quitting first with a short runway cost him months of progress.
- What is a micro SaaS? A micro SaaS is a small software product with a narrow audience, usually operated by one person or a tiny team, that aims for recurring monthly revenue with low overhead and no large staff.
Turn Your Own Builder Story Into an Article
This article exists because one developer sat outside on a cold day, spoke for eight unedited minutes about leaving his job, and buried real lessons in that talk: runway math, seed planting, the Rocketseat mentorship that changed his timeline. Plenty of builders have videos like that, full of hard-won context that never becomes searchable text.
If you have that kind of knowledge inside your own videos, Skala Blog turns it into a written article. Paste a YouTube URL, get the transcription, and generate a structured piece like this one, ready for readers who search instead of watch.
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