30 Claude Prompts That Build RevOps Dashboards

You are a revenue-operations analyst who builds CAC-by-channel dashboards finance and demand gen can share. <context> I need a CAC-by-channel dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample spend and new-customer counts so CAC renders when I open it as a working screen in the chat. </context> <inputs> - Channels: [CHANNELS] - Period: [E.G. LAST QUARTER] - CAC target: [E.G. 1200 USD] - What counts as a new customer: [E.G. FIRST PAID INVOICE IN PERIOD] - Currency: [E.G. USD] </inputs> <task> Build the dashboard with: a KPI row (total spend, new customers, blended CAC, channels over target); a bar of CAC by channel versus the target line; a grouped bar of spend versus new customers; a table (spend, customers, CAC, versus target, share of spend, share of customers); and a click on a channel that highlights the row. Generate spend and customer counts in labeled JS constants. CAC = spend / new customers. Guard divide-by-zero. Show the formula on the page. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - CAC is computed, not hardcoded. Over-target channels flagged with a text label. - Currency formatted consistently. Responsive and accessible. - Do not invent ad-platform APIs. Sample constants plus a note on where a spend export goes. </constraints> <format> Return the full HTML file, then write the CAC formula and which constants to replace with a spend and customer export. </format>

You are a revenue-operations analyst who builds LTV-by-segment dashboards from ARPU and churn, not from a guessed lifetime. <context> I need an LTV-by-segment dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample segment stats so LTV renders when I open it as a working screen in the chat. </context> <inputs> - Segments: [SEGMENTS] - LTV method: [E.G. ARPU DIVIDED BY LOGO CHURN] - Period the ARPU and churn come from: [E.G. LAST 12 MONTHS] - Gross-margin percent if I want LTV on margin: [E.G. 80 OR SKIP] - Company: [NAME] </inputs> <task> Build the dashboard with: a KPI row (blended LTV, highest segment, lowest segment, customers in the sample); a bar of LTV by segment; a table (customers, ARPU, churn %, implied lifetime months, LTV, optional margin LTV); a small chart of lifetime months; and a formula callout that states the method. Generate per-segment ARPU, churn, and customer counts in labeled JS constants. Compute LTV and lifetime months in JS. If churn is zero, show [VERIFY] instead of infinity. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - LTV is computed from the method I gave, not hardcoded on each row. - Label logo versus revenue churn. Accessible contrast. - This is unit economics, not a sales account-health score. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then write the LTV formula and which constants to replace with a cohort extract. </format>

You are a revenue-operations analyst who builds LTV-to-CAC boards a weekly RevOps review can trust. <context> I need an LTV-to-CAC ratio dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample channel and segment rows so the ratio and payback render when I open it as a working screen in the chat. </context> <inputs> - Company: [COMPANY] - Cuts to show: [E.G. CHANNEL AND SEGMENT] - Target LTV:CAC band: [E.G. 3X TO 5X] - Monthly gross margin per customer if known: [OR "DERIVE FROM LTV AND LIFETIME"] - Currency: [E.G. USD] </inputs> <task> Build the dashboard with: a KPI row (blended LTV:CAC, channels below the band, segments below the band, blended payback months); a bar of LTV:CAC by channel with a target band; a scatter of CAC versus LTV by segment; a table (LTV, CAC, ratio, versus band, payback months); and chips to switch the bar between channel and segment. Generate LTV and CAC inputs in labeled JS constants. Ratio = LTV / CAC. Payback = CAC / monthly gross margin. Guard divide-by-zero. Show both formulas. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Ratio and payback are computed, not hardcoded. - Below-band rows flagged with a text label. Currency consistent. - Do not invent a statistical model. Arithmetic only. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then write the ratio and payback formulas and which constants to replace. </format>

You are a revenue-operations analyst who builds CAC payback boards from CAC and monthly contribution margin. <context> I need a CAC payback dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample channel rows so months-to-recover render when I open it as a working screen in the chat. </context> <inputs> - Channels: [CHANNELS] - Payback target months: [E.G. 12] - CAC and monthly contribution margin per channel: [NUMBERS OR "INVENT PLAUSIBLE"] - Period the CAC was earned in: [E.G. LAST QUARTER] - Company: [NAME] </inputs> <task> Build the dashboard with: a KPI row (blended payback months, channels inside target, channels over target, worst channel); a bar of payback months versus the target line; a table (CAC, monthly margin, payback months, months over target); a simple cumulative-margin sketch for the selected channel (month 1..N until CAC is recovered); and channel chips that switch the sketch. Payback months = CAC / monthly contribution margin. Show the formula. If margin is zero, mark [VERIFY]. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Payback is computed from CAC and margin, not hardcoded. - Over-target bars flagged. Accessible contrast. - Label this as contribution-margin payback, not cash-in-bank. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then write the payback formula and which constants to replace with a finance extract. </format>

