Pipeline-wise behavior:

Rental Pipeline

Card structure designed around tenant requirements and leasing flow

Focus on inquiry → viewing → negotiation → closure

Sales Pipeline

Card structure aligned with buyer journey

Focus on lead qualification → property matching → offer → closing

Property Management Pipeline

Card structure aligned with owner onboarding and asset management

Focus on onboarding → documentation → activation → ongoing management

System Expectations:

Each pipeline acts as an independent data container with its own card logic

Opportunity cards are not reusable across pipelines unless explicitly mapped

Frontend UI renders cards based on the pipeline context only

Backend should enforce strict association between pipeline and card structure

Automations and workflows should trigger based on pipeline-specific stages and card logic

Goal:

Ensure each business function (rental, sales, property management) operates with its own structured workflow, instead of forcing a one-size-fits-all opportunity card.