Back to method archive
VB-M004 Provisional E0

Sample-first paid data brief

Publish a small, useful sample of structured market intelligence before building a recurring report or data product.

Provisional record. A structured hypothesis with a named buyer, mechanism, first test, and guardrails. No market evidence is claimed. Structured hypothesis only.

Economic job

Buyer, problem, and value

Buyer
An operator who needs a current shortlist, benchmark, market map, or opportunity scan but cannot justify doing the research from scratch.
Problem
Data products are expensive to maintain when freshness, buyer use, and willingness to pay are unknown.
Value created
A sample proves whether structure and freshness reduce enough research time to justify payment.

Method

Operating sequence

  1. Choose one recurring decision that depends on scattered public information.
  2. Define a compact schema that makes comparison easier.
  3. Publish a representative sample with source dates and confidence notes.
  4. Offer one paid issue, update, or custom slice.
  5. Track which fields buyers use, question, and request next.

Economics

How value is captured

Pricing basis
Price against research time saved, update frequency, and decision value.
Capital required
Low
Time to first test
One to two weeks
Fulfillment load
Medium

Revenue models

  • one-off report
  • subscription
  • custom data slice

First test

A defined buyer will pay for a current, structured brief when the free sample clearly shortens a recurring research decision.

Setup

  1. Create one sample with 10 to 25 records.
  2. Show source dates, confidence, and missing fields.
  3. Offer one paid full issue or custom cut.
  4. Ask buyers which decision they used it for.

Primary metric

paid_brief_orders

Budget cap

Cap paid data access until the sample produces direct buyer pull.

Scale

Build a repeatable update cycle after 5 paid orders or 10 qualified requests for the next issue.

Iterate

Change the schema, niche, or update frequency when the sample is used but not purchased.

Archive

Archive when targeted buyers do not use the sample or request deeper coverage.

Distribution and capability

Inputs

Channels

  • email
  • search content
  • direct outreach
  • professional communities

Skills

  • source evaluation
  • data normalization
  • clear comparison design
  • update discipline

Tools

  • source registry
  • structured data file
  • report generator
  • change log

Compounding asset

What remains after the test

A normalized dataset, update history, buyer-request map, and reusable reporting system.

Method priority scores
Speed4 / 5
Capital Light4 / 5
Codex Leverage5 / 5
Feedback Speed4 / 5
Margin5 / 5
Risk Control4 / 5
Defensibility4 / 5
Strategic Fit5 / 5

Risk controls

What can break the method

Freshness costs can exceed revenue.

Control: Record update frequency, source rights, and maintenance time before promising a subscription.

A report can repeat public information without adding value.

Control: Make the schema, comparison logic, confidence notes, or update speed the paid advantage.

Source trail

Why this record exists

  • Economic Value Librarydocs/08-economic-value-library.md

    Defines data products as a core economic category.

  • Roadmap And Architecturedocs/09-roadmap-and-architecture.md

    Defines the Opportunity Radar as a future recurring data product.

Experiment history

Observed contact with the market

  • No completed Value Bureau experiment

    This record remains at its current evidence grade until a test is logged.

Current archive decision

Keep provisional until a buyer decision and sample schema are selected.

The method fits the archive mission but has no completed demand test in the repository.

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