"A New Science of Venture Building" Explained - part I: The Demand-First Principle
The first in a series of posts explaining the founding principles, the operative commitments and the functional deployments of the framework at the core of this publication.
Every serious methodology for building ventures rests on a founding assumption about where value comes from. Get that assumption right and everything downstream, the process, the capital structure, the team design, works with the grain of reality. Get it wrong and no amount of execution discipline recovers the loss. The New Science of Venture Building is built around four operative commitments, each of which addresses a specific point where the founding assumptions of the existing playbook have stopped holding. This post is about the first and most foundational of them.
If you are encountering the framework for the first time, the About post sets out what it is and why it exists. The short version: it is a systematic playbook for building ventures that are more likely to succeed, more capital-efficient, and more profitable, designed for the techno-economic conditions that actually exist today rather than the ones that existed thirty years ago.
The first commitment is called Demand-First Design, and it begins with a reordering of the question that venture building asks at inception. The existing playbook, the one that still governs most of what happens in VC-backed startups and corporate innovation centres, asks: what can we build, and who might want it? The new one asks: who needs a transformative solution, and what would it take to build it for them? The sequence looks like a small adjustment. It is not. Everything else in the architecture follows from which question you start with.
The idea to rethink existing venture development principles arose out of necessity. The dominant model served its era well. The first generation of digital ventures was built in conditions that were structurally forgiving: technology was genuinely scarce, building was hard, and first-mover technical advantage translated reliably into market position. In that environment, assembling a capable team around a promising capability and then finding its market made sense. The methodology fit the reality.
That reality is gone. The cost of building has collapsed. Capable teams are abundant. Technological advantage, in most domains, has a shorter shelf life than the ventures designed around it. In this environment the possibility-first model does not just underperform. It systematically misdirects effort, capital, and time toward the wrong question.
The Demand-First Principle is the architectural response to this shift. Its formulation is simple: the success of new ventures is no longer primarily determined by what can be built, but by what needs to be solved. The winning narrative is no longer a new capability looking for a market. It is a named buyer looking for a transformative solution. Everything that follows in venture design, from strategy and capital structure through team composition, milestones, and the conditions under which a venture is wound down rather than extended, flows from this single inversion.
The operative word is named. Not a market segment. Not a persona. Not an assumed future user. A specific organisation, with a specific operational problem, whose willingness to pay has been established before capital is deployed. The demand signal is real, not inferred.
This is not a customer discovery methodology. Customer discovery, in the Lean Startup tradition, is a process applied after a venture thesis exists, a way of testing and refining assumptions that were formed on possibility grounds. Demand-First Design operates upstream of that entirely. The venture thesis is constructed from the demand signal, not adjusted against it. The buyer is the origin point, not the validation checkpoint.
The implications cascade through the entire venture architecture. Financial modelling becomes more honest: you are projecting against a known willingness to pay, not an assumed market size. De-risking becomes structural, because the named buyer relationship is itself the primary risk mitigation mechanism, not a milestone to be achieved after funding. Exit architecture becomes designable at inception, because you know who the likely acquirer is. And the conditions under which a venture should be terminated rather than sustained on optimism can be defined at the outset rather than negotiated in distress.
That last point is underappreciated. One of the persistent failure modes of possibility-first ventures is the inability to distinguish between a pivot and a rationalisation, between a genuine strategic adjustment and a team unwilling to acknowledge that the original thesis was wrong. When demand is named and specific, this distinction becomes considerably cleaner. Either the named buyer is moving toward a transaction, or they are not. The signal is less ambiguous.
Demand-First Design is the first and deepest of the framework’s operative commitments. The others, Ecosystem Architecture, Portfolio Strategy, and Falsifiability, are downstream of it. Get the demand question wrong and the rest of the architecture, however sophisticated, is optimising the wrong system.
The next post in this series takes up Ecosystem Architecture: how the relationships between corporations, capital, governments, and academia are designed as functional assets before execution begins, and why a venture builder that leaves this to chance is competing with one hand tied.