Reference platform · not a live agency
Five doors. One tenancy. A regulated book we built to prove the platform path.
This is a working New Zealand property-management platform we forged in-house. Seeded demo data, not an agency running its book on it. It exists so a licensed firm can see what replacing a rented system looks like before a working session.
What we built
Agency, manager, owner, tenant, supplier.
Five installable PWAs on one tenancy loop: listings and screening, signed agreements, bond lodge, rent into trust, maintenance across three desks, inspections, arrears, and renewals. New Zealand tenancy rules sit in the product, not a PDF in a drawer.
- 5 PWAsRole-specific workspaces
- RTA / HHRules in the product
- Demo bookSeeded, labelled as such
What this is, and what it is not
It is studio proof for the custom-platform path: multi-seat, multi-role, a system of record with a trust ledger and a compliance engine. The same class of work as replacing a licensed or rented agency stack.
It is not a live client, not a product you can buy off a card, and not a certified legal opinion. Bond lodgement in the demo returns sandbox references. Restarting the API resets created records. We keep that on the login screens.
The loop we forged
One chain, five doors. Nobody forwards a PDF to keep the job moving.
-
01
Win the management
Enquiry, appraisal, rent indication, proposal, owner accepts. The property is then a file, not an email thread.
-
02
Let and activate
Listing, screening, agreement, tenant sign, bond lodge. The tenant portal is issued as part of the same chain.
-
03
Run the tenancy
Rent posts to trust. A maintenance job is the same record for tenant, supplier, and owner. Inspections, arrears, and renewals sit on that file.
Why this sits off the live-project grid
Absolute House Wash, Miss Kat D, and Clean Cuts are businesses running on Own Forge stacks. This page is different on purpose. Mixing a seeded reference into “live projects we have shipped” would make those client sites look less true.
If you run a local service business, stay on the published cards. If you are leaving a rented agency system, or you need a multi-team book that has to stand up later, this is the proof we show in a working session. Your build is scoped to your licences, your historic file, and your cutover. You own that asset.
Straight answers
Is an agency using this in production?
No. This is a working reference with seeded demo data. It becomes a case study the day a real book is imported and running.
Can we buy this off the shelf?
No. The published homepage cards are for local service sites and CRMs. A regulated book is scoped after a working session. You would own the system we forge for you, not rent this demo.
Are you saying this is certified NZ-compliant?
No. Rules for bonds, rent increases, notices, and Healthy Homes are written into the product so the workflow cannot shrug them off. That is not a legal certification, and the bond path in this demo is sandbox.
Why show a demo at all?
Because the custom-platform path needs proof that is not a house-wash site. This is the deepest multi-role system we have forged. We would rather show the work and name it honestly than hide it.
Related pages
Next step
Ready to forge your system?
Tell us about your business. We'll recommend the right build within 24 hours.