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. The LeadSimple handoff is implemented in the Obsidian portal and configured to each client workspace before use. HubSpot and Pipedrive are available to scope as custom API work; they are not pre-built connectors. Each implementation is scoped around your fields, pipeline stages, access rules, and approved next-action workflow.
| CRM | Status | Programmatic handoff | Typical owner-lead fields | Limit |
|---|---|---|---|---|
| LeadSimple | Implemented in the Obsidian portal. Configured per client workspace. | A deal is created in your chosen pipeline and stage with a named lead source, the contact, and the property; the source evidence goes in as a note. Call outcomes can be logged against the existing deal without creating deals or moving stages. | Owner or entity name, mobile phone or email, property address, bedrooms, estimated rent, days on market, source URL, source name, score band, disposition and call notes. | Pipeline, stage, and source names must match the client workspace. Obsidian never moves deal stages; your automations stay yours. |
| HubSpot | Available to scope. Custom API work, not a pre-built connector. | 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 | Available to scope. Custom API work, not a pre-built connector. | 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.
Illustrative example
What a LeadSimple handoff looks like.
This is an illustrative record with made-up details. It shows the shape of the implemented LeadSimple handoff, not a real owner, property, or client workspace. Field names on the LeadSimple side follow your workspace configuration.
| Lands in LeadSimple as | Illustrative value | Where it comes from |
|---|---|---|
| Deal name | Example Owner, 123 Example St | Owner of record and property address. |
| Pipeline and stage | Your owner-acquisition pipeline, first stage | Chosen with you at setup. Obsidian never moves the stage afterwards. |
| Lead source | Obsidian FRBO | A named source in your workspace, created if it does not exist. |
| Contact | Example Owner, one mobile number, one email if known | Permitted enrichment, screened before handoff. |
| Property | 123 Example St, Example City, ST 00000, 3 bed, estimated rent $2,100 | Listing and property context observed at the source. |
| Note on the deal | Days on market: 34. Beds: 3. Rent: $2,100. Source link. Source: Obsidian FRBO. | The evidence a BDM needs to decide the next action. |
| Call log (when outreach is in scope) | Outcome: callback requested. Notes: owner asked to be called after the 15th. | Logged against the existing deal; no new deal, no stage change. |
Illustrative only. Values are invented. Exact fields, stages, and source names are confirmed in the written scope.
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. The LeadSimple handoff is implemented in the Obsidian portal and is configured to your pipeline, stage, and source names before the first push. HubSpot and Pipedrive handoffs are scoped as custom API work 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.