Account executives
Use a prioritized pipeline, due follow-ups, and recent engagement to plan the day and keep deals from becoming stale.
Concept Preview
Fictional sample dataCRM Overview
Open pipeline$486k
New leads128
Due today17
Win rate31%
Opportunity pipeline
Qualified · 8
Northwind$24k · Tue
Cedar Labs$18k · Thu
Proposal · 5
Harbor Co.$42k · Today
Juniper$31k · Fri
Negotiation · 3
Atlas Works$67k · Wed
Who This Dashboard Is For
The dashboard should change emphasis by role without changing the meaning of the underlying stages and metrics.
Sales managers
Use stage movement, aging, coverage, and rep-level workload to coach the process instead of reacting only to closed revenue.
Revenue operations
Use completeness, ownership, source, and conversion data to find broken handoffs and inconsistent pipeline hygiene.
KPIs and Data
CRM metrics should describe both inventory and flow. A large pipeline can be unhealthy when it is old, underqualified, or missing next steps.
Open pipeline value
- What it measures
- The total potential value of active opportunities inside the selected scope.
- Why it belongs
- It shows the revenue currently in motion and provides context for coverage and stage distribution.
- How to present it
- Show the amount with stage segments, owner filters, and an explicit rule for excluded lost, duplicate, or unqualified records.
Stage conversion rate
- What it measures
- The share of opportunities that advance from one defined stage to the next.
- Why it belongs
- Stage conversion exposes where the process loses qualified opportunities and where coaching or qualification may need work.
- How to present it
- Use a funnel or stage-to-stage table with counts, percentages, and a cohort window. Avoid presenting one overall rate without transitions.
Lead response time
- What it measures
- Elapsed time between a qualified lead event and the first accepted sales response.
- Why it belongs
- It turns an operational service level into something visible before pipeline outcomes arrive.
- How to present it
- Show median time, breach count, and a distribution by source or team. A median alone can hide a long tail of ignored leads.
Stale opportunities
- What it measures
- Open deals with no qualifying activity or next step within an agreed threshold.
- Why it belongs
- Staleness directs attention to records that inflate pipeline or require a decision.
- How to present it
- Use a count plus a sortable queue showing age, value, owner, last activity, and next action. Make the threshold visible.
Recommended Layout
Lead with today’s work, preserve the shape of the pipeline, and provide a short path from summary to record detail.
Daily attention row
Place overdue follow-ups, new assigned leads, meetings, and stale-deal alerts above the pipeline.
Stage board or funnel
Give the main canvas to the selected team’s opportunities, with value and aging visible at each stage.
Activity and response panel
Use a secondary column for recent calls, emails, meetings, assignments, and service-level breaches.
Record detail layer
Open contacts and opportunities in a slide-over that preserves context and exposes the next action.
Features and Components
Useful CRM components reduce the distance between noticing a problem and updating the work record.
- Saved filters for owner, team, territory, source, stage, and reporting period.
- A searchable opportunity table with stage, age, value, last activity, and next step.
- An activity timeline that distinguishes human contact from automated system events.
- Categorized alerts for overdue tasks, reassignment, missing data, and stage aging.
- Accessible stage colors paired with written labels and counts.
Mistakes to Avoid
A CRM screen fails when visual polish masks weak process definitions or encourages records to remain ambiguous.
- Treating pipeline as forecast.Open value is not committed revenue; show forecast categories and probability rules separately if the business uses them.
- Rewarding activity volume.More emails or calls do not automatically mean better selling, so pair activity with progression and outcome context.
- Allowing silent stage drift.Make stage definitions and aging thresholds explicit so the board does not become a parking lot.
- Ignoring permissions.Frontend visibility is not authorization; record access and field editing require a real identity and permissions layer.
VibeCodePack Missions Used
These exact feature titles were verified in the inspected VibeCodePack source files. The mapping recommends a frontend mission combination; it does not expose the private instructions inside those files.
Sales Performance Dashboard with Interactive Heatmaps
Provides a performance-analysis pattern for comparing density across stages, teams, or periods.
Interactive Data Table with Sorting and Pagination
Maps to a searchable, manageable opportunity and contact inventory.
Activity Feed Timeline with Expandable Details
Supports the chronological record of calls, emails, meetings, notes, and assignment changes.
User Management Table with Inline Editing Capabilities
Offers a frontend pattern for owner assignment and record administration, subject to real authorization.
User Notification Center with Categorized Alerts
Organizes overdue tasks, ownership changes, and data-quality notices.
Dropdown Menu with Integrated Search and Filters
Supports fast segmentation by rep, team, account, stage, territory, or source.
Interactive Slide-Over Panel for Detailed Information
Keeps record details and next actions available without losing the pipeline context.
Build This Dashboard With Claude Code
Define the sales stages, ownership model, response target, stale threshold, and editable fields before asking Claude Code to assemble components. Run the pipeline, activity, filtering, detail, and alert work as separate missions, then verify keyboard use, small-screen behavior, and empty or error states.
VibeCodePack supplies structured frontend missions and verification gates. It does not create a production CRM database, deliver email, record calls, enforce permissions, or synchronize customer data without the services your project connects.
VibeCodePack supports structured frontend dashboard and UI workflows. Your project must separately provide and validate production databases, APIs, authentication, payments, permissions, live data, and backend services.
Keep exploring