Use cases

Try it on something real

Fifteen worked examples across ten bank functions — a stack of complaints, a credit memo, a regulator PDF, a Greek customer email, an SQL question that died in the gap between data and analyst. Pick one that looks like your day. Each takes 15–45 minutes the first time and a fraction of that once you've done it. And every walkthrough now climbs the same three-rung ladder: run it, make Claude prove it, then level it up into an interactive page. Audience: complete beginner (one capstone for when the loop clicks) · 15 use cases · all doable after Day 1 → haven't done Day 1 yet? Start there.

Unit

Accounting Compliance Contact center Data HR Mortgages Operations Process improvement Retail Risk

• Contact center ~25 min

  Turn a stack of customer complaints into a one-page heatmap

  You ask Claude to invent a realistic complaints CSV (so the use case works without any system access), then a few minutes later you have a one-page markdown report showing the top five themes, how often each appears, and one verbatim quote per theme. Repeatable every Monday on real data once you have it.

  You end up with

  A one-page markdown report — top 5 complaint themes, counts, and one verbatim quote per theme — ready to paste into Teams or email.

  Open the walkthrough →
  Pin
• Retail ~15 min

  Draft a customer reply that doesn't sound corporate

  A frustrated customer emails you. You have three minutes between meetings and a blank reply window. Claude gives you three draft replies in three different tones — you pick the closest one, tweak two sentences, send. The walkthrough works without a real complaint — Claude invents one to practise on.

  You end up with

  Three reply drafts in three different tones (warm / formal / apologetic) with one short rationale each — pick the closest one and polish in place.

  Open the walkthrough →
  Pin
• Compliance ~20 min

  Spot what actually changed between two versions of a policy

  Compliance hands you v3 of a policy and asks "what's different from v2?" Word's track-changes is gone, the diff highlighter shows every comma. Claude reads both, groups the changes by significance, and tells you which two paragraphs you actually need to take to the committee.

  You end up with

  A markdown brief that classifies every change between v1 and v2 as MATERIAL or COSMETIC, with a one-sentence "what this means" line per material change.

  Open the walkthrough →
  Pin
• Mortgages ~30 min

  Build a one-page mortgage eligibility calculator

  A single HTML file with four sliders (income, debts, property value, interest rate) that shows the maximum mortgage amount as you move them. Built in thirty minutes by describing the rules in plain English. You don't write a line of code yourself.

  You end up with

  A single self-contained `index.html` file you can open in any browser — four sliders, a live result with the binding constraint named, ready to share with a colleague or screen-share on a call.

  Open the walkthrough →
  Pin
• Operations ~15 min

  Turn a Teams transcript into proper meeting minutes

  Teams generates a transcript automatically. It is unreadable. Claude turns it into the minutes you actually want — decisions, action items with owners and deadlines, next steps — in your team's template. Five minutes after the call ends.

  You end up with

  A markdown file `minutes-YYYY-MM-DD.md` with decisions, action items (owner + deadline), and a short narrative summary — ready to send to the meeting attendees.

  Open the walkthrough →
  Pin
• Compliance ~25 min

  Compress a 60-page regulator PDF into a 1-page brief

  A new ECB / BoG / EBA paper lands in your inbox. It is 60 pages, half of it is boilerplate, the deadline is Friday. Claude reads it and writes a one-pager — what changed, who's affected, what we need to do, by when — that you can take to your team lead.

  You end up with

  A one-page markdown brief with four labelled sections — What changed · Who's affected · What we need to do · By when — plus a links list back to the source pages for verification.

  Open the walkthrough →
  Pin
• Risk ~20 min

  Compress a 15-page SME credit memo into a 3-bullet summary

  A relationship manager hands you a fifteen-page credit memo and the committee meets in an hour. Claude reads it and produces a three-bullet exec summary plus a risk-flag list — the structured starting point your senior credit officer actually wants, not a paraphrase of the whole memo.

  You end up with

  A one-page markdown brief — 3-bullet exec summary, top 5 risk flags with severity (HIGH/MED/LOW), and an "open questions for the RM" list.

  Open the walkthrough →
  Pin
• Data ~20 min

  Turn a business question into a SQL query you can actually run

  A manager asks "how many cards did we issue to under-25s last quarter, split by branch?" You don't write SQL. You describe the tables to Claude in plain English, ask for the query, run it against the data warehouse. Twenty minutes from question to chart.

  You end up with

  A `query.sql` file you can paste straight into your data warehouse client (DBeaver, SSMS, Snowflake UI, whatever your team uses) and run.

  Open the walkthrough →
  Pin
