Redesign or a brand-new site: figuring out what your business needs
The decision to rebuild a site is rarely made from a checklist — more often from fatigue with how it looks. That is the most common source of overspending in either direction.
Five questions worth asking first
Does the site work technically — no errors, acceptable speed, forms that don't fail? Can content be edited without pulling in a developer for every small change? Both are foundation questions; a 'no' means cosmetics won't help.
Does the site reflect current positioning and offerings, or is it still running two-year-old prices? Does the current structure serve the business's actual needs today — an account area, online payment, a filterable catalogue that didn't exist at launch? And last: what does the needed change actually cost — an interface tweak, or rewriting logic from scratch?
When the answers point to a redesign
The technical foundation is sound and content is self-editable, but the site looks dated or handles poorly on phones, and the business's needs haven't fundamentally changed. This is the most common and cheapest situation.
It also covers a conversion problem rather than a technology one: unclear navigation, weak calls to action, heavy forms — fixed by an interface rework without migrating platforms.
When you need a site from scratch
The platform is unsupported or slow with no room to optimise, needed integrations are physically impossible, every edit needs a developer you can't afford to keep on retainer, and business needs have outgrown the original structure.
In this case, building on top of the old platform is usually costlier and more fragile than a full rebuild — you pay twice, once for workarounds and then again for the redo.
What to protect either way
SEO inheritance transfers regardless of scale: inventory every URL, 301-redirect old addresses, carry text over with its key phrasing, and migrate structured data. The usual post-update traffic loss is not design — it's hundreds of pages returning 404 after the move.