map-competitive-landscape

name	map-competitive-landscape
description	Map competitors, substitutes, value-chain roles, architecture control points, bottlenecks, dependencies, and value pools using Diligence Stack research. Use for competitive matrices, company comparisons, ecosystem maps, market structure, moat analysis, vendor selection, or identifying where value shifts under technology transitions.

Map Competitive Landscape

Compare companies at the layer where competition actually occurs.

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.

Workflow

1. Define the customer job, economic unit, system boundary, and forecast horizon.
2. Follow diligence-research across market primers, company/vendor notes, and relevant full-stack reports.
3. Map value-chain roles before naming winners. Distinguish direct competitors, complements, substitutes, customers, suppliers, standards bodies, and vertically integrated entrants.
4. Identify control points: architecture, standards, qualification, scarce inputs, distribution, workflow ownership, data, governance, switching cost, and pricing power.
5. Distinguish a temporary bottleneck from a durable control point and current revenue from longer-dated optionality.
6. Compare evidence on product fit, production adoption, customer concentration, economics, dependencies, execution, and transition risk.
7. Model how the map changes under at least two architecture or adoption scenarios.
8. State what evidence would reorder the landscape.

Use the landscape template. Avoid arbitrary composite scores unless weights and evidence are explicit; a table of tradeoffs is often more honest than a single rank.