For founders and early teams
Building a business is a sequence of decisions rather than of tasks, and the difficulty is that early decisions quietly become constraints on later ones. Naming a company before settling its positioning, or choosing a channel before knowing the audience, is reversible in principle and expensive in practice. The Omnigoal sets out what has to exist in each part of a business and which decisions depend on which — which is a more modest thing than a recipe, and a more useful one.
The problem
The most costly ordering mistake, and the one customer development literature was written to address. Months of work commit a venture to a value proposition never tested against a real audience, and by the time that becomes clear the investment already argues for continuing.
Positioning, pricing, legal structure and channel choice all narrow what is possible later. Taken in isolation each looks small; taken in the wrong order they compound into a shape the founder did not choose.
A startup checklist records what worked somewhere else under conditions that are rarely stated. It can tell you what others did; it cannot tell you what your venture has not yet decided.
The method
Seven stages in dependency order. Real ventures iterate and backtrack — the order describes what each stage assumes, not a route to follow without deviation.
Begin in the Goal Core. Why should this exist, and what would count as success? The framework treats this as its first principle: single-pointedness precedes creation. Founders who defer it reach the first hard trade-off without a criterion and decide by whichever consideration is loudest that week.
The Market Core comes before the offer rather than after it — the sequencing argument at the centre of customer development. Market opportunity, target audience, and the competitor set understood as the alternatives the customer already has, including doing nothing.
In the Business Core, decide what is offered and how it is monetised in the same conversation. A value proposition with an unresolved monetisation model is a proposition about value to the customer only, which is a necessary half rather than the whole.
Brand promise and positioning belong to the Brand Core and precede the name, the logo and the site. A visual identity built before positioning is settled is typically paid for twice — and the promise matters most of all, because it is a commitment the operation has to be able to keep from the first customer.
Back to the Business Core for the unglamorous half: legal structure, compliance, finance, suppliers, partners, first systems. None of it is interesting and each of it is a hard stop if it is missing at the wrong moment.
Set up the Data Core early. Deciding what to measure while there is nothing to measure is the only point at which it can be decided without motivated reasoning, and early ventures generate their most decision-relevant evidence in the first months — when nobody is yet collecting it.
The Omni Core defines what the customer actually encounters across every channel; the Time Core decides when to go. Launch timing is a strategic variable in its own right rather than the date on which the work happens to finish.
Take this with you
A readiness map for the first operating year. Its use is to locate what has not yet been decided, rather than to certify progress.
The stages overlap heavily in practice. What holds is the dependency: each stage answers a question the next one assumes has been settled.
Standing on other work
The venture literature is unusually rich and unusually contested. The framework does not adjudicate between these positions; it shows where each of them applies.
Market Core before Business Core
Blank’s argument for establishing the customer before building the product — the sequencing this method follows.
Data Core with the iterative loop
Ries’s cycle is the same iterative epistemology the framework describes, applied to a venture.
Market Core and Business Core
Christensen’s reframing of the customer, and a useful discipline when writing a value proposition.
Business Core — Value Proposition
A structured way of connecting what is offered to what was heard in customer conversations.
A different reading of the whole sequence
Sarasvathy’s finding that experienced founders often start from available means rather than from goals. The framework can be read in that direction, beginning in the Business Core.
Business Core and Market Core
Strong on the model itself, and not designed to cover purpose, timing or measurement.
Time Core — Project management
A way of deciding when a stage has produced enough to justify the next commitment.
Effectuation is worth singling out, because it cuts against the order described here. Both readings are defensible; which fits depends on whether your starting point is a goal you hold or a set of means you already have.
Where it lives in the framework
The Omnigoal is holistic: all eight cores are in play here, each supplying something the others cannot. Follow any of them to see the objects it contains.
Purpose and the first goal hierarchy — the criterion for later trade-offs.
Learn the core
Audience, opportunity and alternatives, established before building.
Learn the core
Offer, monetisation, finance, compliance, systems and partners.
Learn the core
Promise and positioning, settled before identity is commissioned.
Learn the core
Vision, mission and values, written while they are still honest.
Learn the core
Instrumentation put in place before there is data to bias it.
Learn the core
The customer journey across every channel, including after the sale.
Learn the core
Launch timing, market windows and contingency.
Learn the coreChecklist
In fairness
The evidence on what makes new ventures succeed is genuinely unsettled, and a framework should not imply otherwise.
Questions
The questions people ask most often about building a business and The Omnigoal.
Purpose, then market, then offer and monetisation, then identity, then the operating foundation, then instrumentation, then experience and launch timing. The order reflects dependency: each stage answers something the next one assumes. The clearest case is building before the customer is understood, which customer development literature identifies as the most costly inversion — though it is worth knowing that effectuation research describes experienced founders working the other way round, from means to goals.
Write one sentence of purpose that would remain true if the product changed entirely, and a rough goal hierarchy for one year and five. It takes an afternoon, and it becomes the criterion for the trade-offs that follow — which is precisely what founders tend to lack when a decision has to be made quickly.
Settle brand promise and positioning early; commission visual identity late. Positioning is a strategic decision that shapes the offer, while a logo expresses a decision already taken. The promise matters most, because it is a commitment the operation has to keep from the first customer rather than from the point at which it becomes convenient.
All eight are worth considering; volume in all eight is not required. The framework’s own account is that the components are not indispensable to the system’s existence but enrich it. A solo founder who has read all eight and written a paragraph in most has used it as intended — the value is in knowing what was skipped by choice rather than by oversight.
Read through the eight cores and their objects and mark everything you cannot yet say anything about. The blanks are the answer. This is the difference between a framework and a checklist: a checklist records what other companies did, while a map shows what your own venture has not yet decided.
There is no good evidence that it does, and it would be misleading to suggest otherwise — venture outcomes turn heavily on market timing, capability and circumstances no framework controls. What a structure can reasonably offer is fewer decisions taken by default and a clearer record of what was assumed, which makes it easier to see later where a judgement went wrong.
