I've worked under both systems. I've watched projects thrive under design-build approaches and others suffer from the traditional architect-bid-contractor model. The difference isn't subtle, and it matters more than most homeowners realize when making the choice between design-build vs. general contractor models.
Let me walk you through what each approach actually means, where they excel, and—most importantly—when you should choose one over the other.
The Traditional Model: Architect, Bid, General Contractor
For decades, this was the only real option. Here's how it works:
You hire an architect to design your renovation. The architect creates detailed plans, schedules, and specifications. You (or your architect) use those plans to get competitive bids from general contractors. You select a contractor based on price and reputation. Construction begins.
Sound straightforward? It is. And it has real advantages.
The traditional architect-led model works particularly well for projects where the design is stable, the scope is well-defined, and the contractor will build exactly what was drawn. It's proven. It's standard. Courts and contracts understand it.
But here's what I've seen happen over 40 years: this model creates a natural separation between design thinking and construction knowledge. The architect designs. The contractor builds. If the design has a construction problem—something that won't actually work as drawn, or that costs far more to build than anticipated—that becomes a conflict. The contractor wants changes; the architect defends the design; the owner pays for both the problem and the solution.
Even worse, the competitive bidding phase often creates pressure to low-bid, which means contractors cut their estimates to win the job, and then fight over change orders to recover profitability.
The Design-Build Model: Single-Source Accountability
Design-build means one entity—one company, one team—is responsible for both design and construction. I lead the design-build process for our projects. This changes everything about how decisions get made.
In design-build, the designer and the builder aren't adversaries with different interests. They're the same team. When I'm designing your kitchen renovation, I'm already thinking about how to build it, what materials actually work, where budget makes sense, and where premium choices pay off.
Here's what this looks like in practice:
You meet with the design-build team. We listen. We understand what you're trying to achieve. We sketch possibilities, discuss options, and develop a design concept collaboratively. The designer isn't creating a pristine ideal that someone else will fight to build. The builder isn't looking for ways to minimize cost while the designer dreams. It's all one conversation.
Once you approve the direction, the design work proceeds with full knowledge of construction methods, material availability, and honest cost implications. We can explore alternatives—"If we use this limestone instead, here's the actual cost difference and the performance trade-off." No surprises. No adversarial bidding.
When construction begins, the designer (me) is still involved. I'm not gone. If a better solution emerges as we're building, if we discover something unexpected, we solve it together as a team with you, not through change order disputes.
Design-Build vs. General Contractor: The Core Difference
The key distinction isn't just organization—it's philosophy.
With a general contractor in the traditional model, the contractor's job is to build what the architect designed. If the architect designed something that costs more than expected or doesn't work perfectly, that's technically not the contractor's responsibility. They build it anyway. Or they bid it wrong and lose money, creating pressure to cut quality.
In design-build, the builder owns the design from the start. We can't blame the designer for poor construction decisions because we're both. We can't bid low and make up the margin on change orders because we established the actual cost upfront. We can't separate the design vision from the buildability because they're integrated.
This alignment solves a lot of problems.
When Design-Build Is Clearly Better
Complex Renovations
The moment a project gets complex—multiple systems, structural changes, integration of indoor and outdoor spaces, or specialized finishes—design-build excels. Complexity requires constant communication between design and construction thinking. In the traditional model, you're playing telephone between architect and contractor. In design-build, there's one conversation.
I've renovated mountain resort properties in Aspen and Jackson where the complexity demanded this. A high-end kitchen that integrates with dining and living areas, that connects to outdoor views, that coordinates structural and mechanical systems, that sources materials from three different vendors—that project needs single-source accountability from design through completion.
Whole-Home Transformations
When you're reimagining your entire home—not just updating a kitchen, but rethinking how all the spaces work together, how systems integrate, how the interior connects to grounds—design-build is the right approach. The design vision needs to be consistent across the whole project. The execution needs to integrate these systems. A general contractor building from someone else's designs can execute the drawing. The design-build approach creates cohesion.
Budget Transparency
If you want to know where every dollar goes, design-build is clearer. You're not negotiating competitive bids between contractors who've already allocated different amounts to different line items based on their bidding strategy. You're working with one team that's building to an honest cost estimate and transparent markup.
When Design Integration Matters
Some projects succeed with traditional separation. A straightforward kitchen remodel with stock cabinetry and standard finishes can work fine with architect drawings and contractor bids. But the moment you want custom details, integrated design elements, material choices that require thoughtful coordination, or a vision that spans multiple rooms and outdoor spaces—you need the designer and builder thinking together.
That's where design-build wins.
The Traditional Approach Still Has Value
I don't want to suggest the architect-bid-contractor model is obsolete. It isn't.
For projects with simple scope, straightforward budgets, and clear specifications, the traditional model works fine. It also works well when you already have a designer you love and want to use them specifically, or when you have strong contractor relationships you want to maintain.
The traditional model also creates a different kind of check-and-balance. An independent architect can be a neutral observer of contractor performance. An independent contractor isn't beholden to the architect's design vision and can push back on unrealistic specifications.
But in my experience, those theoretical advantages matter less than the practical benefits of alignment. I'd rather have one team solving problems together than two teams with different incentives fighting over change orders.
The Single-Source Advantage: Eliminating Finger-Pointing
Let me be blunt about what happens in the traditional model when something goes wrong:
You call your architect. The architect says, "The contractor didn't build it right." You call the contractor. The contractor says, "The architect designed it wrong." Meanwhile, you're paying for the problem and the solution.
I've seen this dynamic countless times. A high-end stone installation in an Aspen home that had adhesion problems. The architect blamed the contractor for using the wrong mortar. The contractor blamed the design for not accounting for seasonal movement. The homeowner paid twice—once for the failed installation, once for the repair.
In design-build, that problem is my problem. Not my contractor's problem and my architect's problem—my problem. That changes everything about how seriously you take prevention.
There's no finger-pointing because there's nowhere to point. It's all one entity responsible for the outcome.
When to Hire a Remodeling Contractor (Traditional Model)
You might prefer the traditional approach if:
- Your project scope is genuinely simple and straightforward
- You have an architect you're already working with and want to use them
- You have strong relationships with specific contractors and want to maintain them
- You want independent oversight of the contractor
- Your budget is genuinely unlimited and cost is not a concern
Even in these scenarios, verify that your architect and contractor actually communicate. Some traditional projects work beautifully because the architect and contractor respect each other and collaborate. Others fail because no one's talking.
Design-Build for Complex Projects in the Willamette Valley
In my experience working with Oregon homeowners over the past few years, design-build is particularly valuable for whole-home transformations, kitchen and bathroom renovations with custom finishes, and projects that integrate indoor and outdoor living spaces.
The Willamette Valley market is sophisticated. Homeowners here often appreciate thoughtful design. They're not looking for generic renovations. They want spaces that work beautifully with their specific home, their specific landscape, their specific way of living.
That level of customization and integration demands the design-build approach.
The Trust Factor
This matters more than people admit. In design-build, you're trusting one team—one leader responsible for the entire vision and execution. In traditional contracting, you're hoping that two different entities with different incentives will coordinate effectively.
I've earned trust over 40 years by being responsible for the complete outcome. By being available during construction, not just in the design phase. By living with the consequences of decisions I make. That accountability shapes every choice I make in both design and building.
Making Your Decision
If you're considering a home renovation in Oregon and trying to decide between design-build and hiring a general contractor, ask yourself these questions:
- How complex is my project? (More complex = design-build advantage)
- Do I need a cohesive design vision across multiple spaces? (Yes = design-build advantage)
- Is budget transparency important to me? (Yes = design-build advantage)
- Do I want the designer involved during construction? (Yes = design-build advantage)
- Am I renovating multiple areas or is this a single-room project? (Multiple areas = design-build advantage)
If you answer yes to most of those, design-build is right for you.
I started my career working in traditional models in high-end resort communities. I've seen both approaches at their best and worst. The projects that turned out best—the ones homeowners lived in happily for decades, that actually increased in value, that integrated beautifully with how people really lived—those were almost always design-build projects where the designer and builder worked as one team.
It's not always the answer. But when it is, it changes everything about the outcome.
If you're exploring what a design-build approach might look like for your home renovation in the Willamette Valley, I'm happy to talk through your specific project, your vision, and what a partnership approach might achieve. Let's start with a conversation about what you're trying to accomplish.