Skip to content
ARK360

Product area

Leasing

Tenancy records and the rent that runs off them. This is the thinnest of the five areas, and the roadmap below is longer than the shipped list for that reason.

From the running build

The screens.

Captures of the build as it stands. The data in them is a demo dataset, not an operator's.

Leasing and tenancies

Tenancies, terms, rent and status for a site, with the leasing pipeline attached to the units it belongs to.

The leasing screen listing tenancies by unit, with resident, rent, term and status, and a manage action on each row.
Leasing and tenancies, from the running build. Demo dataset.

Rent and arrears

Collection across the site, with arrears surfaced as a count and a total rather than found by reading a ledger.

The payments screen showing five residents in arrears against an outstanding total, with succeeded, pending and failed rows.
Rent and arrears, from the running build. Demo dataset.

Status

What is built in Leasing, and what is not.

Three states, from the same capability map the platform is governed by. The middle one is the one worth reading.

Shipped

Built, and working in the running build.

  • Tenancy records carrying rent amount, cadence and status
  • Unit-to-tenancy linkage
  • Operator-side payment recording, marking paid, refunds and arrears
  • A card-present-never payment model: no cardholder data is stored, only provider references, with exactly-once transition-safe webhooks and atomic refunds

Roadmap

Not built. Named here so it cannot be implied elsewhere.

  • Full leasing-cycle automation, covering renewals and rent reviews
  • An enquiry-to-application funnel
  • An Australian tenancy-law model: bond lodgement, notice periods and statutory receipts
Apply for the Founding Pilot Programme