The first number a client sees from a design-build studio nearly always looks expensive. Set next to a design fee on its own, it should. The two are describing different amounts of work. The comparison people make in that moment is the one that tends to cost them later.
It helps to be clear about what the two arrangements actually are. In the conventional route you appoint a designer, receive a set of drawings, and then take those drawings to contractors for pricing. In design-build, the people drawing it and the people building it sit under one agreement. That is the whole difference, and everything below follows from it.
Where the money actually goes
A design fee buys drawings. It does not buy the resolution of everything those drawings did not anticipate. That resolution still happens. It just happens later, on site, under time pressure, and it gets paid for through variations.
Four things I see repeatedly, none of them dramatic on their own.
A material gets specified, and comes back priced differently because procurement found a different grade, a different thickness, or a lead time nobody asked about at design stage. The specification was not wrong. It was written without a price attached.
A detail looks straightforward on paper and turns out to be awkward to fabricate. It can be built, but it takes a skilled carpenter longer than the rate assumed, and the difference surfaces as a claim.
A client approves a design without anyone having explained what one decision inside it does to the budget. Nobody hid anything. The conversation about consequence simply did not happen, because the person who knew the cost was not in the room.
And a change comes late. Late changes are rarely expensive in themselves. They are expensive because of what has already been ordered around them.
Individually these are small. Together they are the reason a project that started at one number finishes at another.
Three questions asked at the same time
The advantage of putting design and execution under one roof is not that anyone becomes cheaper. It is that three questions get asked together instead of in sequence.
What are we designing. How will it be built. What will it take to deliver.
When those are separate conversations, held months apart by different companies, the gaps between them become the client's problem. When they are one conversation, buildability gets tested while the concept is still moving, and the specification gets written to be priced from rather than admired.
There is a second effect worth naming. When the same team carries a decision from drawing to installation, there is nobody to point at. That sounds like a burden and mostly it is. It also removes an entire category of argument.
What it does not mean
Design-build does not mean the project becomes cheap.
Good materials cost what they cost. Skilled workmanship costs money and is worth paying for. Proper detailing takes time, and time is the one thing everybody wants to compress.
What changes is control over how those resources get spent. Fewer surprises, fewer variations, fewer decisions made at the worst possible moment with a trade waiting.
I would also say plainly that design-build is not automatically the right structure for every project. If you already have a designer you trust and a contractor you have used for years, that relationship is worth more than any procurement theory. It suits projects where the programme is tight, where the specification is detailed, or where nobody on the client side has time to referee two companies.
The honest summary
Most of the money that goes missing on a project does not disappear into materials or labour. It goes into the gap between people, information and decisions. Somebody drew something, somebody else priced something slightly different, and somebody on site resolved the difference on a Tuesday without telling anyone.
Close that gap and the cost comes down, not because anything got cheaper, but because less was wasted crossing it.
- Design-build
- Cost
- Procurement
