# Build a lead intake form that starts a useful conversation

A custom builder lead form captures contact details, target location, lot status, plan status, project type and the buyer's main question. Keep the first form short enough to finish. Send every submission into a record you own, with its original page, source details, assigned owner and a specific response task.

## What must the first form tell you?

Enough to prepare the next conversation. It does not need to qualify the whole project. A buyer asking about a plan library needs a different reply from a lot owner holding a survey and asking about setbacks. Both can be good inquiries. The next useful question is different.

Start with facts the buyer can answer without opening a plan set. Ask where they hope to build, what control they have over the lot, how far they have moved on design and what prompted the inquiry. Keep their project description in their own words. It often holds the clearest clue about decision stage, required rooms and features, and the misunderstandings that need correcting.

The form is one part of the [leads and CRM system](/articles/leads-and-crm/). It creates a record that survives a phone call, a plan review, a site discussion and a later [handoff](/process/handoff/) without losing where the conversation began.

### Which fields earn their place?

| Field | Why it belongs | Preferred input |
| --- | --- | --- |
| Name and contact method | Supports a direct response and duplicate matching | Short text plus one choice |
| Target area | Tests the working geography and trade coverage | Short text, not a huge town list |
| Lot status | Separates owned, controlled, identified and searching | Defined choices |
| Plan status | Shows whether the buyer has drawings, a concept or no plan | Defined choices |
| Project type | Separates custom, teardown, infill and available-home interest | Defined choices |
| Main question | Lets the buyer say what matters now | Open text |
| Preferred response | Reduces missed connections | Phone or email choice |

## What should stay off the first form?

Do not turn intake into unpaid preconstruction. Detailed allowance choices, room-by-room selections, full financing history and document uploads rarely belong on the first screen. A buyer may not know yet which documents matter. Asking for all of them creates work before service fit is established.

Drop fields nobody uses. If the sales team never changes its preparation based on architectural style, do not make buyers pick from a long style menu. If a desired start window affects capacity planning, ask for it in broad terms and confirm it on the call. Never let a form answer imply that a slot is available.

Consent language, privacy disclosures and any communication permission should match the tools you use and the follow-up you do. Check disclosure and permission requirements with your communications adviser and the form and messaging providers. Do not hide permission inside unrelated copy.

## How should the form change by page?

Use one core record with small contextual variations. A plan page passes the plan name without asking the buyer to type it again. A community page keeps the community as page context. A [cost-guide](/guides/publishing-a-cost-guide/) page records that interest without treating the download as proof of project readiness.

1. **Set the form purpose.** Decide whether it starts a general inquiry, a plan question, a lot conversation, event follow-up or an available-home request.

2. **Keep the core fields stable.** Name, contact path, area, lot status and project note map to the same CRM definitions on every page.

3. **Pass page context quietly.** Store the page path, the form name and the approved [UTM parameters](/glossary/utm-parameters/) without asking the buyer to copy them.

4. **Change only useful prompts.** A lot page can ask about control and survey status. A plan page can ask what the buyer wants to change.

5. **Test the receiving record.** Confirm the context lands beside the inquiry and does not overwrite original source data.

For the broader source setup, use the [Lead attribution stage](/process/lead-attribution/). For form placement and page roles, see the [custom builder website pages guide](/guides/custom-builder-website-pages/).

## What happens after the buyer presses submit?

The confirmation screen says what happens next without making an unreviewed promise. The submission creates or updates one contact, keeps the original source, stores the exact inquiry text and assigns a response task. The person receiving it needs a clear notification with a link to the working record, not a detached email that starts a second history.

Define duplicate behavior before launch. A person may ask about a plan after a Parade weekend, or submit from two devices. The system adds a new touch to the existing relationship when the match is reliable. It does not silently erase the first source or merge two decision makers with similar details.

The response workflow sits beside the form specification. The tactical handoff is in [speed to lead for builders](/articles/leads-and-crm/speed-to-lead-for-builders/). The deeper conversation is in [custom lead qualification](/articles/leads-and-crm/qualifying-custom-home-leads/).

Write a field-mapping test row before launch: form prompt, CRM field, allowed value, empty-value behavior and receiving owner. Submit a blank optional lot field and confirm it stays unknown. Submit a returning contact and confirm the new page context becomes a touch without replacing the original source.

## How do you test a builder intake form?

Test it like a job-site handoff. Use realistic records, awkward inputs and failure paths. Submit from a phone on a slow connection. Leave optional fields blank. Use a returning contact. Enter a target area outside the normal lane. Confirm the buyer sees a clear result and the office sees the same facts.

Claude and Codex agents on our side check field mapping, find missing context and compare submissions with the written specification. A person reviews the form, the consent language, the routing and every qualification decision. An agent can detect that lot status is blank. It cannot decide that a lot is buildable.

- Confirm required fields block an incomplete submission and optional fields stay optional.

- Check page path, form purpose and source details in the received record.

- Verify notification, ownership and response task creation.

- Test duplicate, spam and integration-failure handling.

- Export a test record and confirm you keep usable data.

## What do builders ask about intake forms?

### Should the form ask for a budget?

Ask for a budget on a builder intake form only when it changes the next conversation. Use reviewed scope language and confirm the answer during qualification.

### Should buyers upload plans or surveys?

Request plans or surveys through controlled follow-up after service fit and document handling are clear. A first general builder intake form can ask whether those documents exist.

### How many fields are too many?

A builder intake form has too many fields when some answers do not change preparation, routing or the next action. Remove unused prompts and test completion on a phone.

### Can an AI agent answer the submission?

An AI agent can draft an intake reply from approved facts. A person reviews project claims, availability, lot questions and commitments before the reply goes out.