Verticals · Commercial property management
Buildings, units, leases, tenants — a lease is a deal with an address.
Properties nest into units, leases run as pipelines with contract terms, and tenants are people in one directory — the whole portfolio in a single system of record.
Why one system
The rent roll lives in one system, the leases in a shared drive, maintenance in an inbox — and the building’s real condition lives in the property manager’s head.
One system where the building, the lease, the tenant, and the work order agree with each other.
The objects you’d define
properties
hierarchy · locations · attachments
Buildings carry units, units carry leases. The structure is the portfolio.
leases
deal · workflow · activity
Two parties, an asking rent and a signed rent, contract start and end — the deal primitive wearing real estate clothes.
tenants
contacts · email · phone
The same tenant across every lease, renewal, and maintenance request they touch.
maintenance requests
workflow · tasks · locations
Staged and gated from report to resolution, tied to the unit they belong to.
- Inquiry
- Tour
- Negotiation
- Signed
A leases pipeline — landlord ↔ tenant — same deal primitive, your labels.
How it runs.
A prospective tenant inquires about a unit. That’s the top of a lease pipeline — and because a lease is a deal, it carries the asking rent, the negotiated rent, and the contract dates from day one.
When the lease signs, the unit’s record shows it; when a renewal window opens, the contract end date is already in the graph, not in someone’s spreadsheet.
Maintenance requests attach to units, tenants attach to leases, and the building’s history accrues on the building.
Nomi flags leases approaching contract end, drafts the renewal record, and answers “which units turn over this quarter?” without a report being built.
Nothing here is an industry edition — it’s the same primitives, named by the people who run the business.