• Accounting ~25 min

  Extract data from a stack of PDF invoices into one clean CSV

  Suppliers send invoices in every format imaginable. You re-type the fields into Excel for hours. Drop the PDFs into a folder, ask Claude for a CSV with supplier, date, amount, VAT, and invoice number — twenty minutes later you import the CSV into your accounting tool.

  You end up with

  A `invoices.csv` file with one row per invoice — supplier name, invoice number, issue date, net amount, VAT amount, gross amount, due date — ready to import into your accounting tool.

  Open the walkthrough →
  Pin
• HR ~20 min

  Generate a personalised first-week checklist for a new joiner

  A new joiner starts Monday. HR sends them a generic 40-item checklist that scares everyone. Claude reads the job description, the team's standard onboarding doc, and the new joiner's CV — then produces a tailored 12-item week-one plan they can actually finish.

  You end up with

  A markdown checklist with three sections (Day 1 · Days 2–3 · Days 4–5), each item including who to talk to and why it matters. Personalised to the joiner's role and prior experience.

  Open the walkthrough →
  Pin
• Operations ~15 min

  Translate a customer email between Greek and English with cultural notes

  A complaint arrives in Greek and the case needs to escalate to a non-Greek-speaking senior in Frankfurt. Or the reverse — a London supplier sends an English contract that needs to land in front of Athens legal. Claude translates both ways and flags the phrases that don't carry across.

  You end up with

  A markdown file with the original on the left and the translation on the right, plus a "notes" section flagging phrases where Claude is uncertain or where literal translation would mislead.

  Open the walkthrough →
  Pin
• Process improvement ~30 min

  Capture how a colleague does a manual process so you can hand it off

  Someone on the team is the only person who knows how the month-end reconciliation actually works. They're going on holiday. Interview them on Teams (recorded transcript), then ask Claude to turn that transcript into a step-by-step runbook anyone on the team could follow.

  You end up with

  A markdown runbook with numbered steps, named tools at each step, decision points called out explicitly, and a "common errors" section — ready to be reviewed by the original colleague and put in the team SharePoint.

  Open the walkthrough →
  Pin
• Compliance ~25 min

  Turn any policy into a quiz your team will actually take

  Nobody reads the updated anti-bribery policy until the annual attestation forces them to. Claude reads it, writes ten scenario questions with explanations, and builds them into a click-through quiz page with instant feedback — every answer citing the exact policy section. Training that takes five minutes to make and five minutes to take.

  You end up with

  A self-contained `quiz.html` — ten scenario-based questions with instant right/wrong feedback, a score at the end, and a policy citation behind every answer — ready to drop in the team Teams channel.

  Open the walkthrough →
  Pin
• Data ~15 min

  Get from a CSV to a chart your boss can read, in one prompt

  Every team has a CSV nobody looks at — exports from some system, columns of numbers, no picture. Claude reads it and builds an interactive chart page you double-click open. No Excel wrangling, no BI-team ticket, no licence. The gateway use case — once this clicks, you'll see CSVs differently.

  You end up with

  A self-contained `chart.html` — an interactive chart of your CSV with toggles for the dimensions that matter, plus a totals strip that proves the numbers match the file.

  Open the walkthrough →
  Pin
• Contact center capstone ~45 min

  Chain it together: complaints in, Monday briefing pack out

  The capstone. You've done the heatmap, you've done the reply drafts — now chain them. One CLAUDE.md describes the whole Monday workflow, and from then on a single line ("do the Monday pack") turns a fresh complaints CSV into a themed report, reply drafts for the worst theme, an interactive dashboard, and a ready-to-send summary email. This is where Claude Code stops being a tool and becomes a workflow.

  You end up with

  A reusable pipeline folder — drop in a complaints CSV, type one line, get four artifacts — heatmap report, reply drafts, interactive dashboard, summary email — all consistent with each other, every Monday.

  Open the walkthrough →
  Pin

No use cases for that unit yet

More are coming — pick a different unit, or tap "All".

Show all

Pattern recognition

Notice the shape of all fifteen

Same loop every time. Get the input as a file. Open Claude Code in the folder. Write the prompt as a briefing, not a one-liner. Review what came back — then make Claude prove its own output with real commands, not assurances. Save the rules in a CLAUDE.md so the second run is one line. And when the markdown version earns its keep, level it up: "turn this into a single self-contained interactive HTML file I can open by double-clicking." Once that shape clicks, you'll start spotting it in your own work — and that's when the hub stops being a reference and starts being muscle memory. The capstone use case chains the whole loop into a one-line Monday pipeline.

→ Tips & tricks for the prompts Or browse skills that automate the patterns