Blume PM Playbook

Blume Ventures published a product management playbook on April 17 that turns early-stage product work into a compact guide for founders and product managers. (blume.vc) The report is by Marmik Mankodi and Muskan Gupta, and Blume says it is aimed at “early-stage founders, PMs, and anyone moving into early stage startup environments.” The firm frames it as guidance for “problems, decisions, and trade-offs,” not a fixed checklist. (blume.vc) The playbook is organized around four jobs: research and problem discovery, solutioning, execution, and metrics and growth. Blume says that includes primary and secondary research, prioritization, minimum viable product thinking, engineering feedback loops, North Star metrics, retention, funnels, and product-led growth loops. (blume.vc) Product management in a young startup usually means deciding what problem is worth solving before deciding what feature to build. Blume’s guide tells teams to “start with the problem, not the product” and rank pain points by how often they happen and how intense they are. (blume.vc) The document also packages a recommended tool stack by stage, covering discovery, design, build, and growth. Blume says the goal is to map tools to the actual work product teams do, instead of letting software choices drive process. (blume.vc) That pitch lands at a moment when product roles are being reshaped by smaller teams and more automation. Blume opens the report by saying “in the age of AI, every job function is changing rapidly, product management included,” while arguing that the basic rules of product building have not changed. (blume.vc) Blume has been publishing playbooks across startup functions, including earlier guides on consumer technology and product-market fit. The new product management edition extends that library with a resource focused on day-to-day product decisions inside seed-stage and early-growth companies. (blume.vc, blume.vc, blume.vc) The result is less a manifesto than a field manual: find a repeated user pain point, test solutions before building, ship with tight feedback loops, and watch whether users come back. That is the through-line Blume is trying to codify for startup teams hiring, interviewing, or learning product from scratch. (blume.vc)