Revenue is valuable, but two companies with the same revenue can be building very different futures. One accumulates reusable capability; the other accumulates obligations. Ask what remains after the work is finished and why that makes the next cycle better.
Use this principle when: choosing between customer projects, prioritising platform work, evaluating an intellectual-property strategy or claiming that growth creates a defensible position.
What to do
- Name the asset and the mechanism. Production learning might improve yield; an evaluation system might reduce failure; a distribution relationship might lower acquisition effort. A patent, dataset or customer count is not its own explanation.
- Track a consequence that matters: customer outcome, reliability, time to value, cost, willingness to pay or access. Check whether the effect improves across comparable cycles.
- Establish what you control and can reuse. Identify rights, dependencies and who gains bargaining power as the business grows. Reassess whether a technical or market change could erode the advantage.
Evidence that changes the decision
Proceed: the work creates a reusable asset and the expected benefit appears in later customers, batches or releases. Invest in the mechanism that makes the improvement repeat.
Change the plan: every contract adds maintenance without strengthening a common core, more data does not improve outcomes, or a partner captures most of the benefit. Change scope, architecture, rights or the route to market.
Stop the claim: you cannot explain or observe how the supposed advantage improves value or economics. Keep it as an unproven hypothesis rather than using it to justify more spending.
Where founders misapply it
Do not spend years constructing a moat around demand that has not been established. Early custom work can be valuable when it earns money, teaches something important or opens access; record its full cost and what can be reused. Network effects need evidence that additional participation improves value for other participants. User growth alone does not demonstrate that mechanism.
Teece distinguishes creating innovation from capturing its returns and explains the role of complementary assets and imitation. The particular advantage still has to be demonstrated in your company. [9]
Next decision: complete: “After the next set of customers or production cycles, we will be better at … because …, and we will observe it in …”.