Property

Every property business keeps a register at its centre. For an agent it is instructions and applicants; for a developer it is plots and registered buyers; for a serviced apartment operator it is units and stays; for a student housing operator it is rooms and tenancies; for a managing agent it is blocks, units and leaseholders. The register carries a status lifecycle that the whole business reads from: available, under offer, reserved, let agreed, exchanged, completed, occupied, vacant. Most operational failure in the sector comes from the register being split across a CRM, a spreadsheet, a website and a feed to somebody else's portal, so that the same property is in three states at once and the person on the phone cannot say which is true.

The second shared fact is that the sector works through enquiries and appointments at volume. Buyers, tenants, students and guests arrive from portals, listing channels, the website and the street, and each wants a viewing, an appointment at the sales suite, a check-in or an arrivals slot. Capturing every enquiry once, routing it to the person who owns the property, booking against real availability and recording what happened afterwards, whether that is viewing feedback, a verification result or an inventory signed on a tablet, is the capability every topic here needs in some form.

Third, property moves money and documents on schedules: offers and reservations, deposits held and released, instalments aligned to term dates, service-charge demands apportioned across leaseholders, owner statements at month end. The systems we build record these amounts, dates and documents and remind the right person when something is due. They do not claim to make a business compliant with tenancy, deposit protection, leasehold or letting rules; those decisions stay with the business and its advisers, and the system gives them an accurate record to decide from.

Finally, the sector lives on integrations it does not control. Property listing portals accept feeds in their own formats and on their own terms, channel managers keep calendars in step, signature services return signed agreements, smart locks issue codes, accounting systems hold the ledger of record. Each is treated as a named integration point in scope, configured and tested one at a time, with a log that shows what was sent and what came back, because the business needs to see the state of a feed rather than trust it. Each topic in the sector then adds its own shape: the agent's portal feeds and viewing feedback, the developer's interactive site plan and phase launches, the operator's verification queue and turnaround tasks, the student operator's allocation board and arrivals slots, and the managing agent's apportioned demands and certificate expiry register.