The rise of the portfolio publisher.

01The center of gravity moved

The mythology of app publishing is hit-driven: one great app, polished for years, riding a store feature to glory. The economics stopped supporting the myth some time ago. Discovery got more expensive, organic featuring got scarcer, genres saturated faster — and the variance of any single launch became a risk most independent publishers can't responsibly carry.

The adaptation was rational: many smaller bets instead of one big one. Ship more, learn faster, let the market vote, concentrate resources on what the votes reveal. The portfolio publisher isn't a lesser version of the hit studio — it's a different asset class, with different math.

02Portfolio economics 101

Inside every healthy portfolio lives a power law: a few titles generate most of the net, a middle band earns its keep, and a tail is either young (still proving itself) or done (and should say so). This isn't failure — it's the expected shape. The skill is managing to the shape:

• The top funds the experiments. Winners' cash flow is the R&D budget; protect their economics daily.
• Expected value beats attachment. Each app is a position. Positions get sized by evidence, not by how much you enjoyed building them.
• Killing fast is a feature. Every month a dead bet stays "live" it consumes attention, maintenance, and often real spend. Fast, criteria-based sunsetting is what makes the many-bets model affordable at all.

03What changes operationally

The single-app playbook breaks quietly somewhere around app number five. What replaces it:

• Per-app P&L becomes non-negotiable. With one app, "how's revenue" is a feeling. With fifty-four, it's a table — every app, every stream, net, monthly — or it's nothing.
• Reporting must scale sub-linearly. Fifty apps cannot mean fifty times the dashboard time. This is why the assembly tax that's annoying for one app is fatal for a portfolio.
• Shared infrastructure compounds. Cross-promotion between titles, monetization learnings applied portfolio-wide, one UA discipline across everything — the portfolio's real moat is that every lesson is bought once and used everywhere.
• Sunsetting becomes hygiene. A quarterly ritual with criteria, not an emotional crisis. The 90-day net-negative rule exists so the calendar makes the call.

04The three portfolio traps

1. Zombie apps. "Almost profitable" titles that are never quite worth fixing and never quite worth killing. Individually cheap, collectively they eat the attention that winners deserve. The fix is a hard rule, enforced on schedule.
2. Blended blindness. Portfolio-level health can hide app-level sickness for quarters. The average is a summary, never a diagnosis — the monthly table exists to read the rows, not the total.
3. The maintenance tax. Every live app carries invisible weight: store policy compliance, SDK updates, API deprecations. Portfolio math must charge each app its maintenance cost, or the tail looks cheaper than it is.

05Running it

The playbooks in our library are, together, the portfolio publisher's operating manual — True ROI for the table, scale/hold/kill for the verdicts, the 4-minute morning for the cadence. The model works because the discipline works. The discipline works because the numbers are assembled before the coffee is.