# Comparing markets, demand and opportunity

Availability: Planned API.
Last reviewed: 2026-08-28.

Compare markets using explicit evidence and modeled assumptions. The planned result helps explain a market decision; it does not prove revenue, observed business rank or an activated business.

## Define the comparison

Provide the product or business scope, candidate territories, customer hypotheses, demand inputs and the decision horizon. Record the source time, model version and any default assumptions.

Demand, reachable audience, competitive pressure and expected capture are different quantities. A revenue scenario must retain its unit, time period and capture assumptions.

## Keep the output reviewable

A comparison artifact should include territory identities, evidence, normalized metrics, assumptions, confidence and unresolved gaps. Derived opportunity plans or Product/Customer/Demand/Reach/Launch projections remain drafts until their own prerequisites are met.

For example, a modeled annual opportunity range can inform territory selection without claiming a sale, an available operator route or a ready Store.

## Promote deliberately

Selecting an opportunity can prepare a plan, draft Store or campaign. It does not authorize launch, a domain purchase, paid discovery or operator dispatch. Subsequent operations need immutable scope and separate approval/funding.

## Availability

Business APIs are planned. Empty or unsupported evidence is not a zero-demand market. Use [territory rank](/docs/guides/territory-rank) for observed comparative position and [performance](/docs/guides/performance-attribution-growth) for measured results.