Build the Zero-to-One Muscle Early

The second product is a physics problem, not a scheduling one

Eric Glyman describes the launch of Ramp's second major product as one of the company's most uncommon early choices. Ramp started in March 2019 and shipped its first product, the corporate card, in February 2020. Roughly eighteen months later it launched Bill Pay, a structurally distinct second product, while the company was still, in Glyman's word, "raw."¹ The timing was deliberate. His stated reasoning is not about ambition or roadmap greed but about the mechanics of creation itself.

Glyman frames taking a product from zero to one as governed by different physics than scaling something that already works. "The physics of taking a product from zero to one is very unusual, very unlike the later stages of scaling something that works. We wanted to build it when the company was still raw, before we needed that second act."¹ The claim is that the two activities draw on different capabilities, and that a company optimized for one atrophies at the other unless it practices both.

Building the muscle before the company needs it

The failure mode the principle is designed to avoid is a company that spends years only scaling its first product, then tries to learn zero-to-one creation for the first time under duress, once growth has stalled or the first product has matured. By forcing a second creation event while the team was small, Glyman treated product-building as a capability to be exercised rather than an event to be survived. His shorthand for the mechanic is blunt: "Lock five people in a room and say don't come out until you have a working product."¹

Done early and repeatedly, that becomes muscle memory instead of a one-time scramble. The point is that the capability is perishable and path-dependent. A company that waits until it is forced to build a second act has to acquire the skill at the worst possible moment, while a company that builds early carries the skill forward as a standing organizational asset.

Relationship to focus and to the compound end state

The principle sits in tension with the more familiar counsel of ruthless single-product focus, the view that a young company should do one thing and refuse distraction. Glyman's implied resolution is to separate the thesis from the capability. The thesis stays focused, in Ramp's case saving companies money, while the company deliberately builds the capacity to spin up new products under that thesis so that focus does not ossify into a single-product trap. This connects the principle to singular-product-focus less as an opposite than as a boundary case: focus the mission, multiply the products.

The move is also the enabling mechanism behind the compound-startup end state associated with Parker Conrad, where multiple integrated products create switching cost. A company cannot assemble a compound product surface without first being fluent at zero-to-one, and this principle is a claim about how that fluency is acquired: early, on purpose, before the market demands it. In that sense it rhymes with building capacity ahead of demand rather than in response to it.

Limits

The evidence here is a single founder's account of a single company, and the causal claim, that early second products build durable capability, is difficult to separate from the specific talent and capital Ramp had. A young company with a fragile first product may find that a forced second creation event starves the first of the attention it still needs. The principle asserts that zero-to-one and scaling are distinct muscles, but it does not by itself specify when a first product is stable enough to safely divert five people into a room to build the next one.