Finance KPI benchmarking analyzer

Purpose

Take a set of finance function KPIs, benchmark each against industry and company-size norms, and identify where the finance organization is leading, at median, or lagging — then convert the gaps into ranked, time-bound targets with a realistic path to top-quartile performance. Replaces gut-feel judgments about "how good is our finance function" with a defensible, comparative scorecard.

When to Use

Invoke this skill when the user asks to:

• Benchmark finance function KPIs (cost of finance, close cycle time, forecast accuracy, DSO, etc.) against industry norms
• Build a finance KPI scorecard for a board deck or leadership review
• Diagnose whether the finance function is efficient relative to peers
• Prepare a business case for a finance transformation or automation initiative
• Set realistic performance targets for the FP&A or accounting team
• Justify headcount, tooling, or process investment with comparative data

Inputs Required

Before starting, collect:

• KPI values: The current metrics to benchmark (e.g., cost of finance as % of revenue, days to close, forecast accuracy %, DSO, invoices per FTE)
• Industry/sector: The company's industry (e.g., SaaS, manufacturing, retail, professional services)
• Company revenue band: Annual revenue range (e.g., <$50M, $50–250M, $250M–1B, $1B+)
• Finance team size: Total finance FTE count, and split across accounting / FP&A / treasury if available
• Business context: Public vs. private, single vs. multi-entity, high vs. low transaction volume
• Priority areas: Any KPIs leadership is already worried about, if known
• Target horizon: How long they have to improve (e.g., 12 months, 2 years)

If industry benchmarks for a specific metric are unavailable at the exact revenue band, use the closest adjacent band and note the assumption. If a KPI is provided without a definition, state the definition assumed.

Instructions

Step 1: Normalize and Validate the KPI Set

Before benchmarking, confirm each metric is measured consistently:

• Cost of finance as % of revenue: Total finance function cost (people + systems + outsourcing) ÷ total revenue
• Close cycle time: Business days from period-end to books closed (distinguish soft vs. hard close if stated)
• Forecast accuracy: 1 − (|actual − forecast| ÷ actual), typically at the revenue or EBITDA line
• DSO / DPO: Standard working capital cycle metrics
• Transactions per FTE: Invoices, journal entries, or reconciliations processed per finance headcount Flag any metric where the definition is ambiguous and state the definition you are benchmarking against.

Step 2: Assign Benchmark Bands

For each KPI, place it against industry and revenue-band norms using this tiering:

• Top quartile (leading): Top-tier performance for the sector and size
• Median (at norm): Typical performance for a comparable finance function
• Third quartile (lagging): Below typical — an improvement opportunity
• Bottom quartile (critical): Materially behind peers — priority intervention

Use directionally reliable industry reference points calibrated to the stated sector and revenue band. Where public benchmark data varies, present a range rather than a single false-precision number, and note that finance-intensive or high-transaction industries (banking, insurance) carry higher cost-of-finance norms than asset-light ones.

Present this as a table:

Step 3: Diagnose the Drivers Behind Lagging KPIs

For each KPI in the third or bottom quartile, identify the most likely structural cause:

• High cost of finance %: Manual processing, low automation, over-tenured structure, fragmented systems
• Long close cycle: Manual reconciliations, late intercompany settlements, spreadsheet-based consolidation, no close calendar discipline
• Low forecast accuracy: Poor driver-based modeling, siloed inputs, infrequent reforecasting, weak sales pipeline linkage
• High DSO: Weak collections process, unclear terms, invoicing delays, no dunning automation Tie each diagnosis to the specific input context (team size, systems, transaction volume) rather than generic causes.

Step 4: Set Ranked Improvement Targets

Convert each gap into a concrete target and rank by expected value ÷ effort:

1. State the current value, the recommended target (usually median first, then top-quartile as a stretch), and the interim milestone
2. Rank targets so the highest-impact, most-achievable improvements come first
3. For the top 3 targets, note the primary lever (process, automation, structure, or capability) and a rough effort level (low/medium/high)

Step 5: Build a Phased Roadmap

Sequence the targets across the stated horizon:

• Phase 1 (0–3 months): Quick wins — process discipline, close calendar, low-effort automation
• Phase 2 (3–9 months): Structural changes — system consolidation, driver-based forecasting, collections overhaul
• Phase 3 (9+ months): Capability and top-quartile push — advanced automation, org redesign, continuous forecasting Note dependencies (e.g., system consolidation must precede close-time targets).

Step 6: Summarize the Scorecard Verdict

Deliver a 3–4 sentence executive verdict: overall standing (leading / at norm / lagging), the single biggest opportunity, and the expected trajectory if the roadmap is followed. Be direct — name the weakest area explicitly.

Output Format

• Structure: Executive verdict → benchmark scorecard table → driver diagnosis → ranked targets → phased roadmap
• Length: 900–1,300 words
• Format: Structured document with one benchmark table; ranked targets and roadmap as structured lists
• Sections: Executive Verdict → KPI Benchmark Scorecard → Driver Diagnosis (lagging KPIs only) → Ranked Improvement Targets → Phased Roadmap
• Tone: FP&A director briefing a CFO — analytical, comparative, direct; no hedging on where the function is weak

Quality Checklist

Before delivering output, verify:

• [ ] Every provided KPI appears in the benchmark table with a current value, median, top-quartile reference, and band
• [ ] Each benchmark is calibrated to the stated industry AND revenue band — not a generic all-industry figure
• [ ] Gap to top quartile is quantified numerically for each KPI, not described vaguely
• [ ] Every lagging KPI (third/bottom quartile) has a specific driver diagnosis tied to the input context
• [ ] Improvement targets are ranked by impact/effort, not listed arbitrarily
• [ ] The phased roadmap sequences targets across the stated horizon with any dependencies noted

Notes

• Cost of finance as % of revenue is the single most industry-sensitive metric — a "good" number for a bank is very different from one for a SaaS company; always anchor to the stated sector
• Where a metric's definition wasn't specified, state your assumed definition rather than benchmarking silently against an unstated one
• Median-first targeting is usually more credible than jumping straight to top-quartile; frame top-quartile as a stretch goal tied to specific enabling investments
• When benchmark data for an exact revenue band is thin, present a range and flag the confidence level rather than manufacturing false precision

How to use this skill

This file is a Claude Code skill in Anthropic's standard format — markdown with YAML frontmatter at the top.

Installing in Claude Code:

• ~/.claude/skills/<folder-name>/SKILL.md — auto-loads in every session anywhere on your machine (recommended for skills you'll use across multiple projects)
• <your-project>/.claude/skills/<folder-name>/SKILL.md — auto-loads only when working in that project (recommended for project-specific skills)

Restart Claude Code or open a new session to register.

Using in Claude.ai, ChatGPT, Gemini, or other AI tools:

1. Drag this file into a new chat, or copy and paste its contents
2. Send your task or request as your next message — the AI will apply the skill where it fits

For Claude Code skill details: https://docs.anthropic.com/en/docs/claude-code/skills