One platform, one object model

The chain that everything hangs from

Real estate software usually fails at the joints. The CRM knows a prospect but not the building. The management tool knows the lease but not the mandate that allows you to charge for it. The accounting export knows amounts but not which unit produced them. Every joint is a place where data is retyped and where numbers stop agreeing.

REOS starts from one chain: organisation, users and offices, then owners, properties and units, then mandates, contacts, leases and transactions, then documents, finance and operations. Everything else attaches to a link in that chain. A photo belongs to a unit. A commission belongs to a mandate. A ticket belongs to a unit and a vendor. Nothing floats.

Money is derived, not entered

The mandate is the contract that defines what the agency manages and what it charges. In REOS the mandate carries the commission model, so agency fees and net owner payout are computed from the signed terms and the actual rent collected.

That single decision removes most month end reconciliation. An owner statement is a query over leases, tickets and mandate terms, which is why it can be produced in seconds and defended line by line.

Country rules as configuration

A Belgian lease indexes on the health index at the anniversary date. A French lease uses the IRL and may sit in a tension zone. A Dutch unit has a points valuation that caps the rent. A United Kingdom tenancy requires client money separation and deposit scheme references.

None of these belong in code branches. In REOS they are configuration carried by the market and the unit, which is what allows one group to operate in six countries without six versions of the software.

Permissions that match how agencies work

• Organisation, office and team scopes, so a branch manager sees their branch and the group sees everything.
• Roles for administrators, managers, agents, accountants and technicians with different write rights.
• Owner and tenant portals as separate, narrower scopes on the same data.
• Vendor access limited to the tickets assigned to them.
• Append only audit logs on every sensitive change.

Open by default

A platform that becomes operational infrastructure has to be open. REOS exposes a REST API, webhooks for events such as a signed mandate or a published statement, scheduled exports and a read only connector for business intelligence tools.

Accounting stays where it is. REOS is the property side of the ledger and feeds the accounting package the group already uses rather than trying to replace it on day one.

European hosting and data protection

Data is hosted in the European Union, with storage attached to your organisation and access governed by the same permissions as the records themselves. Customer data is never used to train models.