Modules
Fourteen modules, one database. Start with the core, add the operational layers when the data is ready.
How the modules fit together
The first four modules are the base that everything else needs: the portfolio, the owners, the contacts and the mandates. Without them, letting management is a spreadsheet with better colours.
The operational layers come next: lettings, maintenance, planning, the owner portal and portal syndication. Then the commercial and financial layers: transactions, finance and the executive dashboard. The AI layer sits on top and is only useful once the data underneath it is real.
Portfolio
One record per building, lot and unit, with everything attached to it.
Owners
The relationship that pays your fees, treated as a first class object.
CRM
Two pipelines, owner acquisition and demand, in the same database as the portfolio.
Mandates
The contract that defines what you manage, what you charge and until when.
Lettings
From listing to lease to indexation, without a spreadsheet in the middle.
Transactions
A sales pipeline that knows the property, the mandate and the commission.
Portal syndication
Publish once, update everywhere, through official portal APIs.
Documents
A document management system that knows what each file is for.
Finance
The property specific financial layer, not a replacement for your accountant.
Maintenance
From a tenant report to a paid invoice, with the owner able to follow.
Planning
One calendar for agents, technicians, vendors and units.
AI layer
Questions answered from your own portfolio, not a chatbot bolted on the side.
Owner portal
The retention tool your competitors do not have.
Executive dashboard
The numbers a managing director asks for, without asking anyone.
Ready to see it on your own portfolio
A demo runs on a structure that looks like yours: your unit count, your mandate model, your portals. Forty five minutes, no slide deck.