Identify the problem in one sentence
“The site looks old” may describe a presentation concern. “Staff cannot update products” describes an operating constraint. “Forms say sent but no inquiry arrives” describes a delivery defect. These need different scopes.
Compare the options
| Option | Useful when | Evidence to gather |
|---|---|---|
| Focused repair | One contact or navigation task fails | Reproducible defect and affected route |
| Visual refresh | Structure works but hierarchy or assets need improvement | Mobile screenshots and content review |
| Content restructure | Services overlap or customers cannot find answers | Page inventory and intent map |
| Platform rebuild | Publishing or integrations no longer fit | Editing needs and maintenance plan |
Protect what already helps
Record useful URLs, content, contacts, and integrations. A new template is not a reason to lose a search-visible guide. If a page is consolidated, move useful material and map it to a relevant replacement.
Define acceptance before design
Agree on content ownership, editing access, responsive checks, contact delivery, redirects, and rollback. Include maintenance and licensing responsibilities in the written scope. Do not treat a screenshot as the complete project.
Budget around the actual scope
Joe Design Group’s website advertises starting website packages of $997, $2,497, and $4,997. Those are existing offers, not a universal quote for every rebuild. Confirm content, features, hosting, ongoing support, and integrations before comparing prices.
Prepare the release
Use the redesign migration checklist when paths or platforms change. Save the old files and server rules together. After approval, verify the live release separately from the local package.
Bring your website and your next goal
Share your current URL, the service you want to improve, and the action customers should be able to complete. We’ll review the scope with you.
Request a free auditPage imagery is illustrative. It is not a customer project or a performance result.