Why We Turn Down Some Projects

We don’t take every project that comes through our door. That might sound like a strange thing for a business to say out loud, but after 40 years in this industry, we’ve learned that saying yes to the wrong project serves no one — not the homeowner, not our crew, and not the long-term reputation we’ve spent four decades building across Seattle and the Eastside.

This isn’t about being selective for the sake of exclusivity. It’s about being honest. Some projects aren’t a good fit for our team. Some aren’t a good fit for the homeowner’s actual goals. And some are projects where we know — from having seen this play out hundreds of times — that what the homeowner is asking for won’t produce the result they’re imagining. In those cases, the most helpful thing we can do is say so clearly, explain why, and point them toward someone better suited to what they need.

Here are the most common reasons we pass on a project, and what each one reveals about how we approach the ones we take on.

This is the most frequent reason we decline a project, and it’s also the most awkward — because nobody wants to hear that their budget won’t get them what they’ve described. But we’d rather have that conversation in the living room during the consultation than halfway through construction when the money runs out and the project sits unfinished.

Landscape construction in the Seattle area has real costs. Materials, skilled labor, equipment, engineering, permits — these aren’t flexible numbers. When a homeowner describes a full backyard renovation with a paver patio, retaining wall, irrigation system, and comprehensive planting plan, and their budget is $15,000, we have a choice: we can try to squeeze an inferior version of their vision into that number, or we can be straightforward about what that budget actually affords.

We choose straightforward. Sometimes that means suggesting a phased approach — do the structural and drainage work this year, add the patio next year, and handle the planting the year after. Sometimes it means scaling the scope to match the budget honestly. And sometimes it means acknowledging that we’re not the right company for this particular project at this particular budget, and recommending a smaller crew that can deliver good work at a lower price point.

What we won’t do is take the project knowing the budget will be exceeded, plan to address the shortfall with change orders mid-construction, or cut corners on materials and base preparation to hit a number. We’ve spent too many years fixing projects from companies that took that approach.

Classic Landscaping is a design-build and maintenance company. That’s what we do well. But “landscaping” is a broad term, and homeowners sometimes contact us for work that falls outside our wheelhouse.

We don’t install pools or hot tubs (though we design the landscape around them). We don’t build full outdoor kitchens with gas lines and plumbing — we’ll design the hardscape surround and connect you with a licensed plumber and gas fitter. We don’t do artificial turf installation — we have opinions about that, and we’re transparent about our preference for natural lawns, but more importantly, it’s a specialized skill set that dedicated turf companies execute better than we would.

When a project’s core scope falls outside what we do best, we refer the homeowner to someone who specializes in it. We’d rather lose a project than deliver mediocre work in an area where we don’t have deep expertise. In our experience, the companies that try to do everything tend to do nothing exceptionally well.

Seattle’s geography creates some challenging building sites. Steep slopes, shoreline setbacks, wetland buffers, critical areas mapped by King County — these conditions don’t make a project impossible, but they do change what “responsible construction” looks like.

Occasionally, we evaluate a property and determine that what the homeowner wants to build isn’t appropriate for the site’s conditions. A paver patio on a slope that needs a retaining wall system first. A planting plan that ignores the 60-foot Douglas fir canopy that will shade the entire bed by 2:00 PM. An outdoor living space positioned exactly where the property’s natural drainage corridor runs.

In these cases, we explain what we see and propose an alternative that works with the site rather than against it. If the homeowner’s heart is set on the original plan and isn’t open to the alternative, we step back. Building something we know won’t perform in our climate isn’t something we’re willing to attach our name to.

This happens most often on waterfront properties in Kenmore and Kirkland, where shoreline management regulations and slope stability constraints limit what can be built and where. We’d rather tell a homeowner upfront that their vision needs to be adapted than discover the constraints during construction when the options are fewer and the costs are higher.

Design-build landscape projects take time. A typical residential renovation — from initial consultation through design, permitting, and construction — runs 3 to 6 months depending on scope and season. Complex projects with engineered retaining walls, significant grading, or custom stonework can take longer.

When a homeowner needs a project completed in a timeframe that doesn’t allow for careful design, proper permitting, and quality construction, we explain what a realistic timeline looks like and why. Sometimes the deadline is flexible and we can make it work. Sometimes it’s not — a wedding in six weeks, a home sale in a month — and the homeowner needs a company that can move faster, even if that means fewer design options and a less customized result.

Rushing a landscape project rarely ends well. Concrete poured in the wrong weather conditions cracks. Plants installed without proper root preparation fail. Retaining walls built without adequate drainage behind them develop the problems we described in our article on the cost of waiting. We won’t compress our process below the point where we can guarantee the work.

This one is harder to articulate, but it matters. A design-build landscape project is a relationship. We’ll be on your property for weeks, sometimes months. Our crew will be in your yard every day. Decisions need to be made collaboratively — material selections, plant placement, grading adjustments as the site reveals itself.

Occasionally, during the consultation process, it becomes clear that the working relationship won’t be productive. Maybe the homeowner has had a bad experience with a previous contractor and, understandably, approaches the relationship with distrust that makes collaboration difficult. Maybe there’s a fundamental disagreement about process — a homeowner who wants to direct every construction decision rather than trusting our crew’s expertise, or one who expects a completely hands-off experience when the project genuinely needs their input at key decision points.

We don’t take these situations personally. A good working relationship requires trust flowing in both directions, and if either side senses it won’t be there, it’s better to recognize that early.

Every project we take on carries our name. When we install a retaining wall in Bellevue, our reputation is tied to whether that wall is still standing and performing 20 years from now. When we plant a Japanese maple in a Redmond front yard, our horticultural credibility is tied to whether that tree thrives or struggles. When we design an outdoor living space in Kirkland, our design judgment is tested every time the homeowner uses that space in a January downpour.

That’s why we’re careful about which projects we accept. Not because we don’t want the work, but because every project we complete either strengthens or weakens the standard we’ve built over 2,000+ installations across 40 years.

The companies that say yes to everything — every budget, every timeline, every scope — are making a different calculation. They’re optimizing for volume. There’s nothing inherently wrong with that, but it produces a different kind of work and a different kind of relationship.

We’d rather build 40 projects a year that we’re proud of than 80 where we compromised to fit.

We don’t just decline and wish you luck. When we pass on a project, we try to be specific about why, and we try to point you in a productive direction:

• If the budget is the constraint, we’ll tell you what your budget can realistically accomplish and suggest companies that work well at that price point.
• If the scope is outside our expertise, we’ll refer you to a specialist we trust.
• If the timeline is the issue, we’ll explain what’s realistic and let you decide whether to adjust the timeline or find a faster option.
• If the site conditions need a different approach, we’ll explain what we see and what we’d recommend — even if we’re not the ones who build it.

The consultation itself is always worth the time, even if we’re not the company that does the work. You’ll walk away with a clearer understanding of your property, your options, and what questions to ask the next company you talk to.

If you’re considering a landscape project and want an honest assessment of whether it’s a fit — for your property, your budget, and your timeline — we’re glad to have that conversation.