Marc Lou made 1.23 million dollars in twelve months as a one-person studio

AI Summary

Marc Lou’s own revenue panel shows $1,234,900 across the twelve months to November 2026, built from 43 products shipped solo since 2021 with no employees and a stated 90 per cent gross margin. Three products carry most of the weight: TrustMRR at $35,608 a month, DataFast at $29,188 and Ship or Die at $16,397. The structure, not the total, is the lesson. A portfolio of small products spreads the risk of any one failing, and the reader can copy the structure without copying the income.

What happened

Marc Lou publishes a live revenue panel on his personal site. Read on 7 November 2026, it shows $1,234,900 in revenue across the twelve months to November 2026. The same page lists his products with their last-30-day revenue, and states a team size of zero employees and a gross margin of 90 per cent.

The product list is the interesting part. TrustMRR, a product he runs, shows $35,608 a month. DataFast shows $29,188 a month. Ship or Die shows $16,397 a month. ShipFast, the product most readers outside the indie software world have heard of, shows $1,146 a month. Since 2021 he has shipped 43 products.

Indie software: small software businesses built and run by one person or a very small team, usually sold as a subscription over the internet, with no outside investors and no sales staff. The builder writes the code, sets the price and answers the support email.

The figures come from one place: his own site. There is no audited statement, no payment-processor export and no third-party verification in the material available. The Indie Hackers forum discusses his year, but a forum thread is a conversation, not an audit. Treat the numbers as self-reported and internally consistent, which is what they are.

Why now

The twelve-month total is the headline, but the thread that produced it runs back to 2021, when the first of the 43 products went out. Five years of shipping is the actual story. A single product that earns $35,608 a month in November 2026 did not start there; it started at zero and moved.

The reason this surfaces now is that the twelve-month window has just closed. A rolling annual figure becomes quotable once there is a full year behind it, and the product-level monthly figures give the total a shape. The shape is what matters: three products carry the bulk of the money, and the rest of the 43 are small or dormant.

The third reason is the audience. The indie software world has spent several years arguing about whether one big product or many small ones is the better bet. A public panel with a five-year track record and a stated margin is the kind of evidence that argument runs on. It is not proof. It is a data point with a date on it.

So what

The gain lands on the builder who treats products as a portfolio. If one product in ten works, and the working one earns enough to cover the nine that do not, the portfolio survives. That is the mechanism: many small bets, each cheap to start, with the winners paying for the losers. The 43 products are not 43 successes. They are 43 attempts, and the revenue panel shows which ones cleared the bar.

The cost lands on focus. Running several products at once means splitting attention across support inboxes, billing systems, bug reports and marketing. A solo builder with zero employees absorbs all of that personally. The stated 90 per cent gross margin describes the money left after the direct cost of delivering the software, which for hosted software is mostly servers and payment fees. It does not describe the hours.

The third actor is the reader who sees $1,234,900 and concludes that shipping more products is the path to it. The panel does not show what the 40 products outside the top few earn, and it does not show what was spent building them. The visible structure is a portfolio. The invisible part is the five years and the failures inside the 43.

What it means for Malaysia

The consequence lands on Malaysian software builders selling to overseas customers in US dollars. A Malaysian who builds a subscription product priced in dollars and hosted on a foreign cloud is running the same model Marc Lou runs, at a smaller scale. The ringgit conversion is the carrier: dollar revenue against ringgit costs is the whole reason the model appeals here.

The concrete group is small studios and solo developers in Kuala Lumpur, Penang and Johor, the same people the digital-services tax change reaches when they bill overseas clients. The portfolio logic applies directly to them: several small products, each cheap to host, is a way to spread risk when there is no salary behind the work. The cost side is local and predictable; the revenue side is foreign and volatile.

The second carrier is the reader who wants to sell software into Malaysia rather than out of it. The same structure works, but the price points are lower and the payment rails are local. The panel says nothing about that market. A Malaysian builder copying the structure should expect the arithmetic to look different, because the customers and the currency are different.

How we calculated this

The shares in the table are the three largest products divided by their combined monthly total. The annual figure is not divided by twelve here, because the monthly product figures cover the last 30 days and the annual figure covers twelve months; mixing the two would produce a number that means nothing.

