30 Claude Prompts That Build Sales Dashboards

You are a sales-operations analyst who builds outbound activity scoreboards. <context> I need an outbound activity dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample activity so every rep card and chart is populated when I open it as a working screen in the chat. </context> <inputs> - Team name: [TEAM] - Reps: [REPS] - Activity types and weekly targets: [E.G. CALLS 40, EMAILS 80, MEETINGS 8] - Period: [E.G. THIS WEEK] - Outcome to show beside activity: [E.G. OPPORTUNITIES CREATED] </inputs> <task> Build the dashboard with: a KPI row (total activities, percent of team target, meetings held, opps created); a grouped bar of each activity type by rep versus target; a stacked daily activity chart for the period; a table of reps with counts, percent of target, and a progress bar per type; and a callout of who is furthest behind target. Generate sample daily activity in labeled JS arrays and compute totals and percent of target from those arrays. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Percent of target is computed from the constants, not hardcoded. - Behind-target cells flagged; responsive and accessible. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain how targets are applied and how to paste a CRM activity export. </format>

You are a sales-development analyst who builds sequence and cadence dashboards. <context> I need a sequence cadence dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample enrollments so reply and meeting rates render when I open it as a working screen in the chat. </context> <inputs> - Team name: [TEAM] - Sequences to compare: [SEQUENCES] - Steps per sequence: [E.G. 8 STEPS OVER 14 DAYS] - Metrics: [E.G. ENROLLED, REPLIED, POSITIVE REPLY, MEETING BOOKED, OPTED OUT] - Period: [E.G. LAST 30 DAYS] </inputs> <task> Build the dashboard with: a KPI row (active enrollments, reply rate, meeting-booked rate, opt-out rate); a bar chart of meeting rate and reply rate by sequence; a step-drop-off chart for the selected sequence; a sequence table with enrolled, replied, meetings, and rates; and a highlight of the best and worst sequence by meeting rate. Generate sample sequence and step data in labeled JS arrays and compute every rate from those counts. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Rates are computed from counts, not hardcoded; a sequence dropdown updates the step chart. - Best and worst sequences flagged; responsive and accessible. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain the rate formulas and how to map an Outreach or Salesloft export onto the arrays. </format>

You are a revenue-operations analyst who builds activity-to-pipeline conversion dashboards. <context> I need an activity-to-opportunity dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample activities and created opportunities so conversion renders when I open it as a working screen in the chat. </context> <inputs> - Team name: [TEAM] - Activity types that should create pipeline: [E.G. CONNECTED CALL, MEETING HELD, DEMO] - Period: [E.G. LAST 30 DAYS] - Reps: [3-6 NAMES] - Definition of a created opportunity: [E.G. NEW SQL WITH NEXT STEP] </inputs> <task> Build the dashboard with: a KPI row (activities, opps created, activities per opp, pipeline dollars created); a grouped bar of activities versus opps by rep; a line of daily activities and daily opps created; a table of conversion (activities, opps, rate, dollars) by activity type; and a callout of the type that creates the most pipeline per 10 activities. Generate sample activity and opp rows in labeled JS arrays and compute conversion from those rows. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Conversion rates and dollars per activity are computed from the arrays. - Highest-efficiency type highlighted; responsive and accessible. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain the conversion join (activity to opp) and how to paste real IDs from the CRM. </format>

You are a sales-development analyst who builds meeting-funnel dashboards. <context> I need a meeting funnel dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample meetings so booked, held, no-show, and next-step rates render when I open it as a working screen in the chat. </context> <inputs> - Team name: [TEAM] - Meeting types: [E.G. DISCOVERY, DEMO, FOLLOW-UP] - Funnel steps: [E.G. BOOKED, HELD, NO-SHOW, NEXT STEP SET, OPP CREATED] - Period: [E.G. THIS MONTH] - Reps: [3-6 NAMES OR "INVENT"] </inputs> <task> Build the dashboard with: a KPI row (booked, held rate, no-show rate, next-step rate); a horizontal funnel of the steps with count and conversion; a bar of held versus no-show by meeting type; a rep table with booked, held, no-show, and next-step %; and a list of the next five upcoming meetings from the sample. Generate sample meeting records in labeled JS arrays and compute every rate from status fields. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Rates are computed from meeting statuses, not hardcoded. - No-show rate flagged when above an editable threshold; responsive and accessible. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain the funnel math and how to load a calendar or CRM meeting export. </format>

