Custom Remodeling

Why Your Best Projects Aren't Selling You (And What Remodelers Should Show Instead)

Why beautiful project photos don't build trust—and what custom remodelers should show instead to convert high-end prospects.

I've reviewed dozens of remodeler websites over the past year—and in a few cases, helped rebuild them—and I keep seeing the same pattern.

Beautiful finished kitchens.

Stunning bathroom transformations.

Impressive before-and-after sliders.

All presented with almost no context.

The photos are professional. The work is clearly skilled. But something fundamental is missing.

These sites treat past projects like a gallery wall: here's what we built, here's another one, here's another. The assumption seems to be that quality work speaks for itself.

It doesn't.

In my experience reviewing remodeler sites—and building a few of these myself—the projects that convert aren't the prettiest ones. They're the ones that explain decisions.

If you're a custom remodeler or luxury builder working on projects that cost $75,000 or more, your website isn't competing with other portfolios. It's competing with a homeowner's anxiety about hiring the wrong contractor.

That anxiety has very little to do with style—and almost everything to do with trust.

The Portfolio Dump Problem

Most remodeler websites present projects the same way:

  • Project title

  • Location (sometimes)

  • Three to five shots of the finished space

  • Maybe a before-and-after comparison

  • Occasionally a short description like: "Complete kitchen renovation featuring custom cabinetry and quartz countertops."

Then on to the next project.

This approach makes sense if you assume people hire remodelers based purely on aesthetic preference. But that's not what's actually happening in the decision process.

When someone is vetting contractors for a $100,000 kitchen remodel or a $200,000 addition, they're not just asking: Do I like their style?

They're asking:

  • Can this contractor handle unexpected problems?

  • Will they communicate when things go wrong?

  • Do they understand how real projects actually unfold?

  • Have they dealt with situations similar to mine?

A gallery of finished photos doesn't answer any of those questions. It just shows that you can execute when everything goes according to plan.

Most remodeler portfolios fail not because the work isn't good—but because they're silent where homeowners are most nervous.

What "Storytelling" Actually Means

When I talk about storytelling, I'm not talking about dramatic narratives or manufactured conflict.

I'm talking about showing the decisions and tradeoffs that define real remodeling work.

That means answering questions like:

What problem were you actually solving?

Not the obvious one ("they needed a new kitchen"), but the specific constraint that made the project challenging. Was it an awkward floor plan? A load-bearing wall in the wrong place? A homeowner trying to modernize a 1920s craftsman without erasing its character?

What did you recommend—and why?

This is where judgment shows up. If you suggested a specific layout, material, or approach, explain the reasoning. What were you optimizing for? What options did you rule out—and why?

What tradeoffs did the homeowner have to make?

Every project involves compromise. Budget versus timeline. Function versus aesthetics. Original vision versus structural reality. Being honest about this builds trust because it shows you're not pretending the process is simpler than it is.

What happened that wasn't in the original plan?

This is the part most remodelers avoid—and it's often the most persuasive. Did you discover something during demo? Adjust when materials were delayed? Find a better solution mid-project? Homeowners already know things don't go perfectly. Showing how you handled it proves competence.

A Practical Example

Here's the difference in practice.

Portfolio dump approach:

Craftsman Kitchen Remodel – Chapel Hill

Complete kitchen renovation featuring white shaker cabinets, subway tile backsplash, and butcher block island. Custom pantry storage and new lighting throughout.

[Five photos of the finished space]

Storytelling approach:

Working Around a Load-Bearing Wall That Couldn't Move

The homeowners wanted an open-concept kitchen, but the house had a load-bearing wall exactly where the island needed to go. Removing it would have added roughly $15,000 in structural work before the remodel even started.

Instead, we kept the wall and turned it into an architectural feature—wrapping it with matching cabinetry on both sides, adding open shelving on the living room face, and using it to mount pendant lighting. The wall became intentional rather than something to hide.

The tradeoff: the kitchen isn't quite as open as they originally imagined.

The benefit: they got the function they needed at about 40% less cost, and the wall gives the space more definition than a fully open floor plan would have.

[The same five photos—but now they illustrate a decision process]

The second version does something the first doesn't.

It shows how you think.

When Less Detail Is Actually Better

There's an important tradeoff here that makes this harder than it sounds.

Not every project needs—or deserves—a full narrative treatment.

If you've completed 50 projects and you write 800 words about each one, your website becomes exhausting to navigate. More importantly, you dilute the impact of the projects that actually demonstrate judgment.

What I usually recommend looks like this:

Flagship projects (3–5): Full narrative treatment. These are the projects that best show how you think, solve problems, and navigate constraints. Aim for 400–600 words.

Standard projects (10–15): Brief context plus one key decision point. Around 100–150 words. Enough to show it wasn't paint-by-numbers work.

Gallery projects (everything else): Photos only, minimal text. These establish volume and aesthetic range, but they're not doing the trust-building work.

This structure gives serious prospects something meaningful to evaluate—and casual browsers enough visual context to understand your style.

The Wrong Situations for This Approach

Storytelling doesn't work for every remodeler, and pretending it does would be dishonest.

If your projects are genuinely formulaic, narrative treatment won't help because there's no story to tell. If you repeat the same layout with minor variations, lean into that as a strength: specialization, refined process, predictable outcomes.

If your market competes primarily on price, storytelling is probably irrelevant. Homeowners shopping on cost aren't reading 500-word project descriptions—they're comparing bids.

If you're already booked 12 months out from referrals alone, your website's job is different. It's not about persuasion; it's about filtering and setting expectations.

If your typical project is under $30,000, the decision process is faster and less anxious. People aren't agonizing the way they do over a six-figure addition.

This approach works specifically for remodelers doing complex, expensive work where trust—not preference or price—is the primary barrier.

What This Actually Looks Like in Practice

When I build sites for custom remodelers, project pages usually include:

  • A brief project overview (the basics)

  • The challenge or constraint that made it interesting

  • One or two key decisions and why they were made

  • What the homeowner was optimizing for—and what they weren't

  • Honest acknowledgment of tradeoffs or limitations

  • Photos that illustrate decisions, not just finished aesthetics

This isn't about writing more. It's about writing differently.

The goal isn't to impress people with your projects. It's to show that you think clearly when things don't go perfectly.

Those are the qualities homeowners are actually trying to evaluate when they're deciding whether to trust you with $150,000—and six months of their life.

Most remodelers already do this work. They make these decisions, navigate these tradeoffs, and solve these problems every day.

They just don't show it on their websites yet.

The portfolio is already there.

The storytelling simply makes explicit what you already know about how the work actually happened.

Ready to Build a Website You're Actually Proud of?

Reach out and let's get a conversation going

Reach out and let's get a conversation going

Reach out and let's get a conversation going

import * as React from "react" export function useReportHeight() { React.useEffect(() => { // 1. Function to send the current scrollHeight to the Parent (Framer) const sendHeight = () => { const height = document.documentElement.scrollHeight window.parent.postMessage({ type: "reportHeight", height }, "*") } // 2. Create an observer to watch for any size changes in the body const observer = new ResizeObserver(() => { sendHeight() }) if (document.body) { observer.observe(document.body) } // 3. Initial call to set the height on first load sendHeight() return () => observer.disconnect() }, []) }