Basics
| Item | Details |
|---|---|
| Founder | Marc Lou (French, @marc_louvion) |
| Products | ShipFast (SaaS template), CodeFast (coding course), DataFast (data platform), TrustMRR (startup acquisition marketplace), and 13+ more |
| Team size | 1 person (zero employees) |
| Revenue | $1,032,000 in 2025; $81,683 in Feb 2026 |
| Feb 2026 breakdown | TrustMRR $33.3K, DataFast $19.7K, CodeFast $14.9K, ShipFast $8.8K, Twitter $3.2K |
| AI stack | Cursor (primary coding tool) |
| Source | Marc Lou Newsletter / LinkedIn Feb 2026 update |
Storyline
Background: Marc Lou is a French indie hacker who lives by the “ship fast, fail fast” indie philosophy. Over 3 years he shipped 25 projects, 12 of which made money — roughly 48%, well above the traditional ~10% startup hit rate. His strategy isn’t “find one perfect product and go all in” — it’s “hedge single-product risk with volume.”
Turning point: 2024 was Marc’s breakout year — ShipFast (Next.js SaaS template) and CodeFast (coding course) became the twin revenue engines, breaking $1M combined. Then in 2026 came an interesting structural shift: TrustMRR (a startup acquisition marketplace that charges 3% transaction commission) quietly became his #1 revenue source, overtaking all code products. That means Marc’s business model has upgraded from “sell tools to developers” to “run the marketplace for the developer ecosystem” — from mining gold to selling water to building the exchange.
Outcome: $1,032,000 for full-year 2025. $81,683 in February 2026 alone, ~$980K annualized. The revenue mix has tilted from product sales toward platform commission. 100K+ Twitter/X followers form the core distribution engine of his Build in Public flywheel.
Workflow Breakdown
Minimum loop analysis
| Step | What he did | AI involvement | Notes |
|---|---|---|---|
| 1. Think it through | Picks topics from his own needs (“if I need it, others probably do too”) | Low | Relies on instinct and community feedback |
| 2. Write a spec | Minimal — “ship if it works,” no detailed spec | Low | Marc’s style is anti-spec |
| 3. Implement | Cursor + AI “Vibe Coding” for rapid prototyping | High (~80%) | 25 projects in 3 years means roughly one every 6 weeks |
| 4. Validate | Launch on Product Hunt + Twitter/X, watch first-week metrics | Low | Social media feedback as the validation signal |
| 5. Iterate | Iterate on products with traction; abandon the rest | Medium | Ruthless culling: 13 of 25 projects were dropped |
Tool stack
- Cursor: primary coding tool. Across 25 fast iterations, Cursor’s AI completions drive dev speed far beyond traditional developers.
- Next.js: nearly every project uses the same stack, lowering switching cost.
- Twitter/X (100K+ followers): Marc’s biggest “tool” isn’t AI — it’s social distribution. Every new product launch gets 100K+ free impressions.
Roles one person carried
| Role | AI replacement | Notes |
|---|---|---|
| Development | 80% | Cursor speeds things up; architecture decisions are human |
| Product | 10% | Topic and positioning are fully human |
| Marketing | 30% | Build in Public content strategy + AI-assisted copy |
| Design | 60% | Template-driven design + AI assistance |
| Customer support | 70% | Automation + community-driven |
3 Reproducible Key Moves
-
“Product factory” mode — hedge risk with volume: Single-product hit rate is ~10–15%, but 12 profitable out of 25 = portfolio strategy wins. This is the extreme application of the minimum loop — every product is one fast validation. How to do it: set a “2-week rule” — ship an MVP and launch within 2 weeks, abandon it if there’s no traction in week one. AI coding tools make this speed possible.
-
“Sell shovels” beats “mine gold”: ShipFast (a SaaS template) doesn’t build a SaaS — it sells the tool for building SaaSes. The buyers are other indie hackers — a market that keeps growing. How to do it: watch the recurring pain points in your community → package a problem you’ve already solved and sell it to others.
-
Build in Public is the cheapest distribution: Marc spends $0 on ads; 100K+ followers = free impressions on every launch. But Build in Public requires continuous, authentic content — revenue screenshots, failures, lessons learned. It’s not a “post once and done” strategy — it’s 2–3 years of compounding. How to do it: post one thing on Twitter/X every day from what you did that day. Authentic beats polished.
Limits and risks
- Build in Public requires long-term investment: Marc’s 100K+ followers are the product of 3+ years. Without a distribution base, a newcomer’s first product-factory products will struggle to get attention.
- Inter-product competition: 25 products means attention and maintenance are extremely diluted. Marc pulls it off because most products are minimalist and automated — but each one’s moat is shallow.
- Revenue-model pivot risk: Shifting from code products to TrustMRR (platform commission) means Marc is entering an unfamiliar domain (deal brokerage) with more established competitors (Acquire.com, MicroAcquire).
- Self-reported numbers: All revenue numbers are self-reported, with no third-party audit. The indie hacker community has a pervasive “only post good news” survivorship bias.