Marc Lou: From 20+ Failed Projects to $80K+/mo Solo Portfolio
French indie maker who ships fast, shares numbers publicly, and now runs TrustMRR, DataFast, CodeFast and ShipFast — all solo.
- MRR
- $50K–$80K+
- ARR
- $1M+ (2025)
- Users
- 20k+ across products
- Founded
- 2023 (ShipFast)
- Team
- Solo
- Stack
- Next.js, Stripe, Vercel, Cursor
What is your current portfolio and how did it start?
I run a portfolio of micro-products aimed at indie makers and developers. The main ones right now are TrustMRR (a verified-revenue marketplace and ad-supported board), DataFast (analytics for startups), CodeFast (a practical coding course), and ShipFast (the Next.js boilerplate that started it all). There are smaller products too — Indie Page, Zenvoice, ByeDispute, and experiments that come and go. Everything is solo, bootstrapped, and I publish the numbers every month.
The real starting point was ShipFast in 2023. Before that I had launched roughly twenty projects that made almost nothing. I waited tables in France, lived with my parents between attempts, spent time at a VC-backed AI company that produced zero customers, and eventually moved to Bali with limited savings. I copied the build-in-public style of people like Pieter Levels and just kept shipping. Most launches were ignored. A few made a couple hundred dollars. Then ShipFast happened.
ShipFast was not a brand-new idea. It was the accumulation of two years of rebuilding the same boring pieces — auth, Stripe, emails, landing page, dashboard shell — for every new project. I packaged that internal stack into a reusable boilerplate, priced it, and launched it to the audience I had already been talking to for years. The first 48 hours made more money than I had earned in the entire previous year. The first month was around $40k. That single product changed how I thought about risk and volume.
How do you decide what to build next?
I listen more than I invent. TrustMRR is the clearest example. Pieter Levels posted about fake MRR screenshots. I woke up still thinking about it. I care about trust because I share my own numbers. So I opened Cursor, used my own ShipFast boilerplate, and in about a day had a page where founders could connect a read-only Stripe key and get a verified revenue page. I launched it with almost no monetization plan. I added a few sidebar ad spots at $299 a month. As the tweet grew I raised the price. Within days the spots sold out and the project had made over $20k. Later I added a 3% acquisition fee when founders started selling through the board. It became my largest product.
I do not spend months on formal validation. I ship a usable version, put a price on it, and watch whether people pay. If they pay, I improve it. If they do not, I move on. The audience and the public posting act as the filter. Ideas that get no engagement or no sales die quickly. Ideas that get both get more of my time.
What’s the real advantage of building in public?
Distribution is the advantage. My X account and newsletter are the engine. When I launch, a portion of the first buyers already know who I am and have followed the journey. That first $6k–$20k in the opening days is not pure luck — it is the result of years of posting daily, sharing failures, and being consistent when almost nobody was watching.
The downside is obvious: people copy fast. Features, positioning, even pricing get mirrored within weeks. So I treat every successful product as temporary. I keep shipping the next thing instead of trying to defend one product forever. ShipFast was once the majority of revenue. Later TrustMRR and DataFast took the lead. The portfolio shifts. The audience stays.
Building in public also forces honesty. When the numbers are public, you cannot hide a bad month or a dying product. That pressure is useful. It keeps me from staying too long on something that is no longer working.
How do you actually work day to day?
I keep the stack simple and the tools modern. Next.js, Stripe, Vercel, and a lot of Cursor for the coding speed. I do not maintain large teams or complex infrastructure. Most products are designed so that one person can understand the whole system. Support is handled with clear docs, templates, and a willingness to say no to custom requests that do not scale.
I batch work. I ship features or new products in focused bursts, then switch to distribution and support. I do not try to do everything every day. The goal is to keep the portfolio moving, not to perfect any single line of code.
Margins matter. Most of these products run at very high margins because the marginal cost of software is low and I do not have payroll for a large team. That gives room to experiment and to survive when one product slows down.
What changed after the first big win?
After ShipFast I stopped searching for “the one perfect product.” I started treating launches as a portfolio strategy. Some products will be big for a while and then decline. Others will appear from nowhere and take the lead. The job is to keep the overall number healthy and to keep learning what the audience actually wants to pay for.
AI changed the speed. I can now vibe-code prototypes in hours that used to take days. That makes the cost of an experiment lower, so I can afford more experiments. It also means competition appears faster, which is another reason not to bet everything on one product.
What would you tell someone starting today?
Ship something this week. Charge money even if the price feels low. Post the numbers even if they are embarrassing. Most people never get past the “almost ready” stage. They polish, they wait for the perfect domain, they wait for the perfect landing page. The people who win are the ones who keep shipping after the first ten projects fail.
Build an audience while you are still failing. The audience compounds. The products rotate. Never bet your entire future on a single product. Build a portfolio, keep the margins high, and treat every launch as both a product and a marketing event.
Finally, be honest in public. The trust you build by sharing the real numbers — good and bad — is worth more than any individual feature. People buy from people they feel they know. That is still the strongest advantage a solo founder has.
More stories
Meta
The Portfolio Pattern: Why Top Indie Makers Run Multiple Products
Product Origin
Marc Lou: The Week ShipFast Changed Everything
Mature
Pieter Levels (Part 2): Nomad List & Remote OK — The Original Audience Engine
Profitable
Jon Yongfook: Bannerbear — Automated Image Generation to Solid ARR
Educator + Builder
Arvid Kahl: From FeedbackPanda Exit to Teaching Bootstrappers
Early Growth
Fernando Mendes: ScanQueue — QR Queues for Real Businesses
Scale
Danny Postma: HeadshotPro — AI Headshots to Six-Figure Months
Scale
Tony Dinh: TypingMind from 5-Day Build to $130K+/mo
Mature Solo