Design a Finance KPI Dashboard for Leadership
Specifies a grouped, audience-appropriate finance KPI dashboard with exact metric definitions and a layout plan.
Most finance dashboards fail in one of two ways: too many metrics that no one acts on, or metrics defined so loosely that the data team builds the wrong thing. This prompt produces a tight spec — 8 to 12 KPIs chosen for a specific audience, each with an exact definition the data team can build without guessing. The structure matters. Grouping KPIs into growth, profitability, efficiency, and liquidity gives the dashboard a narrative; labeling leading versus lagging indicators tells the reader which numbers predict and which confirm. And the one-screen layout — what's the headline metric, how the rest flows — is the difference between a dashboard people scan in seconds and one they ignore. By tying each KPI to a question the audience actually needs answered, it avoids vanity metrics. The data-availability check keeps you honest about what you can measure today versus what needs new instrumentation. Use it to spec a dashboard before you build, so the build is right the first time.
You are an expert FP&A analyst designing a finance KPI dashboard for [AUDIENCE] at a [BUSINESS TYPE] company. The priorities I want the dashboard to answer are: [KEY QUESTIONS]. Recommend 8 to 12 KPIs grouped into logical sections (for example growth, profitability, efficiency, and liquidity). For each KPI, give its precise definition or formula, the recommended visualization, a sensible comparison (versus plan, prior period, or target), and why this audience needs it. Note which KPIs should be leading versus lagging indicators. Then propose a one-screen layout describing what sits top-left as the headline metric and how the rest flows. Keep definitions exact so the data team can build them without guessing. Use [DATA AVAILABLE] to flag any KPI I can't yet measure.
What you can expect back
Finance KPI dashboard spec — exec/board, SaaS: Growth (leading): MRR (sum of active recurring billings) — line vs. plan; Net New MRR (new + expansion − contraction − churn) — bar vs. prior month; NRR (retained+expansion revenue / starting revenue) — vs. target 110%. Profitability (lagging): Gross margin % (revenue − COGS / revenue) — line vs. plan; Gross profit $ — vs. prior quarter. Efficiency: CAC payback (S&M spend / new MRR × margin) — vs. target <12 mo; Burn multiple (net burn / net new ARR) — vs. target <1.5. Liquidity (lagging): Cash balance — vs. prior month; Net burn — vs. plan; Runway months (cash / net burn) — vs. 18-mo target. Layout: Runway top-left as the headline (the board's first question), MRR and Net New MRR beside it, NRR and CAC payback in the efficiency row, margin and burn multiple below, cash trend along the bottom. Can't measure yet: gross-margin-by-segment needs per-customer cost allocation you don't have — flag as a future addition.
Illustrative example — your results will vary by tool and inputs.
Get sharper results
- 01Anchor every KPI to one of your key questions; if a metric doesn't answer a question the audience asked, cut it.
- 02Make the headline metric the audience's single biggest worry — runway for a board, margin for an operator — so the dashboard opens with what they came for.
- 03Insist on exact formulas in the spec; 'churn' means three different things and the data team will pick the wrong one without a definition.
- 04Use the data-availability flag honestly so you don't promise a KPI you can't yet instrument.
Adapt it for your case
Change the audience to department heads and ask for KPIs tied to controllable line items rather than company-level metrics.
Ask it to output a separate metric-definitions table the data team can use as the build spec.
Have it tag each KPI as daily, weekly, or monthly refresh so the dashboard mixes real-time and periodic views appropriately.
Common questions
Why does it limit me to 8–12 KPIs?
A dashboard people act on is focused. More than a dozen metrics dilutes attention and hides the ones that matter. The prompt forces prioritization tied to your stated questions.
Will the definitions be precise enough to build?
It gives exact formulas, but you should confirm each maps to fields in your actual data. The availability flag exists precisely so you catch KPIs that need new instrumentation before building.
What's the point of leading vs. lagging labels?
Leading metrics (like net new MRR) hint at where you're headed; lagging ones (like gross margin) confirm where you've been. Labeling them helps the audience know which numbers to act on early.
You may also need
Stress-Test the Assumptions Behind a Financial Model
Critically reviews a financial model's assumptions for aggressiveness, sensitivity, and internal consistency.
Explain Budget vs. Actual Variances for the Period
Computes and prioritizes material budget-versus-actual variances and proposes plausible root causes to investigate.
Break Down Unit Economics: CAC, LTV, and Payback
Calculates and interprets CAC, LTV, LTV:CAC, and payback period from acquisition and retention inputs.
Analyze Pricing Changes and Their Margin Impact
Quantifies the margin and break-even impact of a price change and stress-tests it against several volume scenarios.