Cheap Building, Scarce Judgment

When AI makes building cheap, more things get shipped, so the person who decides what not to build matters more, not less.

Contents
    Hand-drawn diagram: four boxes (feature, experiment, prototype, demo) all flow into one dark red box labeled "what to build, what to kill". A red arrow leads to "ships", and a grey dashed arrow leads to "no, not that", with the note that without a filter you get bloat and slop.

    Use it when Someone proposes dropping the PM role because everyone on the team can now vibe-code a prototype.

    The builder model says: everyone codes, everyone talks to customers, everyone ships. The translation layer between idea and prototype really is compressing, from weeks to hours.

    But “everyone can code” is not “everyone can build.” Making a demo work is engineering on easy mode. Making it work reliably, securely, at scale, for years, is still hard.

    It also misdiagnoses the PM bottleneck. The meetings exist because someone has to:

    • Align stakeholders who want conflicting things.
    • Say no to most feature requests without making enemies.
    • Turn messy customer signals into a strategy.

    None of these get easier because a PM can write code.

    Faster building means more need for someone deciding what to build. When shipping is cheap, you get more features, experiments and prototypes. Without a filter you get bloat, slop and inconsistent UX. Cheap building makes the person who says “no, not that” more important.

    The builder model fits small teams, developer tools and low-stakes internal tools. At scale, roles don’t dissolve; “what to build, what to kill” becomes the scarce skill.

    Topics

    Agents in Production 10Building with AI 9AI Product Strategy 24

    Start here

    How Agents Run in ProductionBeyond LLMs: The Whole Product Framework for AIThe Verification Bottleneck: Why AI's Real Cost Is Human Attention

    ↑ ↓ to move, Enter for all results