Your team manages production models in Excel or Sheets. You want version control, auditability, and faster iteration cycles — without rebuilding everything from scratch.
Financial models,
as code.
A free, login-gated course for FP&A analysts and finance operators. 14 lessons teaching you to build version-controlled financial models with an AI agent — starting with a field card and a free lesson, no paid tier required.
Syllabus at a glance
14 lessons across four phases — from diagnosing spreadsheet failure to delivering board-ready outputs with full lineage.
14-module curriculum
Why spreadsheet models fail and what it costs the business.
Treating financial models as software: inputs, logic, outputs, and dependencies.
The four agent loops: build, explain, refactor, and review.
Four-layer model architecture: data, assumptions, logic, and reporting.
Translating Excel formulas into recognizable Python patterns.
Data vs drivers vs derived values -- and how to source defensible rationale.
Customer roll-forward, ARR, expansion, and net new revenue modeling.
Headcount, COGS, sales capacity, and CAC payback.
P&L to cash flow to balance sheet -- the connected three-statement model.
Seven tests every financial model should pass before it goes to the board.
Commits, branches, pull requests, tags, and rollbacks for finance.
Classifying, diffing, and approving forecast changes as a team.
Base, bull, bear, sensitivity sweep, and variance bridge.
Run IDs, board packs, metric lineage, and driver rationale.
From opaque cell references to named dependency graphs
The same model logic — expressed two ways. On the left: Excel cell references that require tracing every formula to understand a number. On the right: named nodes where every dependency is explicit and every output is traceable.
Six things you can do when you finish
- Build a version-controlled financial model that any team member can run and reproduce from a single command.
- Direct an AI agent to write, refactor, and review model logic — without writing Python from scratch.
- Separate data, assumptions, logic, and reporting so every board-pack number traces back to a defensible source.
- Write a test suite that catches the seven most common financial modeling errors before the forecast goes to review.
- Run base, bull, and bear scenario branches with git — no duplicated workbooks or manual reconciliation.
- Present board-ready outputs with a run ID and full driver lineage, auditable on demand.
Built for finance professionals, not software engineers
You sign off on the numbers. You want every board-ready output to trace back to a defensible rationale, with a full audit history no spreadsheet can provide.
You build revenue, cost, and scenario models to support decisions. You want reproducible runs, clean review workflows, and a board pack that explains itself.
What you get with every lesson
Self-paced written lessons covering the full arc from spreadsheet diagnosis to reproducible reporting.
One field card per lesson: key concepts, the core diagram, and the prompts you need to apply the lesson in Bridge Town.
The four essential prompts of financial model engineering and a cheat sheet of 20 reusable modeling patterns.
Reusable driver-layer, revenue engine, cost engine, three-statement model, and scenario template packs.
PR review checklists and sample pull requests for classifying and approving forecast changes.
Written and maintained by the Bridge Town team at Knightian Labs. Built for the practitioners who live in forecasts — not for software engineers.
Common questions
Start lesson 01 — free
Login with your Bridge Town account to unlock all 14 lessons, field cards, starter packs, and review checklists. No paid tier, no time limit.
Start lesson 01 — free →