Revenue tracking across several products

Updated 2026-08-04

The portfolio approach — several small products rather than one big one — is common among indie hackers and creates a specific measurement problem: the total tells you whether you can pay yourself, but nothing about where to spend your time.

Two views, two decisions

The portfolio total answers can I keep doing this? It's the number that matters for runway, and the one to check daily.

The per-product split answers what should I work on next month? It's the number that matters for allocation, and checking it daily is counterproductive — individual product movements are noise at short timescales.

Most tools give you one or the other. Being able to see both is the actual requirement.

The trap: subsidising a loser

A portfolio total of $8,000 MRR feels healthy. But if product A is $7,400 and products B and C are $300 each, you probably have one business and two hobbies consuming your maintenance time.

That's not necessarily wrong — B might be six months old and growing — but it should be a decision, not something you discover a year later. The blended number actively hides it.

When products span platforms

The complication that makes this genuinely hard: products rarely map cleanly to platforms.

• Product A: Stripe subscriptions
• Product B: Gumroad one-offs plus a Lemon Squeezy licence
• Product C: an iOS subscription

Now the per-product view requires reconciling across three platforms with different reporting models, different fee structures and different definitions of a period. See the integrations for how each platform reports.

Keep recurring and one-off separate, per product

This matters more in a portfolio. A product selling $2,000 of one-off Gumroad sales and a product with $2,000 MRR are not equivalent assets — the second is worth many times the first, because it recurs.

Blending them makes a launch-driven product look as durable as a subscription one. See does one-off revenue count towards MRR?.

A practical setup

1. One aggregate view for the daily glance and cash decisions.
2. A monthly per-product review, recurring and one-off separated.
3. A hand-maintained log — product, month, MRR, one-off cash. Thirty seconds a month, and it's the only history you'll actually own.

What FRGMNT does and doesn't do here

Does: aggregate across all five platforms into one True MRR and one cash figure, with a per-platform breakdown.

Doesn't: split by product. The breakdown is by platform, not by product — so if two products both bill through Stripe, they appear as one line.

If per-product attribution is your core need, you'll want per-product Stripe accounts, or a tool with tagging. Said plainly so you don't buy expecting it.