Source-bounded implementation brief

Property-source check for a Investor lead

For a investor lead, property-source check should preserve the person’s stated context, create an auditable record and stop before unsupported automation. It does not prove that a production CRM, calendar, messaging or property-data connection is active.

Direct answer

Capture strategy, capital range, location, asset type, hold period and evidence requirements only as relevant to this stage. Store listing identifier, approved source, retrieval time, status, fields used and freshness rule. Use that evidence to decide whether a property statement can be shown or must be withheld, then hand off to an investment-property specialist when the stop conditions require it.

Required workflow record

Lead context

strategy, capital range, location, asset type, hold period and evidence requirements.

Stage record

listing identifier, approved source, retrieval time, status, fields used and freshness rule.

Four-step implementation

  1. Collect only the stated strategy, capital range, location, asset type, hold period and evidence requirements.
  2. Create the stage record: listing identifier, approved source, retrieval time, status, fields used and freshness rule.
  3. Use the record to decide whether a property statement can be shown or must be withheld.
  4. Stop when missing source, stale record, conflicting fields or licensing restriction; pass context to an investment-property specialist when required.

Stop and escalate

Stop automation for missing source, stale record, conflicting fields or licensing restriction. Do not use this flow for guaranteed returns, fabricated cap rates or unverified projections.

Evidence boundary

A property-data connection requires authorization, licensing and freshness controls. The public demo does not prove a live MLS connection. This guide describes a workflow specification, not a deployed integration, legal conclusion, fair-housing approval, response-time promise, conversion forecast or transaction result.

Scope a reviewed workflow

Use this brief to document sources, records, stop conditions and ownership before implementation.

Discuss a custom PropBot Studio workflow