The eight artifacts every launch actually needs

The traditional launch document is a business plan: thirty pages, written once, read by nobody, obsolete on contact with a customer. It survives because it feels like the responsible thing to produce.

The useful replacement is not a shorter plan. It is a set of eight artifacts, each answering a distinct question, each small enough to revise when the answer changes.

Why eight and not one

A business plan fails because it fuses questions that move at different speeds. Your market analysis changes slowly. Your positioning changes when a competitor ships. Your pricing changes when you talk to the fifth prospect. Fusing them into one document means updating any of them requires reopening all of them, which means none of them get updated.

Splitting them means each can be revised on its own clock, and each can be wrong in isolation without invalidating the rest.

Each of the eight names its framework composition — the analytical heritage it is built from — rather than presenting a generated document as if it came from nowhere. Naming the framework is not academic decoration. It tells you what the artifact is good for and what it will systematically miss.

The eight

Business model and position. Built from weighted SWOT, the Business Model Canvas, and Five Forces. Answers where you sit and why the position is defensible. The weighting matters — an unweighted SWOT is a list, and a list is not an analysis.

Product definition. Built from House of Quality plus design thinking. Answers what you are building, expressed as a mapping from customer need to product property rather than as a feature list. This is the artifact that catches "we built the thing we wanted to build" early.

Market and competitive picture. Built from PESTLE and a competitor war room. Answers what is true outside your building. PESTLE is unfashionable and remains the most reliable way to notice the regulatory or economic factor you were about to be surprised by.

Brand and identity. Built from a brand kit plus design thinking. Answers what you sound and look like, and it belongs early rather than late — every artifact after it inherits its vocabulary.

Operating design. Built from Value Chain analysis plus the autonomy ladder. Answers how the company will actually run: what work exists, who does it, and which parts are delegated to software under what level of oversight. Most launch documents skip this entirely and then discover it as a crisis at around the tenth customer.

Strategic dynamics. Built from game theory plus war-gaming and a red cell. Answers what your competitors and customers will do in response to what you do. The red cell — someone whose job is to argue the other side — is the part most teams cut and the part that most often changes a decision.

Venture canvas. Built from Lean Canvas plus current war-room state. Answers the compressed version: problem, segment, value, channel, cost, revenue. This is the artifact you show people.

The synthesis. What the other seven imply together, including where they contradict each other. Contradictions between artifacts are the most valuable output of the whole exercise, because they are the places where two beliefs you hold cannot both be true.

Two ways to work through them

There are two shapes for this, and they suit different situations.

Straight through. Run all eight and read the synthesis. This suits the case where you have context already and want the contradictions surfaced fast. It produces a complete picture in one sitting and a list of things to go verify.

Tool by tool. Work through them in a guided sequence, one at a time, with each artifact informing the next. This suits the case where the thinking has not been done yet, because the sequence itself is the value — the operating design question lands differently once the product definition exists.

Both paths are on starting a business. The choice is mostly about whether you are documenting a decision you have made or making one.

Which two are load-bearing

If you only have an afternoon, the answer is not the obvious two.

Most founders would pick business model and market. Those are the ones that feel like strategy. In practice the two that change decisions most often are product definition and operating design.

Product definition, because the mapping from need to property is where most early products go wrong, and the error is invisible until customers arrive. A feature list conceals the mapping. House of Quality makes you write it down, and writing it down is when you notice that three of your planned features trace to no stated need.

Operating design, because it is the one nobody does and the one that determines whether the company can grow past its founders. Deciding in advance which work is delegated to software, and at what level of oversight, is much easier before there is any work than after there is too much.

The other six are worth having. These two are worth having first.

What to do with them afterwards

Artifacts that are produced and then filed are a slightly more expensive business plan. Two habits keep them alive.

Attach each artifact to the assumptions it rests on, so that when an assumption is tested the affected artifact is findable. And give each one a revisit trigger tied to an event rather than a date — a new competitor, a pricing objection heard three times, a hire that changes capacity.

Then the artifacts feed strategy rather than sitting beside it. The Strategy Engine is where that handoff happens, and talking to design partners before you have a landing page is how you fill in the parts no framework can give you.

Start with an idea, or with the company you already have. Either way the eight questions are the same, and answering them separately is what makes them answerable.