How the pieces connect
Most property software is a set of modules that happen to share a login. This is one record that a unit travels across — listed, applied for, signed, moved into, repaired, paid for, renewed — with each step landing somewhere the next person will find it.
The loop
Each stage says what actually happens and what state it is in. Live means there is a database table and an endpoint behind it — the same test the roadmap uses, so the two pages can never drift apart.
A listing is a version with a publication period, not a post that quietly mutates. What was advertised on the day somebody applied stays recoverable.
The criteria are recorded as a version before the application arrives. That is what makes a decision defensible later instead of a matter of somebody memory.
An invite adds a role to whatever account the person already has. The condition of the unit on day one is recorded where the deposit conversation will happen two years later.
The loop that repeats most, and the one the whole product is shaped around. A request becomes a dispatched job with an arrival window and a photograph proving it closed.
Every charge points back at the thing that caused it. A screening fee knows its application; a payout knows the work behind it.
The tenancy closes. The record does not. The next tenant, the next manager and the next owner inherit context instead of an empty folder.
The roadmap breaks each of these down — what is live, what is moving onto the database, and what is written in the model and waiting.
What every stage shares
A suite becomes a product when the same rules hold at every stage. These four are why a step taken in stage two still means something in stage six.
Every stage writes to the same property, and the property cannot be deleted by anyone. Stages do not each keep their own copy of the truth.
The same person can be an owner here, a tenant there and a vendor somewhere else. They switch workspace rather than keeping three logins and three passwords.
The approval carries the estimate. The completion carries the photo. The decision carries proof it was delivered. Nothing important rests on a claim.
Who may do a thing is defined per capability, not inferred from a job title. Reporting a problem never quietly becomes authority over the asset.
The hard part
Nothing tests a property system like a handoff. Every one of these is the moment a normal tool forgets, because the information was attached to a person or a thread instead of to the unit.
Relationships end without deleting anything. The incoming manager opens four years of repair history on day one instead of asking the owner what happened.
Move-in condition, requests, repairs and notices stay on the unit. The departing tenant can export their own records, and the arriving one starts against a documented baseline.
The job packet, the scope, the access notes and the completion photos belong to the work order. Replacing a vendor does not erase what the last one did.
Ownership is a relationship with a period, not a column on a row. An incoming owner can request the prior history, and a former owner can still export theirs.
Early access
The stages that repeat are the ones that are live. Start with a single property and see the record fill in.