Source evidence
Where the owner or property signal came from, date observed, and the source context your team can review.
Why handoff matters
Leads die when the next action is unclear.
A property-owner record is only useful when a BDM or operator can see why it exists, what was observed, whether contact is permitted, what the owner said, and what should happen next. CRM handoff turns owner intelligence into assigned work.
Supported CRM scope
Only three systems named.
Obsidian currently names three CRM handoff targets publicly: LeadSimple, HubSpot, and Pipedrive. Each implementation is scoped around your fields, pipeline stages, access rules, and approved next-action workflow.
| CRM | Programmatic handoff | Typical owner-lead fields | Limit |
|---|---|---|---|
| LeadSimple | Scoped API handoff for property-management sales workflows. | Owner or entity name, property address, source evidence, contact state, disposition, next action, assigned owner. | Field names, pipeline stages, and permissions must match the client workspace. |
| HubSpot | Scoped API handoff into contact, company, deal, task, or list structures when approved. | Lead source, property fit, qualification status, follow-up timing, notes, suppression status. | Portal configuration and object model determine the exact route. |
| Pipedrive | Scoped API handoff into pipeline records, activities, and owner follow-up queues. | Person or organization, property context, source URL, status, activity due date, BDM notes. | Pipeline stage mapping and duplicate handling are confirmed before launch. |
Handoff fields
What should move into the CRM?
The handoff should preserve enough evidence for a reviewer to decide whether to act, nurture, suppress, or disqualify the record.
Fit fields
Territory, property type, unit count, rent band, asset exclusions, and service-area match.
Contact state
Approved channel, review requirement, suppression status, opt-out state, or no-contact decision.
Qualification
Decision-maker status, stated need, timeline, objection, interest, and follow-up permission when known.
Routing
Assigned user, pipeline, next activity, nurture status, and handoff notes.
Audit trail
What changed, when it changed, and which workflow produced the CRM record.
Franchise operators
Standardize local owner acquisition without losing local control.
Multi-location operators and franchise owners often need a repeatable owner-acquisition workflow that still respects local territory, asset fit, and CRM configuration. For Keyrenter operators, see the Keyrenter franchise owner offer.
FAQ
CRM handoff questions.
Does Obsidian integrate programmatically?
Yes. Programmatic API handoff can be scoped for LeadSimple, HubSpot, or Pipedrive when the client provides the required access, field map, and workflow rules.
Does Obsidian replace LeadSimple, HubSpot, or Pipedrive?
No. Obsidian supplies owner intelligence and handoff workflow. Your CRM remains the operating system for pipeline, tasks, reporting, and team activity.
Can the CRM receive FRBO source evidence?
Yes, when included in scope. The goal is to preserve the source context, not just send a name and phone number.
Can you route only qualified responses?
Yes. The handoff can be limited to agreed dispositions such as qualified, nurture, review required, suppressed, or disqualified.