Redesign, Optimise, or Rebuild? A Decision Framework for Your Website's Architecture

When a client says "our website needs a redesign," what they usually mean is "something about our website is failing us" — and those are two very different engineering problems. Before touching a single component, we run three diagnostic questions: Is the platform itself sound (supported CMS, acceptable security posture, able to scale)? Is the UX/IA meeting business goals? Is the gap narrow enough to be a targeted fix (Core Web Vitals, a broken funnel, stale content)?

If the platform fails the first question — end-of-life CMS, plugin-stack fragility, no API-first path to the integrations the business now needs — no amount of new CSS fixes it. That's a rebuild: new architecture, often a move toward headless content delivery, and a proper data-migration plan. If the platform is fine but the experience layer isn't, that's a redesign: same CMS, same hosting, new design system and IA, content migrated across. If both pass and the problem is isolated — LCP, INP, CLS, a specific conversion funnel — that's an optimisation sprint, and it should stay scoped that way.

We cover the full cost breakdown (2026 India pricing: ₹35,000 for optimisation sprints up to ₹30,00,000+ for full platform rebuilds) and the complete decision framework in the original article: Website Redesign Cost in India 2026: When to Redesign vs Optimise vs Rebuild. Treat those ranges as indicative rather than a quote: page count, integrations and how much content has to move all shift the number, so scope your own site before you budget.

Curious how other teams have drawn this line — at what point did "redesign" actually mean "our CMS can't do this anymore" for you?