Disciplined from the start.
Every InstitutionalModels™ engagement is built on the same framework standard in institutional finance — separating data from logic, and logic from outputs — so that assumptions are transparent, calculations are auditable, and results hold up under scrutiny.
We listen first. From there we develop a clear vision of what the model needs to do, then execute against it — building something that is simple to navigate, universally understood, and built to be handed to anyone in the room.
The same framework applies to every engagement — a single asset or an entire portfolio. Simple, scalable, auditable.
The three layers.
Data — The foundation of every model. Inputs capture the full range of assumptions driving the analysis — timing, operating parameters, capital structure, fees, exit assumptions, and scenario toggles. Complex engagements may require additional input tabs to house deal-specific detail. Third-party data — T12s, historical financials, ARGUS exports — are always imported separately, keeping source data distinct from assumptions so that both can be audited independently.
Calculations — All logic lives here. Debt sizing, waterfall distributions, and other supporting schedules are calculated on dedicated tabs, but everything converges in the cash flow — the core engine of the model. The cash flow tab is built to be read, not just run. Inline formulas, no hidden dependencies, no cross-sheet tracing. Anyone reviewing the model can follow the logic directly on the page.
Outputs — The outputs layer sits on top of the model — drawing from it, never feeding back into it. Because outputs are fully separate from the underlying calculations, they can be designed with complete flexibility. A single-page executive summary, a multi-tab portfolio dashboard, a lender package, a board report. The presentation is fully customized for the decision maker.
Supporting components
Validation — A model used across multiple deals, users, and time periods will be tested in ways its original design never anticipated. Validation ensures it holds up — catching errors early, confirming that data has moved through the model correctly, and flagging anything that falls outside expected parameters. The result is a model the entire team can rely on.
Documentation — Documentation is built into the development process from the start — not added at the end. It captures not just how the model works, but why — the vision behind the architecture, the reasoning behind key assumptions, the logic connecting every layer. Thinking about how each decision will be explained forces clarity in the design itself.
