30 Claude Prompts That Build Fundraising Dashboards

You are a founder who tracks the investor funnel as pipeline of capital, not a sales RevOps funnel and not a pitch rehearsal. <context> I need an intro-to-term-sheet funnel as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample investor rows so it opens as a working screen I can click in the chat. Capital pipeline only. Do not build a sales MQL funnel. Do not build deck slides. </context> <inputs> - Stages in order: [FUNNEL STAGES] - Company name: [COMPANY NAME] - Period of intros: [E.G. LAST 60 DAYS] - Sample investors with current stage and dollars if known: [OR INVENT] - Target conversion at the weakest step you care about: [E.G. 25% FIRST CALL TO PARTNER] </inputs> <task> Build the dashboard with: a header for [COMPANY NAME]; a KPI row (intros, in diligence, term sheets, overall intro-to-term-sheet %, leak stage); a horizontal funnel of count and conversion at each item in [FUNNEL STAGES]; a conversion table (in-count, out-count, rate, versus target if given); and a leak callout. Compute each rate as next-stage count / this-stage count. Clicking a stage filters the investor list. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Investor rows and stage order in labeled JS constants at the top. - Leak is the lowest conversion step, computed. Guard a zero in-count. - Do not invent win rates on product sales. - Accessible contrast; responsive layout. </constraints> <format> Return the full HTML as an artifact, then write the conversion math and which investor array to replace. </format>

You are a founder who splits warm intros from cold outreach on the raise, not a marketer building a lead-source dashboard. <context> I need a warm-intro versus cold dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample outreach rows so it opens as a working screen I can click in the chat. Investor sourcing. Not ads. Not a pitch-deck page. </context> <inputs> - Intro sources to track: [INTRO SOURCES] - Company name: [COMPANY NAME] - Period: [E.G. THIS RAISE] - Sample rows (name, source, warm or cold, reached first meeting yes/no, reached term sheet yes/no): [OR INVENT] </inputs> <task> Build the dashboard with: a header for [COMPANY NAME]; a KPI pair (meeting rate, term-sheet rate) for warm versus cold; a bar of meeting rate by each item in [INTRO SOURCES]; a table (source, sent or intros, meetings, term sheets, both rates); source chips; and a callout of the source that wins on meetings but loses on term sheets, or the reverse. Compute rates from the rows. Clicking a source filters the list. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Outreach rows in labeled JS constants at the top. - Rates computed, never hardcoded. Small-n sources flagged under an editable threshold. - Do not invent email copy or slide outlines. - Accessible contrast; both motions labeled in text. </constraints> <format> Return the full HTML as an artifact, then explain the warm/cold rule and which outreach array to replace. </format>

You are a founder who scores funds against a written thesis filter before another partner meeting, not a deck writer. <context> I need a thesis-fit scorecard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample funds so it opens as a working screen I can click in the chat. Prioritization of capital sources. No slides. No finance statements. </context> <inputs> - Filters to score: [THESIS FILTERS] - Company stage, sector, and check size you want: [YOUR FIT] - Fund rows with stage, sector, typical check, geography: [OR INVENT] - Pass / stretch / miss rule: [E.G. PASS IF 3 OF 4 FILTERS MATCH] </inputs> <task> Build the dashboard with: a header for the raise; a KPI row (pass, stretch, miss, next meeting that is a pass); a table of funds with a fit score from [THESIS FILTERS]; chips for pass / stretch / miss; a bar of miss reasons; and a click that opens which filters matched. Compute the score from the rule constants. Do not invent a fund I did not seed. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Fund rows and the rule in labeled JS constants at the top. - Status uses color plus the word pass, stretch, or miss. - Do not write outreach copy or a pitch narrative. - Accessible contrast; responsive layout. </constraints> <format> Return the full HTML as an artifact, then restate the scoring rule and which fund array to replace. </format>

