The Value Bureau View products
Menu
Back to method archive
VB-M001 Testing E1

Narrow digital product pre-sell

Test willingness to pay for one bounded digital result before expanding the manuscript, asset pack, or catalog.

Created 2026-06-22Updated 2026-06-22By Method ID VB-M001
Testing record. A Value Bureau experiment is active or ready to launch with a pre-written decision rule. Source-backed mechanism or operator evidence.

Economic job

Buyer, problem, and value

Buyer
A creator, freelancer, or small operator with one recurring job they want to complete faster or with fewer mistakes.
Problem
Building a complete digital product before proving that a specific buyer will pay for the result.
Value created
A small paid commitment reveals demand while the offer is still cheap to change.

Method

Operating sequence

  1. Name one buyer, one painful job, and one concrete deliverable.
  2. Publish a proof-led offer page before producing the full asset set.
  3. Ask for a preorder, paid pilot, or qualified waitlist commitment.
  4. Record objections, checkout behavior, and the pre-written decision rule.
  5. Build the complete product only after the demand signal clears the threshold.

Economics

How value is captured

Pricing basis
Price the smallest useful outcome, not the eventual size of the catalog.
Capital required
Very Low
Time to first test
Two to seven days
Fulfillment load
Low

Revenue models

  • preorder
  • low-ticket sale
  • paid pilot

First test

A narrow buyer will commit before the full product exists when the job, proof, delivery, and price are clear.

Setup

  1. Create one page for one job and one tier.
  2. Show one worked example or sample artifact.
  3. Route all traffic through tracked links.
  4. Ask for a preorder or qualified signup.

Primary metric

qualified_paid_commitments

Budget cap

Use no broad paid spend until purchase tracking is reconciled.

Scale

Build and distribute after 5 paid preorders, 10 low-ticket sales, or 50 qualified signups.

Iterate

Change the job, proof, price, or audience when interest is visible but commitment is weak.

Archive

Archive the offer after intentional distribution produces no qualified response.

Distribution and capability

Inputs

Channels

  • owned audience
  • targeted outreach
  • search content
  • small capped paid test

Skills

  • offer design
  • proof writing
  • basic landing page setup
  • customer interview notes

Tools

  • static landing page
  • checkout or waitlist form
  • experiment ledger
  • decision log

Compounding asset

What remains after the test

A library of buyer language, proof examples, price responses, and completed experiment records.

Method priority scores
Speed5 / 5
Capital Light5 / 5
Codex Leverage5 / 5
Feedback Speed4 / 5
Margin5 / 5
Risk Control4 / 5
Defensibility2 / 5
Strategic Fit5 / 5

Risk controls

What can break the method

A weak traffic source can create a false negative.

Control: Define the intended buyer and minimum distribution effort before judging the method.

Pre-selling creates a delivery obligation.

Control: State the delivery date, scope, refund path, and capacity limit before taking payment.

Source trail

Why this record exists

  • Mission Briefdocs/00-mission-brief.md

    Sets the rule to test offers before building products.

  • Product Experimentsdocs/04-product-experiments.md

    Defines first offer candidates and paid commitment thresholds.

Experiment history

Observed contact with the market

  • exp-first-bundleAssets Ready

    Assets were built, but no market result was recorded. The method remains in testing.

Current archive decision

Keep as the default product-development method.

It is the closest match to the mission rule that evidence must precede catalog growth.

Apply the structure

Build a private card for your version of the method.

Export the buyer, mechanism, first test, risk, and stop rule before expanding the work.

Build a method card