Most building projects at Lake Atitlán follow the same sequence: hire an architect, get drawings, find a contractor, break ground. The problems usually start at step three. By the time a contractor sees the drawings, the decisions that most affect what a project costs are already made. Materials are specified. The structural approach is fixed. The layout is locked. The contractor can price it, but cannot improve it.
Integrated project delivery, otherwise known as IPD, changes that sequence. The builder is in the room when the building is still being designed. Not to approve the work, but to contribute to it. Construction knowledge at the design stage changes what gets designed. It changes what materials get specified, how systems are sequenced, where the money actually goes. That is the core argument for integrated delivery, and it is the reason Atitlán Build is structured the way it is.
The decisions that most affect what a project costs are made in the first ten percent of the timeline. IPD puts the right knowledge in the room at that moment.
What design-bid-build actually looks like
In a traditional design-bid-build project, the architect works largely independently until drawings are complete. Then the project goes to bid. Multiple contractors price the work competitively. The lowest qualified number usually wins.
The problem is not the competition, it is the timing. By bid day, the owner has already lost most of the ability to influence cost without paying for redesign. The contractor who wins is pricing a finished design, not contributing to one. If that design has expensive assumptions baked in, those assumptions get priced, not questioned.
This is how a project can come in over budget before a single shovel goes in the ground. The design was complete. The cost was a surprise anyway.
Design–Bid–Build
- Who's in the room
- Architect first; the builder arrives only after bidding
- Builder joins at
- Bid day — the design is already complete
- Where the risk sits
- The owner absorbs the gap between design and price
Design–Build
- Who's in the room
- Designer and builder as one entity
- Builder joins at
- Early — the same team designs and builds
- Where the risk sits
- Shared inside the design-build entity
IPD / ECI
- Who's in the room
- Owner, designer and builder together from day one
- Builder joins at
- Schematic design — before decisions lock
- Where the risk sits
- Surfaced and priced before the ground breaks
What IPD and early contractor involvement change
Early contractor involvement (ECI) is the version of this principle that works at project scales common to Lake Atitlán. Rather than a full multi-party contract structure, ECI means the contractor joins the project at schematic design, contributing budget feedback, constructability input, and logistics knowledge before decisions get locked.
At Atitlán, where every project carries the variables of boat logistics, community relationships, wet season timing, and material lead times, that construction knowledge is not optional. It is the primary design input. A layout that looks efficient on paper may require materials that add a 30 percent logistics premium. A structural system that reads simply in section may be impossible to execute with the labor available. Finding those mismatches at design is a rounding error. Finding them at construction is a change order.
What ECI looks like on a typical lake project
At Atitlán Build, early contractor involvement typically begins at schematic design — before any structural system is selected, before materials are specified, and before the layout is locked. At that stage, the cost of changing a decision is low. The cost of not changing it can follow a project all the way to completion.
In practice, ECI at the lake means the contractor reviews the emerging design against four variables that an architect working remotely will not have current knowledge of: material availability and lead times, logistics costs from the point of delivery to the actual building site, local labor capability for the systems being specified, and wet season access windows that affect when certain phases can realistically be executed.
The output of that review is not a report. It is a set of specific recommendations — whether that be a concrete block wall instead of the imported brick that adds three boat loads, a roof detail adjusted to handle the rainy season load the original spec would not have survived, or a phase sequence that keeps the access road clear until the foundation is poured. These are not value engineering concessions. They are construction knowledge applied before the design is finished, which is the only time that knowledge is free.
On a typical residential project at the lake in the $200,000 to $500,000 range, the ECI phase runs four to eight weeks depending on the responsiveness of your team and you. What it produces is a design that has been tested against construction reality before anyone breaks ground. In reality a one to two month review period to make sure a thirty-plus year build stands the test of time is one of the best development decisions that can be made.
What this looks like in practice
The best example I can give from personal experience comes from a concrete buyout on a $120 million, 43-story apartment tower in Miami. We needed to find $10 million in savings before construction could start, and we were not going to get there by cutting quality.
During a negotiation with the second-lowest concrete subcontractor, my boss noticed something in their bid: they had assumed 20 hours per week of crane access and a 16-month schedule. He asked a simple question. What would happen if we paid a crane operator their rate of $200 an hour to run the crane an extra 8 hours every Saturday, dedicated entirely to the concrete and formwork trade?
The answer was a 40 percent increase in productive time for that sub. They reduced their bid by $1.3 million because their skilled labor could put work in place instead of moving material. They also cut two months off their schedule. Our construction loan was carrying $500,000 a month in interest. Two months saved was worth $1,000,000 — not counting the benefit of reaching the market faster. Total value created: $2.2 million, with a healthy $100,000 bonus for the crane operator. No quality compromise. No margin cut on the subcontract.
That is what early, integrated problem-solving actually looks like. The solution was not a design change or a spec reduction. It was a scheduling insight that only existed because the owner's team was deeply inside the buyout process, not reviewing bids at arm's length.
On a hospital project in San Francisco, our team used an Integrated Form of Agreement that placed the owner, architect, general contractor, the mechanical, electrical, plumbing, and fire protection subcontractors, and the concrete shell contractor all under a single contract. Fifty percent of any savings below the target cost went to the owner. The rest was split among the project team. That structure made collaboration the financially rational choice — not just a best practice, but an incentive.
Before a single piece of work went into the ground, trades coordinated using clash detection: finding and resolving conflicts between structural elements, ductwork, piping, and electrical before they became field problems. Solving a coordination issue on screen takes minutes. Solving it in the field costs time, material, and money.
A smaller example, but one that has stayed with me. On a mid-rise residential project in Tampa, we were slightly over budget during construction and the team was watching every line item carefully. When it came time to select the exterior paint color for the building, my boss proposed spending $30,000 to scaffold two bays in front of the pool deck and paint both finalist colors on six stories of the actual building before committing to the full contract.
I thought it was an unnecessary cost. We had color boards. We had renderings. We knew what we were selecting.
What we did not know was that the color we were planning to use turned the shade of sewage green when direct sunlight hit it at golden hour. It looked fine on a chip. On six stories of building facing west, it was not fine. We selected the other color and spent $30,000 to learn that.
The full paint contract was $300,000. Had we discovered the problem after the building was painted, remediation would have cost more than the original contract. The $30,000 validation spend was not a luxury. It was the cheapest risk mitigation on the project.
Early validation costs money. Not validating costs more. That is the principle behind ECI, applied at every scale.
How this applies at Lake Atitlán
The scale is different. The principle is not. On a $300,000 residence at the lake, the owner does not need a multi-party contract. They need a builder who understands the design before the design is final, who can tell the architect that the stone specified for the terrace adds three extra boat loads, or that the roof detail proposed will trap moisture in the wet season.
That is what Atitlán Build offers through ECI: construction knowledge early, when it can still change outcomes. The contractor who arrives at bid day with finished drawings is pricing the project. The contractor who was in the room when those drawings were made helped shape them.
The difference shows up in the budget. It shows up in the schedule. And it shows up in the building itself, because the decisions that went into it were made with full information.