You are a founder who runs a diligence request board so the data room does not stall the close, not a lawyer and not a pitch-deck owner. <context> I need a diligence-request dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample requests so it opens as a working screen I can click in the chat. Raise ops. Do not draft the answers. Do not design slides. </context> <inputs> - Request list: [DILIGENCE LIST] - Company name: [COMPANY NAME] - Asking firm: [FIRM] or several firms - Status values: [E.G. OPEN, DRAFTING, SENT, WAIVED] - Asked-on dates: [OR INVENT] </inputs> <task> Build the dashboard with: a header for [COMPANY NAME]; a KPI row (open, sent, waived, oldest open age in days); a bar of requests by status; a sortable table from [DILIGENCE LIST] (item, firm, asked on, status, owner, age); chips that filter by firm or status; and an oldest-open callout. Compute age from asked-on versus a today constant. Clicking a row opens a one-line next step labeled as a sample, not legal advice. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Request rows in labeled JS constants at the top. - Age and oldest-open are computed. Do not invent legal conclusions. - Accessible contrast; keyboard-usable filters. - No P and L widgets and no slide outline. </constraints> <format> Return the full HTML as an artifact, then say which request array to replace with the live data-room log. </format>

You are a founder who logs pass, hold, and advance outcomes so the next intro list gets smarter, not a salesperson logging closed-lost. <context> I need a pass / hold / advance log as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample outcomes so it opens as a working screen I can click in the chat. Investor outcomes. Not a sales loss reason dashboard. Not a pitch rewrite. </context> <inputs> - Outcome reasons: [OUTCOME REASONS] - Company name: [COMPANY NAME] - Sample rows (firm, outcome, reason, stage they left, date): [OR INVENT] - Period: [E.G. THIS RAISE] </inputs> <task> Build the dashboard with: a header for [COMPANY NAME]; a KPI row (advanced, hold, pass, top pass reason); a bar of pass reasons from [OUTCOME REASONS]; a stacked bar of outcomes over weeks if you seed dates; a table (firm, outcome, reason, stage left); and a top-reason callout. Compute ranks from the rows. Clicking a reason filters the table. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Outcome rows in labeled JS constants at the top. - Do not invent a reason I did not list. Put leftovers in Other only if I said so. - Do not generate a new pitch story from the reasons. - Accessible contrast; not color-only ranks. </constraints> <format> Return the full HTML as an artifact, then say which outcome array to replace with your notes. </format>

You are a founder who puts remaining cash on the same clock as the raise close, not a controller building an operating cash forecast. <context> I need a runway versus close date dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample cash so it opens as a working screen I can click in the chat. The question is will cash last until [CLOSE DATE]. Do not build a 13-week treasury. Do not build a pitch slide. </context> <inputs> - Target close date: [CLOSE DATE] - Company name: [COMPANY NAME] - Current cash: [AMOUNT] - Monthly net burn: [AMOUNT] - Currency: [E.G. USD] - Today: [DATE I CAN EDIT] </inputs> <task> Build the dashboard with: a header showing [CLOSE DATE]; a KPI row (cash, net burn, runway months, months until close, gap in months); a dual line of ending cash and a marker on the close date; a table of month-end cash until cash-out or close plus two buffer months; and a gap callout (runway months minus months until close). Compute runway as cash / net burn when burn is positive, and say not burning when it is not. Months until close from today to [CLOSE DATE]. Clicking the close marker shows ending cash that month. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Cash, burn, dates in labeled JS constants at the top. - Gap and cash-out month are computed. Guard zero or negative burn. - Do not add hiring toggles or department opex. Close clock only. - Currency consistent; accessible contrast. </constraints> <format> Return the full HTML as an artifact, then write the gap formula and which constants to replace. </format>

You are a founder who tests what a late close does to cash, not an FP and A partner building budget versus actual. <context> I need a close-slip cash scenario dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample cash so it opens as a working screen I can click in the chat. Scenario on the close date only. Not a department budget. Not a deck. </context> <inputs> - Slip options in weeks: [SLIP WEEKS] - Company name: [COMPANY NAME] - Base close date, cash, monthly net burn: [OR INVENT] - Currency: [E.G. USD] - Minimum cash you refuse to cross before a wire: [AMOUNT] </inputs> <task> Build the dashboard with: a header for [COMPANY NAME]; slip chips from [SLIP WEEKS] including a 0-week base; a KPI row (close date under that slip, ending cash on that date, weeks under the minimum if any); a line of ending cash with a moving close marker; a table of each slip (close date, cash at close, status versus minimum); and a callout of the first slip that crosses the minimum. Clicking a chip rebuilds the marker and cards from the same burn constant. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Slip list, cash, burn, and minimum in labeled JS constants at the top. - Ending cash at close is computed as cash minus burn times months (or weeks/4.345) to that date. Show the rule on the page. - Do not invent a new raise. Accessible contrast. </constraints> <format> Return the full HTML as an artifact, then explain the slip math and which constants to replace. </format>

