A custom builder sales pipeline uses stages that describe observable buyer and builder conditions, not vague activity. Each stage needs entry evidence, a responsible owner, a required next action and an exit condition. Keep long-term nurture outside the active pipeline, and define exactly when a qualified opportunity becomes preconstruction work.
Why do ordinary sales stages break on custom builds?
New, contacted, hot and closed do not describe the work between inquiry and contract. A custom project may need lot review, plan discussion, design decisions, allowance education and several internal checks before you can decide what to offer. The pipeline should make those conditions visible without pretending the CRM is the construction schedule.
A stage is a shared operating state. Anyone reading it should know what evidence exists and what has to happen next. "Proposal sent" is useful if the company defines which proposal and who is deciding. "Following up" is an activity, and it can run forever.
Use this structure with the leads and CRM hub. The stages govern active sales work. Source tracking, field definitions and follow-up rules support each move.
Which stages fit a custom builder pipeline?
The exact names should match your process, but the conditions below are a practical start. A spec home inquiry may take a shorter path. A build-on-your-lot project may need deeper site review.
| Stage | Entry evidence | Exit condition |
|---|---|---|
| New inquiry | A buyer record entered from an approved source | Initial review and response task completed |
| Fit review | Basic location, lot, plan and project context available | Advance, request facts, nurture, refer or close |
| Discovery scheduled | Appropriate participants and meeting purpose confirmed | Discovery held or scheduling attempt resolved |
| Project review | Required lot, plan and expectation facts gathered | Defined sales or preconstruction decision reached |
| Decision pending | Buyer has the approved next-step terms or proposal | Accept, decline, pause or revise through an approved path |
| Preconstruction handoff | Agreement and required information satisfy the handoff rule | Receiving system and owner confirm receipt |
Long lot searches and distant projects usually belong in nurture, not an active stage. Keeping them active hides the opportunities that need work now.
How should stage-entry rules be written?
Write each rule as evidence another operator can verify. Skip intuition labels. "Discovery scheduled" needs a calendar event, participants and a purpose. "Project review" may need a stated lot condition, a design starting point and your defined discovery notes. If evidence is missing, the record stays in the prior stage with a next action.
- Name the condition. Describe what is true about the buyer-builder process.
- List the required evidence. Name the fields, documents, conversations or approvals that support entry.
- Assign the stage owner. One role stays accountable even when technical input comes from others.
- Define the next action. State what moves the record forward and when it is due.
- List the valid exits. Advance, return for missing facts, nurture, refer, lose or hand off.
- Test the exceptions. Use referrals, plan-only inquiries, lot owners, event leads and available-home buyers.
The field support for these rules is in builder CRM fields.
Who should own each pipeline transition?
Ownership matches authority. Intake owns the new-inquiry review. Sales owns discovery and the buyer conversation. Site, design, estimating or leadership supply evidence during project review. The sales owner does not quietly hand off responsibility because someone else answered a technical question.
Define approval boundaries. A salesperson can request a survey without approving the lot. A plan reviewer can flag open issues without promising a build slot. A CRM administrator can correct a field mapping without changing the qualification outcome.
The qualification decision is covered in qualifying custom home leads. Use it to keep fit decisions tied to the operating lane instead of enthusiasm.
How does nurture stay separate from active sales?
Nurture is a condition with a future trigger, not a parking lot. Record why the project is waiting, what event justifies contact, who owns it and when to review the condition. A lot-search prospect comes back when property is controlled. An early researcher comes back when the decision makers are ready for discovery.
Do not keep dormant records in "proposal" or "qualified" because the team hopes they return. That inflates the apparent workload and makes stage review useless. Move the record to nurture with its history intact, then use an approved follow-up path.
What makes the preconstruction handoff complete?
A signed decision alone may not complete the operating transfer. Define which contact details, lot records, plan version, project notes, communication expectations and approved documents the receiving team needs. State which system becomes authoritative and who confirms receipt.
The handoff keeps the sales history without dumping every email into the project workspace. Summarize open questions, promises, exclusions and buyer priorities. Link to controlled documents. Mark the CRM record handed off only after the receiving owner confirms the required information is usable.
The Operating profile stage establishes the underlying responsibilities and documents. The builder CRM guide explains how to configure and test the system around them.
Test a rejected transition as well as an accepted one. Try moving an inquiry to discovery scheduled without a confirmed meeting. Keep it in fit review and assign the missing scheduling task. After confirmation, record the supporting event and the reviewer. Neither transition should touch the source history.
How should the pipeline be reviewed?
Review stage exceptions, not only totals. Look for records with no next action, stage age with no explanation, missing entry evidence, repeated backward moves, dormant decision stages and handoffs the receiving team never confirmed. Read a small sample beside the notes to see whether the label matches reality.
Our Claude and Codex agents flag missing fields, summarize stage history and find records that break written rules. A person reviews every output and approves stage changes. No agent decides that a lot works, a plan is feasible or an opportunity deserves priority beyond the criteria people set.
When the sales process changes, update stage definitions, CRM fields, follow-up paths and reports together. Train with real scenarios: a Parade lead, a referral with no lot, a plan owner outside the service area.
When should a pipeline stage change?
How many pipeline stages should we use?
Use the fewest builder pipeline stages that represent meaningful conditions. Add a stage only when it changes the required evidence, the ownership, the next action or the reporting.
Should lost opportunities stay in the pipeline?
Remove lost opportunities from active pipeline stages while keeping their history and the factual outcome reason. Reopen a record only when new evidence supports renewed work.
Can different project types use different pipelines?
Different builder project types can use different pipelines when their decisions differ. Keep shared field definitions consistent and assign an owner to maintain each path.
Should stage changes happen automatically?
Automate pipeline changes only where clear evidence supports a tested rule. Keep human approval for transitions that imply fit, feasibility, agreement or project acceptance.