Portfolio model

A portfolio model is running several small businesses or products as a deliberate set rather than betting everything on one. Instead of pouring years into a single company hoping it becomes huge, you hold a basket: some throw off cash now, some are early bets, some you'll kill. The portfolio absorbs individual failures because no single line is load-bearing.

For a solo or near-solo founder, the appeal is risk spreading and compounding. One product's distribution can feed the next; shared infrastructure, an audience, or a team lowers the cost of each new launch. The discipline is staying lean per asset so a loser costs little and a winner can scale. The trap is spreading attention so thin that nothing reaches escape velocity.

In practice this lives in the plumbing. Say you're tracking the whole basket in Coda: one doc with a row per asset, each tagged grow, maintain, or kill, so investment decisions are visible at a glance instead of in your head. Say you reuse infrastructure across lines with n8n, wiring one signup flow or billing webhook once and pointing every new product at it, so launch number four costs a fraction of launch number one. And say you watch which line actually compounds in Databox, one board pulling revenue and CAC from every asset side by side, so your time always flows to where it pays back.

A working portfolio model has clear rules for what earns more investment, what gets maintained, and what gets shut down.