You are a founder who clocks cash until the first wire of this raise hits the bank, not a collections analyst and not a pitch writer. <context> I need a cash until first wire dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample wires so it opens as a working screen I can click in the chat. Raise timing. No AR aging. No slides. </context> <inputs> - Monthly net burn: [MONTHLY BURN] - Company name: [COMPANY NAME] - Current cash: [AMOUNT] - Expected first-wire date and amount: [OR INVENT] - Later wires if useful: [OR INVENT] - Currency: [E.G. USD] </inputs> <task> Build the dashboard with: a header for [COMPANY NAME]; a KPI row (cash, weekly burn from [MONTHLY BURN] / 4.345, weeks until first wire, cash on the morning of that wire); a week bar of ending cash with the first-wire week marked; a wire table; and a callout if cash on that morning is below an editable floor. Compute weekly burn and the morning-of-wire cash. Clicking the first-wire week opens amount and source. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Burn, cash, and wire dates in labeled JS constants at the top. - Show the weekly-burn rule on the page. Do not hardcode the morning-of cash. - Do not add customer invoices. Investor wires only. - Currency consistent; accessible contrast. </constraints> <format> Return the full HTML as an artifact, then explain weekly burn and which wire array to replace. </format>

You are a founder who compares cash after a minimum close versus a full close, not a board pack author. <context> I need a minimum versus full close cash dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample raise sizes so it opens as a working screen I can click in the chat. Two close sizes, two runways. Not a use-of-cash-after-the-raise spend tracker. Not a slide. </context> <inputs> - Minimum raise: [MINIMUM RAISE] - Full target raise: [AMOUNT] - Company name: [COMPANY NAME] - Cash today and monthly net burn: [AMOUNTS] - Fees or holdback to subtract if you have them: [E.G. 0 OR 6%] - Currency: [E.G. USD] </inputs> <task> Build the dashboard with: a header for [COMPANY NAME]; a toggle (minimum versus full); a KPI row (net proceeds after the fee rule, cash after close, runway months after close); a grouped bar of runway under both sizes; a small table (size, fees, net, cash after, runway); and a callout of how many months the full close buys over the minimum. Compute net proceeds as size times (1 minus fee). Cash after close is cash today plus net proceeds. Runway is that cash / burn when burn is positive. Toggling restates the cards. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Sizes, fee, cash, burn in labeled JS constants at the top. - Do not invent post-close opex buckets. Runway math only. - Label the fee rule as a sample haircut, not legal or tax advice. - Accessible contrast; currency consistent. </constraints> <format> Return the full HTML as an artifact, then write the net-proceeds rule and which constants to replace. </format>

You are a founder who computes the bridge dollars a slipped close would force, not a strategist writing a new pitch. <context> I need a bridge-need-if-slip dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample cash so it opens as a working screen I can click in the chat. This is the hole between cash-out and a late close. Not a product roadmap. Not a deck. </context> <inputs> - Stated bridge need if you already have one: [BRIDGE NEED] - Company name: [COMPANY NAME] - Cash, monthly net burn, base close date: [OR INVENT] - Slip weeks to test: [E.G. 4, 8, 12] - Currency: [E.G. USD] </inputs> <task> Build the dashboard with: a header for [COMPANY NAME]; a KPI row (cash-out month at current burn, base close, computed hole at each slip, versus [BRIDGE NEED] if given); a bar of hole dollars by slip week; a table (slip weeks, close date, cash at that date, hole as max(0, -cash at close), versus stated need); and a callout of the first slip where a hole appears. Hole is computed, not hardcoded. Clicking a slip restates the cards. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Cash, burn, dates, stated need in labeled JS constants at the top. - If I gave [BRIDGE NEED], show the gap between computed hole and that number. - Do not invent terms or a valuation for the bridge. - Accessible contrast; currency consistent. </constraints> <format> Return the full HTML as an artifact, then write the hole formula and which constants to replace. </format>

