# Track referral leads without flattening the relationship into a source label

Track a builder referral by recording the introducer, the relationship type, the introduction method, the buyer's existing source history, the project facts and the promised follow-up in one CRM record. Keep referral credit separate from campaign attribution. Update the introducer only with information the buyer and the builder have approved, and close the loop without exposing private project details.

## Why is a referral more than a value in the source field?

A referral carries two relationships: yours with the prospective buyer and yours with the person who made the introduction. One source label cannot show who introduced whom, why the match looked useful, what the buyer had already researched or what follow-up was promised.

The record needs enough context to protect both relationships. A past buyer introduces a neighbor with a teardown. A trade partner hears about an owner holding a difficult lot. A designer connects a client whose plan is already developed. A buyer's agent introduces a client through your listing agent. Each path needs different handling.

Referral tracking sits inside your larger [leads and CRM system](/articles/leads-and-crm/), with its own relationship fields and review rules.

### What should never be assumed from the introduction?

An introduction does not prove project fit, decision readiness, lot feasibility, plan feasibility or permission to share updates with the referrer. Record what the introducer said and ask the buyer directly for the missing project facts. Do not move the record to a later pipeline stage because the source is trusted.

## Which referral details belong in the CRM?

Separate the buyer record from the referrer record, then connect them. That keeps a relationship note out of the wrong place and lets you see several introductions from one source without exposing every buyer's file.

| Record | What to capture | Why it matters |
| --- | --- | --- |
| Buyer contacts | Decision makers, representation, preferred contact, location, lot status, plan status | Supports the actual fit conversation |
| Referrer | Name, relationship type, contact details, owner inside your team | Preserves the business relationship |
| Introduction | Date, method, stated reason and any approved context | Shows what happened without relying on memory |
| Attribution | Original discovery source, referral touch and later meaningful touches | Avoids replacing the buyer's earlier path |
| Permission | What follow-up or status sharing has been approved | Limits unnecessary disclosure |
| Outcome | Fit review, active, paused, referred elsewhere, not a fit or advanced | Allows honest relationship review |

Define each field in your CRM runbook. "Partner" is too vague if it lumps together agents, designers, trades, lenders, land contacts and past buyers. The [builder CRM fields guide](/articles/leads-and-crm/builder-crm-fields/) shows how controlled values keep later reports usable.

## How does a referred inquiry move from introduction to next step?

Respond to the introduction with care, and keep qualification grounded in observable project facts. You still need to know where the work is, what site control exists, what design direction exists and what the project expects from the process.

1. **Capture the introduction.** Save the original message or a short note, then connect the buyer and referrer records.

2. **Check for an existing buyer record.** Keep earlier website, event, call or lot-owner activity instead of creating a duplicate.

3. **Acknowledge both parties.** Confirm receipt without promising fit or sharing private details.

4. **Speak with the buyer directly.** Verify project location, lot status, plan status, intended use and the immediate question.

5. **Assign a next action and an owner.** Schedule the fit review, request a document, send approved process information or record a clear nonfit reason.

6. **Close the relationship loop.** Thank the referrer and share only the status the people involved have approved.

### How should a buyer-agent introduction be handled?

Your listing agent and brokerage set how a buyer's agent registers a client and how the two agents cooperate. Record the agent, the brokerage, the buyer, the project, the timing and the documents supplied, then pass the introduction to your listing agent. Do not invent a policy inside a CRM note. The [listing agent guide](/guides/listing-agent-for-custom-builders/) explains what the listing agent brings to that path and what the builder hands over.

## How do you preserve attribution when the buyer already knew you?

Keep first discovery, the meaningful referral and the conversion touch as separate facts when you know them. A buyer may have followed project galleries, toured a Parade house and later asked a past buyer for an introduction. Calling that only "referral" hides the content and event work. Calling it only "website" ignores the relationship that caused action. That is the whole problem [lead attribution](/glossary/lead-attribution/) exists to solve.

Use neutral labels when the path is uncertain. "Buyer reported prior website research; introduced later by past buyer" is more defensible than full credit to one channel. The [Lead attribution stage](/process/lead-attribution/) sets the source rules and the builder-owned reporting that keep those distinctions.

### Can AI agents help reconcile referral records?

Claude and Codex agents on our side flag likely duplicate contacts, extract stated project facts from an introduction, draft an acknowledgment and find records with no relationship owner. A person reviews the match, the permissions, the wording and the next step. No agent infers personal relationships or decides what project information can be shared.

## What should a referral report tell you?

Introductions, source types, fit-review movement, stated nonfit reasons, next-action gaps and relationship follow-up. It should not rank people by raw introductions. One carefully matched lot-owner introduction may deserve more attention than a list of weak names, but the report describes conditions. It does not manufacture a value claim.

Review the patterns that can improve operations. If designers keep asking for a clearer preconstruction path, improve that material. If past buyers cannot explain your service area, clarify it. If trade partners send warranty requests through the sales channel, build a better routing page. Good referral reporting exposes confusing handoffs as well as opportunities.

Never turn a referrer's contact list into a bulk campaign. Keep each introduction tied to a defined purpose and an approved communication path. Check platform requirements with the provider, and communication or recordkeeping requirements with your qualified advisers. The [lead data ownership guide](/articles/leads-and-crm/lead-data-ownership/) explains how access, exports, retention and [handoff](/process/handoff/) stay under your control.

## How should you handle referral updates and conflicts?

### Should the referrer get updates on the project?

Share referral status only within the limits the buyer and the builder approved. Thanking a referrer does not require disclosing private plans, lot facts, contract discussions or schedules.

### What if two people claim the same referral?

When two people claim a referral, keep both documented touches and ask the buyer about the introduction when appropriate. Follow your reviewed policy without rewriting the history.

### Does a referred buyer skip qualification?

A referred buyer still needs qualification. Prompt relationship handling does not replace direct review of location, lot, plan, project type and fit with your operating process.

### How should a referral that is not a fit be closed?

Close a nonfit referral with a factual reason and a respectful buyer response. Thank the introducer without assigning blame or sharing private project details.