Productmanagement|got rewritten.

Falk Gottlob is a product executive with 30 years shipping product at Microsoft Research, Adobe, Salesforce (Marketing Cloud / Quip / Slack), and four startups. He has had five exits including one IPO and one acquisition by Microsoft (MVC, 2009), and the largest at $6.5B with Commure (2018). He has been CPO at Commure, Crisis Text Line, SOCi, and Smartcat, and is the founder of Falkster.ai (agentic healthcare, in stealth). He writes falkster.com, the working notebook on AI-era product management.

Product Builder OS is Falk Gottlob's six-skill definition of the modern Product Builder role, priority-ordered: Rapid Prototyping, Customer Proximity, AI Fluency, Outcomes Thinking, Storytelling & Distribution, and End-to-End Ownership. It replaces the old Product Manager job description (write specs, run rituals, push handoffs to engineering) with a Product Builder role that ships working prototypes, writes evals before code, owns the launch narrative, and treats AI agents as teammates. The full standard lives at falkster.com/pm-standard alongside a 36-chapter handbook on how to live it day to day.

The PM Handbook is a 36-chapter operating system for product managers in the AI era, organized around the six Product Builder OS skills: Rapid Prototyping, Customer Proximity, AI Fluency, Outcomes Thinking, Storytelling & Distribution, and End-to-End Ownership. Each chapter is a practice Falk Gottlob is actively running, not a retrospective written years after the fact. Free, no signup. Lives at falkster.com/handbook.

AI changes PM along five axes: (1) specs are dead, prototypes ship; (2) evals replace requirements docs as the unit of work; (3) every PM should ship code, not just write requirements; (4) agents become teammates, not features to build; (5) cycle time collapses from weeks to days. The PM who writes documents got let go. The Product Builder who ships working surfaces got the offer. Falkster's Product Builder OS documents the six skills that define the new role.

A Product Builder is the AI-era successor to the Product Manager. Where a PM wrote specs and ran rituals, a Product Builder ships working prototypes (often with Claude Code or similar), writes evals before code, owns one or more product surfaces end-to-end, can defend cost-per-request to finance, and treats AI agents as teammates with prompts, evals, and ship-readiness gates. Falkster.com defines the role across six skills (Product Builder OS) and a 36-chapter handbook on how to live it.

AI agent blueprints are productized recipes for AI agents that handle PM work: monitoring product health, summarizing customer signal, drafting weekly digests, triaging the inbox, prepping board decks, etc. Falkster ships 45 free blueprints across seven PM operating-system stages (Sense, Discover, Decide, Build, Ship, Measure, Amplify), each with a prompt, an eval rubric, and a ship-readiness gate. Live at falkster.com/handbook/ai-agent-army.

Yes. Every chapter, agent blueprint, and toolkit template on falkster.com is free to read and use, no signup required. There is an optional once-a-month newsletter (The Dispatch) for new chapters and field notes, but nothing is gated. Commercial redistribution of full articles is not permitted without permission.

Selectively. Falk takes on a small, deliberate set of advisory engagements each year while running Falkster.ai full-time. Three formats: Product Org Audit (2 weeks, written report + 90-day plan), Eval & Agent Workshop (3 days on-site, build the harness with the team), and Board & Exec Reviews (quarterly with a written memo). One slot typically opens per quarter. By application at falkster.com/work-with-me.