You are a revenue-operations analyst who splits blended CAC from paid-only CAC so organic logos cannot hide paid cost. <context> I need a blended versus paid CAC dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample acquisition rows so both CAC views render when I open it as a working screen in the chat. </context> <inputs> - Company: [COMPANY] - Period: [E.G. LAST QUARTER] - Paid spend: [AMOUNT OR "INVENT"] - New customers split: [PAID VERSUS ORGANIC COUNTS] - Organic definition: [E.G. NO PAID TOUCH IN 30 DAYS] </inputs> <task> Build the dashboard with: a KPI row (paid spend, paid new customers, organic new customers, blended CAC, paid CAC); a grouped bar of blended versus paid CAC over the last 6 sample months; a donut of new customers by paid versus organic; a table (month, spend, paid logos, organic logos, blended CAC, paid CAC); and a note that states both formulas. Blended CAC = spend / all new customers. Paid CAC = spend / paid new customers. Organic spend stays zero unless I add it. Compute both from labeled JS constants. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Both CAC numbers are computed, not hardcoded. - Show the organic definition on the page. - Do not invent a multi-touch model. Two denominators only. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then write both CAC formulas and which arrays to replace with an acquisition export. </format>

You are a revenue-operations analyst who builds hierarchical quota rollups, not a rep attainment race. <context> I need an org quota rollup dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with a realistic company-region-team tree so bookings versus quota render when I open it as a working screen in the chat. </context> <inputs> - Company: [COMPANY] - Regions and teams: [E.G. AMER / EMEA, 2 TEAMS EACH] - Period: [E.G. THIS QUARTER] - Bookings field: [E.G. CLOSED WON ARR] - Currency: [E.G. USD] </inputs> <task> Build the dashboard with: a KPI row (company quota, bookings, percent to quota, gap); a stacked bar of bookings versus remaining quota by region; an expandable table (company, region, team) with quota, bookings, percent, gap; a click on a region that expands its teams; and a callout of the weakest region. Generate the tree in a labeled JS structure. Team bookings sum to region, regions sum to company. Percent and gap are computed. This is an ops rollup, not a named-rep leaderboard. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Totals roll up in JS, not hardcoded at parent rows. - Behind-pace rows flagged with a text label. Currency consistent. - Do not list individual reps as the primary view. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain the rollup math and which structure to replace with a quota-tree export. </format>

You are a revenue-operations planner who checks whether assigned quota fits the ramped seats you actually have. <context> I need a quota-versus-seat-capacity dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic team headcount so over-assigned quota renders when I open it as a working screen in the chat. </context> <inputs> - Team or org slice: [TEAM] - Teams to compare: [E.G. 4 TEAMS] - Full quota per ramped seat: [AMOUNT] - Ramp plan: [E.G. MONTH 1 25%, MONTH 2 50%, MONTH 3 75%, MONTH 4 100%] - Period: [E.G. THIS QUARTER] </inputs> <task> Build the dashboard with: a KPI row (assigned quota, ramped capacity, over-assigned amount, teams over 100% of capacity); a grouped bar of assigned quota versus ramped capacity by team; a table (seats, ramped seats, capacity dollars, assigned quota, assigned / capacity); and a watchlist of teams whose assigned quota exceeds capacity. Generate people with start dates and team quotas in labeled JS arrays. Ramped capacity = sum of each seat's ramp percent times full quota. Show the formula. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Capacity is computed from start dates and the ramp plan, not hardcoded. - Over-assigned teams flagged. Currency consistent. - Do not build a per-rep percent-to-quota race. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then write the capacity formula and which arrays to replace with a roster and quota export. </format>

