# Ask the questions that reveal a buildable project

Builder discovery questions reveal the project's current facts, its missing decisions and its operating fit. Ask about the lot, the plan revision, scope boundaries, decision roles, the funding path, selections expectations and communication habits. Record the source behind each answer, then turn every unknown into assigned follow-up work instead of an optimistic assumption.

## What makes a discovery question useful to a builder?

A useful question changes the next action. "What style do you like?" starts a conversation. It does not tell the team whether a plan exists, whether the lot can support it or whether the buyer understands the decision process. Ask questions that expose readiness, constraints and responsibility.

Good discovery separates three things: a confirmed fact, a buyer preference and an unresolved condition. "We own the lot" is a claimed fact that records can support. "We want a wide rear porch" is a preference. "The porch will fit inside the buildable area" stays unresolved until the right review happens.

This question set sits inside the wider [sales process](/articles/sales-process/). It follows the [first builder meeting](/articles/sales-process/first-meeting-with-a-custom-builder/) and gives the proposal team a cleaner basis for deciding what work comes next.

## Which questions establish lot and plan readiness?

Start with the land and the drawing set, because both create false confidence. A street address does not establish buildability. A floor plan image does not establish a coordinated house. Ask what exists, who prepared it, when it was updated and which review has actually happened.

1. **What is the lot status?** Owned, under contract, under consideration or still unknown.

2. **Which lot records exist?** List the survey, recorded documents, site information and any prior reports without assuming what they prove.

3. **What plan material exists?** Separate sketches, marketing plans, design development sheets and coordinated construction documents.

4. **Which revision is current?** Record the sheet date or revision marker the team will use for review.

5. **What has been checked against the site?** Name the reviewer and the scope of that review.

6. **What is still undecided?** Capture structure, exterior, room program and site features that could change scope.

Do not ask the buyer to certify technical conditions they cannot evaluate. Ask what they have been told, then find the source and the review still needed. Discovery is an intake discipline. It does not replace site, design or legal work.

## How do you uncover the real scope?

Buyers describe scope through visible rooms and finishes. You have to ask about the whole project: demolition, clearing, access, utilities, retaining conditions, exterior living, driveway, landscaping, detached structures, owner-supplied items and work expected after closing. You are not solving every item. You are stopping invisible scope from showing up later as a surprise.

| Discovery area | Question to ask | What the answer controls |
| --- | --- | --- |
| House program | Which spaces and adjacencies are required? | Plan fit and design work |
| Specification level | Which materials or systems are nonnegotiable? | Early scope and research |
| Site scope | Which exterior and lot improvements are expected? | Responsibility and review list |
| Owner work | Will the buyer supply or contract any item? | Coordination, warranty and schedule questions |
| Future work | What is intended now and what is designed for later? | Plan coordination and exclusions |

Ask the buyer to rank priorities when several requests compete. Do not turn that ranking into a budget promise. The [budget conversation guide](/articles/sales-process/budget-conversations-with-buyers/) covers how scope, allowances and uncertainty get discussed once the facts are organized.

## Which questions reveal decision and communication fit?

A custom build is a long chain of approvals. Discovery should identify who decides, who advises and how decisions become final. Ask whether every decision maker will attend key meetings. Ask how the group handles disagreement and who can approve a selection or a change in writing.

Then explain your communication system, as written in your [operating profile](/glossary/operating-profile/). Which role owns design questions? Where do selection approvals live? How are field questions routed? What belongs in a scheduled update instead of a direct call to a trade? The buyer is not being tested. Both sides are checking whether their working methods line up.

### What should you ask about previous building experience?

Ask what worked and what failed in prior renovation, design or construction experiences. Listen for expectations about access, response, changes and documentation. Do not criticize another project team. Turn the answer into a process question: "What would you need to see in our weekly update to feel informed?"

The [Operating profile stage](/process/operating-profile/) gives the sales team an approved source for these answers. If the internal process has no clear owner or record, discovery will expose the gap.

## How do discovery answers become a working record?

Use a structured record with fields for answer, source, status, owner and next review. Do not bury the result in a long email thread. Mark statements as confirmed, buyer-stated or unresolved. Link the current documents and keep the date of the conversation.

After the meeting, send a short confirmation of the project facts and the requested follow-up. Ask the buyer to correct any misunderstanding. Keep internal fit notes separate from the buyer-facing recap. Sensitive observations about capacity, risk or operating fit belong in the internal system.

The Claude and Codex agents we run organize notes, compare terminology against the intake fields and flag unanswered questions. A person checks every extracted fact, resolves contradictions and decides fit. No agent turns silence into an answer or infers approval from an offhand comment.

When the record is complete enough for a formal next step, use it to shape [the builder proposal](/articles/sales-process/presenting-a-builder-proposal/). For the wider system behind reliable fields and follow-up, see the [builder CRM guide](/guides/builder-crm/).

## What do builders ask about discovery?

### How many discovery questions should we ask?

Ask enough builder discovery questions to determine project fit and define the next review. Branch from the buyer's answers instead of running every question on every inquiry.

### Should discovery happen before a site visit?

Complete basic builder discovery before a site visit so the visit has a purpose, the right people attend and the available lot records can be reviewed.

### What if two buyers give different answers?

When buyers give conflicting discovery answers, record both positions and ask the decision group to resolve the affected scope before approval advances.

### Can an intake form replace the discovery meeting?

An intake form gathers initial discovery facts. A builder discovery meeting tests their meaning, finds missing sources and lets both sides assess working fit.