Property portfolio
Elena · Product specialist · 34 s
A working day with Portfolio · illustrative scenario
You do your work.
The context stays with you.
Combine rental income, maintenance costs and vacancy data from different files. Explore how the intended workflow keeps the work together. This is an explanatory scenario, not a functioning customer environment.
01Select the propertyAccording to configured rules
YOUR ACTION
You select the property you want to assess.
THE SOFTWARE HELPS
Income, costs and available rental context are reviewed together.
WHAT THIS DELIVERS
One comparable starting point.
02Review the causeAccording to configured rules
YOUR ACTION
You open a notable cost item.
THE SOFTWARE HELPS
The source remains linked to the property or intervention.
WHAT THIS DELIVERS
From amount to explanation.
03Explore a scenarioAccording to configured rules
YOUR ACTION
You enter your own assumptions.
THE SOFTWARE HELPS
The formula calculates using that input, not a forecast.
WHAT THIS DELIVERS
A transparent basis for your own decision.
04Finish with a clear resultYour review
YOUR ACTION
You review the recorded data and decide what is complete and what still requires follow-up.
THE SOFTWARE HELPS
The decision refers to the same source, task or file context; there is no silent copy to another workspace.
WHAT THIS DELIVERS
A clear status and a traceable next step.
Less spreadsheet work and faster insight into which properties need attention.
Automation remains dependent on configuration and available features. No real message, document or instruction is processed here.
Meet Elena
Property portfolio
An overview of your property portfolio, with access to every building.
Explore a practical example
Elena
Property portfolio
Product specialist
Calls and live chat are not available yet. Contact us for more information.
Contact usWatch the practical example
Finance
Elena · Product specialist · 36 s
Pilot direction: start with one workspace and expand later.
ObraPad is designed to keep Obra Core as the shared foundation while you add capabilities over time.
Building-specific activation and restricted installer access are being prepared for the pilot and verified end to end. Ask which scopes can currently be tested.
Intended starting point
The pilot direction is to begin with one workspace and add more later.
Planned per-building expansion
The planned flow activates Construction only for the building being renovated; other buildings stay unchanged.
Planned access model
The access model is being developed so an installer or partner can use only the selected building, installation or task.
Intended example: heat pump maintenance
In the intended scenario, the installer only accesses the heat pump, its documents and assigned maintenance tasks in one building. Other buildings, financial information and private documents remain outside the scope. View, change, duration and revocation controls must be proven server-side before availability.
The design keeps an additional workspace and partner access as separate choices, with the building passport as the shared foundation.
