Purpose
Produce a structured evaluation of a finance technology landscape — mapping each system to the finance capabilities it should serve, scoring maturity, and surfacing gaps, redundancies, and integration risks — so the finance leader can prioritize investment and consolidation with a defensible rationale rather than vendor-driven guesswork.
When to Use
Invoke this skill when the user asks to:
- Assess or audit their current finance systems landscape
- Decide whether to replace, upgrade, or consolidate an ERP or EPM platform
- Identify overlapping or redundant finance tools to rationalize
- Diagnose why the month-end close, reporting, or forecasting is slow or manual
- Build the systems portion of a finance transformation business case or roadmap
- Compare their stack against leading practice before a re-platform decision
Inputs Required
Before starting, collect:
- Current systems inventory: Named systems and versions across ERP, EPM/planning, financial close/consolidation, treasury/cash, tax, procurement/AP, expense, and reporting/BI
- Deployment model: On-premise, cloud/SaaS, or hybrid per system where known
- Key pain points: The 3–6 most-cited problems (e.g., manual close, no rolling forecast, spreadsheet dependency, poor data lineage)
- Company profile: Revenue band, entity/legal-entity count, currencies, and industry
- Integration state: How systems currently connect (native, middleware, manual/file-based, none)
- Strategic drivers: What's forcing the evaluation (growth, M&A, IPO readiness, audit findings, cost reduction, end-of-support)
- Budget/timeline constraints: Any known investment ceiling or transformation horizon
If deployment model or integration state is unstated, infer from the systems named and flag the assumption.
Instructions
Step 1: Map Systems to the Finance Capability Model
Assign every named system to the capabilities it should support. Use this reference model:
- Record-to-Report: GL, sub-ledgers, intercompany, close/consolidation, reconciliation, reporting
- Plan-to-Perform: budgeting, forecasting, driver-based planning, scenario/what-if, profitability analysis
- Order-to-Cash: billing, AR, collections, revenue recognition
- Procure-to-Pay: procurement, AP, invoice processing, expense
- Treasury & Risk: cash positioning, bank connectivity, debt/investment, FX exposure
- Tax: provision, indirect tax, compliance/filing
- Data & Analytics: master data, data warehouse/lake, BI/self-service reporting
Produce a coverage matrix: capability rows × current system(s) covering it. Immediately note any capability with no system, multiple systems, or spreadsheet as system of record.
Step 2: Score Each Capability Area for Maturity
Rate each of the seven capability areas on a 1–5 scale:
- 1 – Manual: spreadsheet-driven, no dedicated tooling, high key-person risk
- 2 – Fragmented: point tools exist but disconnected, heavy rework
- 3 – Functional: adequate system in place, meets basic needs, some manual gaps
- 4 – Integrated: connected, largely automated, reliable data flow
- 5 – Optimized: real-time, self-service, low-touch, analytics-enabled
For each score, cite the specific evidence from the inputs (a pain point, a missing system, a manual integration). Never assign a score without a stated reason.
Step 3: Flag Gaps
Identify capabilities that are missing or under-served relative to the company profile. Calibrate expectations to size — a single-entity mid-market firm needs less than a 40-entity multinational. For each gap, state:
- The capability missing
- The business consequence (close delay, audit risk, forecast blind spot, compliance exposure)
- Whether it's a table-stakes gap (below expected baseline) or an advancement gap (leading-practice upside)
Step 4: Flag Redundancies and Overlaps
Identify where two or more systems serve the same capability, or where a platform's native module is being duplicated by a bolt-on tool. For each, note:
- The overlapping systems
- The likely cost of redundancy (duplicate license, duplicate maintenance, reconciliation effort)
- A consolidation recommendation (retire, absorb into platform, keep with defined boundary)
Step 5: Assess Integration and Data Architecture
Evaluate how well data flows across the stack:
- Identify file-based or manual handoffs — these are the highest-risk integration points
- Flag no single source of truth for master data (chart of accounts, entity hierarchy, customer/vendor)
- Note where a lack of integration directly causes a named pain point (e.g., manual GL-to-planning refresh → stale forecast)
- Comment on data lineage and auditability where relevant to audit/IPO drivers
Step 6: Rank Modernization Priorities
Produce a ranked list of 6–10 modernization actions ordered by a combined view of business impact and feasibility. For each action:
- The move: replace / upgrade / consolidate / integrate / add
- Rationale: which gap or redundancy it resolves and the driver it serves
- Build/Buy/Consolidate recommendation with brief reasoning
- Sequencing note: prerequisite dependencies (e.g., master data cleanup before planning re-platform)
- Effort tier: Quick win / Medium initiative / Major program
Anchor the top priority to the strongest strategic driver and the most severe table-stakes gap. Be opinionated about sequence — foundational data and ERP decisions generally precede EPM and analytics investments.
Step 7: Summarize the Transformation Thesis
In one paragraph, state the overall condition of the stack, the single highest-leverage move, and the recommended horizon (e.g., "stabilize close in 6 months, re-platform planning in 12–18 months").
Output Format
- Structure: Coverage matrix → maturity scorecard → gaps → redundancies → integration assessment → ranked modernization priorities → transformation thesis
- Length: 1,000–1,400 words
- Format: Tables for the coverage matrix and maturity scorecard; structured bullets for gaps, redundancies, and integration; a numbered ranked list for modernization priorities; short prose for the thesis
- Sections: Capability Coverage Matrix, Maturity Scorecard (7 areas), Gaps, Redundancies & Overlaps, Integration & Data Architecture, Modernization Priorities (ranked), Transformation Thesis
- Tone: Finance transformation advisor — analytical, vendor-neutral, decision-oriented; no product marketing language
Quality Checklist
Before delivering output, verify:
- [ ] Every named system is mapped to at least one capability in the coverage matrix
- [ ] All seven capability areas have a maturity score (1–5) with cited evidence
- [ ] Each flagged gap is labeled table-stakes vs. advancement and tied to a business consequence
- [ ] Redundancies name the specific overlapping systems and a consolidation call
- [ ] Modernization priorities are ranked (not listed arbitrarily) with a build/buy/consolidate recommendation each
- [ ] Recommendations are calibrated to the company's size, entity count, and stated drivers — not generic
Notes
- Master data and chart-of-accounts cleanup is frequently the unglamorous prerequisite that determines whether an EPM or analytics investment succeeds — call it out even when it isn't the buyer's stated pain.
- Spreadsheets used as the system of record for close or consolidation are a table-stakes gap for any multi-entity company and should rarely score above a 2.
- When end-of-support or audit findings are among the drivers, weight those actions higher regardless of enthusiasm for analytics upside — they are non-discretionary.
- If the systems inventory is thin, ask one clarifying question: "Which system holds your consolidated financials of record today?" — the answer usually reframes the entire evaluation.
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:
- Drag this file into a new chat, or copy and paste its contents
- 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