Take inventory before deciding what to rebuild.
We review the pages, content, assets, and contact paths that matter to your business. Useful existing material may deserve a better home rather than a complete rewrite. Missing information, confusing navigation, and difficult booking routes become specific decisions to work through.
Available search or website reports can add context about the pages people use. We also ask which links appear in emails, directories, printed materials, and other places your business relies on.
- Current pages and important website addresses
- Content, photographs, logos, and permissions to reuse them
- Domain, hosting, and website account access
- Contact forms, booking links, and connected tools
Agree on content responsibilities and ownership.
A redesign is easier to manage when the source material and approvals are understood. We discuss who supplies missing information, who reviews wording, and who approves service details before anything goes live.
We establish who controls the domain, website accounts, and tools involved. Third-party subscriptions, licensed materials, and access limitations belong in the scope. If moving content requires cooperation from an existing provider, that dependency belongs in the plan.
Plan the move as well as the new design.
Changing a website can affect its existing page addresses and the links that point to them. We can scope a list of old and proposed addresses, identify redirects where the hosting setup supports them, and review important destinations before launch.
The migration plan should also cover forms, booking handoffs, and any material that is being retired. Domain or hosting changes are discussed separately from visual design so the required access and responsibilities are visible. No redesign can promise to preserve a particular search ranking.
Review the new experience before launch.
A preview or staging version provides a place to review the proposed website before approving publication. We work through the agreed pages, content, and feedback there, with checks suited to the project.
Those checks can include mobile layouts, navigation, contact links, form responses, and the route into existing booking tools. Your team reviews the information it is responsible for, including clinical wording and practice details when relevant. The launch decision follows that review.
Decide what happens after the switch.
We agree who handles launch, what to check afterward, and how corrections are reported. Project terms should explain ongoing support and which changes need a separate scope.
Practice Relay collaborates entirely online from Waterford, Connecticut. You work directly with the builder, using an agreed inventory, review process, and launch plan to keep the project understandable.
Questions before we begin.
Can you improve my current website instead of replacing it?
Possibly. We first review the platform, access available, and changes you need. That assessment helps determine whether targeted improvements are practical or whether a new build would better suit the agreed scope.
Will my existing page links keep working?
We identify important current addresses and plan how each should be handled. Redirects depend on the systems and access involved, so the scope needs to state what can be implemented and what requires another provider.
Will the existing website stay live while we review the redesign?
We normally plan a separate review environment when the setup allows it. The intended staging and launch arrangement is agreed before work begins, including any steps that depend on your current host or provider.
What should I bring to the first conversation?
Your current website address, the problems you want to solve, and any known account or ownership details are useful. You do not need a finished replacement plan; reviewing the existing site is part of defining it.