How We Run 12 Apps With 5 People: Our Weekly Operating Cadence

Run a cadence, not a hero effort

The failure mode for a small team with many products is not laziness. It is context loss. Five people cannot hold an entire portfolio in their heads at once, so gaps appear: unreviewed metrics, undocumented decisions, tests that outlived their purpose.

A decision cadence without a record is just a series of guesses you cannot audit.

Instead of leaning on individual memory, the team runs a structured weekly loop that surfaces priorities, records reasoning, and closes unfinished work. Consistency in the process is what lets the team spend its attention on product, not on process.

Monday: signal triage across every product

The week starts by looking at the whole portfolio and sorting raw data into three buckets: act now, watch, ignore. Most apparent urgencies are noise; real problems often show up quietly. The output is one ranked list any teammate can read in two minutes.

Triage runs across the portfolio, not per app, because looking at products individually hides the trade-off. Every app looks like it deserves more when viewed alone. Comparing across the portfolio makes the real question obvious: given this week's capacity, which product earns the attention.

Keep a decision record so the why is not lost

For each significant bet, the team writes one paragraph: date, decision, rationale, and the condition that would reverse it. Three weeks later the reasoning behind a pricing change or a paused campaign is otherwise gone, and the decision gets silently re-argued by people who never saw the original logic.

Share cross-product context on purpose

Once a week, one person writes up a pattern that applies across apps. A paywall change that lifted conversion on one product becomes a free experiment for another. A support issue that ate a week on one app becomes a warning for the rest. Left unshared, the portfolio's most valuable asset (lessons already paid for) stays trapped inside one contributor.

The weekly portfolio review

Once a week every product lands on one page, and each active task gets a status: go, hold, or kill. No product is exempt; nothing defaults to continuing. The review is short because the week prepared it: triage ranked the items, records preserved the reasoning. The focus is deciding, not discovering.

Kill stale or stuck work on schedule

Every Friday the team finds work that has gone quiet or lost its reason and ends it deliberately. Small teams fail not from wrong initial choices but from holding too many half-active initiatives at once. If an initiative cannot answer "what are we still learning here," it ends, recorded with its reason, so it is not accidentally resurrected.

The weekly cadence, in one table

Why the cadence beats more people

The instinct when you have too many products is to hire. But adding people to a context problem usually makes it worse: more inboxes, more meetings, more places for reasoning to leak. Real scaling for a small team comes not from headcount but from systems that remember and decide on a schedule, which is the idea underneath Qualia: one operating mind across the whole portfolio.