You are a revenue-operations planner who shows how much company quota sits on seats that are still ramping. <context> I need a ramped versus unramped quota-mix dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic hires so the mix and expected attainment render when I open it as a working screen in the chat. </context> <inputs> - Team: [TEAM] - Ramp plan: [E.G. M1 25, M2 50, M3 75, M4 100] - Full quota at 100%: [AMOUNT] - Hires and start dates: [OR "INVENT 8 PEOPLE, 3 RAMPING"] - Period: [E.G. THIS QUARTER] </inputs> <task> Build the dashboard with: a KPI row (quota on fully ramped seats, quota on ramping seats, mix %, expected bookings if everyone hits ramp plan); a stacked bar of ramped versus unramped quota; a histogram of seats by ramp month; a table (name, start date, ramp month, expected %, assigned quota, expected dollars); and a callout of how much of the company number depends on unfinished ramp. Generate people in a labeled JS array. Compute ramp month from start date and a period-start constant. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Mix percents and expected dollars are computed from start dates. - This is a quota-mix board, not a new-hire coaching scorecard. - Currency consistent; accessible contrast; data at the top. </constraints> <format> Return the full HTML file, then explain how ramp month is derived and how to add a new hire to the array. </format>

You are a revenue-operations analyst who audits quota versions so mid-year edits cannot hide the original number. <context> I need a quota change-log dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic quota versions so original versus current versus bookings render when I open it as a working screen in the chat. </context> <inputs> - Period: [PERIOD] - Teams: [E.G. 5 TEAMS] - Original quotas and current quotas: [OR "INVENT A FEW CUTS AND RAISES"] - Bookings to date: [AMOUNTS OR "INVENT"] - Company: [NAME] </inputs> <task> Build the dashboard with: a KPI row (original company quota, current company quota, net change, bookings versus original, bookings versus current); a grouped bar of original versus current by team; a change table (team, original, current, delta, reason field, bookings, % vs original, % vs current); a log of sample edits (date, team, old, new, reason); and a flag on any team whose % versus original and % versus current tell a different story. Generate versions and bookings in labeled JS arrays. Compute every percent from those constants. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Percents versus both quotas are computed, not hardcoded. - Show both denominators. Do not drop the original. - Currency consistent; accessible contrast; data at the top. </constraints> <format> Return the full HTML file, then explain both attainment views and which arrays to replace with a quota-history export. </format>

You are a revenue-operations analyst who allocates quota by product and segment, then measures attainment on those slices. <context> I need a product and segment quota dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic split quotas and bookings so the slice view renders when I open it as a working screen in the chat. </context> <inputs> - Products or lines: [PRODUCTS] - Segments: [E.G. ENTERPRISE, MID-MARKET, SMB] - Period: [E.G. THIS QUARTER] - Quota per product-segment cell: [OR "INVENT A GRID"] - Bookings per cell: [OR "INVENT"] </inputs> <task> Build the dashboard with: a KPI row (total quota, bookings, percent, farthest-behind slice); a product-by-segment heatmap of percent to quota; a toggle that switches cells to dollars booked or dollars remaining; a table of each slice (quota, bookings, percent, gap); and a click on a cell that lists sample booking rows in that slice. Generate a quota grid and booking rows in labeled JS structures. Compute cell percents from quota and bookings. Empty quota cells stay visible as unassigned. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Heatmap numbers are computed, not hardcoded. Show the number, not color alone. - This is allocation and attainment by slice, not a win-rate-by-segment sales board. - Currency consistent; responsive (grid can scroll); data at the top. </constraints> <format> Return the full HTML file, then explain the slice math and which structures to replace with a split-quota export. </format>

You are a revenue-operations analyst who scores forecast snapshots against the close, not a live commit stack. <context> I need a snapshot-versus-close accuracy dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic weekly locked calls and a final actual so week-N accuracy renders when I open it as a working screen in the chat. </context> <inputs> - Period: [PERIOD] - Snapshot weeks to keep: [E.G. W1, W4, W8, W12] - What was locked each snapshot: [COMMIT DOLLARS OR "INVENT A PATH"] - Final actual closed: [AMOUNT] - Team: [NAME] </inputs> <task> Build the dashboard with: a KPI row (final actual, best snapshot by absolute miss %, worst snapshot, average absolute miss); a grouped bar of each snapshot versus the final actual; a line of miss % by snapshot week; a table (snapshot, locked call, actual, miss $, miss %, over or under); and a callout of the first week the call was inside an editable tolerance. Generate snapshot pairs in labeled JS arrays. Miss and absolute miss are computed from locked versus actual. This is an archive board, not a what-if deal mover. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Miss and bias are computed from the snapshot constants, not hardcoded. - Over-forecast and under-forecast colored differently with a text label. - Currency consistent; accessible contrast; data at the top. </constraints> <format> Return the full HTML file, then explain the miss formula and how to paste a locked-forecast archive. </format>

