Fix it or
rebuild it?
Start with the problem, not the redesign. A broken contact button may need one repair. A different offer, inaccessible platform or changed publishing needs may call for a wider plan. Get a scoped comparison before throwing away the working parts.
- Name the problem
- Protect working parts
- Compare scopes
The details.
What should I check first?
Write a short list of things that fail or no longer fit. Use examples: a form does not deliver, a phone layout hides the button, a product page has old details, or you cannot edit an article.
Keep preferences separate from failures. You may want a new look, but that is a different requirement from fixing a broken checkout.
When does a small repair make sense?
Ask about a repair when the problem is specific and the surrounding site still does its job. The person reviewing it needs access and a way to test the agreed change.
Request a written boundary: what gets changed, what stays alone, how it is checked and what happens if the review uncovers a bigger issue.
When should I compare a rebuild?
Compare a rebuild when the site structure no longer fits what you publish or sell, the platform cannot support an essential requirement, or repairs would leave important gaps unresolved.
Ask the reviewer to explain the constraint rather than simply call the site old. A rebuild should solve named problems, not just replace the colors.
What needs protecting during a change?
List the pages people already use, domain access, business email, shop connections, forms, tracking and content you need to keep. Save a usable backup before changing the site.
For moved pages, agree where each old address should go. Plan checks for email, inquiry delivery and any payment route. Do not treat a successful homepage load as a complete launch test.
How do I compare the two quotes?
Compare the same required outcomes, not just the total. Read what is included, what is excluded, who supplies content, how revisions work and who maintains the result.
Ask for the price and scope before work begins. Sitewhip can discuss an existing-site improvement or a larger project after reviewing the requirements; this page does not promise a particular fix or outcome.