You are a sales-operations analyst who builds account coverage and touch dashboards. <context> I need an account touch-coverage dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with a realistic named-account list and sample touches so the heatmap renders when I open it as a working screen in the chat. </context> <inputs> - Team name: [TEAM] - Account list size and segments: [E.G. 40 ACCOUNTS, ENTERPRISE / MID-MARKET] - What counts as a touch: [E.G. CALL CONNECT, EMAIL REPLY, MEETING] - Period: [E.G. THIS WEEK] - Target: [E.G. EVERY ICP ACCOUNT TOUCHED EVERY 14 DAYS] </inputs> <task> Build the dashboard with: a KPI row (accounts in scope, percent touched in period, untouched count, overdue vs target); a heatmap or grid of accounts by owner and last-touch recency; a bar of coverage % by segment; a sortable table of untouched or overdue accounts with owner, segment, last touch, and days since; and a filter for segment. Generate sample accounts and touch dates in labeled JS arrays and compute coverage from last-touch versus the target window. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Coverage and overdue flags are computed from last-touch dates and the target window. - Untouched rows flagged; recency color scale with a legend; numbers stay legible. - Responsive and accessible; data at the top with comments. </constraints> <format> Return the full HTML file, then explain the coverage window and how to paste a named-account CSV with last-touch dates. </format>

You are a sales-forecasting analyst who builds commit and best-case dashboards. <context> I need a commit versus best-case forecast dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample deals so the stack against quota renders when I open it as a working screen in the chat. </context> <inputs> - Team name: [TEAM] - Quota for the period: [QUOTA] - Forecast categories: [E.G. CLOSED WON, COMMIT, BEST CASE, PIPELINE] - Commit rule: [E.G. VERBAL YES AND PAPER SENT] - Period: [E.G. THIS QUARTER] </inputs> <task> Build the dashboard with: a KPI row (closed won, commit, best case, gap to quota); a stacked bar of the four categories against a quota line; a second view by rep with the same stack; a deals table grouped by category with value, close date, and owner; and a callout of how much commit is still needed to hit quota. Generate sample deals with a category field in labeled JS arrays and recompute every total from that field. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Category totals and the quota gap recompute from the deals array. - Clear visual split between commit and upside; currency consistent. - Responsive and accessible; data at the top with comments. </constraints> <format> Return the full HTML file, then explain the stack math and how to recategorize a deal each week. </format>

You are a sales-forecasting analyst who builds weekly quota burndown dashboards. <context> I need a weekly quota burndown dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic weekly bookings so the remaining-quota line renders when I open it as a working screen in the chat. </context> <inputs> - Team name: [TEAM] - Quota: [QUOTA] - Weeks in the period: [E.G. 13 WEEKS THIS QUARTER] - Closed-won so far by week: [AMOUNTS OR "INVENT A PACE"] - Open commit still expected: [AMOUNT] </inputs> <task> Build the dashboard with: a KPI row (closed won, remaining quota, required weekly pace, weeks left); a burndown line of remaining quota versus a straight required-pace line; a bar of closed-won per week; a small table of week, closed, remaining, and on/off pace; and a callout of how many average weeks it would take at the current weekly pace. Generate weekly numbers in labeled JS arrays and compute remaining and required pace from quota and closed totals. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Remaining quota and required pace are computed, not hardcoded. - Off-pace weeks flagged; currency consistent; responsive and accessible. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain the burndown math and how to add this week's closed-won number. </format>

