Skip to content
← Back to CLSkills
FINANCE

Claude for financial analysis, done properly.

The tested prompt, the codes that help, and the setup finance pros run. Copy, adapt, ship.

One-time purchase. Lifetime updates. Works with Claude, Codex, and Gemini.
Why this needs a proper prompt

Financial analysis requires synthesizing numbers into narrative. Most people can pull data but struggle to tell the story — what the numbers mean for the business.

Why Claude for this

Three reasons this actually lands.

The prompt, the codes, the fit. Each one on its own is a nice-to-have. Together, they change the workflow.

The prompt is the product.

One tested prompt, copy-paste ready. Rules baked in, placeholders marked, tone locked down. No prompt-engineering trial runs, no back-and-forth.

Codes that stack.

Prefix with REASON, V=2, REFINE for compound effects. Each code is a documented technique, not a magic word.

Built for the role.

Tuned for finance workflows. Not a generic template, and not another "you are a helpful assistant" hack.

Without the pattern vs with it.

What the day looks like when you keep winging the prompt, and what it looks like when you stop.

The prompt
Without it

Generic prompt. Claude writes something that could be about anyone, in any industry, from anywhere. Sounds like a template because it is one.

With it

The CLSkills prompt with placeholders for your context. Claude writes it like a specialist who actually knows the work. Publishable after one edit pass.

The workflow
Without it

You paste, Claude answers, you rewrite, you paste again. Ten minutes of back-and-forth per output. Three hours across a batch of five.

With it

Prompt loaded once. You feed the specifics, Claude returns the finished output. Two minutes per, twenty across five. Same tone, same structure, every time.

The result
Without it

Middle-of-the-road copy that reads AI-flavoured. Recipients notice. Response rates stay low. You end up rewriting most of it anyway.

With it

A clear financial analysis that translates numbers into narrative. Ratios benchmarked against industry standards, red flags highlighted, and an executive summary ready for stakeholders.

The prompt

Copy this, replace the placeholders, ship.

Analyze these financial statements.

Company: [NAME]
Period: [QUARTER/YEAR]
Industry: [INDUSTRY]
Purpose: [INTERNAL REVIEW / INVESTOR PRESENTATION / BOARD MEETING / LENDING]

Financial data:
[PASTE P&L, BALANCE SHEET, AND/OR CASH FLOW STATEMENTS]

Analyze:
1. **Revenue trends**: Growth rate, seasonality, customer concentration
2. **Profitability**: Gross margin, operating margin, net margin — trends and benchmarks
3. **Cash flow**: Operating cash flow vs. net income, burn rate, runway
4. **Balance sheet health**: Current ratio, debt-to-equity, working capital
5. **Key ratios**: 5 most relevant ratios for this industry with benchmarks
6. **Red flags**: Anything concerning in the numbers
7. **Narrative**: 3-paragraph executive summary of financial health

Format: Ratios in a table, narrative in plain English.
Audience: [CFO LEVEL / BOARD LEVEL / NON-FINANCIAL STAKEHOLDERS]

Replace the [BRACKETED] placeholders with your context.

Codes that help

Stack these prefixes for compound gains.

Prepend one or more of these to the prompt above. Each code is documented on its own page with before and after examples.

REASONV=2REFINE

Every prompt, once.

The Cheat Sheet is every tested code, with a before and an after.

Get the Cheat Sheet, $19Read the free guide
More finance tasks

Nearby prompts for the same role.

CLAUDE FOR
Variance Analysis

Budget-to-actual variance reports are tedious but critical. Most analyses stop at 'we were over budget' without explaining why or recommendi…

CLAUDE FOR
Financial Forecasting

Financial forecasts are either too optimistic (hockey stick projections) or too conservative (just last year +5%). Building a credible, assu…

CLAUDE FOR
Audit Preparation

Audit prep is stressful and time-consuming. Missing documentation, inconsistent records, and last-minute scrambles make audits worse than th…