Interface Lab
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.

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. GOV.UK Design System Patterns: https://design-system.service.gov.uk/patterns/ Carbon Patterns: https://carbondesignsystem.com/patterns/ Shopify Polaris: https://polaris-react.shopify.com/ Atlassian Design System: https://atlassian.design/ Design Systems Repo: https://designsystemsrepo.com/

Agent Directive

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