Home
Back to Blog
GUIDEBasic

From Spreadsheet Grunt to Analyst: A 90-Day AI-Assisted Finance Curriculum

A 13-week plan for learning financial modeling with Claude Code as a tutor, not a shortcut: Excel and data hygiene, three-statement models, DCF, comps, LBO and audit, with a build-it-yourself, shadow-build, diff method and a tested tie-out check.

November 19, 202613 min readClaude Code Playbooks
learn financial modeling fastfinance analyst roadmapfinancial modeling curriculumlearn finance with aifinancial modeling for beginners90 day finance planclaude code finance

This post contains affiliate links. If you sign up through one, we may earn a commission at no extra cost to you. How we handle this.

Ninety days is enough to go from "I can use Excel" to "I can build and defend a three-statement model, a DCF, a comps table and a simple LBO." It is not enough if you let an AI do the building. The skill you are buying is the ability to look at a model and know whether it is right, and you only get that by building models yourself and being wrong a few times.

So this curriculum uses Claude Code for what it is good at in a learning context: explaining, quizzing, checking and showing you a second version to compare against. The plan runs 13 weeks at roughly 8 to 10 hours a week, which gives you 100 to 130 hours. That lines up with what CFI says its FMVA certification takes (100 to 120 hours, self-paced), so you can run this alongside a structured course or on its own.

The Method: Build, Shadow, Diff

Every phase below uses the same three steps:

  1. Build it yourself. From a blank workbook, with the course material or the filings open. It will be slow and it will have errors. That is the point.
  2. Shadow-build with Claude. Give Claude the same inputs and the relevant playbook, and let it build its own version. You don't look at it until yours is finished.
  3. Diff the two. Every difference is either your mistake, Claude's mistake or a legitimate choice. Classify each one. This step is where most of the learning happens.

Set Claude up as a tutor with a rule that protects you from yourself:

You are my finance tutor. When I ask a modeling question, ask me what I think first and don't give the answer until I commit to a number or a formula. When I finish a model, find errors by asking me questions that lead me to them, not by fixing them. Give me the correction only after I have tried twice.

New Claude workflows for finance professionals, every week

One email a week with the newest playbooks. Free, like everything here.

No spam. Unsubscribe anytime.

The 13-Week Plan

WeeksFocusPlaybook for the shadow buildDeliverable
1 to 2Excel habits and clean dataSpreadsheet Data CleanerA messy export cleaned with no hardcodes and a change log
3 to 5Accounting and the 3-statement model3-Statement Model BuilderA balancing model of one public company
6 to 7DCFDCF Model BuilderA DCF with a sensitivity table you can explain
8Trading compsFinancial Modeling AssistantA comps table with a clean EV bridge
9 to 10LBOLBO Model BuilderA single-tranche LBO that ties to a paper check
11 to 12Audit and communicateModel AuditorAn audit of your own work and a two-page memo
13Package and reviewFinancial Analyst ToolkitA portfolio folder and a self-review

Use the same company all the way through. By week 10 you will have its history, its forecast, a valuation and a buyout case in one place, and the models will feed each other.

Weeks 1 to 2: Excel habits and clean data

Most analysts' first real job is cleaning and tying out other people's numbers. Pull a messy trial balance or a bank export and clean it: consistent dates, no merged cells, numbers stored as numbers. Learn lookups, SUMIFS, named ranges and the rule that assumptions live in one place and formulas never contain a typed number. Then give the same file to Claude with the Data Cleaner playbook and diff the change logs.

Weeks 3 to 5: Accounting and the three-statement model

Take a public company's last three years of statements from its 10-K and build the income statement, balance sheet and cash flow statement, then a five-year projection. The three statements must tie, and ties are easy to check with code. Here is a small checker you can run against your model's outputs. It tests that the balance sheet balances, that ending cash on the cash flow statement equals cash on the balance sheet, and that retained earnings roll forward correctly:

def check_three_statements(years, tol=0.01):
    """years: list of dicts with keys
       assets, liabilities, equity, cash_bs, cash_cf_end,
       net_income, dividends, retained_earnings.
    Returns a list of (year_index, problem). Empty means every check passed."""
    problems = []
    for i, y in enumerate(years):
        if abs(y["assets"] - (y["liabilities"] + y["equity"])) > tol:
            problems.append((i, "balance sheet does not balance"))
        if abs(y["cash_bs"] - y["cash_cf_end"]) > tol:
            problems.append((i, "cash flow ending cash != balance sheet cash"))
        if i > 0:
            prev = years[i - 1]["retained_earnings"]
            expected = prev + y["net_income"] - y["dividends"]
            if abs(y["retained_earnings"] - expected) > tol:
                problems.append((i, "retained earnings roll-forward is off"))
    return problems

On a consistent two-year sample it returns an empty list. When we break the second year on purpose (assets off by 10, ending cash off by 5, retained earnings off by 10), it reports all three problems. Use the same discipline in Excel: a check row at the bottom of every statement that must equal zero. Then have Claude build its own version and compare the two, line by line.

Weeks 6 to 7: DCF

Discount your own free cash flow forecast. The failure to avoid is a valuation that looks precise and rests on two numbers, the discount rate and the terminal growth rate. Build the sensitivity table by hand, then ask yourself what each cell is telling you. For a code-first version that pulls statements from an API, see our DCF walkthrough, which also explains why reported free cash flow has to be adjusted before you discount it at WACC.

Week 8: Trading comps

Choose peers for your company, build the enterprise value bridge for each, and compute LTM multiples. The hard part isn't the arithmetic. It is consistent definitions and a defensible peer set, both of which we cover in how to run comps with AI and where the data comes from.

Weeks 9 to 10: LBO

Build the five-part skeleton (sources and uses, operating case, debt schedule, exit, returns) and check it against a paper LBO. Our LBO walkthrough has a tested engine you can compare yours against, and a returns attribution that shows where the money came from.

Weeks 11 to 12: Audit and communicate

Audit your own models with the Model Auditor, then fix what it finds. Then write a two-page memo on the company: the business, the valuation range and the three assumptions that matter most. A model nobody can read is half finished, and writing the memo is how you learn whether you understand your own numbers.

Week 13: Package it

Put the models, the memo and your audit notes in one folder with a short README that says what each file does and what you would do next. That folder is your evidence. It's worth more in an interview than a list of courses.

Where Paid Courses Fit

You can run this entirely on free material: company filings, the playbooks and Claude as a tutor. A paid course helps if you want a curated sequence, exams and a certificate. Corporate Finance Institute is organized the way this plan is, with accounting, three-statement, DCF and valuation courses leading into a certification; we explain who should and shouldn't pay for it in Is the CFI All-Access bundle worth it? If you also want Python or SQL alongside the modeling, DataCamp lists a Finance Fundamentals track built with CFI and a Finance Fundamentals in Python track, each with six courses, and has a free tier that gives you the first chapter of each course. Both are optional, and neither replaces the build-it-yourself step.

Tripwires: Signs You Are Outsourcing the Learning

  • You can't explain why a number in Claude's model is what it is without asking Claude.
  • Your model and Claude's always agree, because you copied its structure early.
  • You skip the by-hand step because "it would take too long." That is the step that makes it faster later.
  • You can't rebuild a simple version from a blank sheet on a bad day.

If two of those are true, go back a week and do that week's build without the assistant. The plan is meant to be slightly uncomfortable. If you want to see why that matters for your career, read AI won't replace the analyst; it will replace the spreadsheet grind.

This article is for education and isn't career or investment advice. Course details are from CFI's and DataCamp's own pages as of November 2026 and change, so confirm them before you enroll. Time estimates are guides, not guarantees.