You are a founder who shows how this raise will be allocated before it closes, not a CFO tracking spend after a close. <context> I need a use-of-proceeds mix dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample buckets so it opens as a working screen I can click in the chat. Planned allocation of the raise. Do not build a spent-to-date post-close tracker (that lives on finance dashboards). Do not build slides. </context> <inputs> - Planned buckets and percents or dollars: [PROCEEDS BUCKETS] - Company name: [COMPANY NAME] - Raise size this mix applies to: [AMOUNT] - Currency: [E.G. USD] - Months the plan covers: [E.G. 18] </inputs> <task> Build the dashboard with: a header for [COMPANY NAME]; a KPI row (raise size, allocated, unallocated, month span); a donut or bar of [PROCEEDS BUCKETS]; a table (bucket, percent, dollars, months of that spend if you seed it); and a callout if percents do not add to 100 or dollars do not add to the raise. Clicking a bucket highlights the slice and shows dollars. Compute dollars from percent times raise when I gave percents, or percents from dollars when I gave dollars. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Buckets and raise size in labeled JS constants at the top. - Flag a break if allocation does not reconcile. Do not invent spent-to-date. - Accessible contrast; currency consistent. - No pitch narrative paragraphs. </constraints> <format> Return the full HTML as an artifact, then explain percent-versus-dollar math and which bucket array to replace. </format>

You are a founder who builds a simple post-round ownership screen for the raise, not legal advice and not a pitch-deck cap-table slide. <context> I need a post-round cap table dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample holders so it opens as a working screen I can click in the chat. Ownership math for allocation. Label it a sample model, not counsel. No slide layout. </context> <inputs> - Current holders and shares: [CAP TABLE] - Company name: [COMPANY NAME] - New money shares or ownership percent for the round: [OR INVENT] - Option pool before and after if you have it: [OR INVENT] </inputs> <task> Build the dashboard with: a header for [COMPANY NAME]; a KPI row (pre fully diluted, new shares, post fully diluted, new-money percent); a pre versus post ownership bar by holder group (founders, employees, existing investors, new money, pool); a sortable holder table from [CAP TABLE] plus the new money row; and a click that shows pre %, post %, and share delta. Compute percents from shares / fully diluted. Flag if group percents do not add to 100 plus or minus rounding. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Holder rows and new-money shares in labeled JS constants at the top. - Print a footnote: sample ownership model, not legal advice. - Do not invent liquidation preferences or voting terms. - Accessible contrast; not color-only groups. </constraints> <format> Return the full HTML as an artifact, then explain fully-diluted math and which holder array to replace. </format>

You are a founder who shows how an option-pool refresh changes ownership in this raise, not a compensation designer. <context> I need an option-pool refresh dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample shares so it opens as a working screen I can click in the chat. Pool allocation inside the round. Not a hiring plan. Not a slide. </context> <inputs> - Target pool percent: [POOL PERCENT] - Company name: [COMPANY NAME] - Whether the refresh is pre-money or post-money: [PRE OR POST] - Founder shares, existing pool, new-money shares: [OR INVENT] </inputs> <task> Build the dashboard with: a header naming [POOL PERCENT]; a KPI row (pool before, pool after, founder % before, founder % after, dilution points); a toggle that restates the pool using the pre or post rule I gave; a simple ownership bar; a table of groups; and a footnote that prints the rule. Compute the new pool shares from the rule and the target percent. Clicking a group shows share counts. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Shares and the pre/post flag in labeled JS constants at the top. - Show the formula in a comment and on the page. Label as a sample, not legal advice. - Do not invent hire names or grant sizes. - Accessible contrast. </constraints> <format> Return the full HTML as an artifact, then write the pre versus post pool rule and which constants to replace. </format>

You are a founder who splits insider follow-on from new money in this close, not a board secretary and not a deck designer. <context> I need an insider versus new money dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample checks so it opens as a working screen I can click in the chat. Who fills the raise. No operating finance. No slides. </context> <inputs> - Insider checks: [INSIDER CHECKS] - Company name: [COMPANY NAME] - New-money checks: [OR INVENT] - Target raise: [AMOUNT] - Currency: [E.G. USD] </inputs> <task> Build the dashboard with: a header for [COMPANY NAME]; a KPI row (insider dollars, new-money dollars, insider share of committed, remaining to target); a two-slice bar; chips that show insiders only, new money only, or all; a table (name, insider yes/no, dollars, status); and a callout if insiders are carrying more than an editable share. Compute insider share as insider dollars / (insider + new money). Clicking a row highlights the slice. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Check rows in labeled JS constants at the top. - Insider share is computed. Do not hardcode it. - Do not invent board seats or voting. - Accessible contrast; currency consistent. </constraints> <format> Return the full HTML as an artifact, then explain the insider rule and which check arrays to replace. </format>

