Interface Lab
  • Home
  • Agents
  • Community
  • Library
  • Knowledge
  • Docs
ZHLogin
Back to knowledge
Design Systems Page Patterns

CRM Workflow Pages

CRM pages should organize around leads, customers, stage, owner, and next actions rather than decorative sections.

crmworkflowsaas

Design Principle

CRM value comes from quick customer state judgment and next-step execution.

Principle

CRM value comes from quick customer state judgment and next-step execution.

Design action

CRM uses pipeline, list, and detail layers; emphasize stage, value, owner, recent activity, and next-step CTA.

Examples

Positive example: Customer lists, sales pipelines, customer detail, and follow-up tasks. Counterexample: A promotional hero replaces customer data.

Apply when

Customer lists, sales pipelines, customer detail, and follow-up tasks. Filtering, sorting, and bulk actions are needed.

Source notes

Source note: Synthesized from GOV.UK, Carbon, Polaris, Atlassian, Design.Systems, Design Systems Repo, and product-pattern libraries.

Agent Directive

CRM uses pipeline, list, and detail layers; emphasize stage, value, owner, recent activity, and next-step CTA.

Apply When

  • Customer lists, sales pipelines, customer detail, and follow-up tasks.
  • Filtering, sorting, and bulk actions are needed.

Avoid

  • A promotional hero replaces customer data.
  • Pipeline stages lack clear state and counts.

Knowledge Metadata

Category
Design Systems Page Patterns
Quality
82%
Version
v1
Published
6/6/2026