Your site is not performing. Somebody suggests a rebuild. It is a large number and a long project, and you have no way to judge whether it is necessary.
Here is how to work it out yourself, before anyone quotes you.
Start with the diagnosis, not the treatment
The mistake is deciding on a rebuild before establishing what is wrong. A rebuild is a treatment, and prescribing treatment before diagnosis is how people spend a lot of money and end up with a prettier version of the same problem.
So first, get specific about the symptom. “It’s not working” is not a diagnosis. These are:
People arrive and leave immediately. People cannot find what they need. People find what they need but do not make contact. Nobody arrives at all. It looks unprofessional next to competitors. It cannot be updated without help. It is broken on phones.
Each of those points somewhere different, and only some of them are about the website at all. If nobody arrives, your problem is upstream of the site and a rebuild will not solve it.
The case for fixing
Repairs are the right answer more often than the industry admits, because the industry is paid for rebuilds.
Fix if the structure is sound and the problems are specific. Slow loading, an untappable phone number, a confusing homepage sequence, missing evidence, outdated content. These are afternoon jobs on an existing site.
Fix if it works on phones. Mobile capability is the dividing line. A site that is genuinely responsive can usually be improved. A site built before mobile mattered, that only works on desktop, generally cannot be patched into shape.
Fix if you can edit it. If you or someone in your business can update text and images without paying a developer, that is a functioning asset worth improving.
Fix if you are under two years old. Early businesses change what they sell. Building an expensive site around a proposition that will shift in eight months is a common and avoidable waste.
The case for rebuilding
Rebuild if it does not work on phones. Not “looks a bit cramped.” Genuinely broken. Sideways scrolling, unreadable text, buttons that cannot be tapped. Retrofitting responsiveness onto a site that never had it usually costs more than starting again.
Rebuild if nobody can edit it. A site where every text change requires a developer will not be maintained, and an unmaintained site decays into a liability regardless of how good it looked at launch.
Rebuild if the platform is dead or unsafe. Abandoned software, unpatched, unsupported. This is a security issue and not really a marketing decision.
Rebuild if the business genuinely changed. Different services, different market, different name. When the underlying proposition changed, the structure usually has to.
Rebuild if you have tried fixing and measured no change. Note the word measured. Fixed it, gave it a fair period, compared like with like, and nothing moved.
The question that resolves most cases
Ask this: if every specific problem I can name were fixed on the current site, would I be satisfied?
If yes, do not rebuild. Fix the specific problems. You have just described a repair job and the answer is not a new site.
If no, and you cannot articulate what else is wrong, be careful. That usually means the dissatisfaction is aesthetic or emotional rather than functional. Sometimes that is legitimate, because looking dated has a real cost when you are quoting against competitors. But it is worth being honest that this is the reason, rather than dressing it up as performance, because it changes what you should be buying.
Getting an assessment you can trust
The person telling you what to do usually stands to be paid for the answer. That does not make them dishonest, but it is a real bias.
Ask for the diagnosis separately. “Before we discuss a rebuild, tell me what specifically is wrong with the current site.” A good answer is a list of concrete issues. A vague answer about it being outdated is a warning sign.
Ask what a repair would look like and cost. If they refuse to consider repairs at all, that is information about them rather than about your site.
Get the free evidence yourself first. Run PageSpeed Insights. Do the phone test at evening brightness with one thumb. Have somebody who does not know your business try to find your prices while you watch. That gives you an independent picture before anyone quotes.
Ask what happens to your search presence. A rebuild done carelessly can lose accumulated ranking, because URLs change and redirects get missed. Anybody competent will raise this before you do.
The middle option nobody offers
There is a third path that rarely gets proposed because it is less profitable: a targeted rework.
Keep the platform, keep the structure, replace the homepage and the two or three pages that matter, fix the speed, replace the stock photography with real work, and leave the rest alone.
This is frequently the correct answer for a small business. It addresses the pages that actually get seen, costs a fraction of a rebuild, and takes weeks instead of months. If your site is fundamentally sound but the important pages are weak, ask specifically for this and see what comes back.
An order of operations
If you are unsure, do it in this sequence and stop as soon as things improve.
First, fix what is free. Speed, tappable phone number, correct details, real photos, homepage sequencing. Days of work, little or no money.
Then measure. Give it a fair period and compare against the same period last year, not last month, especially if your business is seasonal.
Then rework the key pages if the fundamentals are fine but the important pages are not doing their job.
Then rebuild, if you have done the above and the constraint is genuinely structural.
Most businesses that follow this order never reach step four, and the ones that do reach it arrive with a clear brief and evidence about what was actually wrong, which produces a much better rebuild than starting from a vague dissatisfaction.
The honest summary
Rebuilds are sometimes necessary and frequently oversold. The tell is whether anyone diagnosed the problem before proposing the treatment.
Do the free diagnosis yourself. Write down the specific failures. Then ask whether fixing that list would satisfy you.
Most of the time it would, and most of the time nobody asked.
What a rebuild actually involves
If you do decide on one, knowing the shape of the project helps you judge quotes and spot omissions.
Discovery and structure. What pages exist, what each is for, what the site is trying to achieve. Skipping this is how you end up with a prettier version of the same problems.
Content. Somebody has to write the words and supply the photographs. This is the step that delays most rebuilds, because businesses assume the designer handles it and designers assume the business does. Agree explicitly who is doing it before you start.
Design and build. The visible part, and usually the shortest.
Migration and redirects. Every old URL needs to point to its new equivalent. Get this wrong and you lose accumulated search presence, which is a genuinely painful and entirely avoidable loss. Ask about it specifically.
Testing. On real phones, on cellular, by somebody who is not the person who built it.
Handover. Can you edit it? Do you own the domain, the hosting and the accounts? Get answers in writing.
That last point matters more than it sounds. A rebuild that leaves you unable to change your own text, or unable to access your own domain, has replaced one dependency with another.
The question to ask yourself in a year
Whichever route you take, the outcome worth aiming for is a site you can and will maintain.
The most common cause of a bad website is not a bad build. It is three years of nobody touching it. Services changed, prices changed, staff left, photos aged, and nothing got updated because updating required a phone call and an invoice.
So when comparing options, weight this heavily: after this project, can somebody in my business change the text and swap a photo without paying anybody?
If the answer is no, you are buying something that will decay on a schedule, and you should factor that into the comparison alongside the price.
The seasonal timing question
One practical consideration that gets ignored and occasionally costs a lot.
Do not rebuild during your busy season.
A rebuild needs your attention: content, decisions, feedback, testing. If it lands during the eight weeks when your phone does not stop, one of two things happens. Either the project stalls because you cannot respond, or it ships without your proper review because you were too busy to look.
There is also risk in changing your site right before the period when it matters most. Migrations occasionally go wrong, redirects occasionally get missed, and the worst time to discover that is the week your customers are actively searching.
Rebuild in your quiet season, launch before the busy one starts, and give yourself a few weeks of buffer to catch problems.
This article contains no statistics and no pricing claims. Where numbers appear elsewhere on this site, they are measured with free public tools or cited to a named source.