Ask a developer and an asset manager what they need from software and you get two different answers, and it is not just a matter of which screen they open first. A developer needs depth on one asset while it is being built. An asset manager needs the same handful of numbers computed consistently across every asset in the book, every quarter, without anyone rebuilding the roll-up by hand.
Depth on one asset: the developer's problem
During a build, the unit of work is the project, and the software has to hold DIN 276 cost groups down to KG 800, cost plan versions with approvals as scope changes, and a cash flow projection that gets more accurate as actuals replace estimates. Getting one project right, in depth, is the whole job.
Consistency across many assets: the asset manager's problem
Once a property is held rather than built, the question changes from "is this project on budget" to "how is the book performing." That means NOI, cap rate, IRR and DSCR have to aggregate the same way from every asset up to the fund and the portfolio, and recalculate when a lease changes or a quarter closes, rather than getting recomputed by hand from twenty separate asset files. Depth on one asset does not help here. Consistency across all of them does.
Where Excel breaks down differently for each role
A developer's spreadsheet usually breaks first on change orders: enough Nachträge on enough cost groups and the budget-versus-actual picture stops matching what actually happened on site. An asset manager's spreadsheet breaks on scale instead: it works fine at three properties and stops working at thirty, not because the formulas are wrong but because every new asset is another tab that has to be manually rolled into the fund-level number, every quarter, for as long as the portfolio exists. Stop rebuilding the portfolio book from scratch each close and the job changes from reproducing the numbers to actually reading them.
ESG reporting adds a second axis most developers never touch
Increasingly, portfolio-level reporting under the EU's sustainability disclosure framework needs the same thing NOI does: a consistent figure per asset that rolls up cleanly. Energy performance, emissions and other ESRS-aligned data points sitting on the asset record, rather than in a parallel ESG spreadsheet someone reconciles once a year, is what turns portfolio-level sustainability reporting from a special project into a normal part of the close.
Same property, two different jobs, one record
Because REPM keeps one property record across develop and manage, an asset that started as a development project carries its DIN 276 history forward into the portfolio book it eventually joins, instead of arriving as a fresh file with no memory of what it cost to build. The developer's depth and the asset manager's consistency read from the same numbers underneath, not two different systems reconciled by hand at handover.
See your own portfolio roll up. Start a free REPM Lite trial at app.repm.cloud and add a second asset to see the fund-level numbers move.
FAQ
What does asset management software need that development software doesn't?
Consistent aggregation across many assets rather than depth on one. NOI, cap rate, IRR and DSCR have to roll up from every asset to the fund and portfolio level the same way, and recompute automatically as a quarter closes, rather than being reassembled by hand from separate asset files each time.
Why does a spreadsheet work fine at first and then stop working for portfolio reporting?
It scales linearly with effort. Each new asset is another tab that has to be manually reconciled into the portfolio total, so the work of producing the roll-up grows with the portfolio even though the analysis itself does not get any harder.
What is ESRS and why does it matter for portfolio software?
ESRS is the European Sustainability Reporting Standards framework under the EU's corporate sustainability disclosure rules. It increasingly requires asset-level environmental data to roll up to portfolio and fund-level reporting, which is only manageable if that data sits on the asset record rather than in a separate annual reconciliation exercise.
Can a property be tracked as a development project and later as a portfolio asset in the same system?
Yes. On REPM the property is one record across its lifecycle, so the DIN 276 cost history from the build carries forward once the asset moves into ongoing portfolio reporting, rather than starting over in a separate system.