Somewhere in the first ten minutes of most consultations, an owner says some version of the same sentence: “We need a new website.” That sentence hides two completely different projects, with different price tags, different timelines, and different risks. One is a redesign. The other is a rebuild. Choosing the wrong one is the most expensive mistake I see small organizations make with their websites, and it usually doesn’t show up as a mistake until eighteen months later.
Here is how to tell which project you actually have.
The two words mean genuinely different things
A redesign changes what visitors see. New layout, new typography, new color, reorganized pages, rewritten content. The platform underneath stays where it is. Same WordPress install, same database, same hosting, same content types, same editing workflow. You are renovating rooms, not moving the walls.
A rebuild replaces the structure. New templates, often a new build system, frequently new hosting, and content migrated on purpose rather than dragged across. Counterintuitively, the visible design after a rebuild is sometimes close to what you had. The work went into the parts nobody sees, which is exactly why rebuilds are hard to sell and easy to underestimate.
Most owners describe a redesign and need a rebuild. They have been living with a structural problem for so long that it has stopped registering as a problem. It just feels like “how our website is.”
Four questions that settle it
You do not need a technical audit to get most of the way to an answer. You need honest answers to four questions.
1. When you want to change a sentence, who does it? If the answer is you, and it takes two minutes, your foundation is probably fine. If the answer is “I email someone and wait three days,” that is not a design problem. No amount of new typography fixes it.
2. What happens when you add a new page? A site built on real templates lets you add the eleventh service page the same way you added the third. A site without them needs custom work every single time, which is why so many organizations have a website that stopped growing the year it launched. If every addition is a small project, the templates are the problem.
3. How much of what is installed do you still use? Open your plugin list. Count the ones you could not explain to a stranger. Sites accumulate abandoned features the way garages accumulate paint cans: a booking tool from a service you no longer offer, two competing form plugins, a slider nobody has touched since 2019. Each one is code running on every page load, and each one is a door someone left unlocked.
4. Is the slowness in the pictures or in the plumbing? Oversized images and too many scripts are fixable inside a redesign. A bloated theme fighting a page builder fighting a caching plugin is not. If you haven’t diagnosed which you have, start by testing your site speed and finding the usual culprits before you spend anything on visuals.
When a redesign is the right call
Redesign when the bones hold. Specifically: your platform is current and supported, you can edit your own content without help, your templates already cover the kinds of content you publish, and the actual complaint is that the site looks dated or does not convert.
That is a real and common situation, and it is good news. A redesign on a sound foundation is faster, cheaper, and far less likely to go sideways because you aren’t touching URLs, hosting, or data. The riskiest parts of a website project are the ones a redesign leaves alone.
When a rebuild is the right call
Rebuild when any of these are true, and do not let anyone talk you out of it:
- Your theme or platform is abandoned. No updates, no security patches, an author who has gone quiet. This is a deadline, not a preference.
- Every content change requires a developer. You are paying rent on your own website.
- Accessibility problems are structural. Heading order, form labels, focus handling, and keyboard navigation live in the templates. You can’t paint them, and you can’t solve them by dropping in a widget that promises compliance. If you are not sure where you stand, the ADA compliance checklist is a reasonable first pass.
- A series of hands built the site with no shared system. Four developers over nine years, each solving their own problem their own way. Nothing coherent remains to renovate.
- Commerce outgrew the setup. A store that started as an afterthought and now carries real revenue needs a foundation chosen for that job.
The expensive middle, and how to spot it
The pattern I have seen most often over twenty years of building these things isn’t a bad redesign or a bad rebuild. It is a redesign performed on a foundation that needed replacing. It goes well. Everyone is pleased at launch. Then, within two years, the same structural limits reassert themselves, and the organization pays twice for a project it should have done once.
The tell is in the proposal. If a proposal talks only about pages and visuals and never mentions templates, content types, hosting, redirects, or how you will edit it after launch, it is scoped as a redesign whether or not that is what you need. Ask directly: which of these problems does this proposal solve, and which does it leave in place? A straight answer to that question is worth more than a portfolio.
The inverse mistake is worth naming too: being sold a rebuild when a redesign would have done. The check is the same. If nobody can name a specific structural limitation the rebuild removes, you are buying it for someone else’s convenience.
How to scope either one honestly
Whichever project you have, three questions separate a firm that has done this from one that has not.
Ask about staging. Work should happen on a copy, not on the site your customers are using. Any shop that edits production directly is telling you something about how the rest of the project will go.
Ask what happens to your URLs. If pages move, old addresses need redirects, or you hand away search rankings you spent years earning. This five-minute conversation can save a year of recovery.
Ask who can edit what after launch. Get it specific: which pages, which sections, which content types, and with what training. This is the difference between owning a website and renting one. At Modus Medium, the handover is part of the work, not an upsell, because a site you cannot maintain starts decaying at launch. That standard comes from two decades of building for clients who needed the work to keep working: enterprise email programs for major appliance brands, national-scale e-commerce operations, and a number of client relationships now past their eighth year, including ongoing work with Maestro Filmworks.
For budget reference, website projects at Modus Medium start at $3,500 and care plans start at $200 per month. Those numbers are published rather than quoted privately, so you can tell whether a conversation is worth having before you have it.
Your next step
Do not book a consultation to ask “what would a new website cost.” That question cannot be answered usefully, and the answer you get will be a guess. Instead, bring three specific things to the conversation:
- A list of every change you wanted to make in the last twelve months but couldn’t make yourself. This single list distinguishes a redesign from a rebuild faster than anything else.
- Your current platform and hosting details, including who has access and when it was last updated.
- The two pages that actually make you money, so the work is aimed at them rather than spread evenly across pages nobody visits.
With those three things in hand, scoping takes about thirty minutes and produces a real answer instead of a range. You can see what website development and care plans involve on the Modus Medium services page, and when your list is ready, book a consultation.