For Build-to-Rent operators
The AI-native operating platform for Build-to-Rent.
ARK360 gives Build-to-Rent leasing, community and operations teams governed AI teammates that carry the coordination load across the systems they already run. A human is always in command.
A complete reference platform, now selecting its first operators.
Your data. Your systems. Your authority. Human in command.
The operational problem
Where a Build-to-Rent operating day loses time.
Great buildings do not fail. The follow-through does. Five places the day goes, none of which is a missing system.
- Enquiries sit
- An enquiry arrives while the building is busy, and the reply that converts it happens tomorrow, or not at all.
- Viewings end nowhere
- The viewing happens. The next action is somebody's memory of it.
- The manager is chasing
- Community managers spend more of the week chasing work than with the residents the role exists for.
- Maintenance is scattered
- Coordination lives across inboxes, texts and supplier calls, and the state of a job is whoever last spoke to the trade.
- The report is rebuilt
- The weekly operating report assembles numbers by hand that already exist in three systems.
The problem is not a lack of systems. It is a lack of time and visibility to coordinate the work between them.
The answer
Put an intelligent teammate inside the role.
Not a bot beside your stack. A layer between the systems you already own, working inside one person's role, under authority you set.
Role
One person whose time disappears into coordination, preparation and follow-up.
Verifiable workflow
The work written down so its output can be checked. Verification precedes delegation.
Bounded agent authority
What the agent may do, what it must hand back, what it may never touch. Role-scoped, in writing, before any code.
Human judgement
The decision returns to the person at the point where judgement is the work.
Auditable outcome
What acted, under whose authority, with what result. A record, not a recollection.
ARK360 does not replace your property-management platform or your access-control system. It reads context from the systems you already own, prepares the next action, coordinates approved work across them, and writes back outcomes your team authorises.
Every capability is role-scoped, bounded and auditable. Nothing reaches a resident, a supplier or a prospect without a person releasing it.
First roles
The four roles a pilot can start with.
Start where the week disappears. These are roles a Build-to-Rent operator already staffs, and a pilot begins with one of them.
Leasing
From first enquiry to viewing, follow-up and the next action.
- Every enquiry has a next action
- Follow-up happens on the day it should
- The pipeline moves while the team owns the conversation
Your team approves what ARK360 sends.
Community
Resident requests, building updates, amenity coordination and the work that protects the resident relationship.
- Requests are acknowledged and routed, not queued
- Exceptions surface before they become complaints
- The community manager spends the week on residents
Nothing reaches a resident without a person releasing it.
Operations
Maintenance coordination, supplier follow-up, exceptions and the handoffs between them.
- Chasing happens without a person doing the chasing
- Jobs that stall are raised, not discovered
- The trail of who did what is written as it goes
Work orders and supplier messages are drafted for approval.
Asset management
Weekly operating briefs, portfolio exceptions and board-ready reporting.
- The brief is assembled from evidence, not rebuilt by hand
- Exceptions arrive with their context attached
- The numbers trace back to the system that holds them
You read a draft, not a published claim.
The platform
See the platform running.
It exists, and you can look at it. These are screens from the running build, not mockups, and the data in them is a demo dataset.
Governance
Autonomy earns its way in.
A workflow moves up a ladder, and only when its verification arrives. This is a progression, never a promise.
- Level 01Assist
The agent prepares and suggests. The person does the work, and every suggestion is checkable against it.
- Level 02Agent in the loop
The agent carries the task. The person approves what matters before anything leaves the room.
- Level 03Artefact deleted
The intermediate artefact goes. The agent works from the system of record, and the record writes itself.
- Level 04Domain autonomous
Inside one bounded domain, the agent acts under its delegated authority, with the hand-back conditions written first.
- Level 05The captain
The person commands a set of agents across domains. Judgement stays human; the grind does not.
Founding Pilot Programme
Shape the operating platform for the next generation of BTR.
A small number of Australian operators taking the first workflows into live operations, with direct access to the person building it.
01
Select the role
One operational role with a measurable coordination burden. Not a department and not a process: a person whose week is being spent on the wrong things.
02
Configure the workflow
One governed workflow around the team and the systems already in place. What the agent may do, what it must hand back, and what it may never touch, written before any of it runs.
03
Set the boundaries
Data, authority, audit and approval boundaries established and agreed before deployment. Identity through your directory, residency stated, every action recorded.
04
Prove it live
The workflow runs in live operations with a person in command. Then you decide what expands, what changes, and whether anything should.
Who builds it
Who builds ARK360.
ARK360 is built by James Park, with around twenty years of enterprise delivery across property, construction and federal government: product engineering, architecture, integration, governance and operational systems. That work was delivered as employed or contract work, including at Mirvac, ADCO and ANSTO, and none of it is ARK360 client work.
Choose the role. Prove the workflow. Build the capability.
If your Build-to-Rent team carries more coordination than judgement, ARK360 may be worth a conversation. Apply to be considered for the Founding Pilot Programme.
Apply for the Founding Pilot Programme