Built for
For acquisition teams with established Excel templates, model-cell conventions, scenario logic, and approval workflows that cannot be reduced to a one-size-fits-all web form.
Populate an Excel underwriting model
Populate your existing Excel underwriting model from the deal package
Your workbook contains years of firm-specific judgment. Rook maps deal evidence into that model instead of asking the team to abandon it for a generic calculator.
The outcome
Receive a populated first pass in the workbook the team already knows, with sourced historical inputs, labeled assumptions, and exceptions ready for analyst review.
How it works
From source package to reviewable work
- 01
Understand the workbook
Identify the sheets, input cells, units, periods, signs, formulas, and scenario controls that define the firm’s underwriting process.
- 02
Read the deal package
Extract relevant facts from the OM, rent roll, T12, and supporting files while preserving their provenance.
- 03
Map evidence to inputs
Place reviewed facts and clearly labeled forward assumptions into the model locations that expect them.
- 04
Validate the completed first pass
Surface unmapped requirements, conflicts, formula issues, and high-impact assumptions before the workbook advances.
What the team gets
Fast enough to use. Clear enough to review.
Template-specific mapping
Respect the firm’s sheet names, named ranges, input conventions, and calculation architecture.
Historical fact preservation
Keep value, unit, sign, period, and source aligned when moving a document fact into a workbook cell.
Assumption provenance
Explain why a future input was proposed and distinguish it from observed historical performance.
Review-oriented output
Focus attention on unresolved inputs and consequential judgments rather than forcing a reviewer to inspect every populated cell equally.
Why the details matter
The model is the firm’s decision language
An underwriting workbook is more than a set of formulas. It encodes how a firm defines revenue, recasts expenses, sizes debt, runs sensitivities, and presents risk. Replacing it can erase the decision process the team is trying to accelerate.
Rook treats model population as a mapping and evidence problem. Source values retain context, forward estimates carry reasoning, and missing historical facts remain missing rather than being disguised as forecasts.
That approach preserves control while reducing transcription. Analysts review what entered the model and why, then spend their time on the business plan, market evidence, financing, and downside cases.
Frequently asked questions
Questions acquisition teams ask
Can AI populate our existing Excel underwriting model?
Yes. Rook is designed to map deal facts and labeled assumptions into an existing firm-specific workbook rather than requiring a replacement model.
Will Rook overwrite our formulas?
The implementation identifies intended input locations and preserves the workbook’s calculation logic. The completed file should still be reviewed and recalculated in the firm’s supported spreadsheet environment.
How are missing inputs handled?
Missing historical facts remain visible. Where a required forward input needs a defensible estimate, it can be proposed with reasoning and labeled as an assumption instead of being presented as sourced history.
Can reviewers see where a workbook value came from?
The workflow is designed to retain source and reasoning context so a reviewer can distinguish document-backed values, firm assumptions, and unresolved questions.
Keep exploring
Related acquisition workflows
Bring a deal and the model you use today.
See how Rook handles the source package, the unresolved questions, and the workbook your team already reviews.