You are a founder who tracks pro rata take-up and leftover allocation in the close, not counsel and not a pitch writer. <context> I need a pro rata and leftover dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample rights so it opens as a working screen I can click in the chat. Allocation leftovers. No legal opinion. No slides. </context> <inputs> - Holders with pro rata rights and max dollars: [PRO RATA LIST] - Company name: [COMPANY NAME] - Taken / waived / pending per holder: [OR INVENT] - Target raise and already reserved lead/new-money dollars: [AMOUNTS] - Currency: [E.G. USD] </inputs> <task> Build the dashboard with: a header for [COMPANY NAME]; a KPI row (pro rata taken, waived, pending, leftover dollars); a bar of taken versus waived versus pending; a table from [PRO RATA LIST]; and a leftover callout (target minus reserved minus taken). Clicking waived shows how much room that opened. Pending does not count as taken. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Rights rows and reserved dollars in labeled JS constants at the top. - Leftover is computed. Flag a negative leftover. - Do not invent statutory rights. Use only the list I gave. - Accessible contrast; currency consistent. </constraints> <format> Return the full HTML as an artifact, then write leftover math and which rights array to replace. </format>

You are a founder who builds a weekly raise-status strip the team can click through on Monday, not a board pack and not a pitch email. <context> I need a weekly raise status strip as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample weeks so it opens as a working screen I can click in the chat. Raise ops update. Not a finance flash. Not a deck. </context> <inputs> - Week label: [UPDATE WEEK] - Company name: [COMPANY NAME] - Weeks of history: [E.G. LAST 8 WEEKS] - Per week: intros, first meetings, dollars newly soft, dollars newly signed, dollars wired: [OR INVENT] </inputs> <task> Build the dashboard with: a header naming [UPDATE WEEK]; a KPI row for the selected week (intros, meetings, new soft, new signed, new wired); a week picker; sparklines for each series; a table of the eight weeks; and a next-week ask list of five sample follow-ups you generate from the weakest funnel step that week. Clicking a week restates the cards. Compute week-over-week deltas. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Weekly rows in labeled JS constants at the top. - Deltas are computed. Do not invent product MRR on this strip. - Accessible contrast; print-friendly. - No slide-style cover. </constraints> <format> Return the full HTML as an artifact, then say which weekly array to replace with your standup notes. </format>

You are a founder who builds the number row for an investor update during a raise, not a board KPI pack and not a pitch-deck appendix. <context> I need an investor update number-row dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample metrics so it opens as a working screen I can click in the chat. The numeric spine of an update. Do not write the letter. Do not build an eight-card board pack. </context> <inputs> - Metrics with this month, last month, and plan: [UPDATE METRICS] - Company name: [COMPANY NAME] - Update month: [E.G. AUGUST 2026] - Raise extras to include as two extra cards: [E.G. COMMITTED, WEEKS TO CLOSE] </inputs> <task> Build the dashboard with: a header for the update month; a row of metric cards from [UPDATE METRICS] plus the two raise extras; each card with this, last, versus last %, versus plan; a small sparkline if you seed history; and a click that opens a one-line definition. Compute variances. Flag a metric that would contradict a sample one-line header you also print, if I give that line. Otherwise skip the contradiction check. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Metric arrays in labeled JS constants at the top. - Do not draft email prose. Numbers and definitions only. - Accessible contrast; status uses color plus a word (up, down, flat). - Not a full board RAG pack. </constraints> <format> Return the full HTML as an artifact, then list which metric array to replace before you paste the letter. </format>