You are a revenue-operations analyst who scores each manager's commit call against what that team actually closed. <context> I need a commit-accuracy-by-manager dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic weekly manager calls so hit rate, miss, and bias render when I open it as a working screen in the chat. </context> <inputs> - Managers: [MANAGERS] - Period: [E.G. LAST QUARTER BY WEEK] - Hit rule: [E.G. ABSOLUTE MISS UNDER 10%] - Sample weeks: [E.G. 13] - Team: [NAME] </inputs> <task> Build the dashboard with: a KPI row (managers, weeks scored, company hit rate, company bias over or under); a grouped bar of forecast versus actual by manager for the selected week; a table (manager, weeks hit, hit rate, average miss %, bias, miss dollars); a week slider or chips; and a click on a manager that draws that manager's miss % line. Generate weekly forecast and actual pairs per manager in labeled JS arrays. Hit = absolute miss under the rule. Bias = average (forecast minus actual) / actual. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Hit rate and bias are computed from the pairs, not hardcoded. - Show the hit rule on the page. Guard divide-by-zero on zero actual. - This is process accuracy, not a rep coaching flag board. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then write the hit and bias formulas and which arrays to replace with a manager-call log. </format>

You are a revenue-operations analyst who charts forecast bias across quarters so a systematic over-call is visible. <context> I need a forecast-bias trend dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic quarterly and weekly errors so over-call versus under-call renders when I open it as a working screen in the chat. </context> <inputs> - Team: [TEAM] - Quarters to show: [E.G. LAST 4] - Weekly signed error inside each quarter: [OR "INVENT A SLIGHT OVER-FORECAST"] - Bias formula: [E.G. AVERAGE OF (FORECAST MINUS ACTUAL) / ACTUAL] - Tolerance band: [E.G. PLUS OR MINUS 5%] </inputs> <task> Build the dashboard with: a KPI row (latest-quarter bias, streak of over or under quarters, weeks inside the band, weeks outside); a bar of bias by quarter; a line of weekly signed error with the band drawn; a table (quarter, weeks, bias, absolute miss, over-weeks, under-weeks); and a callout that names whether the team systematically over or under calls. Generate weekly pairs in labeled JS arrays and compute bias from the formula I gave. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Bias and streak are computed from the weekly pairs. - Over and under use different colors plus a text label. - Do not rebuild a live commit-versus-quota stack. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then write the bias formula and how to paste a weekly forecast log. </format>

You are a revenue-operations analyst who autopsies deals that exited commit between a locked snapshot and the close. <context> I need a commit-slippage autopsy as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic snapshot-versus-outcome rows so slipped commit dollars render when I open it as a working screen in the chat. </context> <inputs> - Team: [TEAM] - Snapshot to judge: [E.G. WEEK 8 LOCK] - Outcomes that count as slip: [E.G. CLOSED LOST, PUSHED NEXT PERIOD, DEMOTED FROM COMMIT] - Reason codes: [E.G. CHAMPION LEFT, PRICE, NO DECISION, TIMING] - Period: [E.G. LAST QUARTER] </inputs> <task> Build the dashboard with: a KPI row (commit dollars at snapshot, dollars that held through close, slipped dollars, slip rate); a bar of slipped dollars by outcome; a reason mix for the slipped subset; a sortable autopsy table (deal, snapshot amount, snapshot category, final outcome, reason, owner, days from snapshot to change); and a held list for contrast. Generate snapshot rows with a later outcome in a labeled JS array. Slip flags are computed from snapshot category versus final outcome. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Slip flags and dollars are computed, not hardcoded. - Table is the main object; charts support it. - This is forecast-process quality, not a late-stage sales risk haircut. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain the slip rule and which array to replace with a category-history export. </format>

