A website project starts with what your business needs the site to do. You may want customers to understand a new service, make booking easier, improve an online store, or give your team a simpler way to publish updates. Those goals help determine whether to improve the current site or build a replacement.

Before choosing, take one important customer task and follow it from beginning to end. Can someone find the service, understand whether it fits, and take the next step? Then ask your team what it takes to keep that information current. This gives the discussion a concrete starting point.

When a focused improvement makes sense

An existing site can be a useful foundation when the platform supports the work you need and your team can maintain it. The next project might be a clearer set of service pages, a simpler menu, a repaired inquiry form, or a better route to booking.

Consider a business whose services have expanded since the site was written. If the pages and editing tools still work well, a content and navigation project could give customers the missing information. Rebuilding every page would add work without necessarily addressing a different need.

Ask a provider to name the changes, explain how they support the customer task, and identify what the project leaves for later. A focused scope should still include checks of the affected pages and contact routes.

When a rebuild deserves consideration

A rebuild becomes more useful when the current structure or platform makes important work difficult. Your team may struggle to update the site, the product catalog may require functionality it cannot support, or several overlapping workarounds may make each change expensive.

Describe those limitations specifically. "We need a modern site" is a reasonable ambition; "our team needs to update service availability by location" gives a designer and developer something to solve.

A replacement also needs a plan for the parts that already serve the business: useful content, established page addresses, search visibility, forms, account access, and integrations. Ask how those will be carried forward and checked at launch.

Compare the whole scope

Use the same questions to evaluate both options:

  • Customer tasks: Which services, products, and actions will become easier to understand or complete?
  • Content: What can be kept, what needs rewriting, and who supplies and approves it?
  • Daily use: Who will make updates, and what training or documentation will they receive?
  • Connections: What happens to booking, store, CRM, and reporting integrations?
  • Launch: Which existing pages need redirects, and how will important routes be tested?
  • Ongoing costs: What hosting, licenses, subscriptions, and maintenance will remain?

A repair and a rebuild can look quite different on price when one includes content, migration, and handover and the other leaves those tasks to you. Compare the responsibilities as well as the deliverables.

Make the first step useful

If the right option is unclear, a defined review can assess the current site against the tasks you need it to support. The useful output is a prioritized recommendation: what can be improved now, what would justify replacement, and what each approach depends on.

For example, a first project could cover three service pages, the menu that connects them, and the form customers use to inquire. A broader rebuild could follow when the business is ready. Another site may need its platform replaced before those improvements are practical. The recommendation should follow the actual situation.

Our website design and development work covers new builds and improvements to existing sites. For repairs or a planned move, explore site health and migration. If you have a proposal already, use the free Proposal Review Checklist to identify questions to discuss with the provider.