Creating a new asset inside the system.​

 

What This Is

Add Property is how a new home is introduced into Cohos as a standalone asset.

This is not just adding an address.
It is the act of creating a container that will hold structure, data, history, permissions, and lifecycle intelligence over time.

Once added, the property exists independently of any single project or person.

 

Why This Exists

Most platforms treat properties as temporary inputs.

They appear for a transaction and disappear when work is done. That destroys continuity and forces rediscovery on every return.

Add Property exists to establish permanence.

The home becomes something the system can learn from, build on, and retain.

 

What Happens When a Property Is Added

At creation, the system establishes:

A unique property identity
Baseline location and type data
Ownership or control association
Eligibility for intake and modeling

This is the foundation everything else attaches to.

 

Relationship to Intake and Modeling

Add Property does not attempt to define the home fully.

It creates the shell that intake will later populate.

This separation matters.

It allows properties to be added early, transferred, shared, or staged before deeper data is captured.

 

Multi Property and Portfolio Behavior

Add Property enables scale.

Once multiple properties exist:

Planning can span homes
Maintenance can be coordinated
Pricing leverage improves
Insights aggregate

The system begins to behave differently when it sees assets instead of one offs.

 

Transferability and Longevity

A property added today may outlive:

The current owner
The current manager
The current use case

Add Property ensures the asset can persist, evolve, and move without losing its intelligence.

 

Structural Role

Add Property is the entry point into an asset first model.

It is where Cohos stops thinking in terms of users and starts thinking in terms of real world properties with long lives and compounding data.