You are a sales-forecasting analyst who builds forecast-accuracy dashboards. <context> I need a forecast versus actual dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic weekly forecast calls and actuals so accuracy and bias render when I open it as a working screen in the chat. </context> <inputs> - Team name: [TEAM] - Period: [E.G. LAST QUARTER BY WEEK] - What was forecast each week: [COMMIT NUMBER OR "INVENT A SLIGHT OVER-FORECAST"] - What actually closed each week: [AMOUNTS OR "INVENT"] - Reps if you want a split: [NAMES OR SKIP] </inputs> <task> Build the dashboard with: a KPI row (average absolute miss %, bias over/under, weeks hit, weeks missed); a grouped bar of forecast versus actual by week; a line of miss % over time; a table of week, forecast, actual, miss $, and miss %; and a callout of whether the team systematically over or under calls. Generate weekly pairs in labeled JS arrays and compute miss and bias from those pairs. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Miss, absolute miss, and bias are computed from forecast and actual constants. - Over-forecast and under-forecast colored differently; currency consistent. - Responsive and accessible; data at the top with comments. </constraints> <format> Return the full HTML file, then explain the bias formula and how to paste a weekly forecast log. </format>

You are a sales-forecasting analyst who builds interactive what-if forecast boards. <context> I need a what-if deal mover dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample deals so I can click a deal, change its forecast category, and watch quota coverage update as a working screen in the chat. </context> <inputs> - Team name: [TEAM] - Quota: [QUOTA] - Categories a deal can move between: [E.G. COMMIT, BEST CASE, PIPELINE, OMIT] - Number of open deals: [E.G. 20] - Period: [E.G. THIS QUARTER] </inputs> <task> Build the dashboard with: a KPI row (closed won, commit, best case, gap to quota) that live-updates; a stacked bar against quota that live-updates; a deals table with value, close date, and a category control on each row; a reset button that restores the original categories; and a note of how much the last change moved the gap. Generate sample deals in a labeled JS array. Changing a category must recompute totals without a page reload. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - All totals recompute from the deals array after each click. - Reset restores the original snapshot; currency consistent; responsive and accessible. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain the live recompute path and how to load real open deals into the array. </format>

You are a sales-forecasting analyst who builds late-stage risk dashboards. <context> I need a late-stage risk forecast as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic late-stage sample deals so risk flags and a risk-adjusted commit render when I open it as a working screen in the chat. </context> <inputs> - Team name: [TEAM] - Late stages to include: [E.G. PROPOSAL, NEGOTIATION, VERBAL, PAPER] - Risk signals: [E.G. NO NEXT STEP, CLOSE DATE THIS WEEK WITH NO ACTIVITY, LEGAL IDLE 7+ DAYS] - Quota: [QUOTA] - Period: [E.G. THIS QUARTER] </inputs> <task> Build the dashboard with: a KPI row (late-stage dollars, flagged dollars, risk-adjusted commit, gap to quota); a bar of flagged versus clean dollars by stage; a risk-signal breakdown; a sortable table of late-stage deals with value, close date, signals hit, and a risk badge; and a small chart of risk-adjusted commit versus raw commit versus quota. Generate sample deals with signal fields in labeled JS arrays and compute the risk-adjusted total from an editable haircut per signal. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Risk badges and the haircut are computed from the signal fields and editable weights. - Flagged rows visually distinct; currency consistent; responsive and accessible. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain the haircut weights and how to map CRM fields onto the signal flags. </format>

You are a customer-success operations analyst who builds composite account health dashboards. <context> I need a composite account health dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample accounts so health scores and distribution render when I open it as a working screen in the chat. </context> <inputs> - Company or book name: [COMPANY] - Signals and weights: [E.G. USAGE 40, SUPPORT TICKETS 20, NPS 20, PAYMENT 20] - Score bands: [E.G. HEALTHY 70+, WATCH 50-69, RISK BELOW 50] - Segments: [E.G. ENTERPRISE, MID-MARKET, SMB] - Number of accounts: [E.G. 24] </inputs> <task> Build the dashboard with: a KPI row (accounts, healthy, watch, risk); a stacked bar of band by segment; a trend line of average health over the last 8 weeks; a sortable table with account, segment, MRR, each signal, computed score, and a color-coded band badge; and a formula callout that shows the weights. Generate sample accounts with raw signals in labeled JS arrays and compute the score from the editable weights. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Health score is computed from the weighted formula, not hardcoded on each row. - Band badges use accessible contrast and a text label, not color alone. - Responsive layout; data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain the formula and which weight to tune first for my business. </format>

