Skip to content
BiliMind
Roadmap

How to learn financial modeling

This path assumes you can read a set of accounts and use a spreadsheet. It takes you from a blank workbook to a three-statement model with scenarios, a debt schedule and a defensible valuation. The aim is a model you can explain in plain English, not a spreadsheet that only you can operate.

Hours

90-120 hours

Calendar

about 15 weeks at 6-8 hours a week

Stages

6

Start from

You need basic accounting literacy (how the three statements link) and spreadsheet competence: formulas, references, named cells, data tables. You do not need coding, statistics, or a finance degree.

Why the usual order fails

Most financial modeling courses start with Excel shortcuts and end with a discounted cash flow template. That order produces people who can operate a spreadsheet but cannot say why a revenue line grows at 6% rather than 4%, or what would make the model wrong. A model is an argument about a business: how it makes money, what drives its costs, and what assumptions would change the answer. The spreadsheet is the language that argument is written in. If you learn the mechanics first, you spend months getting fluent in a language without having anything to say.

This path starts with the argument. In week one you build a one-page driver-based revenue model for a single product business, using three or four assumptions you can defend. Most plans have you formatting a three-statement template in week one, which teaches you nothing about why the template is shaped that way. By week five you will have built a full three-statement model from scratch, and by week ten you will have taken it apart with scenario analysis and a debt schedule. The mechanics are introduced only when they serve a modeling decision.

The path, in the order it has to be walked.

Each stage assumes the one above it and nothing below it. The check at the foot of each is the point — you are meant to fail it, go back, and try again before moving on.

  1. Model logic and revenue build

    weeks 1-2

    Start with a single-product revenue model so the structure of the argument is visible. This is where you learn what a model is for and what good assumptions look like, before the complexity of three statements.

    • Inputs vs calculations vs outputs
    • Price-volume-mix revenue build
    • Unit economics and contribution margin
    • Time series with month and year granularity
    • Scenario switching with a single driver cell
    • Sensitivity tables on price and volume
    • Model design principles: separation, consistency, auditability

    You can now: Build a one-page revenue model for a single product and change the price assumption, then watch the sensitivity table update without breaking a single formula.

  2. Three-statement model

    weeks 3-5

    Extend the revenue build to a full income statement, balance sheet and cash flow statement. The point is the reconciliation: the model must balance every period, and you must know why when it does not.

    • Income statement build from revenue to net income
    • Working capital: receivables, payables, inventory days
    • Depreciation schedules: straight-line and opening/closing balance
    • Cash flow statement: direct and indirect methods
    • Balance sheet balancing and the plug
    • Circularity and interest expense iteration
    • Error checking with variance flags

    You can now: Build a three-statement model for a single business with monthly periods for two years, and make a change to any single assumption, then trace the effect through all three statements to a balanced balance sheet.

  3. Debt, tax and capital structure

    weeks 4-5

    Add a debt schedule and tax calculations. This is where the model starts to answer financing questions, not just operational ones. It sits after the three-statement build because you need a balanced base model first.

    • Interest expense calculation and average debt balance
    • Revolving credit facility and cash sweep
    • Term loan amortisation and prepayment
    • Deferred tax assets and liabilities
    • Net operating loss carryforwards
    • Capital structure ratios: debt-to-EBITDA, interest coverage

    You can now: Add a term loan to your three-statement model and show how the cash balance changes if the company prepays 20% of the principal in year two.

  4. Valuation and DCF

    weeks 6-8

    Turn the three-statement model into a valuation. The DCF is a natural output of the model logic, not a separate skill. It sits here because the model must be stable before it can support a valuation.

    • Free cash flow to firm and to equity
    • WACC: cost of equity, cost of debt, capital structure weights
    • Terminal value: perpetuity growth and exit multiple
    • Mid-year convention for discounting
    • Sensitivity tables on WACC and terminal growth
    • Football field valuation summary

    You can now: Take your three-statement model, calculate free cash flow to firm for five years, and produce a DCF valuation that changes when you alter the revenue growth assumption.

  5. Scenarios and stress testing

    weeks 9-10

    The model is only as good as its behavior under stress. This stage teaches you to build scenarios, run sensitivities, and identify the assumptions that actually move the output.

    • Base, upside and downside cases
    • Scenario manager and data tables
    • Tornado charts and sensitivity ranking
    • Breakeven analysis on revenue and cost
    • Monte Carlo simulation with a few key variables
    • Model risk and assumption documentation

    You can now: Run a three-case scenario analysis on your model and identify which two assumptions account for more than 60% of the change in valuation.

  6. Presentation and review

    week 15

    A model that cannot be explained is not finished. This stage is about presenting the model's logic, checking it for errors, and preparing it for someone else to use. It sits last because you can only present what you understand.

    • Model structure and navigation
    • Executive summary and key output pages
    • Formatting conventions and print setups
    • Error checking and third-party review
    • Documentation of assumptions and sources
    • Handoff and version control

    You can now: Hand your model to someone who has not seen it before, with no verbal explanation, and have them find the key assumptions and outputs within five minutes.

