“It happened mid-workflow — they're building a 3-year P&L model for a new product line.. excel handled something they'd been doing manually, and it just worked. That was the moment it stopped being a tool they were evaluating and became one they relied on.”
When I'm building a 3-year p&l model for a new product line, I want to build models that are fast, accurate, and can be handed off without a tutorial, so I can refresh data from source systems without rebuilding anything.
A financial analyst at a corporation, investment firm, or consultancy for whom Excel is not software — it is the medium of thought. They spend 5–7 hours a day inside spreadsheets. They build models that other people are afraid to open. They have keyboard shortcuts memorized that the rest of the company doesn't know exist. They've rescued a broken model the night before a board presentation. They have opinions about Excel that they share without being asked.
To reach the point where build models that are fast, accurate, and can be handed off without a tutorial happens through excel as a matter of routine — not heroic effort. Their deeper aim: refresh data from source systems without rebuilding anything.
excel becomes invisible infrastructure. Build models that are fast, accurate, and can be handed off without a tutorial works without intervention. The old problem — workbooks that slow down because of volatile functions nobody removed — is a memory, not a daily fight. Faster co-authoring that doesn't corrupt structure lets collaboration happen without fear.
They're building a 3-year P&L model for a new product line. Finance has asked for three scenarios by Thursday. The revenue assumptions are linked to a marketing model a colleague built last quarter that has since been updated — but they're not sure how the update affected the numbers they're pulling. It's Tuesday. There is also a pivot table that has stopped refreshing and they're not sure why.
Works in Excel 6–7 hours per day. Uses Windows — Excel on Mac is a different, lesser product in their view. Has a personal library of templates they carry between jobs. Knows VBA well enough to be dangerous. Has started using Python for some data prep but returns to Excel for the actual model. Uses Excel with two monitors — the model on one, source data on the other. Has dark feelings about Google Sheets.
The proof is behavioral: build models that are fast, accurate, and can be handed off without a tutorial happens without reminders. They've customized excel beyond the defaults — templates, views, integrations — and their usage is deepening, not plateauing. When new team members join, they hand them their setup as the starting point.
It's not one thing — it's the accumulation. Workbooks that slow down because of volatile functions nobody removed that they've reported, worked around, and accepted. Then a competitor demo shows the same workflow without the friction, and the sunk cost argument collapses. Their worldview — a model is only as good as its assumptions — and those need to be visible, not buried — makes them unwilling to compromise once a better option is visible.
Pairs with `finance-manager` for the model review and presentation workflow. Contrast with `google-sheets-user` to map the power-user vs. collaboration tradeoff. Use with `data-engineer` for scenarios involving Excel-to-database migration.