Present a builder proposal as a decision document, not a reveal. Reconfirm the plan revision, the site assumptions, the included scope, the allowances, the exclusions and the unresolved items before you discuss the path forward. Walk the buyer through how the proposal was assembled, record questions beside the controlling section and issue revisions through one documented channel.
What should a builder proposal help the buyer decide?
Whether the defined project, the working assumptions and your process are ready for the next agreement. It should not imply that every unknown has been settled. Custom work carries open conditions. Those conditions can be named, assigned and handled through a visible review path.
State the decision at the start of the meeting. The buyer may be deciding to enter preconstruction, approve a revised scope or supply missing information before another review. If the team cannot say which decision the proposal supports, the document is trying to do too much.
Place the presentation inside the sales process. Discovery establishes the inputs. The proposal organizes them into a reviewable path. Later agreements and contract documents govern their own terms.
What has to be confirmed before the proposal meeting?
Confirm the proposal basis before you schedule the presentation: the current plan revision, the identified site records, the written scope notes and the approved discovery record. If an updated drawing arrived after the proposal was prepared, stop and decide what needs another review. Do not present a stale proposal and promise to patch it out loud.
| Proposal basis | Confirm before presentation | If it is unclear |
|---|---|---|
| Plan set | Current revision and sheets used | Hold affected scope for review |
| Lot information | Records received and assumptions made | List the required site work or source |
| Specifications | Included level and buyer priorities | Use a clear allowance or unresolved item |
| Responsibility | Builder, buyer and outside-party scope | Assign ownership before acceptance |
| Open decisions | Effect on scope and next deadline | State the review path, not a guess |
The discovery record makes this check routine. See builder discovery questions for the intake structure that separates buyer statements, confirmed facts and unresolved conditions.
How should you walk through the proposal?
Present in the same order the team used to assemble the work. Start with the project definition, then show inclusions, allowances, exclusions, assumptions, decision responsibilities and the next phase. Do not open with the last page and make the buyer reverse-engineer what it represents.
- Restate the project. Confirm the lot, the plan revision and the scope the proposal covers.
- Show the included work. Connect major categories to the plan and the specification source.
- Explain allowances. Say what each category includes, the quantity or scope basis and the later selection record.
- Review exclusions. Say which party owns each excluded or outside item.
- Name assumptions. State what information could change the proposal and how that question gets resolved.
- List open decisions. Assign an owner and a next review point.
- Explain the next agreement. Separate the proposal from preconstruction or construction documents.
Pause after each section for questions, but keep the answer attached to the source. If a question needs plan, field, trade or contract review, write it down and name the responsible role. A confident presentation can include "not yet determined" when the next step is specific.
How should you handle visual materials?
Use the plan set, spec excerpts and the allowance schedule as working references. Show the relevant sheet when you discuss scope. If renderings are present, say what they illustrate and which written documents control. Attractive images help orientation. They also imply details that were never included.
How do you explain allowances and assumptions without confusion?
Keep them separate. An allowance is a defined part of the project waiting on a later selection or final basis. An assumption is a condition used to prepare the proposal because information is incomplete. The buyer should be able to name the category, its scope basis, the selection responsibility and what happens when the actual information differs.
Do not describe an allowance as a spending suggestion detached from specifications, quantity and responsibility. The allowance explanation guide gives a meeting method that ties each category to plan sheets, selection records and written changes.
For assumptions, state the missing fact and the planned check. "Site condition to be verified through the identified review" is more honest than a polished sentence that sounds final. The applicable agreement controls how resulting changes get handled.
What happens after the presentation?
Send the same proposal version you presented, along with a question log. Do not circulate edited copies under the same filename. Use revision markers and keep the prior version so the buyer and the internal team can see what changed.
Sort questions into clarification, missing information, scope revision and agreement review. Clarification may point back to an existing section. Missing information needs an owner. Scope revision needs a new review. Questions about obligations get answered through the governing document and professional review, not an informal sales message.
If the buyer is ready for a defined planning phase, move to preconstruction agreements. The Operating profile stage keeps the proposal language in step with your real handoffs. For the larger public explanation, use the written build process guide.
The Claude and Codex agents we run compare the presented version with meeting notes, organize open questions and flag inconsistent terms. A person approves every revision and decides whether a question changes scope. No agent silently rewrites a responsibility or turns a verbal discussion into acceptance.
What do builders ask about proposal review?
Should we send the proposal before the meeting?
Use a consistent policy for sending builder proposals before presentation. If buyers get a proposal early, label it for review and schedule a walkthrough of scope, assumptions and open items.
What if the buyer wants an immediate revision?
Record a requested builder proposal revision, identify the affected sections and issue a new version after the responsible reviewers check dependencies. Keep the version presented at the meeting.
How do we answer a question that is not covered?
When a builder proposal does not cover a buyer question, record the open issue, the responsible reviewer and the next review point before you offer an answer.
Is the proposal the contract?
A builder proposal should explain its stated purpose and its relationship to later agreements. Check its intended effect with the builder's legal adviser before you describe it as a contract or a substitute.