You are a founder who logs new commitments this week so the raise total cannot drift, not a CRM admin and not a pitch writer. <context> I need a this-week commitment log as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample yeses so it opens as a working screen I can click in the chat. Weekly capital in. No slides. No P and L. </context> <inputs> - New commitments this week: [NEW COMMITMENTS] - Company name: [COMPANY NAME] - Raise total before this week: [AMOUNT] - Target: [AMOUNT] - Currency: [E.G. USD] </inputs> <task> Build the dashboard with: a header for [COMPANY NAME]; a KPI row (added this week, raise total after, remaining to target, count of new yeses); a daily bar of added dollars; a log table from [NEW COMMITMENTS] (name, day, dollars, status); and a running-total line from the before-week constant plus each row in date order. Clicking a row restates what the running total was after that yes. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Week rows and the before-week total in labeled JS constants at the top. - Running total is computed in order. Do not hardcode the after-week card. - Accessible contrast; currency consistent. </constraints> <format> Return the full HTML as an artifact, then explain the running-total order and which log to replace. </format>

You are a founder who puts the next ten investor meetings on one screen, not an exec assistant tool and not a pitch coach. <context> I need a next ten meetings dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample meetings so it opens as a working screen I can click in the chat. Calendar of capital conversations. Do not write talking points. Do not design slides. </context> <inputs> - Upcoming meetings: [MEETING CALENDAR] - Company name: [COMPANY NAME] - Today: [DATE] - Stale-hold rule: [E.G. HOLD WITH NO MEETING IN 14 DAYS] </inputs> <task> Build the dashboard with: a header for [COMPANY NAME]; a KPI row (meetings in 7 days, in 14 days, partner-level count, stale holds); a chronological list of the next ten from [MEETING CALENDAR] (when, who, firm, stage, owner); a small stage mix bar; and a stale-hold callout using the rule. Clicking a meeting opens a one-line purpose field already filled with sample text. Sort is by datetime. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Meeting rows and the stale rule in labeled JS constants at the top. - Counts are computed from dates versus today. Do not invent agendas. - Accessible contrast; keyboard-usable list. </constraints> <format> Return the full HTML as an artifact, then say which meeting array to replace with a calendar export. </format>

You are a founder who checks raise-update claims against the live numbers before anyone hits send, not a copywriter and not a board secretary. <context> I need a claim versus number checker as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample claims and numbers so it opens as a working screen I can click in the chat. Fact check for the raise update. Do not rewrite the pitch. Do not build a board narrative header. </context> <inputs> - Claims I want to make: [CLAIMS] - Supporting numbers (target, committed, wired, runway months, weeks to close): [OR INVENT] - Company name: [COMPANY NAME] - What I will not claim: [OFF-LIMITS] </inputs> <task> Build the dashboard with: a header for [COMPANY NAME]; the number cards; a list of [CLAIMS] each tagged supports, tensions, or unclear; a click that shows which number you used; and a warning if a claim would break [OFF-LIMITS] or contradict committed versus target. Use simple labeled rules (for example a claim of oversubscribed is tensions unless committed is at or above target). Print the rules. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Claims and number constants at the top. - Do not invent a second story. Honor [OFF-LIMITS]. - Status uses the words supports, tensions, or unclear plus color. - No slide layout. </constraints> <format> Return the full HTML as an artifact, then list the check rules and which claim array to replace. </format>

You are a founder who runs a week-by-week close plan, not a project manager for the product roadmap and not a pitch coach. <context> I need a week-by-week close plan dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample tasks so it opens as a working screen I can click in the chat. Path to money in the bank. No slides. No operating OKRs. </context> <inputs> - Weeks to close: [CLOSE WEEKS] - Company name: [COMPANY NAME] - Tasks with week, owner, status (open, blocked, done): [OR INVENT] - Target close date: [DATE] </inputs> <task> Build the dashboard with: a header toward the close date; a KPI row (weeks left, open tasks, blocked tasks, done %); a week strip from [CLOSE WEEKS]; a task table; a blocked-week flag when a week still has a blocked task; and a click on a week that filters the table. Compute done % as done / all tasks. Cards recompute from the task list. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Task rows and week labels in labeled JS constants at the top. - Blocked uses color plus the word blocked. - Do not invent legal steps I did not list. - Accessible contrast; responsive layout. </constraints> <format> Return the full HTML as an artifact, then say which task array to replace with the live close checklist. </format>

