A weekly review routine for founders with several products

With one product, you notice when something is off. You are in the dashboard every day, you see the support emails, and a drop in signups is hard to miss.

With three products, you stop noticing. Each one gets a glance when something breaks, and the slow problems slip past: a payment method that keeps failing, a page that used to bring in visitors and quietly stopped, a site that went down for twenty minutes on Saturday night.

A short weekly review fixes that. Here is the routine we use, in the order that catches the most for the least time.

Pick one time and keep it small

Monday morning works for most people, before the week fills up. Give it 30 minutes for all products together, not per product. If the review takes longer than that, it will not survive a busy week, and a review you skip is worth nothing.

The goal is not to understand everything. It is to end with a short list: at most three things to do this week, each with a reason.

1. Money first: what is at risk

Start with revenue, because it is the one place where waiting costs you directly. For each product, look at:

Past-due subscriptions. These are customers who want to pay and could not. Most can be saved with one email asking them to update their card.
Subscriptions set to cancel. They have not left yet. A short, personal note asking what was missing sometimes changes the answer, and the reply tells you something either way.
Failed payments this week. One is noise. Several on the same product can mean a checkout or billing problem.
MRR against last week. Only after the above, since the total moves slowly and the problems inside it do not.

If your products bill through separate Stripe accounts, total them carefully. This post on MRR across Stripe accounts covers the details that make totals wrong.

2. Did anything break

Next, look back over the week for outages and errors. Two questions matter:

Was anything down, and for how long? Uptime checks every few minutes give you the start, the end, and what the failed check saw, like a timeout or a server error.
Is one error growing? In your error tracker, sort unresolved issues by events in the last day. A new error near the top that lines up with an outage is usually the one to fix first.

If customers could have noticed downtime, write a short note for your status page or changelog: what happened, when, and that it is fixed. Plain and calm beats detailed. People mostly want to know you saw it.

3. Traffic: what moved, and why

Compare this week's visitors with last week's for each product. Do not chase small changes; a busy news day elsewhere can move a small site's numbers. Look for:

A page that dropped out of your top pages. Check whether it still ranks for the searches that used to bring people in.
Pages that people see in search but do not click. A clearer title and description is often the cheapest win you have.
Visitors that do not turn into signups. If traffic rose and signups did not, the new visitors may be looking for something else.

4. What shipped, and what to share

Last, list what went out this week: features, fixes, articles. Two reasons. It keeps the review honest about where time went. And anything worth building is usually worth one post: a line on X, a few on LinkedIn, a paragraph in your newsletter, or a helpful summary in a community where people talk about the problem it solves.

5. Write the short list

End by writing down at most three actions, each with the reason from the review. For example: email the four past-due customers on one product, rewrite the title of a page people see but skip, post a status note about Saturday's outage. Then close the tabs.

Next Monday, start by checking whether last week's three got done.

Doing it with LopeBase

We built this routine into LopeBase because we run several products ourselves. Every product's revenue, traffic, uptime, and errors sit on one screen. On top of that, AI reviews do the reading for you: a weekly briefing on Overview, a revenue review that flags what is at risk, a traffic review that points at the pages to work on, an incident review that drafts the status note after downtime, and posts to share any article. Each one uses only your own numbers and lists what it read. The weekly digest email covers the same week if you would rather read it in your inbox.