Patch it, rebuild it,
or leave it alone?

A tired-looking site tempts you to buy a new one. Sometimes that’s right. But rebuilds cost time and money, and a plain site that does its jobs can be exactly right.

1. Start with the jobs, not the looks

List the three to five things customers visit your site to do: see if you do their kind of job, check where you work, get a feel for price or process, contact you, book. Add what it does for your team: taking inquiries, answering common questions, passing details to other tools.

Try each job on your phone. Mark it: works, works but awkward, doesn’t work, or not possible. Use that list to compare the current site with the options.

2. When to leave it alone

Leave it when the site supports the jobs customers and staff need, and the cost or risk of changing it is not justified by a clear benefit. That can be true of a plain brochure site. It may still need routine maintenance.

3. When a patch is enough

Patch it when a specific problem can be addressed within the current site: an incorrect link, an unclear service page, outdated information such as hours that differ between pages, or a confirmed delivery issue.

4. When to consider rebuilding

Consider rebuilding when the current structure or platform cannot support agreed needs well enough, and a rebuild compares favorably with a smaller repair or supported connection after cost, maintenance and disruption are considered. Signs to look for:

• Important customer tasks cannot be supported reliably within the existing structure.
• The service structure has changed enough that local edits would leave it confusing.
• Repeated workarounds have documented costs or risks worth addressing.
• Needed connections cannot be supported adequately by the current setup.
• The cost and disruption of rebuilding are justified against the alternatives.

Then a new site, sometimes with a way for your team to manage requests, can be right. A good rebuild starts from the jobs list, keeps what works and agrees what “done” means before anything is built.

One caution: a rebuild does not, by itself, establish that more relevant people will find you or buy. Search visibility, the offer, price and capacity need their own evidence.

5. The checklist

1. Can a customer complete each important task without unnecessary difficulty?
2. Can you change hours, prices, services and photos yourself?
3. Are the domain, hosting and site login in your name, and do you know where?
4. What does the site cost a month or year, and what does that cover?
5. Does anything get retyped between the website and your other tools?
6. What should the site do a year from now that it can’t today?
7. Is the problem really the website, or how many people find you, your pricing or your capacity?

Keep a site that meets the need. Repair a specific fault where that is sufficient. Compare a rebuild only when the evidence supports changing the foundation.

A manageable next step

Bring your list to a free First Look: a 15-minute call, one real observation and a straight answer on whether more work is worth it, with no obligation. If it is, Diagnose gives you a written plan first. Build ranges from one fix to a full website with a way for your team to manage requests, scoped and priced before work starts. Smaller checks: why a website isn’t getting calls and the website inquiry checklist. Retyping between tools: tools that don’t talk to each other.

The right answer depends on your customers, your tools and what you want the business to do next.