You are a revenue-operations analyst who audits whether the forecast process was completed, not whether the call was right. <context> I need a forecast-submission completeness dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic submission rows so late calls and missing categories render when I open it as a working screen in the chat. </context> <inputs> - Team: [TEAM] - Submit deadline: [E.G. TUESDAY 14:00 LOCAL] - Owners who must submit: [NAMES] - Late-stage deals that must have a category: [COUNT OR "INVENT 40"] - Period: [E.G. THIS QUARTER, WEEKLY] </inputs> <task> Build the dashboard with: a KPI row (expected submitters, on-time %, late count, late-stage dollars missing a category); a bar of on-time versus late by week; a table of owners (last submitted at, on-time flag, deals missing category, missing dollars); a watchlist of this week's late or incomplete owners; and chips for late / missing category. Generate submissions and deal-category rows in labeled JS arrays. Late = submitted-at after the deadline. Missing = late-stage deal with a blank category. Include a now and timezone constant. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Late and missing flags are computed from timestamps and category fields. - Do not score whether commit was correct. Completeness only. - Show the deadline on the page. Accessible contrast. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain the late and missing rules and which arrays to replace with a submission log. </format>

You are a revenue-operations analyst who measures whether SDRs accept marketing-qualified leads on time. <context> I need an MQL-accept dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample MQLs so accept rate, reject reasons, and SLA render when I open it as a working screen in the chat. </context> <inputs> - SDR team: [SDR TEAM] - Accept SLA: [E.G. 24 BUSINESS HOURS] - Reject reasons: [E.G. BAD FIT, DUPLICATE, NOT READY, CANNOT REACH] - Period: [E.G. LAST 30 DAYS] - MQL count: [E.G. 80] </inputs> <task> Build the dashboard with: a KPI row (MQLs, accept rate, reject rate, percent inside SLA, median hours to first disposition); a funnel of MQL to accepted to SQL; a bar of reject reasons; a line of daily accept rate; a watchlist of open MQLs past SLA; and chips for accepted / rejected / waiting. Generate MQL rows with created-at and disposition-at in a labeled JS array. Hours to disposition and SLA flags are computed from those timestamps and a now constant. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Rates and SLA flags are computed from the MQL array, not hardcoded. - Past-SLA rows flagged with a text label. - Do not build an outbound activity scoreboard. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain the SLA clock and which array to replace with an MQL export. </format>

You are a revenue-operations analyst who measures the SDR-to-AE handoff clock and bounce-backs. <context> I need an SDR-to-AE handoff SLA dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic SQL handoff rows so wait time, accept lag, and bounces render when I open it as a working screen in the chat. </context> <inputs> - Teams: [TEAMS] - Handoff SLA: [E.G. AE ACCEPTS WITHIN 8 BUSINESS HOURS] - Bounce rule: [E.G. RETURNED TO SDR WITHIN 7 DAYS] - Period: [E.G. LAST 30 DAYS] - SQL count: [E.G. 40] </inputs> <task> Build the dashboard with: a KPI row (SQLs handed, accepted inside SLA, median hours to AE accept, bounce rate); a bar of accept lag by AE; a funnel of SQL to accepted to first meeting set; a bounce table (SQL, SDR, AE, hours to accept, bounced, bounce reason); and chips for on-time / late / bounced. Generate handoff rows with SQL-at, accepted-at, and bounce flags in a labeled JS array. Compute lag and SLA from those timestamps. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Lag, SLA, and bounce rate are computed, not hardcoded. - Show the SLA and bounce rules on the page. - This is a handoff clock, not a meeting-funnel sales board. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain the clock and which array to replace with a SQL handoff export. </format>

You are a revenue-operations analyst who checks whether a closed-won deal arrived to CS with the fields a kickoff needs. <context> I need an AE-to-CS handoff completeness dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic won deals so missing kickoff fields and delayed starts render when I open it as a working screen in the chat. </context> <inputs> - Required handoff fields: [FIELDS] - Example if needed: [USE CASE, CHAMPION, GO-LIVE DATE, SUCCESS METRIC, SEATS] - Kickoff SLA days after close: [E.G. 10] - Won deal count: [E.G. 18] - Team: [NAME] </inputs> <task> Build the dashboard with: a KPI row (won deals, complete handoffs, missing-field count, kickoffs past SLA); a bar of blank rate by required field; a table of deals with a pass/fail chip per field, close date, kickoff date, days to kickoff; a watchlist of thin or late handoffs; and chips for missing field / late kickoff. Generate won deals with field flags and dates in a labeled JS array. Complete = every required field filled. Late = kickoff minus close greater than the SLA, or kickoff blank and days since close over the SLA. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Completeness and late flags are computed from the field map and dates. - Show the required-field list on the page so I can edit it. - Do not build a CS account-health score. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then list each required field in plain English and which array to replace with a won-deal export. </format>

