Property platforms, built around money that was never yours.

Inventory: properties, units and leases

What you are actually modelling is rarely a property. It is a building containing units, each with a lease that has a term, a rent, occupants who are not always the signatories, and a history that outlives every one of them. A schema built around a listing will not express a lease renewal, a mid-term occupant change or a unit taken off market for works.

Commercial adds another layer entirely: floors subdivided per tenant, service charges apportioned by area, and rent reviews on a schedule. A residential model will not stretch to it, and pretending otherwise is the most common architectural mistake in this sector.

The output is an inventory model that separates the physical asset, the marketable unit and the contractual relationship, because those three change independently.

Listing ingestion, syndication and freshness

If you run a portal, your product is trust in the data, and the thing that destroys it is a listing that is no longer available. A user who arranges a viewing for a let property does not blame the agent, they blame you, and portals lose users to staleness faster than to any missing feature.

Ingestion arrives from agent systems, feeds and manual entry, in inconsistent quality, with the same property often appearing more than once through different sources. Deduplication is a real engineering problem: the same unit described two ways, with different photographs and a price that differs by a rounding.

Freshness needs enforcing rather than hoping. Listings that have not been confirmed within a defined window should be demoted or withdrawn, and that policy will be unpopular with supply, which is exactly why it has to be a system rule rather than a negotiation.

Leads, viewings and applications

The gap between interest and a signed lease is where most property platforms lose the transaction. An enquiry that waits four hours has usually already been answered by somebody else, which makes routing and response time a product concern rather than an agent's discipline.

Applications are the point where the platform starts collecting sensitive personal information, and where the data minimization question arrives. Collecting identity documents and financial history before an applicant is seriously in contention creates a liability with no corresponding benefit.

Viewing coordination is a scheduling problem with a physical constraint: keys, access and someone present. Treating it as a calendar invitation misses the operational reality.

Screening, leases and automated decisioning

Tenant screening is where a management platform earns its throughput. Automated scoring against your own criteria, instant checks against credit and reference providers, and straight-through approval for applicants who clear every threshold are all standard in what we build, and they remove most of the manual work from a letting pipeline.

We build the full range: automated accept, automated decline, and referral to a human where you want one. You set the thresholds, we make them configurable so your lettings team changes them without a release, and we record every decision with the criteria that produced it so a query months later has an answer.

The lease itself is a versioned document with parties, terms and amendments over time, plus an execution record. Storing a signed file loses the structure that rent, renewals and disputes all need.

Trust accounting, rent and owner payouts

This is the phase that separates property platforms from generic marketplaces. Rent collected on behalf of an owner and deposits held for tenants are client money, and in most jurisdictions must be held in designated accounts, never commingled with operating funds, and reconciled on a schedule that an auditor can inspect.

The ledger has to express that structurally rather than by convention. Each owner has a position, each tenant deposit is a liability with conditions attached, management fees move between the trust position and your revenue at defined moments, and a three-way reconciliation between bank, ledger and property records must balance.

Get this wrong and the consequence is not a bug report. It is a regulatory finding, and in several jurisdictions a personal liability for the principal.

Maintenance, works and evidence

Maintenance is where a management platform earns its fee and where disputes originate. A request has a reporter, a severity, a contractor, an approval limit, a cost that may be split between owner and tenant, and an outcome that somebody will question months later.

Evidence capture matters as much as workflow. Condition at move-in and move-out, photographs at each stage of works, and the approval that authorized a spend are what resolve a deposit dispute without argument. Reconstructing them afterwards is not possible.

Statutory obligations attach here too: safety inspections with certificates that expire, and works that legally must be completed within a window.

Launch and the first accounting cycle

Migration is the hard part of launch here, because existing platforms hold live leases, deposits and balances that must transfer without a discrepancy. A parallel run through at least one full rent cycle is the only honest way to prove it.

Day two is the first month-end: rent collected, fees taken, owners paid, statements produced and reconciled. That cycle is the real test. Sixty days of dedicated support, six months of priority bug resolution, twelve months of updates.