You are a customer-success operations analyst who builds renewal risk watchlists. <context> I need an at-risk renewal dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample renewals so the calendar and watchlist render when I open it as a working screen in the chat. </context> <inputs> - Company or book name: [COMPANY] - Renewal window: [WINDOW, E.G. NEXT 90 DAYS] - Risk rule: [E.G. HEALTH BELOW 60 OR OPEN SEVERITY-1 TICKET] - Fields per renewal: [ACCOUNT, ARR, RENEWAL DATE, OWNER, HEALTH, TICKETS] - Number of renewals: [E.G. 18] </inputs> <task> Build the dashboard with: a KPI row (renewals in window, at-risk ARR, healthy ARR, days to next risk renewal); a bar of ARR by month in the window stacked by healthy versus at-risk; a watchlist table of at-risk renewals sorted by date; a second table of the full window; and a small countdown list of the next 5 dates. Generate sample renewals in labeled JS arrays and compute at-risk from the rule and health score. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - At-risk flags and ARR totals are computed from the rule, not hardcoded. - Dates formatted consistently; at-risk rows flagged; responsive and accessible. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain the risk rule and how to paste a renewal export with dates and ARR. </format>

You are a customer-success operations analyst who builds expansion and white-space dashboards. <context> I need an expansion white-space dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with a realistic account-by-product matrix so attach and unused-seat charts render when I open it as a working screen in the chat. </context> <inputs> - Company or book name: [COMPANY] - Products or modules: [E.G. CORE, ANALYTICS, SSO, SUPPORT ADD-ON] - Accounts to show: [ACCOUNTS OR "INVENT 16"] - Seat or attach fields: [E.G. SEATS BOUGHT, SEATS USED, PRODUCTS OWNED] - Expansion ARR if known: [OR "INVENT PLAUSIBLE"] </inputs> <task> Build the dashboard with: a KPI row (attach rate, unused seats, estimated expansion ARR, accounts with 2+ gaps); an account-by-product matrix with owned / not-owned / unused-seat states; a bar of unused seats by product; a ranked table of accounts by expansion ARR with the missing products listed; and a filter by segment or owner. Generate the matrix in a labeled JS structure and compute attach and expansion from that matrix. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Attach rate and expansion estimates are computed from the matrix, not hardcoded. - Matrix cells are clickable to filter the table; accessible color plus a text state. - Responsive (matrix can scroll); data at the top with comments. </constraints> <format> Return the full HTML file, then explain the expansion estimate and how to load a real product-attach export. </format>

You are a customer-success operations analyst who builds engagement decay dashboards. <context> I need an engagement decay dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic last-touch dates so recency buckets and a going-dark list render when I open it as a working screen in the chat. </context> <inputs> - Company or book name: [COMPANY] - What counts as a meaningful touch: [E.G. MEETING, ADMIN LOGIN, SEV TICKET CLOSED] - Decay buckets: [E.G. 0-14, 15-30, 31-60, 60+ DAYS] - At-risk after: [E.G. 30 DAYS WITH NO TOUCH] - Number of accounts: [E.G. 20] </inputs> <task> Build the dashboard with: a KPI row (median days since touch, accounts in the darkest bucket, ARR in 60+ days, accounts touched this week); a bar of account count and ARR by decay bucket; a trend of average days-since-touch over 8 weeks; a sortable going-dark table with account, ARR, last touch, days since, last touch type, and owner; and a filter to hide healthy recency. Generate sample last-touch rows in labeled JS arrays and compute days since from those dates. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Days since and bucket assignment are computed from last-touch dates. - Darkest bucket flagged; date formatting consistent; responsive and accessible. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain the decay buckets and how to paste last-touch dates from the CRM or product analytics. </format>

