How to turn a business idea into an economic method.

Definition

What is an economic method?

An economic method is a repeatable route for creating a useful change for a defined buyer and capturing a lawful share of that value. The record is more specific than a business model and more durable than a campaign. It connects the buyer, mechanism, economics, distribution, first test, evidence, risks, and current decision.

The method is the unit worth archiving because product formats change. A diagnostic audit might begin as a service, become a template, and later become software. The container changed, but the underlying mechanism may remain the same: reduce uncertainty before a costly decision.

A method is not validated because it is coherent. It is validated only when evidence survives contact with the market.

Why archive methods instead of success stories?

Success stories usually compress context. They show the offer that worked but hide the alternatives, traffic quality, measurement gaps, cost of fulfillment, and stop conditions. A method record keeps those conditions visible. It also keeps failed tests, which prevents a later operator from treating an old mistake as a new idea.

The Bureau uses stable method IDs so experiments can be attached to a method instead of becoming disconnected campaign notes. The public archive currently includes provisional methods, tests in progress, observed methods, and an archived cold-traffic test.

The nine fields in a useful method card

1. Buyer. Name the person or organization that experiences the problem and controls the exchange.
2. Problem. Describe the costly delay, uncertainty, effort, risk, or missed opportunity in the buyer's language.
3. Value created. State the useful change without relying on product features.
4. Value mechanism. Explain how the method creates the change. Examples include reducing uncertainty, compressing time, routing demand, improving quality, or coordinating work.
5. Economics. Record the pricing basis, revenue model, capital required, fulfillment load, and time to first test.
6. Distribution. Choose a reachable path to the buyer. A method with no practical route to buyers is incomplete.
7. First test. Run the smallest test that can produce a decision signal rather than applause.
8. Risk controls. Name what can break the method and the control that limits harm or false learning.
9. Decision. Write the thresholds for scale, iteration, and archive before the result is known.

Use an evidence ladder

An evidence grade is not a quality score. A beautifully designed hypothesis can remain E0. A failed test with clean measurement can reach E2 because it produced interpretable evidence.

Design a first test that can end cleanly

A useful first test has a narrow hypothesis, one primary metric, a budget or time cap, and three decision rules. The rules should be specific enough that another operator can reach the same decision from the same result.

Use the experiment decision-rule template before launching a test. That order matters because a threshold written after the result can become an explanation rather than a rule.

Worked example: when 49,558 clicks did not validate the offer

The Bureau's archived cold-paid-traffic method records a campaign that generated 421,507 impressions and 49,558 clicks, followed by one completed checkout. The result did not prove that paid traffic never works. It showed that this traffic, offer, funnel, and measurement state did not produce a trustworthy path to scale.

The archive decision was to stop buying more clicks until purchase tracking and funnel reconciliation were repaired. The compounding asset was not revenue. It was a failure record with conditions, metrics, and a clearer control for the next test. Read VB-M006 for the full method record.

A seven-step operating workflow

1. Write the method card before creating more inventory.
2. Attach each offer or campaign to one method ID.
3. Choose the smallest observable commitment, not the easiest vanity metric.
4. Record sources and assumptions beside the test.
5. Reconcile attention, actions, checkouts, purchases, revenue, and refunds.
6. Log one decision at the end of the window.
7. Update the method's status and evidence grade only when the record supports the change.

Start with a card, not a catalog.

Building another product creates more inventory. Building a method card creates a decision structure. Use the private browser tool to make the structure visible, then open the public archive to compare it with existing methods.