The hours are fixed. The calendar is yours.

The same path at three speeds, and what actually goes wrong at each.

3 hours a week

This pace takes about 30-40 weeks to finish. What breaks is the continuity: by week 20, the model you built in week 3 feels like someone else's work. You will spend more time re-learning than learning.

8 hours a week

This is the pace for working competence in 15 weeks. It assumes two or three sessions a week, each long enough to finish a build step. What breaks if you skip a week is the model itself; the build is cumulative, and a broken build compounds.

20 hours a week

This pace finishes in 5-6 weeks. It is possible only if you already have accounting and spreadsheet fluency. What breaks is retention: the later stages assume the earlier model is still in your head, and at this pace it often is not.

What goes wrong

Four ways people lose a year on this.

Each of these is appealing for a real reason, which is why they are common. What they cost is the part nobody mentions.

  • Learning Excel functions before learning what a model says

    People spend weeks on INDEX-MATCH, XLOOKUP, and dynamic arrays before they have built a single revenue line. The functions are useful, but they are tools. What costs you is that you can now format and manipulate data but cannot explain why a business grows or what a model is arguing.

  • Building a three-statement model before a one-page revenue model

    The full three-statement build is a rite of passage, so people start there. It is appealing because it feels like the real thing. But it hides the logic: when the balance sheet does not balance, you cannot tell whether the problem is the revenue logic or the mechanics. You end up debugging formulas instead of understanding the business argument.

  • Using historical average growth as a forecast without a driver

    It is tempting to take the last three years of revenue growth, average it, and project that forward. It looks defensible in a spreadsheet. But the model then has no levers: you cannot ask what happens if a driver changes, because no driver is modelled. You have built a straight line, not an argument.

  • Not testing the model against a known company's actual results

    People build models in the abstract and never check them against a real company's published financials. The model feels complete because the formulas work. But a model that cannot reproduce a real company's actual results within a reasonable tolerance is not a model of that company; it is a template with numbers in it.

How to know it worked.

Not a syllabus you tick off — six things to attempt. If one of them is still hard, the stage it belongs to is the one to go back to.

  1. Build a one-page revenue model with three assumptions and explain each one.
  2. Reconcile a balance sheet that does not balance and find the error.
  3. Change one assumption and trace its effect through all three statements.
  4. Build a debt schedule with a cash sweep and explain the interest calculation.
  5. Calculate free cash flow to firm from your model and discount it to present value.
  6. Present a DCF valuation and answer which assumption most changes the result.
Questions

Questions about learning financial modeling.

The five we hear most. The intro film answers most of them in a minute and a half.

how long does it take to learn financial modeling

For working competence, 90-120 hours of deliberate practice, or about 15 weeks at 6-8 hours a week. That gets you to a three-statement model with a debt schedule and a DCF you can explain. Mastery, meaning you can model any business in any structure without a template, takes two to three years of regular use.

do I need to know accounting before financial modeling

You need to read a set of accounts, not prepare one. You must understand how the income statement, balance sheet and cash flow statement connect, and what items like depreciation, working capital and retained earnings mean. A full accounting course is overkill for modeling. If you can explain why a balance sheet balances, you know enough.

is financial modeling just excel

No. Excel is the tool, but the model is the argument. You can learn every function in Excel and still not be able to build a model that explains why a business will grow or fail. The hard part is the business logic and the assumptions, and the discipline to test them.

can i learn financial modeling on my own

Yes, but you need to build models, not watch videos. A course can show you a model, but until you have built one from a blank workbook and fixed it when it broke, you have not learned it. The best self-study approach is to pick a real public company, download its financials, and model it from scratch.

is financial modeling hard to learn

The spreadsheet mechanics are not the hard part. The hard part is holding the full logic of the business in your head while you build it, and then being honest about what the model does not know. Most people who fail do not fail at Excel; they fail at being able to explain why their assumptions are what they are.

A path is not a course.

This is the shape of financial modeling, not the teaching of it. Hand the same path to BiliMind and it writes the lessons onto it — in the form each one calls for, with practice that gets marked and a schedule that bends when your week does. Mapping a course is free and unlimited.

This roadmap was drafted on 18 September 2026 by the same engine that builds BiliMind courses, and reviewed before publishing. Hours are honest estimates for working competence, not for a demo — treat them as a starting point and adjust them against your own first fortnight.

The intro · 1:25