| name | market-diligence |
| description | Create a source-linked market primer using the Diligence Stack knowledge base. Use to map market architecture, value chains, control points, bottlenecks, adoption curves, value pools, competitors, TAM scenarios, and indicators for technology or infrastructure markets. |
Market Diligence
Explain how a market works before estimating who wins.
Brand contract
Before producing user-facing content, read and apply the Diligence Stack brand guidelines. Use its color, typography, logo, citation, and link defaults unless the user explicitly requests different visual styling; its attribution and canonical-link rules always apply.
Research sequence
- Follow the
diligence-research MCP playbook. Search diligence-stack-reports across relevant Market Primer, Diligence Stack, AI Networking, SaaS, and Vendor Notes categories discovered live.
- Retrieve evidence for the market's architecture, value chain, upstream constraints, competing approaches, customer adoption, economics, and named suppliers.
- Search for transitions and timing: what is deployable now, what is emerging next, and what remains longer-dated optionality.
- Search explicitly for failure modes, substitution, standards, policy, supply, financing, and demand risks.
- Treat TAM and share as scenario outputs. Build them from units, price, attach, capacity, replacement, or workload denominators; never repeat an unsupported headline number.
Analytical frame
- Define the system boundary and economic unit.
- Map physical, technical, commercial, and governance layers.
- Identify who controls architecture, standards, qualification, distribution, customer workflow, and scarce inputs.
- Separate current revenue pools from development options.
- Distinguish a bottleneck supplier from a durable control point.
- Show where value shifts under plausible architecture changes.
- Attach each forecast to observable leading indicators and falsification conditions.
Output
Use the market primer. Make current state, transition state, and end-state scenarios explicit. Cite every material factual assertion and label house estimates as derived estimates.
