# Answer the price question without publishing a false number

Your first reply to a custom home price question explains what you can assess now and which lot, plan and scope inputs are still missing. Give the buyer a clear document request and a next review step. Use the same specification and allowance terms you use on the job. Never turn incomplete information into a public price list.

## Why does dodging the price question hurt the sales process?

Buyers know custom work varies. "Every project is different" still tells them nothing about what to do next. When the website gives no framework, they bring assumptions from listings, production plans, old projects or a conversation about a different scope. The first meeting turns into an hour of untangling unlike numbers.

Give a specific first reply: "We need your lot location, plan status and scope priorities to assess fit. Send the drawings and site information you have. We will identify the missing inputs before we discuss project-specific guidance." Adapt the wording to the review your team runs.

This belongs in the wider [positioning system](/articles/positioning/). How a builder handles the price question signals who the process is for, how decisions get made and which projects belong in the pipeline.

### Price language follows operating language

If the specification calls a category site development, the website does not call it lot preparation and imply a different boundary. If an allowance covers product and installation sits elsewhere, the public explanation does not merge them. Consistent terms mean fewer corrections in the sales meeting.

## What does the website explain instead of a list?

The inputs, in the order the team reviews them. Lot and location, then plan status, area types, structural complexity, specification level, allowances and decision readiness. Show that these inputs interact. One plan revision changes structure, windows, mechanical routes and finish quantities at once.

| Input | What the buyer can provide | What the builder reviews |
| --- | --- | --- |
| Lot | Address, survey, available reports and known restrictions | Access, utilities, topography, clearing, drainage and review path |
| Plan | Space program, concept, library plan or current drawing set | Area basis, geometry, spans, roof form, revisions and coordination status |
| Specification | Performance priorities and finish expectations | Systems, materials, responsibilities, exclusions and open choices |
| Allowances | Selection priorities and known products | Category scope, quantities, installation and reconciliation method |
| Readiness | Decision makers, desired path and available documents | Missing approvals, design work and sequence before commitment |

Do not collapse this into cost per area. Buyers misread which area is counted, which scope is included and how site work or covered outdoor space is handled. If the team uses an area-based reference internally, define the basis and keep it subordinate to the full scope review.

## How do you build a useful price conversation?

One intake and review path that sales, estimating and operations all recognize. The buyer knows what the first conversation can settle and what it cannot. A process session establishes fit and missing inputs without pretending to be an estimate.

1. **Collect the starting facts.** Lot control, location, plan status, intended spaces and major priorities.

2. **Define the area basis.** Conditioned, enclosed, garage, porch and other covered areas, kept apart.

3. **Identify the design path.** Library plan, adaptation or new design work.

4. **Review site unknowns.** Mark what needs documents, site access or professional input.

5. **Frame specifications and allowances.** What is defined, what is still a category and how later decisions get documented in the [allowance schedule](/glossary/allowance-schedule/).

6. **State the next review gate.** Which information has to be resolved before you can narrow guidance.

7. **Record the basis.** The documents and assumptions behind the conversation, so later changes are visible.

The [Positioning stage](/process/positioning/) defines the project band and project fit internally without a public price list. For a publishing method, the [custom home cost guide](/guides/publishing-a-cost-guide/) explains how to present ranges only when you have approved scope definitions and review practices.

## How does copy qualify buyers without sounding evasive?

By answering the question: you assess price through lot, plan and specification scope, then explain the next step. List what the buyer should bring. Name the unknowns that usually block useful guidance. Skip the long disclaimer that never tells the reader how to proceed.

### Describe fit before precision

A buyer usually needs to know whether the project belongs in your lane before they need a narrow range. The website describes supported project types, plan paths, service area and decision process. It also says which work sits outside the model.

The article on [defining project fit](/articles/positioning/defining-your-ideal-buyer/) ties the conversation to decision readiness. The article on [publishing exclusions](/articles/positioning/saying-who-you-dont-build-for/) states project boundaries without turning them into judgments about people.

## What stays consistent after the first conversation?

The scope terms. The website, the inquiry form, the meeting agenda and the follow-up draft all use the same ones. A buyer never hears three labels for one allowance category. A plan described as approved is not still waiting for builder review. A range discussed on one drawing issue does not quietly ride along to a later revision.

Record the basis of each working conversation: plan issue, site information, specification version, [allowance schedule](/glossary/allowance-schedule/) and open decisions. When an input changes, name what needs review. That discipline protects you from false continuity and tells the buyer why guidance moved.

### Use automation for controlled support only

AI agents organize intake answers, spot missing documents and draft a follow-up that restates assumptions. People review every output, decide project fit and approve any price-related communication. The agent never invents a range, infers a site condition or treats an unapproved plan as current.

Review public price language when the plan library, the specifications, the allowance schedule, the service area or the intake process changes. Keep prior versions when they shaped an active conversation.

## What else gets asked about the price reply?

### Do we need to publish a price range?

No. The website can explain the review method, supported projects and required inputs. Project-specific guidance comes after review.

### Should we discuss cost per square foot?

Only with a defined area basis and included scope. Explain how site work, covered spaces and specifications change the comparison.

### Can the inquiry form ask for a buyer's budget?

Yes, alongside lot, plan, scope and readiness. Review those answers together, not the budget alone.

### How do we handle a buyer who wants a number today?

Explain what the current information supports, name the missing inputs and offer the next review step.