For Financial Analyst (Corporate)s ·
What you'll accomplish
After completing this guide, you'll be using Claude to draft professional financial communications (emails, memos, and meeting follow-ups) that translate complex financial data into plain English for non-finance business partners. You'll spend less time agonizing over wording and less time in revision cycles with your manager.
What you'll need
The key to getting great email drafts from Claude is providing three things:
Without all three, Claude will write a competent but generic email. With all three, it writes a targeted, action-oriented communication that gets results.
Template for your request:
Draft a [email/memo/Slack message] to [recipient's title and role].
What happened: [2-3 bullet points of financial facts]
What it means for them: [how it affects their team/budget/plans]
What I need from them: [specific ask, by when]
Tone: [professional/direct/collaborative — pick one]
Length: [under 150 words / 1 paragraph / 2 short paragraphs]
The most common communication challenge: explaining why a department's spending was above or below budget without sounding accusatory.
Draft a professional email to the VP of [Department] about their Q[X] budget performance.
What happened: Their department spent $[X]M vs. a budget of $[X]M — $[X]M [over/under] budget.
Main drivers: [list 1-2 specific causes — e.g., "3 open headcount positions filled 2 months early" or "unplanned software renewal"]
What it means: [impact on overall company budget — favorable/unfavorable]
What I need: I need them to confirm whether this level of spend is expected to continue in Q[X+1] or if it was a one-time item.
Tone: Matter-of-fact and collaborative — not accusatory. They're a good partner.
Length: Under 150 words.
What you should see: A diplomatic email that states the facts, explains the implication, and makes a specific ask. No blame implied.
When you update the company forecast and need to communicate the change to stakeholders, the framing matters significantly.
Draft a brief memo to the leadership team announcing a forecast change.
What changed: We are revising full-year revenue guidance from $[X]M to $[X]M.
Why: [main reason — e.g., "three enterprise deals totaling $2.1M have slipped from Q2 to Q3"]
What it means: [impact on annual plan — e.g., "we are now $2.1M below our full-year target with 9 months remaining"]
What happens next: [corrective actions or monitoring steps]
Tone: Transparent and factual. Do not minimize or oversell. The leadership team can handle the truth.
Length: 3 short paragraphs.
Finance business partners are expected to follow up after major meetings with a clear recap of decisions and next steps.
Write a follow-up email after our Q[X] business review meeting.
Attendees: [list of titles, not names]
Key decisions made:
- [Decision 1]
- [Decision 2]
Action items:
- [Person/title]: [action], by [date]
- [Person/title]: [action], by [date]
Tone: Professional and clear. This goes to a broad leadership audience.
Length: Under 200 words with a clear action item list.
What you should see: A professional meeting recap email with a clear decisions section and formatted action items. This is the kind of follow-up that builds your reputation as an organized, reliable business partner.
When business partners ask what a finance term means, turn it into a teachable moment with AI.
Write a plain-English explanation of [accounting term] for a department head with no finance background. Use a simple analogy if helpful. Keep it under 75 words.
Examples:
Budget variance email:
Draft an email to [recipient role] about their [period] budget performance. Spent: $[X]. Budget: $[X]. Variance drivers: [list]. Tone: [collaborative/direct]. Ask: [what you need from them].
Forecast change announcement:
Draft a memo announcing a forecast revision from $[X]M to $[X]M. Reason: [driver]. Impact: [consequence]. Next steps: [actions].
Meeting follow-up:
Write a follow-up email after [meeting name]. Decisions: [list]. Action items: [list with owners and dates]. Length: under 200 words.
Plain English translation:
Explain [finance term] in plain English for a [department head with no finance background]. Under 75 words. Use an analogy.