Running a SaaS Portfolio Solo: The Weekly Ritual

When you run 4, 5, or 6 micro-SaaS products on your own, the real risk isn't running out of work: it's drowning in noise. Every product has its dashboard, its inbox, its billing, its signals. Without a ritual, you spend your week jumping from one tab to the next and steering on gut feel. Here's the concrete weekly ritual we use at Zylior to manage a portfolio from a single command center.

The guiding idea fits in one sentence: you don't want to "monitor" your SaaS products, you want to review them once a week, in a fixed order, on pre-aggregated signals. The ritual below takes between 90 minutes and 2 hours for 5 products. No more. If it overflows, you're doing operator work instead of pilot work — we'll come back to that at the end.

Why a single command center (and not 6 dashboards)

The classic trap of the solo portfolio: you open Stripe for product A, the analytics dashboard for product B, the support inbox for product C, and after 20 minutes you've lost track of what you were looking for. Every context switch is expensive — not in clicks, in mental load. Each time, you have to rebuild "where this product stands."

A command center flips the logic: instead of hunting for info product by product, you surface the signals that demand a decision into a single view. Concretely, you want 4 aggregated cross-product feeds:

• Buying signals: trials that have hit their end date, accounts that crossed a usage threshold, untreated chat→CRM leads, abandoned carts/checkouts.
• Health & revenue: MRR per product + week-over-week delta, failed payments (failed/past_due), the week's churn, 5xx errors or failed jobs.
• Content & distribution: where the "launch the week" stands (newsletter, post, changelog) for each product with an active channel.
• Consolidated inbox: support + sales replies + mentions, deduplicated, sorted by the value of the account behind them.

The weekly ritual, in order (≈90 min)

The order isn't cosmetic. You start with what earns (buying signals, follow-ups), you finish with what protects (billing, health, inbox). That way, if you get cut off after an hour, you've already handled revenue.

1. 1. Review buying signals (20 min). Sort by potential value, not by age. An expired trial on your $99/month plan comes before three free sign-ups. You don't contact everyone: you pick the week's top 5-10.
2. 2. Follow-ups (20 min). Go straight on: for each signal you kept, a personalized 3-line follow-up. No generic sequence on Monday morning — you know the context, use it. Note the date of the next follow-up, otherwise it doesn't exist.
3. 3. "Launch the week" content (25 min). For each product with an active channel: decide the angle, schedule the send/publish, and above all mark the ones that won't publish this week (that's a decision, not an oversight).
4. 4. Billing & health check (15 min). Sweep failed payments, past_due subscriptions, error spikes, red cron jobs. Open a ticket per anomaly, don't fix anything on the fly unless it's bleeding (downtime, blocked payments).
5. 5. Consolidated inbox (10 min). You clear the queue sorted by value. Short replies, escalate anything that needs dev work into tickets, archive the rest. Inbox zero weekly, not daily.

What is NOT in the weekly ritual

A good ritual is defined as much by what it excludes. Explicitly out of the weekly review:

• Product build. Coding a feature isn't a signal to review, it's a block of work planned separately. If you code during the ritual, you'll never finish the review.
• Structural decisions (pricing change, killing a product, hiring). They deserve a dedicated monthly slot, in cold blood, with the month's numbers — not a Monday-morning decision between two follow-ups.
• Vanity metrics. Visitors, impressions, followers: monthly report. In the weekly, only what leads to an action survives.

Making it last over time

The ritual only holds if it's cheap to execute. Two levers: (1) a fixed, protected slot — same day, same time, blocked in the calendar, otherwise it gets skipped the first busy week. (2) A single aggregated view — if you have to reopen 6 dashboards to do your review, you won't do it. That's exactly the role of a command center: turning 6 sources into one sorted action queue.

Start simple: this week, block 90 minutes, open your sources in the order buying signals → follow-ups → content → billing → inbox, and time it. You'll quickly see where it overflows and which product eats your week. From there, you know what to automate, what to aggregate into a single command center, and what to stop monitoring. The ritual isn't a cost: it's what keeps you from flying 6 products blind.