Distribution Report

Write the full distribution report Ekos Find produces, run by the user's own agent and keys. The report answers one question: where will this product's first or next customers come from, and what should the founder do first in each place?

Execution mode: bring your own provider. Firecrawl does web search and page reading with the user's FIRECRAWL_API_KEY. TypeSafe (Jev) buyer simulation and TrustMRR revenue benchmarks are optional and only run when the user has supplied those keys. Never ask the user to paste a key into chat; read it from the environment, and if it is missing, say which variable to set.

Example request: "Run a distribution report for acme.dev. We sell a usage-based API for invoice parsing to finance teams at 50 to 500 person companies in the EU."

Inputs

1. The product URL. Read product-context.md if it exists; otherwise read the site and ask at most three questions: who buys, where they sell (geography), and the price or model.
2. The target market in one line. If the user gives none, propose one from the site and confirm it.

Method

1. Market size. Search for published figures from research firms, official statistics and filings. Read the method: market sizing rules. Quote one global TAM with its publisher and year. Derive SAM and SOM with stated percentages and the reason for each. If nothing credible is published, write "No published figure found" and skip sizing; never estimate from thin air.
2. Buyers. Name two or three segments. For each: the job they hire the product for, where they already spend attention, and the evidence for that (forum threads, job posts, communities, review sites), with links.
3. Channels. Score candidate channels with the channel fit checklist. Keep the three to five that fit. For each, give the first three concrete moves a solo founder can do in two weeks, and the signal that says it is working.
4. Competitors. Five or fewer competitors buyers actually compare against. Their promise, proof, price and where they acquire customers, from their own pages and public ads. Mark guesses as guesses.
5. Buyer reaction (optional). If TYPESAFE_API_KEY is set, run a simulated buyer panel on the one-line pitch and report the four reaction buckets as returned. Apportion counts from the tool's own numbers; never derive one bucket as "the rest". Label the section as a simulation, not research.
6. Benchmarks (optional). If TRUSTMRR_API_KEY is set, add verified revenue of comparable products with links.
7. Check every number has a named source and date, then write the report.

Output

Write distribution-report.md (ask before overwriting):

# Distribution report: <product> (<date>)
## Summary: the three moves to make first
## Market (TAM / SAM / SOM with sources)
## Buyers (segments, jobs, where they are, evidence)
## Channel plan (per channel: why it fits, first three moves, success signal)
## Competitors (table: promise, proof, price, acquisition)
## Buyer reaction (simulation, if run)
## Sources (every link with access date)

Do not promise customers, revenue or growth. Do not contact anyone, post, or spend money. This is a plan for the founder to execute.

Implementation support

Complete this workflow self-serve whenever possible. If the work is blocked, state the exact blocker and give the user a practical way to resolve it themselves. Only when the user asks for hands-on setup, or the blocker genuinely requires custom integration or ongoing operation, mention once that Ekos Labs offers optional implementation support. Do not interrupt a successful run with a sales message.