How many dashboards does a multi-product founder need?

From the SoleOS answers series — written about our own product space; grounded in published definitions and documented behavior, never invented numbers.

The honest answer is one — but only if that one dashboard can actually hold every product you run, across web and mobile, without you rebuilding it every time you ship a new app. If you're stitching together Stripe, RevenueCat, App Store Connect, and a spreadsheet to get one number, you don't have one dashboard. You have four dashboards and a part-time job.

Most solo founders don't start with a dashboard problem. They start with one product and one Stripe tab, which is genuinely fine. The problem shows up around product three or four, when checking "how's the portfolio doing" turns into a 20-minute ritual of opening tabs, remembering which app uses which login, and doing subtraction in your head to figure out if this month is better or worse than last.

Count what you actually have, not what you wish you had

Before deciding how many dashboards you need, count three things honestly:

• Number of products with live revenue. Not "apps in the store" — apps someone is currently paying for, via Stripe, RevenueCat, or store billing.
• Number of distinct data sources per product. A web app might have Stripe + GA4 + Search Console. A mobile app might have RevenueCat + App Store Connect + Play Console + Firebase. Multiply that out and a 6-app portfolio can easily mean 15-20 individual logins.
• How often you actually need cross-product comparison. Daily, weekly, or only when you're deciding where to spend your next month of dev time.

If you run one or two products, the answer is genuinely "zero extra dashboards — your native ones (Stripe, App Store Connect) are enough." Buying a portfolio tool at that stage is buying a solution to a problem you don't have yet. That's the honest "when you don't need this" moment, and it applies whether the tool in question is SoleOS or anything else in this category.

Once you're past three or four products, the math flips. The cost isn't the subscription price of a portfolio tool — it's the hours you spend every week doing manual reconciliation, and the decisions you're making on stale or half-remembered numbers because pulling fresh ones is annoying.

The real question isn't "how many" — it's "how many logins to get one number"

A useful way to reframe the question: instead of asking how many dashboards you need, ask how many logins it takes you right now to answer "what's total MRR across everything I run, and is it up or down this month?"

If the answer is one login, you're fine. If it's five or more, you're not lacking dashboards — you're lacking a single source of truth, and adding a sixth dashboard on top won't fix that. What fixes it is consolidating the sources you already have into one view, which is a different problem than "check a new dashboard." For a concrete walkthrough of what that reconciliation actually looks like when Stripe and RevenueCat both report revenue for the same user base, see tracking Stripe and RevenueCat together.

What "one dashboard" needs to actually cover

If you're going to consolidate down to one view, it has to genuinely replace the native tools you're checking, not just summarize them badly. At minimum, for a portfolio of web and mobile products, that means pulling from:

• Payment and subscription data: Stripe, RevenueCat
• Web analytics and organic visibility: GA4, Search Console, Bing Webmaster
• Store-side metrics: App Store Connect, Google Play Console
• Product signals: Firebase, Supabase

That's the connector list SoleOS runs on, and it's a reasonable checklist even if you never use SoleOS — if a portfolio tool is missing your primary revenue source or your web analytics, it's not actually replacing anything, it's adding a tab. You can see what SoleOS connects to, including the exact scopes and how to revoke access, which is worth checking for any tool before you hand over OAuth access to your Stripe account.

Where projections and AI summaries fit — and where they don't

Once revenue data from multiple products lands in one place, the temptation is to want it to also tell you what's going to happen. That's reasonable, but worth being precise about: SoleOS requires at least 21 days of data before generating a growth projection, and even then reports it with an R² confidence score rather than a bare number, with an 18-month horizon. That's a deliberate hedge — trend lines on under three weeks of data are usually noise, not signal, regardless of which tool draws them.

The AI layer works the same way: it only ever sees aggregated project metrics and project names, never credentials, raw events, or your end users' identities, and it doesn't train on your data. Full detail is in how SoleOS uses AI. If you want an AI summary of "which of my 8 apps is actually declining," that's a real use for it. If you want it to explain a single day's revenue dip, you're usually better off just reading the raw numbers yourself.

When a spreadsheet is still the right call

It's worth saying plainly: if you run two or three products and you're comfortable pulling numbers monthly, a well-built spreadsheet is not a worse tool than a paid dashboard — it's arguably more transparent, since you control every formula. The tradeoff is time and the risk of a broken link or a manual paste error six months from now that quietly understates your MRR. We've written a fuller honest comparison in SoleOS vs a spreadsheet, including a free template, because plenty of readers land here at exactly the "am I ready to pay for this" stage and the answer is sometimes no.

How to decide, concretely

Run this quick test this week:

1. Time how long it takes you to answer "total revenue across all products, this month vs last month" using your current setup.
2. If it's under 5 minutes and you do it rarely, keep your current setup.
3. If it's over 15 minutes, or you've stopped doing it because it's annoying, that's the actual cost you're paying — compare it against the price of consolidating.

For reference, SoleOS pricing runs $19/mo for up to 5 projects, $39/mo for up to 15, and $79/mo for up to 40, with a 7-day trial and locked early-access pricing for founding users. Whether that's worth it depends entirely on how many hours a month you're currently losing to tab-switching — for some readers it's an easy yes, for others with 2-3 stable products it's genuinely not worth it yet.

Disclosure: SoleOS wrote this post about its own space — portfolio dashboards for multi-product founders. We tried to be straight about when you need one and when you don't.

Frequently asked questions

Is one dashboard always better than checking each product's native tool?

Not always. Native tools like Stripe and App Store Connect are more detailed for that one product and don't add a subscription cost. One consolidated dashboard is better when you're actively comparing products against each other, not when you're just monitoring a single app's health.

What's the minimum number of products before consolidation is worth it?

There's no fixed number, but the practical threshold for most solo founders is three to four products with live revenue, or whenever cross-product comparison becomes a weekly rather than occasional task. Below that, the manual check usually takes less time than learning a new tool.

Do I need separate dashboards for web and mobile products?

No — if your portfolio tool genuinely connects to both sides (Stripe/GA4 for web, RevenueCat/App Store Connect/Play Console for mobile), one dashboard can hold both. The failure mode to watch for is a tool that only covers one side well and treats the other as an afterthought.

How much history do I need before a portfolio dashboard is useful?

For basic side-by-side revenue and traffic comparison, any amount of connected history helps immediately. For trend projections specifically, expect to need several weeks minimum — SoleOS, for example, requires 21 days before it will generate a projection, and flags confidence explicitly rather than guessing early.

Can't I just build this myself with a spreadsheet and API pulls?

Yes, and for two or three products it's a reasonable choice — see our spreadsheet comparison for a free template. The tradeoffs are your time to maintain it and the risk of silent errors as you add more products and data sources.