Admin & dashboards · Design concept
A CRM concept linking pipeline review, deal context and a follow-up draft, with proposed ownership and unsent-message states.
Design concepts, not client projects. Screens are static mockups; names and data are illustrative.
Let a sales coordinator move from pipeline position to the context needed for a follow-up. The concept keeps drafting separate from contacting anyone.
A pipeline view organises illustrative opportunities.
Deal detail provides context for the selected opportunity.
A draft workspace presents a proposed message without sending it.
A pipeline stage should reflect an agreed process definition, not an assumed probability of winning.
A draft is preparation. Sending requires a separate action with the recipient and message available for review.
Proposed design specimens. These are static examples, not working controls or a production specification.
Pipeline canvas
#F5F7FC
Deal navigation
#315FBD
Follow-up accent
#B78B2F
Clear information. A considered next step.
Use concise sans-serif deal labels. Keep account names and ownership visible without giving sample monetary values all the emphasis.
Allow enough width for pipeline cards, then give deal notes and the message draft their own reading space.
No assigned opportunities
No opportunities match this owner and filter.
Draft saved
Follow-up draft saved. No message has been sent.
Recipient missing
Choose a recipient before reviewing this message for sending.
A draft shows intended communication; an activity record should describe what actually happened. Mixing them could make a team believe a customer has already been contacted.
