Guide · founder portfolio
How to manage multiple SaaS products as one founder
01The constraint is attention, not ideas
A founder with several products rarely lacks options. What runs out is attention: every product competes for the same hours, and the product that asks loudest (support tickets, outages, a churned customer) tends to get them. That is not necessarily the product where an extra hour is worth the most.
So the job is to treat founder hours as capital: measured, allocated deliberately, and reviewed against returns. The more autonomously each product runs, the more hours are left to allocate. That is why this guide starts where the Zero-Employee Architect ends.
02What portfolio founders report
Few founders publish product-level numbers. Two who do describe a strongly skewed portfolio, in which most launches never make meaningful money. All figures are their own (grade C).
Pieter Levels
Dutch solo founder (@levelsio) who runs several web products himself, including Photo AI, Interior AI, Nomads.com and Remote OK, plus an angel fund (levels.vc). His own project list counts 116 projects, of which he rates 9 a 'Success'. He says he runs everything alone with automation. All figures below are self-reported. No explicit statement on how he splits time between products was found.
- C
His project list classifies projects as Success 9, Okay 11, Failed 19, N/A (non-profit or no profit goal) 71, New 6, which totals 116.
levels.io (Pieter Levels) · 3 Oct 2026
- C
Projects rated 'Success' ('Made or still makes good money for a long time & grew'): levels.vc, Vibe Jam, Photo AI, Interior AI, MAKE Book, Remote OK, @levelsio on X, Nomads.com, Panda Mix Show.
levels.io (Pieter Levels) · 3 Oct 2026
- C
Says 'Most things I made never succeeded or made money.'
levels.io (Pieter Levels) · 3 Oct 2026
- C
In 2021 he wrote that only 4 of his 70+ projects had made money and grown, a hit rate of 'only about ~5%'.
levels.io (Pieter Levels) · 7 Nov 2021
- C
Per-product monthly revenue at a one-day peak ($420K/mo total): Photo AI $161K, ReadMAKE.com $93K, Nomads.com $61K, InteriorAI.com $43K, levelsio.com (merch and X) $34K, RemoteOK.com $29K, ApplicantAI.com $1K, HotelList.com $0K.
levels.io (Pieter Levels) · 22 Sep 2024
Marc Lou
Solo founder whose site lists Cyprus as his location. He runs a portfolio of small products (ShipFast, CodeFast, DataFast, TrustMRR and others) and publishes revenue for each. He owns TrustMRR, the Stripe-verified revenue database, so TrustMRR figures for his own products are not independent. He gives 36 or 38 as his startup count, and a handful drive almost all revenue.
- C
Says 'I've built 38 startups solo.' His site shows 43 product cards and a combined '$89.8k/month'.
marclou.com · 16 Oct 2026
- C
Revenue-producing products on his site (monthly, as displayed): TrustMRR $47.8k, DataFast $30.5k, CodeFast $5k, Ship or Die $3.6k, ShipFast $1.4k, Indie Page $590, Stalkr $290, Zenvoice $187, SuperShrimp $170, ByeDispute $144, MailCheap $77, WorkbookPDF $19, Habits Garden $19, PoopUp $9. That is 14 products above $0; three more show $0/mo.
marclou.com · 16 Oct 2026
- C
Says he has made $3M with his 36 startups over about 10 years, solo, at an 85% margin. He also writes '90% of my 36 startups failed' and 'My other 30 startups never really made money.'
Just Ship It newsletter (Marc Lou) · 8 Sep 2026
- C
Reports $1,032,000 revenue in 2025 from '15 income streams', about 20% less than 2024. Main earners: ShipFast and CodeFast (~$20K/month each), DataFast ($15.8K MRR) and TrustMRR. New launches BioAge and ClipMarc 'failed'.
Just Ship It newsletter (Marc Lou) · 4 Jan 2026
- C
Runs TrustMRR (founded October 2025). Its own listing shows $45,149 revenue in the last 30 days, $23,984 MRR and $383,560 all-time, 'verified with Stripe API key' on a platform he owns.
TrustMRR · 15 Oct 2026
03A weekly allocation framework
- 01
Log founder hours by product
Two weeks of real logs, split into recurring operations, building and strategy. Estimates from memory are reliably wrong.
- 02
Measure each product's maintenance tax
Founder maintenance hours (at an explicit hourly rate) plus infrastructure, software, AI and contractor costs, divided by revenue.
- 03
Assign exactly one decision per product
Validate, build, scale, maintain, harvest, sell or kill. A product without a decision silently becomes maintain.
- 04
Allocate next week's hours by marginal return
Put the next hour where it creates the most value: usually the SCALE product, rarely the loudest one.
- 05
Turn every allocation into a reversible experiment
Time-boxed, with a success threshold and a rollback, decided before you start.
- 06
Review monthly against outcomes
Record what you decided, why, and what happened. The log becomes your best forecasting tool.
04Which product should I focus on?
Focus on the product with the highest marginal founder attention ROI: the value an additional hour creates there, not the average return so far. A mature product can have a high average return and a low marginal one. Use the decision labels to make the choice explicit:
- VALIDATE
- Demand is unproven. Run small, reversible tests until there is a signal, or stop. Minimal, time-boxed attention; no fixed costs.
- BUILD
- Demand is validated, but the product is not yet sellable at scale. Concentrated engineering and agent capacity; little marketing spend.
- SCALE
- Extra attention or capital earns the highest marginal return in the portfolio. More founder hours, distribution spend and agent capacity.
- MAINTAIN
- Stable and healthy. Keep it running with minimal intervention and protect its autonomy. Monitoring only; act on alerts.
- HARVEST
- Growth is flat but cash is positive. Reduce attention and extract cash flow. Cut discretionary spend; automate or drop remaining manual work.
- SELL
- Worth more to another owner than to your portfolio's scarce attention. Prepare transferable documentation; reduce your involvement before the sale.
- KILL
- Consumes attention with no credible path to return. Shut it down cleanly. Migrate or notify customers, then stop all spend.
05When to kill a SaaS product
Consider KILL, or SELL if the product is transferable, when most of these hold:
- Maintenance tax is rising while growth has been flat or negative for two quarters.
- Its share of your attention is well above its share of portfolio revenue.
- You have run the reversible experiments you can think of, and none moved the metric.
- Freeing its hours would fund a SCALE product with a clearly higher marginal return.
Prefer SELL over KILL when customers and documentation can be handed over: the hours are freed either way, and a sale also returns capital. Before either, try HARVEST: automate or drop the remaining manual work and see whether the product can run below 2 founder hours a week. That is the threshold we use for Autonomous MRR.
06How many products can one founder run?
There is no reliable dataset that answers this, and we will not invent one. The honest answer depends on how autonomously each product runs: a founder with ten products that each need two hours a week has more free capacity than one with two products that need twenty. Count the intervention each product needs, not the number of products.
07Portfolio worksheet
A blank template. Fill one row per product each week.
| Product | MRR | Founder h / wk | Maintenance tax | Growth 30d | Decision | Next experiment |
|---|---|---|---|---|---|---|
| Product 1 | ||||||
| Product 2 | ||||||
| Product 3 |