Marc Lou and the Speed Portfolio
What repeated small launches teach about speed, public evidence, selection, and the danger of copying outcomes without context.
6 min read · Sources included
The method
Marc Lou has publicly documented a portfolio approach built around creating and launching many small products. In his own account of building 21 products in two years, he contrasts that rhythm with an earlier year spent on a product that produced no revenue.
The lesson is not simply “move faster.” Speed becomes useful when each launch creates evidence and the builder is willing to stop projects that do not earn continued investment.
What becomes public
The method produces frequent artifacts: landing pages, product demos, launch events, revenue updates, and post-launch decisions. Public shipping provides both distribution and a visible record of selection.
What beginners can borrow
Shrink the first proof
Ask for the 24-hour or seven-day version that can test the central interaction. This does not mean the final product must remain crude.
Separate a launch from a commitment
Launching creates evidence. It does not require maintaining every experiment forever.
Build reusable capability
Repeated products become faster when design, code, distribution knowledge, and operating habits accumulate. A beginner should not compare a first launch with someone else's mature system.
Keep a cost ledger
Portfolio speed can scatter attention and create abandoned users. Record support, maintenance, domain, infrastructure, and reputation costs before adding another product.
Read Marc Lou's original account, How I built 21 products in 2 years, for the method in his own words.