Most businesses that pay for a redesign needed a rebuild, and find out about eight months later when the same problems come back wearing nicer colours.
The distinction matters because the price difference is large and the outcomes are completely different. A redesign changes how your site looks. A rebuild changes how it works.
Here is how to tell which one you actually need.
1. Every Change Requires a Developer and a Week
You want to update pricing. Add a team member. Change a headline. If any of that means emailing someone and waiting days, your site is not a business asset — it is a dependency.
A redesign will not fix this. It is a structural issue: content is hardcoded rather than managed. A rebuild with a proper content layer means you make those edits yourself, in a browser, in a minute.
Signal strength: strong. This one alone often justifies a rebuild on time savings.
2. It Is Slow, and Nothing You Have Tried Has Fixed It
You have installed the caching plugin. You compressed the images. It is still slow on a phone.
At that point the problem is usually foundational — too many plugins each loading their own assets, a bloated theme, or a hosting setup that cannot serve pages quickly regardless of caching. You cannot optimise your way out of it.
Test it honestly at pagespeed.web.dev and read the mobile tab, not desktop. If your Largest Contentful Paint is above four seconds after real optimisation attempts, you are looking at a rebuild.
3. Traffic Is Fine, Enquiries Are Not
This one is frequently misdiagnosed as a design problem, and sometimes it genuinely is. But check the mechanics first:
- Does your contact form actually deliver? Test it. Then check spam.
- Does it work on a phone? A large majority of your visitors are on one.
- How long does the page take to become usable on a mid-range Android?
A meaningful share of "our website does not convert" turns out to be a broken form, a form that silently fails on mobile, or a page so slow that people leave before seeing it. Those are rebuild problems dressed as design problems.
4. It Is Not Actually Usable on a Phone
Not "it resizes" — genuinely usable. Tap targets you can hit. Text you can read without zooming. Forms you can complete one-handed.
Many older sites are technically responsive and practically miserable on mobile. If mobile usability was bolted onto a desktop-first build, retrofitting it properly is usually more work than rebuilding mobile-first.
5. You Are Afraid to Touch It
There is a plugin nobody dares update because last time something broke. A page nobody understands. A developer who left and took the context with them.
That fear has a real cost: it stops you improving the site at all, and it means security updates go unapplied. An unmaintained site is a security problem waiting to become a public one.
Signal strength: strong. Fear is a reliable indicator of foundational debt.
6. Adding Anything New Means Another Plugin
Need a booking form? Plugin. Testimonials? Plugin. A slightly different layout? Plugin.
Each one adds code, database queries, a potential security hole and another thing that can break on update. Sites accumulate these until the plugin stack is the site, and nobody can say what most of them do.
If your answer to every new requirement is another dependency, you have outgrown the setup.
7. Your Content Lives in the Wrong Place
Product details in a spreadsheet. Team bios in a Word document. Pricing in three places that disagree.
This looks like an organisational problem but it is architectural — the site was never designed to hold structured content, so it leaked out into wherever was convenient. A rebuild with a real content model puts it back in one place, with one source of truth.
When a Redesign Genuinely Is the Right Call
To be fair to redesigns — they are correct when:
- The site is fast and works properly, it just looks dated
- You can already edit content yourself without help
- Your brand changed and the site needs to match
- The structure is sound but the messaging is wrong
If your only real complaint is aesthetic, a redesign is both cheaper and correct. Do not let anyone upsell you a rebuild you do not need.
The Honest Test
Ask yourself one question: if the site looked exactly as you want but behaved exactly as it does now, would you be satisfied?
If yes — redesign. If you would still be frustrated by the speed, the editing, the breakages — no amount of visual work will help. That is a rebuild.
What a Rebuild Costs and Involves
For a typical business site: ₹1.5–5 lakh, four to ten weeks. Less than most people expect, because modern frameworks handle a great deal that used to be custom work.
Two things must be handled properly or you will lose search rankings:
- A complete redirect map. Every old URL points at its new equivalent. This is the single most common way rebuilds cause damage.
- Server-rendered content. If your pages only assemble in the browser, search engines see less than they should.
Done properly, a rebuild usually improves rankings, because the result is faster and technically cleaner than what it replaced.
Not sure which side you are on? Here is how I handle rebuilds and migrations, or send me your URL and I will tell you honestly whether you need a rebuild or just a good afternoon of optimisation.