Building

The Spec That Ships

Most products have a spec. Few have a spec that anyone reads, agrees on, and actually builds from. The difference is smaller than it looks.

The Competitor as Proof

Finding a funded competitor in your space feels like bad news. It usually isn't.

The Documented Workaround

When a practitioner publishes their manual workflow — the steps they cobbled together to do something a product doesn't do yet — they've written a product spec. They've also confirmed the demand.

The Cost of Waiting

Waiting has a cost. It's usually invisible — you can't see the customer who found a workaround, the window that narrowed, the competitor who moved. The invisibility makes it easy to underestimate.

The Research Trap

Research has diminishing returns. The arc converges. Continuing to research past convergence isn't information-seeking — it's commitment avoidance dressed up as diligence.

The Minimum Viable Proof

Before building a product, you need to build a proof. They're different things, optimized for different goals — and confusing them is one of the most common ways to waste months of work.