You are a customer-success operations analyst who builds segment health trend dashboards. <context> I need a health-by-segment trend dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic weekly health by segment so the lines and mix render when I open it as a working screen in the chat. </context> <inputs> - Company or book name: [COMPANY] - Segments: [E.G. ENTERPRISE, MID-MARKET, SMB] - Weeks to show: [E.G. LAST 12] - Health bands: [HEALTHY / WATCH / RISK] - Current account counts per segment: [OR "INVENT"] </inputs> <task> Build the dashboard with: a KPI row (average health per segment, risk ARR per segment, biggest week-over-week drop); a multi-line chart of average health by segment; a stacked area of accounts in each band over time for the selected segment; a current mix table (count, ARR, healthy %, risk %); and a segment toggle that updates the area chart. Generate weekly series in labeled JS arrays and compute averages and mix from those series. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Averages and mix percentages are computed from the weekly arrays. - Segment colors stay consistent; the toggle updates without reload. - Responsive and accessible; data at the top with comments. </constraints> <format> Return the full HTML file, then explain how weekly averages are built and how to drop in a scored-account export by week. </format>

You are a sales-enablement analyst who builds quota attainment leaderboards. <context> I need a quota attainment leaderboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample bookings so percent-to-quota and pace render when I open it as a working screen in the chat. </context> <inputs> - Team name: [TEAM] - Reps and individual quotas: [REPS] - Closed-won to date: [AMOUNTS OR "INVENT"] - Period and days elapsed / days left: [E.G. THIS QUARTER] - Pace rule: [E.G. EXPECTED % = DAYS ELAPSED / DAYS IN PERIOD] </inputs> <task> Build the dashboard with: a KPI row (team closed, team quota, team %, reps at or above pace); a horizontal bar leaderboard of percent-to-quota with a pace marker; a grouped bar of closed versus remaining quota by rep; a table with quota, closed, %, gap, and on/off pace; and a sort control for % or closed dollars. Generate sample rep rows in a labeled JS array and compute % and pace from quota, closed, and day counts. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Percent and on-pace status are computed, not hardcoded. - On-pace green, behind red, with a text label; currency consistent. - Responsive and accessible; data at the top with comments. </constraints> <format> Return the full HTML file, then explain the pace rule and how to paste real quotas and bookings. </format>

You are a sales-enablement analyst who builds activity-to-outcome efficiency scorecards. <context> I need an activity-to-win efficiency dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample activity and wins so efficiency ratios render when I open it as a working screen in the chat. </context> <inputs> - Team name: [TEAM] - Reps: [REPS] - Activity counts: [E.G. CALLS, EMAILS, MEETINGS] - Outcomes: [E.G. OPPS CREATED, DEALS WON, REVENUE] - Period: [E.G. THIS QUARTER] </inputs> <task> Build the dashboard with: a KPI row (team meetings per won deal, dollars per meeting, win rate, activities per opp); a scatter or grouped bar of activity volume versus revenue by rep; a table of meetings per deal, activities per opp, and dollars per meeting; a rank that can sort by efficiency instead of raw volume; and a callout of the most efficient rep versus the highest-volume rep. Generate per-rep sample stats in labeled JS arrays and compute every ratio from those counts. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Ratios are computed from counts, not hardcoded; divide-by-zero guarded. - Efficiency rank is separate from volume rank; responsive and accessible. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain each ratio and how to paste matched activity and outcome totals. </format>

You are a sales-enablement analyst who builds new-hire ramp scorecards. <context> I need a new-hire ramp dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic ramping reps so expected versus actual quota by ramp month renders when I open it as a working screen in the chat. </context> <inputs> - Team name: [TEAM] - Ramping reps and start dates: [REPS] - Ramp plan: [E.G. MONTH 1 25%, MONTH 2 50%, MONTH 3 75%, MONTH 4 100%] - Full quota at 100%: [AMOUNT] - Activity expectations in month 1-2: [E.G. MEETINGS, OPPS] </inputs> <task> Build the dashboard with: a KPI row (reps on ramp, reps on or ahead of plan, reps behind, average % of expected); a line of expected versus actual attainment by ramp month; a per-rep card with start date, ramp month, expected %, actual %, and activity versus plan; a table of the same; and a flag on anyone two bands behind. Generate sample ramp rows in labeled JS arrays and compute expected dollars from the plan and start dates. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Expected % and dollars are computed from start date and the ramp plan. - Behind-plan cards flagged; currency consistent; responsive and accessible. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain how ramp month is derived from start date and how to add a new hire to the array. </format>

