Hitting $1M ARR in two years and working four hours per day
Aurélien Amacker runs a business with 3 million users and a team of 90 — and he only works four hours a day. He's never taken a dollar in funding for systeme.io, so he builds it on his own terms. And, as he says, "Growth is a means, not an objective."
Here's Aurélien on how he does it. 👇
A backwards path
I'm Aurélien Amacker, founder of systeme.io. I'm French, based in Lisbon. My path into software was backwards — I never set out to build a SaaS company.
In my twenties, I quit a corporate job, started a blog, and made a living selling online courses about building an online business. That's where I ran into the real problem: running even a simple online business required duct-taping together a landing page builder, an email tool, a membership platform, an affiliate tool, and a checkout. Five subscriptions, five logins, and many things quietly breaking in between. I eventually paid a developer to build a small internal tool for my business. It worked so well that I decided to turn it into a product.
systeme.io is an all-in-one platform for online entrepreneurs: sales funnels, email marketing, online courses, affiliate programs, e-commerce, and automations, all in a single account. We launched in April 2018. In October 2019, I did the math and realized we reached $70k MRR; by the end of our second year, we crossed $1M in ARR. And we currently have over 3 million accounts.
We achieved this bootstrapped, with no outside funding, no paid acquisition, a tiny distributed team, and a founder who couldn't code. Today, we are around 90 people.
Viewing SaaS as an investment
The courses that I was selling provided me with something most first-time SaaS founders lack: cash. I viewed it as an investment decision. Everyone around me invested in real estate, but I had no edge in that market. I was just another buyer with no particular insight, competing against full-time professionals. In software, I had an edge: I knew this exact market because I was the market, understood the flaws in existing tools, and had an audience to whom I could sell. Investing my money where I had domain expertise seemed obviously better than investing it where I had none.
It cost more than I expected. My first contractors proved a dead end, resulting in roughly a year lost with nothing usable. They could not deliver, and I took twelve months to fully accept it. I lost about $30k and, much worse, a year of my life with nothing usable. At one point they even took my email list and promoted a course to my own subscribers without asking me. I still paid them what I owed. As a parting gift, the agency's founder told me my idea was worthless and would never work.
So after a year, I had no product, no usable code, and no idea what to do next. I was close to giving up. Instead, I went to Upwork and started testing freelance developers one at a time. Most were like the agency: lots of confidence, very little delivery. Then, I found one developer who was different. When he told me something, he did it. That sounds like a low bar, but after a year of the opposite, it was everything. I also noticed something telling: other developers were slightly afraid of him and made excuses around him. He actually knew what he was doing.
I decided to trust him, and that decision is why systeme.io exists. He helped me hire a second and then a third developer. That team of three built the initial product in about a year. The timeline was the same as the agency's, with a fraction of the drama, and this time we had something real.
In total, I spent around $200k of my own money to bring systeme.io to break even. No investors, no loans. If it hadn't worked, the money would have been lost.
Its survivability stemmed from not validating in the dark. I already had an audience of people building online businesses, knew what they paid for and complained about, and could present the product to them the day it existed. This differs from market research. It's closer to building a tool for yourself and discovering thousands of others share the same problem.
Symfony talking to Java
We started with PHP and Symfony. That was the pragmatic choice at the time: my first developer knew it well, it was easy to hire for, and it let three people build a lot of product quickly. Most of the original platform — the funnel builder, email sending, courses, checkout — still runs on that foundation today.
As we grew, we moved to Java for the newer modules. The reason wasn't fashion. Some parts of an all-in-one platform are much heavier than others, particularly anything that processes large volumes in the background, and we wanted something built for that kind of load. So the architecture progressively split: the older core in Symfony, newer services in Java, talking to each other rather than one monolith doing everything.
A business model that bets against the market
We bet against the market. Instead of selling to agencies and marketing teams for $300/month, we targeted beginners — those launching their first offer — with a genuinely free plan and paid plans starting at $17. That constraint shaped everything: no add-ons, no upsells to unlock basic features, no pricing that punishes list growth. It also meant we needed to be radically simpler than the competition because our users weren't marketing operators; they were people selling their first ebook.
The free plan is not a trial with a countdown; it's a real product for running a small business. While expensive to support, it's also our best acquisition channel because people who start free and succeed tend to tell others.
Last year, we surprised people by cutting the price of our entry paid plan from $27 to $17 per month. This directly impacts short-term revenue, and no competitive pressure forced us to do it. We did it because our core mission is to enable as many people as possible to launch an online business, and $10 per month is a real barrier before you make your first sale. Being bootstrapped makes such a decision possible. Nobody needed to approve a temporary dip in revenue in exchange for a larger top of funnel and a mission we truly believe in.
Revenue expansion stems almost entirely from customer success rather than from extracting more per account. Plans are tiered by usage, mainly by contact count; customers whose businesses grow move up on their own. Nobody at systeme.io sells them anything. This aligns us with our users: we make more money when they do, and if they stagnate, we don't. Annual plans are the other lever; they cost customers less per month and provide us with upfront cash.
On the cost side, being bootstrapped shaped every decision. We employ around 90 people, are fully remote, hire talent wherever it is rather than in expensive cities, and have never had a sales team. Margins on a subscription product with no field sales and no paid acquisition are very good, and we have been profitable for years. That profitability allowed us to spend a year of engineering time on the white-label offer, where any customer can resell the entire platform under their own brand and keep 100% of the revenue, included free in their subscription. That decision cost us short-term growth, and no board asked me to justify it.
Word of mouth and affiliates
As far as growth, I'd spent years building an audience of people trying to start online businesses, selling them courses, and answering their questions. When the product was finally ready in April 2018, I launched to that list and got around 400 paying customers. That's a very unfair advantage. I solved the hardest part of a SaaS launch — finding the first few hundred people who trust you enough to give you their credit card — before I wrote a line of code. Not because I planned it, but because I'd spent five years in the same market.
After that, word of mouth and our affiliate program generated almost everything. These two are hard to separate because the affiliate program is simply word of mouth that we pay for. We started at 40% commission, raised it to 50%, and today we pay 60% recurring for the lifetime of the customer.
That last number represents our entire strategy, and it's worth explaining why we keep increasing it rather than decreasing it. Most companies treat affiliate commission as a cost to optimize. We treat it as our entire acquisition budget. We don't run ads. We don't have a sales team. So, instead of paying Facebook to interrupt strangers, we pay our own users generously, forever, for bringing us customers who already trust them. A 60% lifetime commission sounds insane until you compare it to a paid acquisition cost that buys a customer with no recommendation attached. And it's self-reinforcing in a way ads never are: our users build online businesses, our product includes an affiliate tool, so we ask them to do what we teach them to do. Some of them make a full-time income promoting us.
Content and SEO in multiple languages serve as our other quiet channel. We sell worldwide, and we invested early in translating the product and content. This made us the obvious all-in-one platform in several markets where nobody competed in the local language.
This worked so well, for so long, that we barely built anything else. When one channel gives you 30 to 50% growth every year without much effort, there's no forcing function to learn paid acquisition or build a real marketing team. Then growth slows, and you discover you have one muscle, and it's the only one. I'm fixing that now by building actual in-house marketing capability. If I could go back, I'd have started that three years earlier, while the affiliate flywheel was still masking the problem.
My advice, however, is the opposite of "diversify early." Find the one channel that fits your product structurally and push it much further than feels reasonable. For us, that meant raising commissions three times instead of protecting margin. Most people spread themselves across five channels, doing all of them badly. Go all-in on the one where you have an unfair advantage, then build the second channel before you need it.
Be suspicious of the consensus
This might be contrarian, but not being plugged in has helped me most. I know almost no other SaaS founders. I have one entrepreneur friend who built his own SaaS over the years and is very successful now, and that's it. A few years ago, in Lisbon, I met the CEO of a company that competes with us, and she asked me if I had entrepreneurs to introduce her to. I thought for a moment and realized I couldn't name anyone. I didn't have a network.
I don't think that held us back, and I now see it as an advantage. Instead, I consume a lot: podcasts, books, biographies of entrepreneurs. Not tactics for this quarter, more like general culture about how businesses get built and how people who built them think. Andrew Warner's Mixergy first put SaaS in my head, years before I acted on it. Long-form content from people who built something teaches you more than a conference conversation, and it doesn't cost you a week.
A network's downside is inheriting its consensus. When you spend your time around other founders, you chase the same things at the same time, because everyone is anxious about the same things. Being in my cave means our roadmap comes from our users and what frustrates me as an operator, not from what everyone in a group chat has decided matters this year.
The clearest example is AI. We were late, and part of that was a trade-off; we spent a year of engineering on the white-label offer instead. But part of it was deliberate: I wanted to see whether the tools were good before rebuilding our product around them. The early ones weren't. Enormous noise surrounded capabilities that didn't survive contact with real users, and many companies shipped AI features that were essentially marketing. Waiting cost us some ground, and I'm catching up now, but we're building on tools that work rather than on a demo.
I recommend protecting your attention. Read widely, follow your customers closely, and be suspicious of anything everyone in your industry agrees about simultaneously.
The combo he'd run if he were starting over today
I had two advantages most people don't: an audience and a problem I lived with daily. That created the opportunity. But if I were starting from zero today, here's what I'd do, and it's not what people want to hear.
Talk to potential customers. Get on calls. Try to sell. That's it, and almost nobody does it because it's uncomfortable, unlike building. Writing code or setting up a landing page feels like progress, and nobody rejects you while you're doing it. A sales call can end with someone telling you your idea is pointless. So people avoid the only activity that provides real information.
Push it as far as taking money. Try to presell. If you can't deliver, refund them; that's not the end of the world, and it's a far cheaper way to discover you were wrong than six months of building. Payment is the only meaningful validation. Compliments are free. If you can't get money yet, the next best signal is several different people independently describing the same pain and showing interest in the same solution. Not one enthusiastic person, but several who don't know each other.
Then use AI to build a prototype.
That's the combo I'd run today: real conversations with real people, ideally from those who have paid, plus a working prototype in front of them as fast as possible. Today's tools make prototyping accessible to non-coders, which was simply not true when I started.
From there, you have two paths. Either keep scaling it yourself, or find a technical cofounder who can build the product properly, still using AI, but with an architecture that supports thousands of users. The prototype gets you to validation. It doesn't get you to a business.
Building your product quietly in a corner and then trying to sell it doesn't work. That's the default failure mode, and it's too risky.
Growth is a means, not an objective
In the short term, my goal is AI. We're shipping our MCP server and an AI chat inside the product so users can run their funnels, emails, and courses by prompting instead of clicking. What I'm most excited about is the internal side: using these tools to make our team dramatically more productive. We can now build things that were not possible eighteen months ago, and after a year of catching up, I'm enjoying that part a lot.
Beyond that, my goals are not what people expect from a founder answering this question. I work about four hours a day. I have a balanced life. I train every day, and I cook dinner for my family almost every evening, which is a genuine hobby rather than a chore. I live in Lisbon with my kids. That's not a phase I'm passing through on the way to something more intense. It's the point.
I have no interest in building an enormous company that goes public. I have no interest in dealing with investors, board meetings, or having to justify a decision like cutting our entry plan price or giving away white label for free. Those are exactly the decisions that made systeme.io what it is, and they only happened because nobody could stop me.
So the goal is boring, and I'm fine with that: a profitable company that keeps creating real value for our customers, run by a team of people I like working with, that lets all of us have a life outside of it. If I can keep adding value and keep enjoying the work, that's the whole ambition. Growth is a means, not the objective.
Follow along
You can create a free account at systeme.io, no credit card, and the free plan is a real product rather than a countdown timer.
Otherwise, I'm on X. Happy to answer questions there, and I'll keep an eye on the comments here too.
Leave a Comment
"Treats affiliate commission as the entire acquisition budget, not a cost to minimize" is a sharper reframe than it looks at first read. Most SaaS founders treat affiliates as one channel among many and cap payouts to protect margin — Amacker basically decided the payout is the CAC and let it be generous on purpose. Explains why 30-50% growth came from word-of-mouth alone instead of paid acquisition.
Also curious how much the "$17/month for beginners instead of $300/month for agencies" call mattered early on — undercutting the obvious high-margin segment to go after the harder-to-monetize one is a bet that usually takes years to pay off, and here it compounded into 3M accounts. Would love to know at what MRR that decision started to feel obviously right instead of just directionally right.
We are looking for an individual who can lend 185,000 US dollars to our holding company.
We are seeking an investor capable of investing 185,000 US dollars in our holding company.
We will establish an animation film production company using the 185,000 US dollars you will lend to our holding company.
We will establish an animation film production company with the 185,000 US dollars you invest in our holding company.
We will use the 185,000 US dollars you invested in our holding company to establish an animation film production company, and we will have increased that investment amount within a few months.
By using the 185,000 US dollars you invested in our holding company to launch an animation film production company, we will increase the value of your investment within a few months.
We will have increased the 185,000 US dollars you invested in our holding company within a few months.
We will use the 185,000 US dollars you lent to our holding company to establish an animated film production company, and within a few months, we will significantly increase the 185,000 US dollars you lent to our holding company.
Since animated films attract significant public interest today and we intend to undertake international animation projects, the animation film production sector will generate substantial revenue for us.
Since animated films currently attract more attention and we will be working on international animated film projects, the animation production sector will provide us with significant revenue.
By establishing an animation production company, we will generate substantial revenue within a few months.
By utilizing artificial intelligence tools as well, we will be able to produce animated films more quickly.
We will produce professional-quality animated films covering a wide range of topics.
Since we will be producing animated films across many categories and in multiple languages, our viewership will increase rapidly.
Since animated films are currently very popular and we excel in the field of advertising, the animated films we produce could garner millions of views in a short time.
How will revenue be generated, and how will we increase our audience?
Since the animated films we will produce will be in many languages, it will increase the viewership of our animated films internationally.
Since we will produce animated films in many categories instead of just one, the animated films we make will receive more viewership.
We will produce animated films in at least seven different categories every year.
Since we will produce high-quality and more professional animated films, our films will be watched by millions internationally.
We will earn money per view by sharing the animated films we produce on various social media platforms such as YouTube, Instagram, Facebook, and TikTok.
Since the animated films we will produce will be in many languages, we will earn money per ticket by screening our animated films in cinemas of many countries.
We will earn revenue per ticket by screening the animated films we produce in movie theaters across many countries.
By releasing the animated films we produce on various streaming platforms such as Netflix and Amazon Prime, we will generate significant revenue.
We will release the films we produce on our own website; through a paid subscription model, viewers wishing to watch our animated films will purchase subscriptions, thereby generating revenue for us.
As the audience for the animated films we produce grows, we will generate significant revenue by promoting sponsors' products in our future animated films.
By embedding trailers of the animated films we produce onto blogs and news sites, we will increase the international viewership of our animated films.
By promoting our animated films on various high-traffic websites and social media accounts, we will achieve a large audience.
By using advertising tools such as Google Ads, YouTube Ads, and Facebook Ads, we will be able to introduce our animated films to the entire world more quickly.
As our fan base grows, we will generate extra revenue by producing and selling products—such as toys, mugs, and sweaters—featuring the characters from our animated films.
We will generate significant revenue by broadcasting our animated films on television channels in many countries.
By employing a very strong marketing strategy, we will generate millions of dollars in revenue from the animated film industry in a short time.
How will the process work?
First, we will establish an educational website offering professional-level training in animated film production.
Even someone with absolutely no knowledge of making animated films can become a professional within one month by studying the animation course on our training site.
We will train and hire our own animation production staff.
Since we will train our team ourselves, we will be able to work in a more coordinated manner, which will enable us to complete the animated films we produce more quickly.
Within two months, we will have trained and recruited staff to establish our own animation film production team.
We will assemble a professional-level animated film production team within two months.
Within two months of assembling our animation film production team, we will produce professionally designed animated films covering various topics and in multiple languages
We will produce animated films in at least 7 different categories within two months.
Once our animated films are completed, we will release them in various places and start earning money within two months.
We will generate substantial profits within two months of completing our animated films, thanks to our strong marketing strategy.
Within two months, we will rapidly generate substantial revenue by releasing our film on platforms such as Netflix, Amazon Prime, TikTok, Instagram, and YouTube, as well as in movie theaters across many countries.
One month after releasing our animated film internationally, we will generate revenue of at least 7 million US dollars.
We will generate at least 7,000,000 US dollars in revenue one month after releasing our animated films in many countries.
Since the animated films we produce will be in multiple languages and across various categories, they will quickly garner high viewership.
Today, animation film production companies generate average annual earnings of at least 800 million US dollars.
Thanks to our strong advertising tactics, we will generate more revenue in the future.
We will have generated at least 7,000,000 US dollars in revenue within a total of 7 months.
How much income will you generate by investing 185,000 US dollars in our holding company?
If you lend 185,000 US dollars to our holding, I will return your money as 370,000 US dollars on 30/04/2027.
If you invest 185,000 US dollars in our holding, I will return your money as 370,000 US dollars on 30.04.2027.
We will increase the 185,000 US dollars you have lent to our holding company by utilizing it in the animated film production sector, and I will return the funds to you as 370,000 US dollars on April 30, 2027.
I will return your money to you as 370,000 US dollars on April 30, 2027.
April 30, 2027, is the date we will repay your money.
You will have generated twice as much revenue within a few months.
I will repay you the 185,000 US dollars you lent to our holding company as 370,000 US dollars when the date of April 30, 2027, arrives.
We will invest the 185,000 US dollars you have lent to our holding company into the animated film production sector to further increase the amount, and when April 30, 2027, arrives, I will return the money to you as 370,000 US dollars.
By investing 185,000 US dollars in our holding company, you will generate substantial returns in a short period—don't miss this opportunity.
How to contact us:
To learn how you can grow your money by investing in our holding company, send a message to my Telegram username, Signal number, or email address listed below, and I will provide you with detailed information.
To learn more about our animated film project and how you can invest 185,000 US dollars in our holding, send a message to my Telegram username, Signal contact number, or email address below, and I will provide you with detailed information.
To learn how you can lend 185,000 US dollars to our holding and increase your money even more within a few months, and to get detailed information, send a message to my Telegram username, Signal contact number, or email address below, and I will provide you with detailed information.
Send us a message via Telegram, Signal, or email for detailed information.
I have listed our contact details below; you can obtain detailed information by sending a message to any of them.
To learn how you can lend 185,000 US dollars to our holding and to get detailed information about our animated film project, send a message to my Telegram username, Signal contact number, or email address below, and I will provide you with detailed information.
To learn how you can further increase your money within a few months by investing 185,000 US dollars in our holding and to get detailed information about our animated film production project, send a message to my telegram username, signal username, or email address below.
To learn how you can increase your money, send a message to my Telegram username, Signal contact number, or email address below.
My Telegram username:
@adenholding
Signal contact number:
+447842572711
Signal username:
adenholding.88
WOOu
The point about 'inheriting consensus' by spending too much time in founder networks is so true. Staying out of the hype cycles allowed you to make contrarian moves like giving away white-label for free and waiting for AI tools to mature before rebuilding your stack. Splitting Symfony for the core UI and Java for heavy background job processing is super pragmatic architecture. Huge respect for building a 3M+ user platform while keeping a 4-hour workday.
The part about viewing SaaS as an investment really stood out to me. Having domain expertise and already understanding the customer’s pain seems like a much stronger starting advantage than simply chasing whatever market looks hot.
I also like the “growth is a means, not an objective” philosophy. Building a $3M+ user business while still protecting your own time is a very different definition of success than simply maximizing revenue or headcount.
The lesson about losing a year and $30k on contractors is painful, but probably one of those experiences that permanently changes how you evaluate people and execution.
The combination of bootstrapping, owning the customer relationship, and using word of mouth/affiliates instead of relying heavily on paid acquisition is especially impressive. Great case study for founders who want to build on their own terms. 👏
This is a remarkably effective business flywheel: teach people how to make money online, sell them the software required to follow the method, then pay them recurring commissions to bring in the next group of people who want to make money online.
This is really inspiring. I'm just starting my own side project and seeing how you grew to $1M ARR in two years gives me a lot of motivation. One question: did you focus on organic traffic from day one, or did you invest in paid acquisition early? Would love to learn more about your growth strategy.
Really valuable perspective. Building around customer success, strong word-of-mouth, and solving real user problems is a lesson many SaaS founders can learn from. Sustainable growth always starts with delivering genuine value.
This was really interesting. Having an audience before building the product seems like such a huge advantage.
If you had to start again today with no audience and almost no money for marketing, what would you do to get your first customers?
Great question. If I were starting from zero today, I would focus less on marketing and more on conversations. I’d talk to potential customers, understand their biggest problems, validate the idea, and try to get the first few paying users manually. Once you find a small group of people who truly need the solution, word of mouth becomes much easier to build. The first customers usually come from relationships and solving real problems, not from ads.
The "find your one channel and go all-in" advice makes total sense when you already have an audience to launch to, like you did. I'm curious how you'd apply that same logic to someone starting a two-sided marketplace with zero pre-existing audience on either side — hosts or guests.
Does the "one channel, pushed hard" principle still hold when there's no audience to leverage from day one, or does the early phase necessarily need to look more scattershot until something click before you can commit fully to it?
The “push it as far as taking money” point is probably the biggest takeaway here. A lot of founders spend months validating with likes, waitlists, and positive feedback, when willingness to pay is a much stronger signal. The combination of customer conversations + a fast AI-built prototype is a very practical approach to reducing wasted engineering time.
The internal tool to product path resonates a lot. We built ours for a GIS consultancy's own project work - coordinate conversion, format conversion, that kind of thing - because standing up a full desktop GIS install for one five-minute task got old fast. We only decided to open it up publicly once we noticed we were reaching for it ourselves more than any of the "real" commercial tools we already had licenses for.
The "free plan as a real product, not a countdown" point stands out too - we're doing the same for a similar reason: a lot of our likely users are students, junior surveyors, or small teams who can't justify a full GIS license just to try something once. If it's genuinely useful the first time, they come back; if it's gated behind a trial, they never get past the first friction point.
Appreciate the honesty on how long "validate in the dark" vs. "the audience already has the problem" took to actually pay off - feels like the kind of thing that's obvious in hindsight and invisible while you're in it.
“Growth is a means, not the objective” is one of my favorite lines from your story. I love seeing a founder define success as building a profitable business that also leaves room for an actual life, rather than endlessly chasing the next number. And doing that with 3M users and a team of 90 makes the point even stronger. Thanks for sharing!
The decision to split the architecture between a core Symfony app and Java microservices for heavy background loads is a great technical lesson. How are you handling load balancing between the two as you prepare to launch the internal AI chat and MCP server tools?
The most useful tension here is one you leave unresolved, and I think it's the actual hard part. Your headline advice is "find the one channel that fits and push it further than feels reasonable." But your one regret is that the affiliate flywheel masked a missing muscle for three years. Those are the same situation from two sides: a channel doing 30-50% a year both is the one to push further AND is hiding your fragility, and in the moment they look identical.
So the question your essay raises but doesn't answer: how do you tell them apart in real time? "Push the winning channel" and "the winning channel is my only muscle" produce opposite actions from the same data. Waiting for growth to slow works, but by then you've lost the three years.
My guess is the tell isn't the channel's performance, it's the counterfactual: not "is this still growing" but "if it stopped tomorrow, how long until I had a second one." You can be crushing it and still be one dependency from stalling. The regret wasn't pushing affiliates too hard, it was not starting channel two while channel one masked the need.
Is that the signal, or was there an earlier one you'd have caught outside the cave?
Reaching $1M ARR in two years while working four hours a day requires a highly focused business model, strong automation, and careful prioritization.
Consistent customer acquisition, scalable systems, and delegation can help maintain growth without extending daily working hours.
I particularly appreciate your perspective of "viewing software as an investment," as well as your persistence in finding a reliable development partner despite having no technical background. This provides valuable lessons for many non-technical founders.
This is such a refreshing perspective on building a sustainable business. The idea that growth is a means, not the objective, really stood out to me. Focusing on customers, profitability, and freedom over chasing growth at all costs is a powerful lesson.
The core insight about validating by getting people to pay—not compliments—is exactly right. But it goes deeper: you're choosing which measurement determines what you learn. By measuring "willingness to pay" instead of "interest clicks," you're betting that financial commitment reveals the truth about product-market fit in a way social approval never can. That's not just validation, it's a measurement choice that forces clarity. Every founder who solves the wrong problem with high velocity is still solving the wrong problem.
the 60% affiliate commission reframe is the real insight here. most founders see affiliates as a cost to minimize. treating it as your entire acquisition budget and just paying more than everyone else is so counterintuitive it works — you're buying word-of-mouth at scale without the CAC volatility of paid ads. curious how the unit economics hold as the price point compresses margins though
Running a 90-person team with 3 million users on a 4-hour workday is the ultimate masterclass in leverage! Treating affiliate commission as your entire acquisition budget by giving away a 60% recurring lifetime payout is brilliant business design.
The decision to split the architecture between a core Symfony app and Java microservices for heavy background loads is a great technical lesson. How are you handling load balancing between the two as you prepare to launch the internal AI chat and MCP server tools?
Running a 90-person team with 3 million users on a 4-hour workday is the ultimate masterclass in leverage! Treating affiliate commission as your entire acquisition budget by giving away a 60% recurring lifetime payout is brilliant business design.
The decision to split the architecture between a core Symfony app and Java microservices for heavy background loads is a great technical lesson. How are you handling load balancing between the two as you prepare to launch the internal AI chat and MCP server tools?
Running a 90-person team with 3 million users on a 4-hour workday is the ultimate masterclass in leverage! Treating affiliate commission as your entire acquisition budget by giving away a 60% recurring lifetime payout is brilliant business design.
The decision to split the architecture between a core Symfony app and Java microservices for heavy background loads is a great technical lesson. How are you handling load balancing between the two as you prepare to launch the internal AI chat and MCP server tools?
What a phenomenal story, Aurélien! Spending $200k of course revenue to bootstrap systeme.io to profitability without taking a dime in VC funding gives you total freedom—cutting your entry plan to $17/mo and offering white-label features for free is proof of that freedom in action.
Loved the reminder that 'growth is a means, not an objective.' Massive respect for building a massive business while keeping life centered around family and balance.
What a phenomenal story, Aurélien! Spending $200k
What a phenomenal story, Aurélien! Spending $200k of course revenue to bootstrap systeme.io to profitability without taking a dime in VC funding gives you total freedom—cutting your entry plan to $17/mo and offering white-label features for free is proof of that freedom in action.
Loved the reminder that 'growth is a means, not an objective.' Massive respect for building a massive business while keeping life centered around family and balance.
I visited your platform and it was awesome. and your will too. As a ML engineer I am very interested in your AI plan about your platform. I really hope to discuss about it together. thank you. Dexter Wei
The four-hours-a-day part only holds up because he had 90 people and no funding pressure, which is a very different constraint set to a solo founder. Curious what the schedule looked like in year one, before the team existed — that's the stretch most of us are actually stuck in.
The affiliate strategy you described is the most honest framing of acquisition cost I've read. "Instead of paying Facebook to interrupt strangers,
we pay our own users generously, forever, for bringing us customers who already trust them." Most founders treat affiliate commission as a cost to minimize. You treated it as the entire budget. That reframe changes every decision downstream. The part that resonated most: your observation about one-channel dependency. You had a flywheel that gave you 30-50% growth annually — and that success masked the fact that you never built a second muscle. I'm at the opposite end of this journey — just launched a digital product for SaaS founders (email templates) with zero audience and zero channel. Building the audience before the product is clearly the right order.
You confirmed what I suspected but hadn't seen stated this clearly.
One question: when you talk about building "actual in-house marketing capability" now — what does that look like practically for a bootstrapped team that has never needed it? Is it content, paid, or something else entirely?
What stood out to me most wasn’t the $1M ARR — it was the idea that “growth is a means, not an objective.”
Bootstrapping, staying profitable, and designing the business around the life you actually want feels much more sustainable than chasing growth at any cost.
Also interesting that word of mouth and affiliates played such a big role. A good reminder that distribution doesn’t always have to mean paid acquisition.
Great story and a lot to learn from here.
Great read, a masterclass of bootstrapping really impressed
The idea that affiliate commissions should be counted as the acquisition budget, not just a small add‑on to growth marketing is really insightful. Most founders see affiliates as a side channel giving them 10‑20% of the budget and then wondering why no one is promoting them. Offering a 60% recurring commission for life may look crazy at first. When you add zero paid ads, zero sales team and a high LTV on bootstrapped infrastructure the numbers make perfect sense. This approach matches the user’s success with the product’s growth. Thanks, for sharing this breakdown James and Aurélien!
Really appreciate how honest this is about the year lost to the agency — that's the kind of detail most "how I built it" posts skip over. The line that stuck with me most is "be suspicious of anything everyone in your industry agrees about simultaneously." I don't have a SaaS to compare against, but I recognize the same trap building as a side project — it's easy to over-index on what's trendy in the maker/indie space instead of trusting what your own users are actually telling you. Curious about one thing: when you were deliberately staying "unplugged" from other founders for years, did you ever worry you were missing something important, or did it only ever feel like the right call in hindsight?
Well worth the read. Thank you for sharing.
So the agency founder took his money, stole his email list, and then told him his idea was worthless. I wonder if that guy is still sending desperate cold outreach emails on LinkedIn while Aurélien is prepping dinner at 3 PM after his grueling four-hour workday. Talk about the ultimate 'living well is the best revenge' story.
Honestly, paying 60% recurring commissions to affiliates is such a power move too—it's basically saying, 'Hey Facebook, keep your overpriced ads, I'm going to make my own users rich instead.' Love the absolute defiance of the standard SaaS playbook.
What I know is that anyone who has built an audience will be successful...
hgj
The "talk to people, try to sell, then build a prototype" sequence is the part that hit me hardest. It's uncomfortable precisely because it's the only step that can reject you — building never does. I've been on the other side, months of polishing something nobody validated, and "payment is the only meaningful validation" is a line I'll keep.
The detail I'll carry: an agency founder told you your idea was worthless. Three million accounts later.
Absolutely agree. The biggest mistake founders make is building first and validating later. Real conversations and customer feedback are the foundation of any successful product. This is a topic we also cover on Incomrise through practical insights about online business and growth strategies.
The path he describes, real conversations, presell, then prototype, is the part most founders actually follow now. The part they skip is the sentence after it: the prototype gets you to validation, it doesn't get you to a business.
What I keep seeing is founders who vibe-coded their way to real users and then discovered the gap. The product works well enough to validate demand but not well enough to scale, add features, or hand to a new developer without starting over. The AI that built it had no memory across sessions, so the codebase has no coherent architecture behind it. It's a prototype that users started paying for.
The decision Aurélien describes, finding someone who actually delivers and trusting them is exactly where those founders get stuck. After a year of vibe coding, most of them don't even know what good technical delivery looks like or how to evaluate it.
The audience-first part is the bit I’d steal here. I’ve found distribution gets much easier when the product comes from a problem you already understand.
superb
I was particularly impressed by the statement that "payment is the only meaningful validation." As a developer, writing code itself feels like progress, making it easy to get bogged down in development for months; however, communicating directly with potential customers is often uncomfortable.
I liked the approach of conversing with customers, driving them to make a purchase, and then using AI to create a prototype. I believe this is a much more effective way to utilize AI than simply developing tools separately and hoping people will want them later.
Furthermore, the story of developing Systeme.io based on problems experienced firsthand serves as a good example demonstrating that expertise in a specific field can be a far greater asset than a perfect startup idea.
The focus on conversing with customers and driving them to make a purchase in the outset is uncomfortable truth that I needed to hear. I've been working on a tool for the past month plus with only 2 beta testers while I continually tweak. The model of building to MVP, getting some initial paid users and then refunding them if doesn't work out is scary, but quicker route to market approach than I'm currently taking right now.
Yes, I agree. It is certainly inconvenient to ask people to pay before everything feels "ready," but I think that very inconvenience makes this approach useful. It is much better to find out early if people are actually willing to pay than to spend months refining something nobody needs. I wish you success with the launch!
$1M ARR in 4h/day only works if the product doesn't break. I spent 3 days fixing an AI scoring bug instead of chasing traffic.
Speed of iteration > hours worked. But only if you're iterating on the right thing.
Honestly i just make my acc and saw your post , its really amazing to see people are doing great
This was a beautiful profile. I love his clear ethos, especially on commissions.
This is a great example of how a “backwards” path can actually become a huge advantage. You didn’t start with a SaaS idea and then search for a market—you already understood the market, experienced the pain yourself, and had an audience ready to use the solution.
The part that stood out most to me was the lesson about validation: getting people to pay is far more meaningful than getting compliments. The combination of real customer conversations, presales, and a fast AI-built prototype is especially relevant today.
I also like the point about not blindly following industry consensus. Building around what your customers actually need instead of chasing every trend seems like a much healthier long-term approach.
And the final perspective—growth as a means rather than the objective—is probably the most refreshing part of the whole story. A profitable business that creates value while still leaving room for family and life is a pretty compelling definition of success.
The part about talking to people and trying to sell first ---I've seen that fail so many time.People build for months and then realize nobody wanted it.
My path was a bit different though. I built a Windows security tool because I had a specific problem --- a friend's suermarket got hit with ransomware and nothing out there did what I needed. So I didn't need to go looking for validation. The problem was already there.
Still, I agree with the core point. If you're not the market yourself, you better talk to people before you start building. And the "be suspicious of consensus" thing — yeah. Too many founders end up building whatever everyone else is building because they're all in the same rooms.
The “talk to people, try to sell, then prototype” sequence really stood out to me. It’s easy to mistake building for progress because you get a sense of accomplishment without having to face rejection.
I also like the distinction between compliments and actual validation. Someone saying they would use your product is very different from someone being willing to pay for it.
For a solo founder, I think this is especially important. Building the wrong thing for 6 months is much more expensive than spending a few uncomfortable weeks talking to potential users first.
The idea of using AI to get a prototype in front of those users quickly makes this approach even more practical today. Really useful framework.
what was your initial marketing strategy when you launch your product ?
Honestly i just make my acc and saw your post , its really amazing to see people are thriving
Aurélien — the part I keep re-reading is the price cut. $27 to $17, no competitive pressure, revenue down on purpose, because $10 a month is a real barrier before someone makes their first sale. Then the line that explains it: "Nobody needed to approve a temporary dip." That's the whole case for bootstrapping in two sentences.
But the part that actually changed something for me is your combo for starting over: talk to people, try to sell, then prototype.
I've been running it backwards. I'm in Brazil, building alone. I have a newsletter live — legal pages, bilingual, the whole publishing rail built, two full editions written and sourced down to the PubMed IDs. My list has one subscriber: me, from a test in May. The first edition has been sitting as a draft, one click from sending, since May 29.
Building was the comfortable part. Nobody rejects you while you're doing it. I think I already knew that and preferred not to.
So I'm inverting it. Find the problem and the buyer first. Build the fastest thing someone can pay for. Get it in front of people early enough that a "no" still costs me nothing.
The detail I'll carry: an agency founder told you your idea was worthless. Three million accounts later.
Sending that edition this week. Thank you for writing this.
The distinction between finding the channel that fits your product structurally and simply “diversifying” is really important. A channel can work exceptionally well for years because it matches how customers naturally discover and recommend the product.
But the second-channel lesson is just as valuable. You don't necessarily need five acquisition channels early on — you need one strong channel and enough time to build another before the first one starts slowing down.
Amazing, from selling courses to running your own SaaS, major props.
This is an incredible breakdown, especially the part about the difference between dealing with agencies versus finding that one reliable developer who actually delivers. As a solo full-stack developer currently building and launching my own utility tools, the insight on 'not validating in the dark' and focusing entirely on real pain points rather than following industry consensus hits home. The 60% affiliate flywheel and bootstrapping approach without outside control is pure gold. Thanks for sharing this reality check!
Super inspiring!
The detail about duct-taping five subscriptions together and having things quietly break in between is the most accurate description of running a solo business I've ever read. It is the silent killer of early operators.
I’ve been obsessed with this exact problem lately—how fragmented admin work (managing tasks in one app, tracking time in another, and billing in a third) creates massive operational drag. It stops being software and just becomes a second, unpaid job. Building a unified environment to completely eliminate that friction is the only way out.
But the most inspiring takeaway here isn't the rapid path to $1M ARR or the massive affiliate engine; it's the 4-hour workday and cooking dinner for your family. Using your own software's efficiency to buy back your time and protect your lifestyle, rather than just scaling for the sake of an exit, is the ultimate ROI.
Thank you for proving that the calm, anti-consensus, bootstrapped path isn't just viable, but actually preferable.
The line about affiliate commission being your entire acquisition budget rather than a cost to optimize is such a mindset shift. Most founders protect margin on that number; you did the opposite three times and it paid off.
Also really respect the wait and see if AI tools actually work before rebuilding around them call. Took guts to eat that short-term cost instead of chasing the hype cycle everyone else was in.
The affiliate commission reframe is the most underrated insight in this post. Not "we pay 60% commission" but "our affiliate commission IS our entire acquisition budget." Most companies treat affiliate as a cost centre to optimise down. Paying affiliates generously when they are also your users and your product teaches people to sell online compounds differently than paying for ads.
The MCP server note is what I am most curious about. Running funnels by prompting instead of clicking is actually a hard problem - not the LLM layer but figuring out what a natural language instruction means in terms of actual tool calls inside your product. Building in the voice-to-action space myself at genie007.com and the disambiguation layer is where most of these systems require the most iteration.
Is the MCP server exposing specific tool primitives or a more conversational layer over existing workflows? Curious how you are approaching the scope boundary.
The affiliate commission reframe is the most underrated insight in this post. Not "we pay 60% commission" but "our affiliate commission IS our entire acquisition budget." Most companies treat affiliate as a cost centre to optimise down. If your affiliates are your users and your product teaches people to sell online, paying them well to promote you compounds differently than paying Facebook. You get a recommendation with trust attached, not an interruption. Raising commissions three times instead of protecting margin is the opposite of what most people do.
The MCP server note is what I am most curious about. Running funnels by prompting instead of clicking is actually a hard problem - not the LLM layer but figuring out what a natural language instruction means in terms of actual tool calls inside your product. Building in the voice-to-action space myself at genie007.com and the disambiguation layer is where most of these systems require the most iteration.
One question: is the MCP server exposing specific tool primitives or a more conversational layer over existing workflows? Curious how you are approaching the scope boundary.
The affiliate commission reframe is the most underrated insight in this post. Not "we pay 60% commission" but "our affiliate commission IS our entire acquisition budget." Most companies treat affiliate as a cost centre to optimise down. If your affiliates are your users and your product teaches people to sell online, paying them well to promote you compounds differently than paying Facebook. You get a recommendation with trust attached, not an interruption. Raising commissions three times instead of protecting margin is the opposite of what most people do.
The MCP server note is what I am most curious about. Running funnels by prompting instead of clicking is actually a hard problem - not the LLM layer but figuring out what a natural language instruction means in terms of actual tool calls inside your product. Building in the voice-to-action space myself at genie007.com and the disambiguation layer is where most of these systems require the most iteration.
One question: is the MCP server exposing specific tool primitives or a more conversational layer over existing workflows? Curious how you are approaching the scope boundary.