Start with the symptom. If the site loads slowly everywhere, the cause could be oversized images, hosting or something shared by every template. If one booking page fails, the rest of the site may be fine. Ask for a diagnosis and a written repair scope before comparing quotes.
Identify what is worth keeping
List pages customers find through search, integrations staff use and content you already paid to produce. Factor in the time your team needs to edit the current site. Repeated workarounds for basic tasks, such as changing hours or adding staff, belong in the cost comparison.
Compare two realistic plans
Ask what a targeted repair would improve this month and what you would still be paying for next year. Compare that with a rebuild that covers redirects, content transfer and staff handoff. Lumos can look at the existing site and help you decide which work is worth paying for first.
When a small repair buys useful time
A site that still brings in calls and is easy for staff to edit may need a focused repair. For example, if the service pages work and one quote form fails on phones, repairing that form is a clear project with a clear test. Ask whether the fix depends on a tool that is already being retired or on custom work that only one person can support.
- Choose repair when the problem is isolated and you can describe what success looks like.
- Consider a staged rebuild when the content is useful but the templates or publishing workflow are getting in the way.
- Include a migration plan when old URLs, orders, bookings, or staff accounts need to survive the change.
Compare the cost of doing nothing
Count repeat work over the next few months. If someone has to call customers to finish every online booking, estimate the staff time and lost opportunities that creates. Put that next to the cost of a focused repair. If a rebuild is still likely, ask which repair work can carry forward, such as cleaning up content and documenting the booking flow.