If your website explains the wrong offer, start with its content and structure. If the platform prevents essential changes, investigate a rebuild. An outdated appearance alone is not enough reason to replace the whole system.
I start by separating what customers struggle with from what the business struggles to maintain. Those problems may need different fixes.
What can you improve without rebuilding?
A working platform may only need clearer service pages, a shorter enquiry form or a design update. Keep the parts that already do their job. Before changing them, check which pages bring relevant enquiries and which tasks your team can complete without a developer.
- Customers cannot understand the offer: review the page structure, copy and examples.
- People abandon an enquiry: test the form on a phone and check whether messages arrive.
- The team cannot update content: review the editing setup and permissions.
- Staff copy enquiries into another tool: investigate an integration.
When does a rebuild make sense?
A rebuild deserves consideration when essential requirements cannot be met reasonably on the current platform. Examples include an unsupported system, a tightly coupled codebase that makes routine changes risky, or several incompatible workarounds around a core sales process.
Ask the developer to demonstrate the limitation. “The technology is old” is less useful than “this checkout cannot support your delivery rules, and here are the available alternatives”. Compare an improvement plan with a rebuild covering the same requirements.
A real example: keeping the website
For Šypsenos akademija, the existing Webflow marketing website stayed in place. Medusa commerce and CRM connections added the missing functions. That project illustrates a third option: retain the useful website and extend the systems behind it.
It does not mean every website can be extended this way. Access to the existing setup, integration options and maintenance responsibilities still need checking.
What to check before approving the work
- Write down the customer action you want to improve.
- List the pages, content and integrations worth keeping.
- Ask for the cost and limitations of both approaches.
- Assign responsibility for copy, testing and ongoing maintenance.
- Agree how the team will check that enquiries, purchases and tracking still work after launch.
If URLs change, include an old-to-new URL map, redirects and updated internal links. Google describes these steps in its site migration guidance. A new design is not a reason to discard useful page addresses.
What should you prepare for the first conversation?
Bring the current website, examples of customer complaints and a list of changes your team cannot make. If available, add enquiry data and the pages that attract relevant visitors. You do not need to choose a new platform first.
See website development and redesign for the service scope. Once the approach is clear, use the redesign cost checklist to compare proposals.
Tell me what you’re considering. I’ll help you weigh the options.
I build websites and business software, and help teams make product and technology decisions.
