Is a refresh always cheaper than a rebuild?
Not necessarily. Compare the actual work required, including content, platform constraints and integrations. HEM does not publish a fixed refresh price; the change list is scoped in writing.
Answers · Website decisions
Choose a limited refresh when the site's structure, platform and visitor path still work and the changes are specific: replace outdated content, improve a few page sections or apply an established identity more consistently. Consider a rebuild when the audience, offer, page structure or technical requirements have changed enough that local edits cannot address the real problem. Start with an inventory, not a new look.
List public pages, forms, downloads, redirects and connected tools. Mark each page keep, update, combine or retire. Note who owns the domain, hosting and editable content. This reveals whether you need a small set of changes or a different site structure.
Can a visitor understand the current offer, find the right information and make an inquiry? Record specific gaps: an obsolete service, missing proof, unclear page labels or a broken call to action. If the structure works, focused edits may be enough. If content belongs in a different hierarchy, consider rebuilding the affected experience.
Review mobile usability, editing access, form delivery and any required booking or other integrations. Use real measurements for performance concerns. A slow image may need optimization rather than a rebuild; a new account area or a platform that cannot support required features may need a larger technical scope.
Write a change list with named pages and a clear completion condition. Keep the existing structure and working connections where possible. A refresh is not a published HEM package with a fixed price; send the actual list for a written scope instead of assuming it fits a care allowance.
Record current public URLs and identify which should stay. Plan redirects for changed paths, retain useful content and check forms and connections before launch. A rebuild does not require replacing an identity that still works. New pages, integrations and content production should be identified before comparing proposals.
Not necessarily. Compare the actual work required, including content, platform constraints and integrations. HEM does not publish a fixed refresh price; the change list is scoped in writing.
No. If the existing identity still fits and you have usable brand files, it can guide the new site. Identity work is separate when the brand itself needs to change.
No. Diagnose performance and search issues before choosing the work. Preserve useful URLs and content, test the changes and measure outcomes afterward; a new design is not a ranking or speed guarantee.
Exact deliverables, revision rounds and schedule are confirmed in a written proposal before work begins.