Where capital efficiency stops being the answer

Capital efficiency gets a company to proof. It doesn't get a company through a wall that only money, not cleverness, can move.

I underwrite lean teams because a small, sharp team shipping fast is the right way to find out whether an idea is real before anyone commits the capital a bigger bet would need. That's the right lens for the proof phase, and it stays right for as long as the constraint is still "can this team build it."

Some categories hit a different wall. The constraint stops being about the team's ability to build and becomes about scale that no lean team builds its way through, a physical distribution network, a sales floor, a data operation nobody runs with five engineers and a laptop. Funding a company at that wall like it's still proving an idea is the wrong call, not because efficiency stopped mattering, but because the question being answered changed underneath it.

The check size changes at that moment, and so does the milestone I'm looking for. Before the wall, the milestone is proof, a working product, real usage, evidence the idea holds. After the wall, the milestone is different. Is the wall itself real and verified, not assumed. And is the team asking for capital to break something they've actually hit, not something they're guessing they'll hit eventually.

Confusing these two moments cuts both ways. Good, capital-efficient teams get underfunded exactly when they finally need real capital, sized like they're still in the lean phase. And teams that haven't actually proven the wall is real get funded to build capital-intensive infrastructure nobody's confirmed is necessary yet.

Different phase, different bar. Not a smaller version of the same bar, a different question entirely.