Three largest products, monthly (USD):
  TrustMRR      35,608
  DataFast      29,188
  Ship or Die   16,397
  Combined      81,193

Share of combined:
  TrustMRR      35,608 / 81,193 = 43.9 per cent  -> 44 per cent
  DataFast      29,188 / 81,193 = 35.9 per cent  -> 36 per cent
  Ship or Die   16,397 / 81,193 = 20.2 per cent  -> 20 per cent

Annual total, twelve months to November 2026: 1,234,900 USD
Products shipped solo, 2021 to November 2026: 43
Employees: 0
Stated gross margin: 90 per cent

How confident

Confirmed. The figures in this piece come from Marc Lou’s personal site, read on 7 November 2026: the $1,234,900 twelve-month total, the four product-level monthly figures, the 43 products shipped since 2021, the zero employees and the 90 per cent stated gross margin. The site is the primary document and it is dated by the read. The newsletter archive and the Indie Hackers discussion exist as secondary material, but neither is an audited record.

Inferred. The portfolio argument is an inference from the product list, not a claim the site makes. The mechanism is that several products with independent customer bases spread the risk of any one declining, and the three largest products carrying most of the visible monthly revenue is consistent with that. The 90 per cent margin is stated, not shown, so the cost structure behind it is inferred from what hosted software normally costs to run.

What would change my mind. A payment-processor export or an audited statement showing a materially different twelve-month total would change the headline. Evidence that the 40 products outside the top few earn nothing, or cost more to run than they return, would weaken the portfolio argument and turn the case into a story about one or two products with a long tail of attempts. A breakdown of hours worked per product would change the cost side of the picture entirely.

For you

• A Malaysian developer with a day job: the copyable move is the shipping cadence, not the revenue. One small product every few months, each cheap enough to abandon, builds the portfolio without risking the salary.
• A small studio billing overseas clients: dollar revenue against ringgit costs is the margin. Price in dollars, host where it is cheap, and keep each product small enough that one failure does not take the studio down.
• A reader who wants to sell into Malaysia: the structure transfers, the arithmetic does not. Local price points and local payment rails mean a smaller ceiling per product, so the portfolio needs more products or lower costs.
• A reader tempted by the headline total: the panel shows the top three products, not the other 40. Budget for the failures, because the visible number is the sum of a five-year run, not a first-year outcome.

The data point

$1,234,900 — revenue across the twelve months to November 2026, from 43 products shipped solo, with zero employees and a stated 90 per cent gross margin. Source: Marc Lou personal site, read 7 November 2026.

Earlier reporting on this site: Singapore ends haze measures as Malaysia watches transboundary smoke season.

FAQ

Is the $1,234,900 figure verified? No. It is self-reported on Marc Lou’s personal site, read on 7 November 2026, and there is no audited statement or payment-processor export in the material available. The product-level monthly figures on the same page are internally consistent with the annual total, which is a reason to take them seriously as a record of what the site claims, not as proof of what was banked. A reader should treat the number as a dated claim from the person who earns it.

Why does a portfolio of small products beat one big bet? Because the cost of a failed attempt is small and the cost of a single failed bet is total. If each product is cheap to build and cheap to host, a builder can afford several attempts, and one that works pays for the rest. The risk is spread across independent customer bases, so a decline in one product does not end the business. The trade-off is attention: a solo builder with no employees carries every product’s support and maintenance personally.

What can a Malaysian reader actually copy? The structure: small products, dollar pricing where the customer is overseas, low hosting costs, and a shipping cadence that produces several attempts rather than one. What does not transfer is the income. The $1,234,900 is the sum of a five-year run with 43 attempts behind it, and the panel does not show what the smaller products earn or what they cost. A Malaysian builder should copy the cadence and the pricing discipline, and expect the totals to look different.

The point

The number that matters in this case is not $1,234,900. It is 43. A one-person studio that shipped 43 products in five years and ended up with three that carry most of the revenue is a portfolio, and a portfolio is a structure a Malaysian reader can build without the luck, the country or the audience. The revenue is the outcome of the structure, not a thing to copy on its own. Build small, ship often, price in the currency your customer earns in, and keep each attempt cheap enough that the failures do not end the run.

Related case: Tony Dinh: TypingMind and the One-Person AI Front End.