Revenue leaders
Use attainment, forecast, coverage, and segment comparisons to identify where the operating plan needs intervention.
Concept Preview
Fictional sample dataSales Overview
Team quota progress
72%
Pipeline by stage
Pipeline$1.2m
Won$312k
Win rate34%
Cycle29d
Who This Dashboard Is For
Keep a shared metric definition while changing the level of detail for leaders, managers, and individual sellers.
Frontline managers
Use stage aging, rep pacing, deal risk, and next actions to prepare focused coaching and inspection.
Individual sellers
Use a personal view of quota, open opportunities, scheduled work, and risk signals to plan the next best action.
KPIs and Data
Separate results already achieved from potential outcomes. Bookings, forecast, and open pipeline answer different questions.
Quota attainment
- What it measures
- Credited bookings divided by assigned quota for the selected period.
- Why it belongs
- Attainment provides the clearest progress signal for the sales plan when crediting rules are stable.
- How to present it
- Use a progress bar or ring with booked amount, quota amount, percentage, and days remaining. Show adjustments explicitly.
Pipeline coverage
- What it measures
- Qualified open pipeline divided by the remaining quota target.
- Why it belongs
- Coverage connects future opportunity inventory to the gap the team still needs to close.
- How to present it
- Show the ratio alongside the numerator, denominator, stage mix, and a documented qualification rule.
Win rate
- What it measures
- Won opportunities divided by won plus lost opportunities in a defined cohort.
- Why it belongs
- Win rate helps explain whether pipeline is converting and supports comparisons by segment, source, or stage entry period.
- How to present it
- Use a percentage with won and lost counts, cohort dates, and minimum sample context. Avoid mixing open deals into the denominator.
Median sales cycle
- What it measures
- The median elapsed time between agreed opportunity start and closed-won date.
- Why it belongs
- Cycle time affects forecast timing, capacity, and the likelihood that late-stage deals close inside the period.
- How to present it
- Show median plus a distribution or upper percentile. Segment by deal type so renewals do not distort new-business timing.
Recommended Layout
Lead with plan progress, show whether enough qualified work exists, and finish with the deals or reps that need attention.
Attainment and time
Put team quota progress, booked amount, forecast range, and days remaining in the first scan line.
Pipeline composition
Use the main canvas for value by stage, coverage, aging, and expected close period.
Rep pacing
Show individual progress and trend without turning the dashboard into a public-shaming leaderboard.
Deal inspection queue
End with large, stale, slipped, or unqualified opportunities and their explicit next actions.
Features and Components
The interface should support inspection while preserving the context behind every percentage and ranking.
- Quota progress with period, booked amount, target, forecast range, and time remaining.
- Pipeline filters for owner, team, region, segment, stage, product, and close period.
- A sortable deal table showing age, value, probability category, last activity, and next step.
- Trend and heatmap views with accessible values that do not depend on color alone.
- Categorized notices for stage aging, close-date slips, and missing qualification data.
Mistakes to Avoid
Sales reporting loses credibility when definitions shift to match the desired story.
- Treating weighted pipeline as certainty.Probability-weighted amounts are estimates; keep actual bookings, forecast categories, and open pipeline visibly separate.
- Comparing unlike quotas.Ramp status, territory, role, product mix, and quota changes need context before rep comparisons are meaningful.
- Optimizing for rank.A leaderboard without coaching context can encourage poor behavior and hide territory or opportunity-quality differences.
- Ignoring data hygiene.A sophisticated chart cannot repair missing close dates, vague stages, duplicate deals, or unlogged next steps.
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 the core performance view for stage, period, territory, or representative comparisons.
Minimalist KPI Card Grid with Trend Indicators
Structures attainment, pipeline, bookings, win rate, and cycle summaries.
Interactive Data Table with Sorting and Pagination
Supports detailed deal inspection beneath the summary.
Activity Feed Timeline with Expandable Details
Adds recent deal activity and significant stage or date changes.
Interactive Slide-Over Panel for Detailed Information
Provides focused opportunity context without leaving the dashboard.
Navigation Bar with Integrated Notification Center
Connects the reporting surface to categorized deal-risk and data-quality notices.
Build This Dashboard With Claude Code
Document quota crediting, forecast categories, stage entry rules, win-rate cohorts, and cycle-time boundaries first. Then use bounded Claude Code missions for summary metrics, stage visualization, rep pacing, the deal table, detail panels, and notifications. Verify the experience with missing quotas, reassigned deals, new hires, and small samples.
VibeCodePack organizes the frontend work with agent-ready instructions and checks. It does not replace a CRM, calculate authoritative compensation, enforce territory access, or guarantee forecast accuracy.
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