Change the website. Start by protecting what needs to stay.
A stronger design is only useful when the transition is thought through. Before replacing a site, list the domain, business email, important page addresses and booking tools that need to keep working.
Separate a design decision from a systems change
A new layout does not automatically require a new booking provider or an email move. A link to an existing booking page can be a much smaller change than a custom integration. Confirm the difference before buying the project.
Keep, change, verify
Keep: useful approved content, existing tools and important business identity.
Change: the agreed layout, page structure, outdated content and supported website components.
Verify: the actual routes, redirects, contact destinations, domain configuration and mobile behavior affected by the plan.
Look at the new direction before changing anything live
Public examples demonstrate the design system. A requested personal sample demonstrates a limited direction. The purchased site is prepared and reviewed separately before an authorized launch. Viewing a design does not alter the current website.
Some transitions need additional scope
Complex stores, unsupported platform features and clinical workflows do not become simple because the new homepage looks clean. Identify limitations early. We will not present a standard page package as an all-purpose integration project.