See account context, active opportunities, stakeholders, recent activity, and the next sales action in one place. The screen connects Overview and Deals so sales teams can find the “Add activity” action while checking account value and open deals.
Use this reference when you need to design this workflow inside an existing product. The example includes practical records such as Northstar renewal · Negotiation and Expansion · Discovery, rather than an empty visual shell.

Workspace
Add activity
Workspace
Default, loading, empty, error, permission, success
Adaptable product UI theme
Sales teams need a clear “Add activity” action without losing sight of account value, open deals and the affected records. Keep the decision and its outcome clear before moving to the next task.
Overview → Deals → Add activity → Review outcome
Workspace, Overview, Deals, Contacts, accessible states, contextual actions
Keep the main job visible above supporting panels. Group related controls and surface exceptions where people act.
In this design, people should be able to compare Northstar renewal · Negotiation with Expansion · Discovery. Make account value clear, then use open deals to explain whether the next step needs attention.
Before handing this to a designer or engineer, check keyboard focus, error copy, permissions and what happens after they choose the “Add activity” action. The happy path alone is not enough.
Related UI examples: Deal Pipeline, Contact Import, Lead Inbox.
Design a account detail screen for our existing software product. Use our real design-system tokens, components and product language. Show Overview and Deals, include believable records such as Northstar renewal · Negotiation, and make add activity easy to find. Map loading, empty, failure, permission and success states before you create editable high-fidelity screens.