Real Estate
Systems integration, software and technical advisory for Australian real estate agencies, connecting sales, property management, trust, listings and portals so the same person is not lost between them.
For principals and licensees in charge, sales managers, property operations leads, trust accountants and whoever looks after systems across more than one office.
Where the work usually breaks
One person, four records
The same person is a vendor, a landlord, a buyer and later a tenant in different systems.
Three contacts from one enquiry
A portal enquiry, a website form and an open-home check-in each create a separate contact.
Approved applicants are re-keyed
An approved applicant is typed in again to the property-management system.
Tenants wait for repairs
Maintenance requests sit without a visible status, so tenants and owners keep asking for updates.
The handover between sales and management leaks
Sales cannot see management history, and management cannot see the original campaign.
A CRM change breaks live listings
Changing CRM without preserving the listing identity used on realestate.com.au breaks or duplicates live listings.
What we do
Join sales and property management
A single person identity across the sales CRM and the property-management system, with duplicates caught on the way in.
Connect listings and portals
Listing feeds and lead flow between the CRM, the website, realestate.com.au and Domain, with listing identity kept through a CRM change.
Build owner, landlord and applicant portals
Web applications that write back to the systems of record and show lettings and maintenance status to owners and staff.
Limit what applications collect
Application forms and workflows that collect what the tenancy decision needs and no more.
Advise on replacing or wrapping
An independent view on replacing a CRM or property-management system versus building around it.
What you end up with
One identity for each person
A single record that follows someone from vendor to landlord to tenant across sales and management.
Listings that survive a system change
A plan for keeping listing identity intact when the CRM or the website changes.
Status that owners and staff can see
Lettings and maintenance status shown in one place instead of being chased by phone.
How a typical engagement works
01Discovery
Follow a person through the agency
We trace one person from enquiry to vendor to landlord to tenant, and list every system and form that holds a record of them.
02Design
Decide what each system owns
We settle which system owns the person, the listing and the tenancy, how duplicates are caught on the way in, and how listing identity survives a system change.
03Build and test
Build and test before anything goes live
Integrations and portals are built in stages and tested on realistic data in a separate environment before they touch live sales, listings or trust records.
04Handover
Train the office and hand over
Sales and property-management staff are shown the changed steps, and credentials, alerting and documentation are handed over so the agency can run the result.
05Support
Support as the stack changes
After handover, support can continue in the background as the CRM, the property-management system and the portals change.
Real Estate in detail
Two businesses, one licence
A sales team is trying to win appraisals, take listing authorities, run campaigns, respond to enquiry, reach exchange and keep the database useful. A property-management team is trying to grow and keep the rent roll, protect trust, let vacancies, collect rent, attend to maintenance, inspect, renew and report to owners.
Licensing often covers both. The day-to-day work, software, money and rules do not. Sales is transactional commission. Property management is recurring fees and a saleable rent roll. The handover between them is a known leak: sales cannot see management history, and management cannot see the original campaign. Tasmania issues separate licences. Lettings sits under property management. Conveyancers and PEXA sit next to a sale. They are not the agency platform.
This page is for principals and licensees in charge, sales managers, property operations leads, trust accountants and the person who looks after systems across more than one office.
How the environment is usually arranged
Australia does not have a multiple-listing service. Listings move from the sales CRM to the website to realestate.com.au and Domain, and leads come back the other way. Sales CRMs commonly include VaultRE, Agentbox, Rex, Eagle and Box+Dice. Property-management and trust platforms commonly include PropertyMe, Console Cloud and MRI Property Tree. Inspection and application tools, contract and e-sign products, and Xero for office books sit around those spines.
A mixed office often runs one sales CRM and a different property-management system. The website should pull listings, not become a second database. Changing CRM without preserving the listing identity used on realestate.com.au breaks or duplicates live listings. The agency is usually not the electronic-lodgement subscriber; the lawyer or conveyancer runs PEXA.
Where records multiply
- The same person is vendor, landlord, buyer and later tenant in different systems.
- A portal enquiry, a website form and an open-home check-in create three contacts.
- An approved applicant is re-keyed into the property-management system.
- Tenants hear nothing more often than they wait too long for a repair.
- Application forms collect more than the agency needs to decide the tenancy.
Speed still matters on the sales side. Accurate records and a complete trust trail matter every day on the management side. Neither is solved by buying one more product that "integrates" and still leaves a person in the middle.
AML sits on the sale
From 1 July 2026, brokering the sale or purchase of real estate is a designated service. For that work the customer is both buyer and seller. Ordinary residential leases of 30 years or less are excluded from "real estate" for that purpose. Property managers are not automatically reporting entities because they manage rent rolls. Enrolment, if the agency already brokers sales, is a fact about that brokering work.
Customer due diligence starts with the seller at the listing authority. Due diligence on the buyer is due when the transaction is reasonably expected to proceed. Delayed due diligence, where it applies to the counterparty, is bounded by the earlier of 28 days after exchange or at least three days before the agreed settlement. Verification products and portal identity checks do not by themselves complete that work. This is not AML or licensing advice.
Privacy obligations also tighten once an agency is a reporting entity for AML-related activity. The OAIC's April 2026 determination on IRE's 2Apply product is a reminder that application forms must not collect more than the agency needs.
Tenancy and trust are state-based
Licensing, trust audit dates, bonds, tenancy notices and contract formalities are not national. No-grounds endings are treated differently across states and territories. New South Wales statewide Smart Rental Bonds changed the bond authority's process; Fair Trading says the agent's lodgement process is unchanged. Do not take a New South Wales trust date, a Queensland licence-month audit or a Western Australian tenancy proposal and apply it everywhere.
If you need a jurisdiction-specific notice or audit trail, say which state the office operates in. The useful software question is whether the property-management system can produce the right notice and evidence for that office, not whether Australia has one tenancy workflow.
What is worth improving
Do not replace certified trust accounting. The useful work is the join: a single person identity across sales and management, listing-identity preservation when a CRM changes, dedupe at ingest, AML checks in the sales CRM, application data that is limited to what the decision needs, and visibility of lettings and maintenance status for owners and staff.
Integration, including API development and automation, is the usual starting point. Web applications fit landlord or applicant portals that write back to the systems of record. Technology advisory is CRM or property-management replacement versus wrap, and the conglomerate-stack decision. Hosting and infrastructure is access after staff leave and after a tenancy ends.
AI only fits bounded jobs such as drafting an inspection comment for a person to approve before it is sent. It is not authority for trust balances, arrears, due diligence or who gets the tenancy.
If the leak is between sales and management, or between the CRM and the portals, tell us about the work.
Frequently Asked Questions
Start with a conversation
Book a free 15 minute call. Describe the problem, the systems involved and what you already know, and we will tell you plainly whether we can help and what a sensible next step looks like. There is no obligation.