You are a founder who tracks closing documents and wires on one screen, not counsel and not a treasury payment-run tool. <context> I need a docs and wire tracker as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample closing rows so it opens as a working screen I can click in the chat. Close mechanics. Not AP bills. Not a deck appendix. </context> <inputs> - Closing docs and per-investor wire fields: [CLOSING DOCS] - Company name: [COMPANY NAME] - Status values: [E.G. MISSING, IN REVIEW, SIGNED, WIRE SENT, WIRE CLEARED] - Currency: [E.G. USD] </inputs> <task> Build the dashboard with: a header for [COMPANY NAME]; a KPI row (docs missing, docs signed, wires sent, wires cleared, dollars cleared); a two-column layout (doc checklist, wire table); chips for missing versus cleared; and a click that opens the next required status. Compute dollars cleared from rows in wire-cleared status. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Doc and wire rows in labeled JS constants at the top. - Do not invent bank rails or legal sufficiency. Status and dollars only. - Accessible contrast; keyboard-usable tables. </constraints> <format> Return the full HTML as an artifact, then say which closing array to replace. </format>

You are a founder who watches the last dollars to a named minimum close, not a sales forecast owner. <context> I need a dollars still to minimum dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample checks so it opens as a working screen I can click in the chat. First-close math. Soft pledges do not shrink the gap. No pitch thermometer slide as the only view (you may use a progress bar, but the table must be the source). </context> <inputs> - Minimum close: [MINIMUM CLOSE] - Company name: [COMPANY NAME] - Signed dollars, wired dollars, named remaining prospects with dollars: [OR INVENT] - Currency: [E.G. USD] </inputs> <task> Build the dashboard with: a header naming [MINIMUM CLOSE]; a KPI row (minimum, signed, wired, gap = minimum minus signed, gap versus wired); a progress bar to minimum using signed, with a second thin bar for wired; a prospect table that I can mark as signed in-sample via a checkbox that recomputes the gap; and a callout of the smallest set of open rows that would cover the gap (greedy by dollars). Clicking a row toggles it into a what-if signed set without changing the base constants unless the checkbox is on. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Minimum and rows in labeled JS constants at the top. - Gap is computed. Soft is not in the gap math. - Accessible contrast; checkboxes keyboard-usable. - Do not invent a second close size here. </constraints> <format> Return the full HTML as an artifact, then write the gap rule and which prospect array to replace. </format>

You are a founder who logs signatures and side letters until the close can fire, not an attorney of record. <context> I need a signature and side letter log as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample signatories so it opens as a working screen I can click in the chat. Close roster. Not legal advice. Not a slide. </context> <inputs> - Signatories: [SIGNATORY LIST] - Company name: [COMPANY NAME] - Fields: name, role (investor, company, counsel), signature status, side letter yes/no, side letter status: [OR INVENT] </inputs> <task> Build the dashboard with: a header for [COMPANY NAME]; a KPI row (signatories, signed, waiting, open side letters); a table from [SIGNATORY LIST]; chips for waiting versus signed versus open side letter; a bar of waiting by role; and a click that opens a one-line blocker field. Compute counts from status fields. Waiting is any row not signed, or a yes side letter that is not done. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Signatory rows in labeled JS constants at the top. - Print a footnote: tracker only, not legal advice. - Do not invent clause text. - Accessible contrast. </constraints> <format> Return the full HTML as an artifact, then say which signatory array to replace. </format>

You are a founder who runs the close-day wire board until every expected check is cleared, not a treasurer running vendor AP. <context> I need a close-day wire dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample wires so it opens as a working screen I can click in the chat. One day, investor wires only. No vendor bills. No pitch celebration slide. </context> <inputs> - Wire schedule: [WIRE SCHEDULE] - Company name: [COMPANY NAME] - Close day: [DATE] - Expected total: [AMOUNT] - Currency: [E.G. USD] </inputs> <task> Build the dashboard with: a header dated the close day; a KPI row (expected from [WIRE SCHEDULE], sent, cleared, still out, percent cleared); a table (investor, expected, sent yes/no, cleared yes/no, amount); a bar of cleared versus still out; and a not-cleared list. Checking sent or cleared in the sample UI recomputes the cards from the same rows. Flag if cleared exceeds expected. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Wire rows and expected total in labeled JS constants at the top. - Totals must reconcile to the sum of rows; flag a break versus the expected constant. - Do not invent FX or bank fees unless I pasted them. - Accessible contrast; currency consistent. </constraints> <format> Return the full HTML as an artifact, then explain cleared versus expected and which wire array to replace. </format>