The Solo PM — Time, Roadmap, and the Portfolio Cadence

Confront the operational reality of being engineering, design, PM, sales, and founder simultaneously: role-switching cost, the founder-as-bottleneck failure mode, the time-blocked week, the honest 90-day roadmap with a real time budget, the quarterly portfolio review that makes M4's discipline permanent, and a written hiring framework — including the explicit case for not yet. The founder-as-bottleneck is the synchronous blocking call: one connection pool gating the whole system's throughput. The correctives map exactly — reduce demand on it, cache its outputs (automate repeated decisions), decompose into bounded calls (delegate a function), and only then parallelize (hire) — and the engineering discipline is considering them in that order, because parallelizing a poorly understood bottleneck multiplies the mess. The week structure is the architecture diagram for your time: different request types routed through isolated paths. The quarterly review is the deprecation cadence: without a calendar, deprecated modules — and zombie products — accumulate. The hiring decision is the architecture rewrite: expensive, risk-laden, short-term negative, and chronically underestimated by exactly the people most eager to start it. And "calm company" is the deliberate monolith: optimizing for manageable complexity over scale potential, valid, and hard to hold when the conference-talk pressure says decompose.