Custom homes discussions and local services.
Discussion options
When should the builder join the design team?
We are at the beginning of schematic design for a custom home and are trying to define the architect-builder handoff before the drawings advance too far.
Our architect prefers to develop the design through schematic design and much of the construction-document phase before bringing a builder on board. The argument is that the design will be easier to evaluate without early pricing pressure. I am concerned that waiting could mean discovering constructability problems, structural complications, or unrealistic allowances after major decisions are already embedded in the drawings.
We have not finalized the structural system, several site-related issues remain unresolved, and the major exterior and interior finish selections are still open. We are also undecided between a fixed-price contract and a cost-plus arrangement. Those choices seem important because a builder involved during schematic design might provide useful estimating and sequencing input, while a builder brought in later might be able to price a more complete scope with fewer assumptions.
For those who have managed a custom build, when did you formally involve the builder or general contractor? Did you use preconstruction services during schematic design, obtain preliminary estimates at each design milestone, or wait until the construction documents were nearly complete?
I am especially interested in how the timing affected four things: the reliability of early pricing, the ability to change the design, responsibility for revisions caused by constructability issues, and the clarity of the architect’s and builder’s contractual roles. If the builder participates early, how did you prevent that input from quietly turning into design ownership or an implied commitment to a later construction price?
Join the conversation
Share your experience or ask a follow-up question.
2 replies
Your concern about structural and site issues becoming embedded is exactly where early builder input has the most value. A middle path is to engage the builder during schematic design under a limited preconstruction agreement, rather than handing over design control or waiting for near-complete construction documents.
That agreement can define:
- Estimates at schematic design, design development, and an agreed CD milestone
- A written list of assumptions, exclusions, allowances, and unresolved scope
- Constructability and sequencing reviews, including site logistics and structural coordination
- A stated fee for preconstruction work and how it converts, or doesn’t convert, into the construction contract
The architect can retain design authority while the builder tests whether the proposed systems and details are practical and within the target budget. Early numbers won’t be a fixed price, but they become more useful when each estimate identifies quantities, pricing basis, escalation, and contingency instead of presenting one apparently precise total.
This also helps with the fixed-price versus cost-plus decision. If the scope is still changing substantially, a fixed price may simply include larger contingencies and exclusions. A cost-plus arrangement can provide flexibility, but it needs clear cost definitions, fee structure, audit rights, and a process for approving allowances and changes.
The milestone estimates will be much more useful if they all use the same cost breakdown and a shared scope matrix. Otherwise, a change from schematic design to design development can look like a major price swing when the builder has simply moved an item from an allowance into a defined scope, or added an exclusion that wasn’t shown before.
I’d want each estimate to preserve the previous version and identify, line by line:
- what changed in the drawings or specifications
- whether the cost is based on quantity, allowance, subcontractor quote, or a rough unit rate
- which items are still excluded or unresolved
- the effect of design changes, escalation, and contingency separately
That creates a traceable conversation with the architect and builder. It also makes the fixed-price versus cost-plus choice less abstract, because you can see which parts of the project are genuinely defined and which are still carrying uncertainty.