Most web developers won’t tell you this. A new site means a new project, a new contract, new revenue. There’s not a lot of financial incentive to talk a potential client out of one.
But I’ve turned down work before, and I’ll do it again. Not because I don’t want the business, but because recommending something a client doesn’t actually need isn’t a good way to do business. And frankly, it’s a bad way to start a relationship.
So here’s how I actually think about it when someone comes to me wanting a new website.
What problem are you trying to solve?
This is always the first question. Not “what do you want the site to look like” or “what’s your budget.” What problem are you trying to solve?
A new website is one way to solve certain problems. It’s not the only way, and it’s often not the fastest or cheapest way. If someone comes to me saying they’re not getting enough leads, that might be a website problem. It might also be a search visibility problem, a messaging problem, or a traffic problem. A brand new site won’t fix any of those on its own.
Getting clear on the actual problem first changes the whole conversation.
When a rebuild makes sense
There are real, legitimate reasons to build a new site. The current one is on technology that’s genuinely limiting what you can do. The structure is so far gone that fixing it costs more than starting fresh. The brand has changed significantly and the site no longer reflects it. The site is slow, inaccessible, or broken in ways that compound over time.
These are problems a new site solves. When I see them, I say so.
When it probably doesn’t
If the site looks dated but works fine, that’s often a design refresh, not a rebuild. If traffic is low, a new site without a content or visibility strategy will be a new site with low traffic. If the main complaint is that the site is hard to update, that’s usually a training issue or a theme issue, not a ground-up problem.
I’ve talked to business owners who spent significant money on a brand new site and saw no change in inquiries because the underlying issues were never about the site. That’s a bad outcome for everyone.
What I do instead
When a full rebuild isn’t the right call, I’ll say so and tell you what I think would actually move the needle. Sometimes that’s targeted fixes to what exists. Sometimes it’s help with content. Sometimes it’s pointing you toward a resource that isn’t me.
That might sound like bad business. I think it’s the opposite. If I help you make a smart decision, even one that doesn’t turn into a project right now, you’ll remember that. You’ll come back when the time is right, and you’ll send people my way.
The goal isn’t to sell a website. It’s to help your business have a website that works.
I would love to hear if this kind of straight talk is what you’re looking for in a web partner. Let me know: hello@nomadigital.dev.