Every product we shipped came with its own dashboard. Stripe for revenue. Vercel for deploys. Sentry for errors. Supabase for the database. Each one was fine on its own — the problem was checking all of them, every day, across every product, just to answer one question: is anything on fire right now?
Most days the answer was no. But finding that out took ten tabs and fifteen minutes, and on the days the answer was yes, we usually found out from a customer before we found out from a chart.
The actual job
Running a portfolio of products isn't really about any single metric. It's triage. You're scanning for the one signal that matters out of a hundred that don't, and deciding — fast — whether it needs you right now or can wait until tomorrow.
Dashboards built for a single product don't do this well, because they assume you're staring at them all day. You're not. You're context-switching between four or five different codebases, and the tool you check in between should tell you exactly one thing: what changed, and does it matter.
What that meant we had to build
- A single Today view across every product, not per-product dashboards you have to click into one at a time.
- An Inbox that doesn't just list alerts, but ranks the likely causes underneath each one — so "what broke" takes seconds instead of a Slack thread with yourself.
- Real numbers, always. If a service isn't connected yet, the widget says so. Nothing is ever a plausible-looking fake.
- A widget grid you control per project, because a two-person SaaS and a solo mobile app don't care about the same things.
That's FounderOS: one place to run every product you ship, built by people who were tired of running theirs from six different places.