Founding Pilot Programme
Shape the operating platform for the next generation of BTR.
ARK360 has been built as a complete, governed Build-to-Rent platform. A small number of Australian operators are being selected to take its first workflows into live operations.
A complete reference platform, now selecting its first operators.
Where this stands
Said plainly, before anything else.
ARK360 has no paying customers and no live operators. It is a complete reference platform: built end to end, deployable, and running against a demo dataset you can see screens of on this site.
That is the entire point of this programme. The first operators are not buying a proven product. They are deciding whether a governed operating layer earns its place in a real building, and shaping what it becomes if it does. If you would rather be the tenth operator than the first, this is not the right moment and that is a reasonable position.
The shape
Four steps, and a decision at the end of each.
A pilot is bounded work with a stated end, not an open engagement.
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.
Selection
Who this is for.
- You operate or are developing a Build-to-Rent portfolio in Australia.
- There is an accountable operational sponsor and an identified role owner.
- You are willing to shape the product, with direct access to the person building it.
- There is a credible path from pilot to production if the evidence supports it.
Applications that do not meet these are declined early rather than carried along. An operator without an accountable sponsor cannot give a pilot the authority it needs, and finding that out in month three helps nobody.
The exchange
What each side brings.
You bring
- One role, and the person who owns it.
- Access to the systems that role works in.
- An accountable sponsor who can set authority boundaries.
- Honest feedback about what does and does not help.
ARK360 brings
- The platform, configured around your role and your systems.
- The governance sheet, written before anything runs.
- Direct access to the person building it.
- An honest read on whether it is working, including when it is not.