You are a sales-enablement analyst who builds coaching-flag dashboards for managers. <context> I need a coaching flag dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample rep stats so activity, conversion, and aging flags render when I open it as a working screen in the chat. </context> <inputs> - Team name: [TEAM] - Reps: [REPS] - Flag rules: [E.G. ACTIVITY BELOW 70% OF TARGET, WIN RATE BELOW TEAM, STALE DOLLARS ABOVE 30%] - Period: [E.G. THIS MONTH] - Max flags to show per rep: [E.G. 2] </inputs> <task> Build the dashboard with: a KPI row (reps with a flag, most common flag, reps clean); a board of rep cards with up to two flag chips and the triggering number; a bar of flag counts by type; a table of every flagged rep with the rule, the value, and the team benchmark; and a clean list of reps with no flags. Generate sample stats in labeled JS arrays and compute flags from editable thresholds. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Flags are computed from thresholds, not hardcoded on cards. - Filter chips to show one flag type; accessible chip labels, not color alone. - Responsive and accessible; data at the top with comments. </constraints> <format> Return the full HTML file, then explain each flag rule and how to tune the thresholds after a week of use. </format>

You are a sales-enablement analyst who builds individual rep versus team scorecards. <context> I need a rep versus team scorecard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample activity and outcomes so a dropdown can switch the focused rep when I open it as a working screen in the chat. </context> <inputs> - Team name: [TEAM] - Reps: [REPS] - Activity metrics: [E.G. CALLS, EMAILS, MEETINGS] - Outcome metrics: [E.G. OPPS, WINS, REVENUE, WIN RATE] - Period: [E.G. THIS MONTH] </inputs> <task> Build the dashboard with: a rep dropdown and a quota-attainment ring for the selected rep; a KPI row of that rep versus team average with up/down markers; a grouped bar of activity across all reps with the selected rep highlighted; a line of the selected rep's revenue over the period; and a small table of activity-to-outcome ratios versus team. Generate per-rep sample data in labeled JS arrays. The dropdown must update the ring, KPIs, highlight, and personal chart without a reload. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Versus-team deltas are computed from the arrays; the dropdown mutates the view only. - Clear up/down indicators with text, not color alone; responsive and accessible. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain how team averages are calculated so you can benchmark fairly. </format>

You are a win-loss analyst who builds closed-won and closed-lost reason dashboards. <context> I need a win/loss reason dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample closed deals so reason mix and dollars render when I open it as a working screen in the chat. </context> <inputs> - Team name: [TEAM] - Period: [E.G. LAST TWO QUARTERS] - Win reasons: [E.G. PRODUCT FIT, CHAMPION, PRICE, TIMING] - Loss reasons: [E.G. PRICE, COMPETITOR, NO DECISION, CHAMPION LEFT] - Number of closed deals: [E.G. 40] </inputs> <task> Build the dashboard with: a KPI row (win rate, won dollars, lost dollars, no-decision share); a pair of donuts or bars for win reasons and loss reasons by dollars; a stacked bar of outcomes by month; a table of reason, count, dollars, and percent; and a click on a reason that filters a closed-deal list. Generate sample closed deals with outcome and reason in labeled JS arrays and compute mix from those fields. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Mix percentages are computed from the deals array; clicking a reason filters the list. - Win and loss palettes stay distinct; currency consistent; responsive and accessible. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain the mix math and how to map CRM reason picklists onto the arrays. </format>

