If you only read two sections
Then decide if you need the deeper detail.
The short answer
Architect-led projects fail when the architect owns design intent, the builder owns execution, and nobody owns integration.
Design-build reduces drift by placing:
- scope
- budget logic
- procurement
- coordination
- recovery behavior
under one accountable posture. If you prefer architect-led, you can still get predictability. You just have to structure it intentionally.
Already working with an architect?
If you are already working with an architect and want to involve us early, we do that through a short paid Preconstruction Alignment Sprint. The goal is not to redesign the house. The goal is to make scope and assumptions real, align procurement and coordination posture, and confirm the team structure will produce predictable outcomes before months are burned.
Why this becomes a problem in Costa Rica
In more mature markets, integration is enforced by the system itself:
- tighter documentation norms
- more comparable bids
- deeper subcontractor ecosystems
- stronger contract enforcement and inspection predictability
In Costa Rica, the system tolerates ambiguity early and punishes it later. When responsibility is split, the gaps are wider. And the penalties are higher.
Where accountability disappears (the three gaps)
Most budget drift traces back to one of these.
Gap 1. Design is real. Scope is implied.
An architect can produce a beautiful design that implies a certain execution level. But unless scope is written, the same design can be built at multiple standards.
When scope is implied, the budget is fiction.
Owners usually do not realize this until:
- glazing systems are chosen
- detailing decisions arrive
- import lead times surface
- substitutions begin appearing
Gap 2. The budget is owned by nobody
The architect produces a budget. The builder produces a different reality. The owner absorbs the delta.
Usually nobody is lying. They are operating in a structure where:
- architect budgets are not commitments
- builder pricing is not anchored to the same scope
This is the most common “how did it get 40 percent more expensive” story.
Gap 3. Coordination lives in the cracks
Who coordinates:
- glass vendors with steel detailing
- waterproofing with roof edge conditions
- MEP routing with structure and ceilings
- cabinet tolerances with wall reality
- pool systems with power and drainage
If the architect believes the builder coordinates, and the builder believes each trade coordinates itself, coordination is nobody’s job until something fails. That is when the owner gets pulled in. Usually too late.
How to structure architect-led builds so they don’t drift
If you want architect-led and still want predictability, these guardrails matter.
1) Integrate the builder early
Not after design is done. Early enough that:
- structural intent meets procurement reality
- detailing choices meet serviceability
- the budget reflects actual scope
This prevents the “we designed something that cannot be built for that number” trap.
2) Make scope explicit and comparable
You need written clarity on:
- glazing performance level
- envelope and waterproofing standards
- structural complexity assumptions
- systems scope (pool, HVAC, backup expectations)
- finish level and fabrication complexity
- what is included versus excluded
Without this, bids are stories, not numbers.
3) Establish a procurement strategy
Decide early:
- what will be imported
- what will be sourced locally
- what gets locked
- what is allowed to float
Improvised procurement creates reactive cost and schedule behavior.
4) Assign integration responsibility explicitly
Write it down. Do not assume. Who owns:
- trade coordination
- clash resolution
- substitution approvals
- schedule impacts
- budget tracking against scope
If the answer is “everyone,” it is nobody.
5) Formalize change control
Changes happen. The question is whether they are:
- explicit
- priced fairly
- tied back to scope and assumptions
- decided calmly
Informal change handling is how drift stays invisible until it is painful.
How we structure accountability at Edificio
Our contract structure is not ideological. It is chosen to match how much of the construction scope has been made real.
The deciding question is simple: Who ultimately controls and validates the construction scope before pricing risk is taken?
| Project starting point | Typical contract posture | Why this works |
|---|
| Full design-build with Edificio | Fixed price | Because we control the design, scope definition, and budget logic from day one, we can take on pricing risk. Accountability is total and centralized. |
| Architect-led project with early technical alignment | Often fixed price | If scope is fully validated through a deep technical alignment process, pricing risk can still be absorbed responsibly, even when the architect is external. |
| Architect-led project with unresolved assumptions | Preconstruction Alignment Sprint → contract determined after | When drawings exist but scope is still implied, assumptions are made explicit before a construction contract is selected. |
In all cases, the objective is the same: the owner does not become the integrator. The contract model may change. The accountability does not.
What design-build changes (and what it doesn’t)
Design-build does not guarantee perfection. It changes one thing: accountability posture.
In strong design-build:
- responsibility cannot be deflected
- procurement is planned as part of design
- scope becomes real earlier
- recovery behavior is owned, not debated
Design-build is not about skipping architects. It is about keeping the owner out of the integration gap.
A neutral way to choose without ideology
Choose architect-led if:
- you care most about pushing design
- you want a specific architect’s vision
- you are willing to be involved
- you will integrate the builder early and enforce guardrails
Choose design-build if:
- you care most about calm execution and predictable outcomes
- you want one accountable posture
- you are remote
- you want decisions reduced, not multiplied
Neither is morally better. One is structurally calmer.
Where this fits in the Edificio process
If you’re a fit for how we work, the next step is simple:
- Clarify scope and assumptions
- Align on accountability posture
- Confirm who owns integration before pricing risk is taken
If accountability is not explicit early, drift is not a surprise. It is a default.
If you want to see how we think in real projects, browse our completed work and client feedback in the gallery.
Keep going
Next: Build Cost in Costa Rica
If accountability structure determines how drift is handled, cost structure determines how it accumulates. This guide explains how to get a number you can actually plan around.
Want help pressure-testing your structure early?
In a private consult, we’ll review your team structure and scope posture at a high level and tell you:
- Where integration risk sits
- What would need to be defined to make predictability realistic
- Whether architect-led or design-build is structurally calmer for your project
