Your property.
Every detail.
One place.

1. Identify: resolve the exact building, lot and property; assign a durable ID and prevent duplicates.
2. Instantiate: apply a versioned property template with rooms, asset categories, relationships and evidence states. Empty fields are expected.
3. Connect: authorise specific sources and record their scope, refresh frequency and usage rights.
4. Ingest: match each item to the property and asset, extract proposed facts, detect duplicates and surface conflicts.
5. Verify: retain the source, date and confidence; review uncertain or consequential changes.
6. Present: generate the appropriate private or public experience from permitted, current information.
7. Maintain: add events as life happens; monitor failed imports and stale facts; support export and handover.

A single maintained application serves many properties. Each property gets its own identity, data and experience, rather than a separate copy of the code.

Store more than a value: what it describes, its source, when it was true, when it was recorded, who can see it, and whether it is verified, reported, estimated, disputed or unknown.

For example: “Bath resurfaced” links to this bath, a dated work event, the contractor relationship, the invoice and the completion report. A later peeling report links to the same asset. The system can surface a recurrence without inventing a diagnosis.

Keep raw source files, structured records and a searchable index separate. AI retrieves authorised evidence to answer a question; a conversational answer never replaces the underlying record.

Design for the full lifecycle now. Build usable services in stages. Create shared identities, assets, evidence and permission boundaries first. A service that has been built can be available but inactive for a particular property.

“Not implemented”, “available”, “enabled” and “running” are different states. A subscription entitlement does not grant access to another person’s data. Turning marketing off should not stop authorised repairs from becoming part of the property’s history.

Charge for valuable workflows and services when they are ready. Keep record portability and data rights explicit rather than making a property’s history depend on its latest agent.

Each provider needs its own authorised connector, data mapping, rate-limit handling, sync cursor, duplicate protection and visible error state. Begin with read-only imports and a supported document/export path before any write-back.

• PropertyMe publishes API documentation ↗; actual account access and allowed data must be confirmed.
• MRI documents a Property Tree integration pathway ↗; this does not establish our own partner approval or coverage.
• Ailo access is an unresolved dependency. No connection or comprehensive export has been verified for this concept.

No connector is live in this website. The source systems retain their roles until an explicit migration is designed.

Use separate views for the public, buyers, current residents, owners, managers and contractors. Permissions must be enforced on the server and on every AI retrieval, not just by hiding a button.

Preserve eligible property evidence through a transfer. Revoke expired access. Redact or exclude personal, financial and security information. Shared maintenance threads can make action visible; unrelated private conversations do not become universally visible.

Provide corrections, source attribution, retention rules and an auditable transfer process. Review Australian privacy requirements during implementation using OAIC guidance ↗.

The owner is the primary customer and continuing authority for the property record. Agencies receive delegated management access; changing the agency should not erase the home’s eligible history.

An agency requests access with its managing agreement, or the owner initiates an invitation. Verify property identity, ownership and co-owner authority; let the owner review the agency, scope, dates and evidence. An uploaded agreement alone does not confer access.

At handover, revoke former access, grant the new agreed permission and preserve the same property and asset IDs in an audited transaction. Keep personal conversations, security details and unrelated financial records separately governed. A property sale requires a separate verified ownership transfer.

Connect the new agency’s management software only after permission is established, through supported integrations. The record stays useful even when a connector is unavailable.

Try the owner-controlled agency journey → · Review the authority fields →

Start with an owner-paid property-record subscription and optional agency collaboration. Explore portfolio tools for professional users and optional paid workflows such as sales packs, photography, floor plans and virtual styling. Pricing is deliberately undecided until the pilot proves value and operating costs.

Short-stay services, resident savings tools and mortgage comparisons are later opportunities. Financial comparisons need appropriate partner and regulatory design. AI imagery must disclose alterations and preserve a clear link to the actual property evidence.

The first commercial question is concrete: will users pay to recover trusted history, reduce repeated work and hand a better record to the next person?

The ambition has useful reference points. Learn from the category and develop a distinct Australian product around continuity, source-backed answers and day-to-day property operations.

Reference links are research inputs, not affiliations, endorsements or claims of unique market coverage.