# product-platform

Use for SaaS, product, platform, security, workflow, and ecosystem decks.

Hard gates:

- Show the product system, not a list of features.
- Tie each capability to adoption, expansion, monetization, efficiency, or
  customer quality.
- Avoid generic architecture boxes. Labels must be concrete enough that the
  diagram would fail if moved to another company.
- Use a small set of recurring diagram primitives so the deck feels authored.
- Connectors, lanes, and containers must have explicit semantics; if a viewer
  cannot say what a line, arrow, or box means, remove or rebuild it.

Required proof objects:

- Platform map or workflow architecture.
- Use-case or customer journey visual.
- Adoption/expansion proof.
- Product-to-financial linkage slide.
- Roadmap or strategic direction slide when asked.

Failure signs:

- Repeated feature-card grids.
- Diagrams with vague labels such as "AI", "Data", "Platform" only.
- Product slides disconnected from business outcomes.
- Flow diagrams whose arrows float, cross unrelated objects, or imply a
  sequence the content does not support.
- Boxes that look aligned decoratively but do not encode a real product system.