You are a revenue-operations analyst who measures recycle and reject loops so the same lead is not quietly re-entering. <context> I need a recycle and reject mix dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic reject and recycle events so volume, re-entry, and time-to-recycle render when I open it as a working screen in the chat. </context> <inputs> - Reason codes: [REASONS] - Recycle window that counts as re-entry: [E.G. 45 DAYS] - Period: [E.G. LAST 90 DAYS] - Event count: [E.G. 60] - Team: [NAME] </inputs> <task> Build the dashboard with: a KPI row (rejects, recycles, re-entry rate inside the window, median days to recycle); a bar of volume by reason; a stacked bar of first-time versus re-entry; a table (reason, count, re-entries, re-entry %, median days); and a list of sample leads that re-entered with both event dates. Generate events with lead id, reason, and timestamp in a labeled JS array. Re-entry = same lead id gets a new MQL or recycle inside the window after a reject. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Re-entry flags and rates are computed from lead ids and dates. - Show the re-entry window on the page. - Do not invent a nurture sequence. Counts and dates only. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain the re-entry rule and which array to replace with a recycle-code export. </format>

You are a revenue-operations analyst who builds open-handoff aging boards a Monday standup can chase. <context> I need a handoff aging watchlist as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic open handoffs so stuck MQLs and SQLs render when I open it as a working screen in the chat. </context> <inputs> - SLA hours by handoff type: [SLA HOURS] - Handoff types: [E.G. MQL TO SDR, SQL TO AE, WON TO CS] - Age buckets: [E.G. 0-8H, 8-24H, 24-72H, 72H+] - Owners: [NAMES OR ROLES] - Open handoff count: [E.G. 28] </inputs> <task> Build the dashboard with: a KPI row (open handoffs, past SLA, oldest hours waiting, dollars on stuck SQLs); a stacked bar of count by age bucket and type; a type-by-bucket table; a chase list sorted oldest first (record, type, from owner, to owner, hours waiting, SLA, past-SLA flag); and chips for type and past-SLA only. Generate open handoffs with a handed-at timestamp in a labeled JS array. Hours waiting and bucket assignment are computed from handed-at versus a now constant. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Age and SLA flags are computed from timestamps, not hardcoded. - Past-SLA rows flagged with a text label. Filters must hide rows. - This is open work waiting on a handoff, not a stale-deal sales aging board. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain the age formula and which array to replace with an open-handoff export. </format>

You are a revenue-operations planner who matches inbound volume to the SDR seats that can actually work it. <context> I need an inbound-versus-SDR capacity dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic weekly leads and roster rows so overflow weeks render when I open it as a working screen in the chat. </context> <inputs> - SDR team: [SDR TEAM] - Horizon: [E.G. LAST 8 WEEKS PLUS NEXT 4] - Leads one productive SDR can work per week: [E.G. 40] - Seats by week with PTO: [OR "INVENT 6 SDRS"] - Inbound volume by week: [OR "INVENT A SPIKE"] </inputs> <task> Build the dashboard with: a KPI row (this-week inbound, productive seats, capacity leads, overflow or slack); a grouped bar of inbound versus capacity by week; a table (week, inbound, seats, capacity, utilization, overflow); a callout of the first week over 100%; and a people strip that shows who is out. Capacity = productive seats times leads-per-seat. Utilization = inbound / capacity. Generate weekly volume and roster in labeled JS constants. Week chips filter the people strip. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Capacity and overflow are computed, not hardcoded. - Over 100% red, 80-100% amber, with a text label. - This is RevOps seat math, not a warehouse shift board. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then write the capacity formula and which constants to replace with a lead and roster export. </format>

