The Product Overhang Doctrine

In any product cycle, there are two curves to follow. The first is what your underlying technology can do. The second is what your users can actually do with it. They are not the same curve, and the gap between them — what the platform makes possible versus what the product surfaces — has a name.

For most of software’s history, the overhang was small. Your stack moved approximately as fast as your team could ship features against it. The two curves stayed close. Product roadmaps were exercises in execution, not in temporal arbitrage. You built for the capability you had; the capability you would have next quarter looked roughly like the capability you had this quarter, plus integrations.

Frontier AI broke this symmetry. Model capability now compounds on a six-to-twelve-month doubling cycle. Per METR’s 2026 benchmark, the time horizon a model can autonomously execute against has expanded roughly 41× in 16 months — from approximately 21 minutes on Sonnet 3.5 to approximately 12 hours on Opus 4.6. Inference price per equivalent unit of work has collapsed by a similar order of magnitude over the same window. The product capability built around those models has not, and structurally cannot, move at the same pace.

Most product organizations are built to ship for the curve they can see today. The frontier moves while they ship. The result is a permanent, widening gap, and that gap is now the most important strategic surface in software.