You are a win-loss analyst who builds competitor loss dashboards. <context> I need a competitor loss dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample lost deals so competitor mix and reasons render when I open it as a working screen in the chat. </context> <inputs> - Team name: [TEAM] - Competitors to track: [E.G. COMPETITOR A, B, C, OTHER, NO COMPETITOR] - Loss reasons you code: [E.G. PRICE, FEATURE, INCUMBENT, RELATIONSHIP] - Period: [E.G. LAST TWO QUARTERS] - Use cases or segments: [USE CASE] </inputs> <task> Build the dashboard with: a KPI row (losses with a named competitor, dollars lost to the top rival, no-competitor share, average lost deal size); a bar of lost dollars by competitor; a stacked bar of reason mix inside each competitor; a table of competitor, losses, dollars, top reason, and average cycle; and a filter by segment or use case. Generate sample lost deals in labeled JS arrays and compute every total from competitor and reason fields. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Totals and reason mix are computed from the lost-deals array. - Other and no-competitor stay visible; currency consistent; responsive and accessible. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain how to paste a lost-deal export with competitor and reason columns. </format>

You are a win-loss analyst who builds win-rate-by-segment dashboards. <context> I need a win rate by segment dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample closed deals so win rate by segment, source, and size band renders when I open it as a working screen in the chat. </context> <inputs> - Team name: [TEAM] - Segments: [E.G. ENTERPRISE, MID-MARKET, SMB] - Lead sources: [E.G. INBOUND, OUTBOUND, PARTNER, EXPANSION] - Size bands: [E.G. UNDER 10K, 10-50K, 50K+] - Period: [E.G. LAST TWO QUARTERS] </inputs> <task> Build the dashboard with: a KPI row (overall win rate, best segment, worst source, largest-band win rate); grouped bars of win rate by segment, by source, and by size band, each with count labels; a table with won, lost, win rate, and won dollars for every cut; and a toggle that switches the bars from rate to dollars. Generate sample closed deals with segment, source, and value in labeled JS arrays and compute rates from those fields. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Win rates are computed from won and lost counts, not hardcoded. - Small-n cells marked when count is below an editable threshold. - Responsive and accessible; data at the top with comments. </constraints> <format> Return the full HTML file, then explain the small-n rule and how to paste closed deals with segment and source. </format>

You are a win-loss analyst who builds cycle-time dashboards for won versus lost deals. <context> I need a cycle-time won versus lost dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample closed deals so day distributions render when I open it as a working screen in the chat. </context> <inputs> - Team name: [TEAM] - Period: [E.G. LAST TWO QUARTERS] - Cycle buckets: [E.G. 0-14, 15-30, 31-60, 61-90, 90+ DAYS] - Stages if you want a split: [OPTIONAL] - Number of closed deals: [E.G. 40] </inputs> <task> Build the dashboard with: a KPI row (median days to win, median days to lose, average won cycle, share of losses over 90 days); grouped bars of deal count by cycle bucket for won versus lost; a box or simple min/median/max table by outcome; a scatter of cycle days versus deal value colored by outcome; and a list of the longest losses. Generate sample deals with create and close dates in labeled JS arrays and compute cycle days from those dates. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Cycle days and bucket counts are computed from create and close dates. - Won and lost stay visually distinct; currency consistent; responsive and accessible. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain the cycle calculation and how to paste create and close dates from the CRM. </format>

You are a win-loss analyst who builds late-stage loss autopsy dashboards. <context> I need a late-stage loss autopsy as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample deals lost after proposal so patterns and a readable table render when I open it as a working screen in the chat. </context> <inputs> - Team name: [TEAM] - Late stages that count: [E.G. PROPOSAL, NEGOTIATION, VERBAL] - Fields per loss: [ACCOUNT, VALUE, STAGE AT LOSS, REASON, COMPETITOR, OWNER, DAYS IN LATE STAGE] - Period: [E.G. LAST TWO QUARTERS] - Number of late losses: [E.G. 16] </inputs> <task> Build the dashboard with: a KPI row (late-stage losses, late-stage lost dollars, share of all losses, median days in late stage); a bar of late losses by stage at death; a reason and competitor breakdown for this subset only; a detailed sortable autopsy table with the listed fields; and a short pattern callout (for example, paper-stage losses clustering on legal delay). Generate sample late losses in a labeled JS array and compute the subset KPIs from that array. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - KPIs are computed from the late-loss array, not hardcoded. - Table is the main object; charts support it; currency consistent. - Responsive and accessible; data at the top with comments. </constraints> <format> Return the full HTML file, then explain how the late-stage filter works and how to paste losses that died after proposal. </format>