Purpose first
Start with the workflow, the question and the minimum context needed. A data source should have a clear job before it is included.
Private by design
Useful work needs a clear data boundary.
Habits is designed around the context an agency chooses to use for a specific workflow. The objective is a useful next step, not unrestricted access to client records.
Context you permit
Relevant CRM, calendar and agent feedback can inform a workflow when the agency authorises that use. Unrelated records should stay out.
Rules you own
The agency defines the routing, review and follow-up rules. Habits should make that logic visible, not replace it with hidden behaviour.
Human responsibility
Drafts and recommendations support the team. Professional judgment and external communication remain with people.
Evidence and operational context are different
A report should distinguish source-led place information, derived interpretation and internal agent context. This makes it easier to see what is factual, what is provisional and what needs verification.
What Habits does not claim
No public AI tool receives client data through the workflow described here.
No valuation, legal opinion, planning determination, lending decision or investment recommendation.
No claim of a particular integration, security control or compliance certification without documented evidence.
No inference of sensitive personal characteristics from location or operational records.
Start with the boundary, then design the work.
The fastest way to scope a useful workflow is to agree the data boundary, the business rule and the human checkpoint together.