You are a revenue-operations planner who measures open pipeline per ramped AE seat, not per name on the org chart. <context> I need a pipeline-per-ramped-seat dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic AE roster and open deals so dollars per productive seat render when I open it as a working screen in the chat. </context> <inputs> - Team: [TEAM] - Full quota per ramped AE: [AMOUNT] - Coverage target: [E.G. 3X QUOTA] - Ramp rule for who counts as productive: [E.G. MONTH 3+] - Open pipeline deals: [OR "INVENT 30"] </inputs> <task> Build the dashboard with: a KPI row (open pipeline, ramped seats, dollars per ramped seat, coverage versus target); a bar of pipeline per seat by team or region; a table (team, ramped seats, open dollars, dollars per seat, quota, coverage multiple); a watchlist of teams below the coverage target; and a note that unramped seats are excluded from the denominator. Generate people with start dates and open deals in labeled JS arrays. Ramped = ramp month at or above the rule. Coverage = open dollars / (ramped seats times quota). </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Dollars per seat and coverage are computed from roster and deals. - Below-target teams flagged. Currency consistent. - Do not build a pipeline-coverage-versus-quota sales board of named deals as the primary view. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then write the ramped-seat and coverage formulas and which arrays to replace. </format>

You are a revenue-operations planner who shows the week assigned quota outruns ramped seats so a founder can hire or cut the number. <context> I need a hire-trigger dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with a realistic hiring plan and quota path so the trigger week renders when I open it as a working screen in the chat. </context> <inputs> - Horizon: [HORIZON] - Current ramped seats and full quota per seat: [NUMBERS] - Planned start dates: [OR "INVENT 3 HIRES"] - Assigned quota by week or month: [OR "FLAT THEN A STEP UP"] - Trigger rule: [E.G. 3 WEEKS OVER 100% OF RAMPED CAPACITY] </inputs> <task> Build the dashboard with: KPI cards (ramped capacity now, assigned quota now, first week over 100%, weeks that meet the trigger); a line of capacity versus assigned quota across [HORIZON]; a table by week (seats, ramp-adjusted capacity, assigned quota, utilization, hire-or-hold); a hire strip of planned starts; and a marked trigger week. Compute capacity from current seats plus planned starts using the same ramp plan. Label this as a simple seat projection, not a statistical model. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Trigger week is computed from the rule, not hardcoded. - Show the trigger rule and ramp plan on the page. - Do not invent salary cost or finance advice. Seat math only. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then write the projection and trigger rules and which constants to replace with a hiring-plan export. </format>

You are a revenue-operations planner who balances territory load so one seat is not carrying two territories of work. <context> I need a territory load-balance dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic territories so accounts, pipeline, and quota per seat render when I open it as a working screen in the chat. </context> <inputs> - Territories: [TERRITORIES] - Load weights: [E.G. ACCOUNTS 30, OPEN PIPELINE 40, QUOTA 30] - Target load band: [E.G. 80-120 INDEX] - Seats per territory: [USUALLY 1] - Account and pipeline sample: [OR "INVENT"] </inputs> <task> Build the dashboard with: a KPI row (territories, seats, territories over the band, territories under the band); a bar of load index by territory; a table (territory, seats, accounts, open pipeline, quota, load index, versus band); a scatter of pipeline versus quota; and a click on a territory that lists its sample accounts. Generate territories, seats, and accounts in labeled JS structures. Load index = weighted mix of the three inputs, normalized so the median territory is 100. Show the weights. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Load index is computed from the weights, not hardcoded. - Over and under band flagged with a text label. - This is seat load, not a CRM territory-coverage hygiene grid. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then write the load-index formula and which arrays to replace with an assignment export. </format>

You are a revenue-operations planner who measures SE and CSM overlay load against a cap, not against a feeling. <context> I need an overlay capacity dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic SE deals and CSM books so load versus cap renders when I open it as a working screen in the chat. </context> <inputs> - Overlay roles: [SE AND CSM] - SE cap: [E.G. 8 ACTIVE LATE-STAGE DEALS] - CSM cap: [E.G. 25 CUSTOMERS OR 6 QBRS PER MONTH] - People: [NAMES OR "INVENT 4 SE AND 4 CSM"] - Horizon: [E.G. THIS MONTH] </inputs> <task> Build the dashboard with: role tabs for SE and CSM; KPI cards (people, over cap, median load, first week a role is over); a bar of load versus cap by person; a table (person, role, load, cap, utilization, next-30-day incoming); a gap-week callout; and a click on a person that lists the deals or customers in their load. Generate people, deals, customers, and QBR dates in labeled JS arrays. SE load = count of late-stage deals assigned. CSM load = customers and QBRs in the month. Utilization = load / cap. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Load and utilization are computed from the assignments, not hardcoded. - Over-cap people flagged with a text label. - Do not invent hiring cost. Show the gap and the week it hits. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then write each load formula and which arrays to replace with an overlay roster export. </format>