Excel is not the competition anyone likes to name, and it is the tool almost every deal is still priced in. It deserves a fair comparison rather than a strawman: a good analyst with a good template is fast, flexible and completely in control of their own assumptions.
What a spreadsheet cannot do is read the documents. Every figure in that model arrived because someone typed it, and that is where both the hours and the errors live.
Worth stating plainly, because a comparison that pretends otherwise is not useful:
Any tool that cannot beat those on the things that matter is not worth switching to.
The data entry, which is most of the work. Pulling a rent roll into a unit mix, coding a T-12 into standard heads, keying comparables — this is the bulk of the hours in a first pass, and none of it is analysis. It is the part a spreadsheet cannot help with, because the spreadsheet's inputs start after it.
Provenance. A cell contains 1,750. Which lease, which page, which amendment? A spreadsheet cannot answer that, so verification means going back to the source documents by hand — which is exactly why, under time pressure, it usually doesn't happen.
Version control. Model_v7_FINAL_revised_JT.xlsx is a joke because it is universal. When two people have opinions about the exit cap, there are two files, and the question of which is current has no technical answer.
Consistency across deals. Two analysts using the same template will still code operating expenses differently, take vacancy on different bases, and define gross potential rent differently. That makes deals incomparable in a portfolio view, and the differences are invisible because both models are internally consistent.
The silent arithmetic errors. The loss-to-lease and vacancy interaction is the clearest example: charge vacancy on gross potential rent rather than on scheduled rent and you deduct the same below-market gap twice. The model still balances, still ties, still looks right. On a 100-unit property with an 8% loss to lease it quietly writes off roughly $196,000 of value at a 5.5% cap.
| Underwriting in Excel | Crevanta | |
|---|---|---|
| Getting data in | Manual entry from PDFs and exports | Extracted from the rent roll and operating statements |
| Where a figure came from | Not recorded | Every cell traceable to its source document |
| Chart of accounts | Per template, per analyst | One coding applied across every statement |
| Reconciliation to stated NOI | Manual, if done | Tied out as part of the spread |
| Version of record | Whichever file you opened | One model per property |
| Comparing deals | Only if the templates match | Same definitions by construction |
| Structural flexibility | Unlimited | Bounded by what the engine models |
| Sharing with a counterparty | Universal | Export required |
| Assumption control | Complete | Editable per line and per year |
The three rows where Excel wins are real and are not going away. The honest framing is not replacement but division of labour: the document reading, coding and reconciliation are mechanical and should be automated; the judgement about what the deal is worth stays with the analyst.
The model still needs an underwriter. What changes is where the hours go: less time assembling the inputs, more time on the assumptions that decide the answer. And the outputs become comparable across deals, because the definitions are the same by construction rather than by everyone remembering to use the same template.
The realistic posture is that Excel remains in the workflow — for the odd structure, for the export a lender wants, for the scratch analysis. What it stops being is the place the underlying data is keyed in by hand.
See How Crevanta Compares
Every CRE portfolio is different. Request a personalized demo and see exactly how Crevanta handles your document types, property classes, and workflow.