Expanding the Rental & Leasing Ecosystem
Software companies do not usually publish this. We are pre-launch, so the most useful thing we can offer is not a feature list — it is an accurate one.
Below is the whole platform, in the order it has to be built rather than the order it happens to arrive. Each rung says what it rests on, because that is the actual argument: reporting reads a ledger, so the ledger has to be true first; intelligence reads everything, so it comes last. The sequence is not a preference. It is a dependency.
The grading is not a marketing judgement: it comes from an internal capability audit run against the codebase and its automated tests, not from a plan or an intention. Anything marked Running today runs and is covered by tests. Anything else does not exist yet, however confidently it may be described elsewhere.
There are no dates on this page. We do not publish a date we would not defend to a customer, so what you get is order rather than deadlines.
A working system of record, now.
RentNLease manages properties, units, tenants and leases, runs rent cycles, allocates and records payments, issues receipts that cannot be altered afterwards, takes a maintenance request through to an assigned vendor with AI triage, imports the spreadsheets you already keep, and holds every role to what it is allowed to see — proven by tests, not asserted. That runs today.
Each Floor Rests on the One Below It
Nothing here is dated, and nothing here is a promise. It is the sequence — what each stage needs to exist before it, and where we are in it.
The record
Rests on: Nothing. This is the floor — everything above it reads from here, so it had to be true before any of it was worth building.
Money moves through it
Rests on: A record that is already true. We built the ledger, the lease and the isolation first, so that when a rail opens the rent it moves lands somewhere correct.
Paper attaches to it
Rests on: A record to attach to. A document store with nothing to file against is a folder, not a feature — which is why this leads the build queue rather than trailing it.
Numbers come out of it
Rests on: A true record with money in it. A report of payments we did not process is not a report, so this cannot honestly precede the rung below it.
It starts telling you things
Rests on: Everything under it. Intelligence is only ever as good as the record it reads, which is why one AI ships today — maintenance triage, the only one that works on what already exists — and the other three wait for money and documents.
It connects to everything else
Rests on: A platform worth connecting to. An API over an incomplete record exports the incompleteness, so this is deliberately last rather than early.
A Unified Platform Across the Complete Asset Lifecycle
Property
Property and unit management. Running today.
Lease
Lease lifecycle management. Running today; e-signature is next.
Tenant
Tenant engagement and the resident portal. Running today.
Pay
Invoicing, allocation, payment records and receipts run today. Live collection — the rail itself — is next, in either market.
Maintain
Maintenance and operations, including AI triage. Running today.
Documents
Documents and compliance. Not started — there is no document store yet.
Intelligence
Analytics and AI. Maintenance triage only today; the rest is in design.
Asset
Specialised asset management beyond real estate. Direction only — nothing built.
Building the ecosystem around the asset.
The furthest thing on this page, and the least certain. The idea is that rental and leasing is not only about managing assets but about connecting everyone around them. We are publishing it because it explains the direction, not because it is close.
Asset owners
Provide the assets.
Customers
Rent or lease them.
Service providers
Maintain them.
Insurers
Protect them.
Financial institutions
Enable financing against them.
Vendors
Provide the services around them.
Technology partners
Extend what the platform can do.
Why we publish this
Every platform in this category can show you a longer feature list than ours. None of them can show you their build state — which is the one thing you actually need to judge a company that has not launched yet.
A feature list tells you what someone wants you to believe. This tells you what is true today, and lets you check us against it later. If something on the first list turns out not to work the way it reads, that is a fair thing to hold us to.
Let's Talk About Your Portfolio
That is the most useful thing an early-access user can tell us, and it is why this page exists.