Website Redesign Scope: What Should Your First Launch Include?

Your first website redesign launch should include everything a priority customer needs to understand the offer, judge whether it fits, and take the next step—and everything your team needs to receive and act on that response.

That usually means clear service content, credible evidence, a working inquiry or booking path, mobile usability, and a plan for existing pages and ongoing care. The exact pages and features depend on the buying decision you need to support.

A page count cannot tell you whether that journey is complete. Five polished pages can still leave a visitor wondering whether you serve their area or what happens after an inquiry.

Before asking an agency for a proposal, define the smallest complete journey you can launch with confidence. Then decide which additional ideas deserve a later phase.

Write one sentence: “We need [specific customer] to understand [specific offer], trust [relevant evidence], and take [next action].”

For an owner-led service business, that action might be requesting a consultation. For an organization with a longer buying process, it might be reviewing a relevant project and contacting the right team. Choose the journey that matters most to this release.

Use recent sales conversations, recurring customer questions, and existing inquiry records to identify missing information. If you have access to Search Console, its Performance report lets you review search clicks and impressions by page and query. Those records can inform the brief; they do not establish why a visitor failed to inquire.

Mark observations and assumptions separately. “Customers ask whether we handle commercial projects” is evidence to investigate. “A new homepage animation will generate better leads” is a proposed solution that still needs a reason.

Review each proposed item against the journey. Keep an item in the first launch when removing it would leave an important buyer question unanswered, break a necessary action, or leave the business unable to operate the site responsibly.

Understanding: the right offer and audience

Specify the services, locations, and customer types the site must explain. Identify which need distinct pages and which can share a clear overview. Include messaging and copywriting in the scope if the existing words no longer describe the business.

If the business has changed direction, settle the positioning question before approving page designs. Our guide to brand refresh versus rebrand can help frame that earlier decision.

Confidence: evidence the business can stand behind

Choose relevant project work, service details, team credentials, or approved customer feedback. Record who will verify claims and obtain permission for material that needs it. A placeholder for a case study is unfinished content, even when its layout is approved.

TVA’s public GenBCorp Health case study describes a mobile foot care brand that needed to balance medical authority with warmth for patients and caregivers. That is a concrete audience tension a brief can address. It gives the creative team a more useful direction than “make it look professional.” The case study documents brand work; it does not establish a website conversion result.

Action: the whole path after the button

Name the next step and follow it through. What information does the visitor submit? Where does it go? Who responds? What confirmation does the visitor receive? Include the actual booking, form, email, or customer-management connection the business needs.

Define a launch check that proves the path works through to its destination. A success message alone does not show that the right person received the inquiry.

For every priority page, record whether the content is ready, needs editing, or must be created. Assign responsibility for copy, photography, approvals, and entry into the website. Ask the proposal to state which of those jobs the agency includes.

Inventory the existing pages before deciding what disappears. If URLs will change, include an old-to-new URL map, appropriate redirects, and checks of internal links and the sitemap. Google’s site move guidance recommends mapping old URLs to their new destinations and using permanent server redirects where possible. Avoid sending unrelated old pages to the homepage. Migration work can reduce avoidable errors; it cannot guarantee unchanged search performance.

Include mobile and accessibility requirements in the scope from the start. Ask who will evaluate the work, what standard and scope they will evaluate against, and how issues will be resolved. W3C’s accessibility planning guidance calls for assigned responsibilities and evaluation early and regularly throughout production.

For the priority journey, plan checks such as reading the content on a phone, using navigation and forms with a keyboard, understanding field labels and errors, and completing the intended action. These checks are useful acceptance criteria, not a substitute for a full accessibility evaluation.

Copy this structure into the brief and replace the examples. The entries below are illustrative planning examples, not a standard package or a claim about a TVA client.

Add the specific pages, content quantities, integrations, review rounds, and exclusions once the decisions are clear. “Website copy included” needs a defined extent. “Booking integration” needs a named system and a description of what it must do.

A later-phase list should have a reason to revisit each idea. Otherwise it becomes a waiting room for features nobody has committed to maintain.

Illustrative scenario: an Atlanta commercial interiors firm is expanding from referrals into direct inquiries. Prospects keep asking whether it handles occupied offices and which surrounding areas it serves.

The first launch could explain that service clearly, show an approved relevant project, describe coverage and project fit, and provide an inquiry path to the person who qualifies new work. Existing useful pages would remain available or receive appropriate new destinations.

A large inspiration library might wait until the marketing team has an editorial owner. A custom estimate calculator might wait until the firm can define reliable inputs and explain the limits of an estimate. Neither needs to delay a complete inquiry journey.

If the team cannot approve the service copy, removing it to meet the date would leave the central problem unsolved. The better decision is to resolve the content dependency or revise the launch plan.

Share the worksheet, the current website, known constraints, available budget range, and the reason for your target date. Identify the person authorized to approve the work. Ask every proposal to answer the same questions:

1. What ships? Which pages, content, features, and customer journeys are included?
2. What must we supply? Which assets, access permissions, and approvals are client responsibilities, and when are they needed?
3. How is readiness verified? Who checks mobile behavior, accessibility, changed URLs, and the complete inquiry or booking path?
4. What changes the scope? How are additions assessed, priced, and approved before work begins?
5. Who operates it afterward? What are the arrangements for hosting, updates, support, account access, and handoff?

Compare the answers before comparing the headline price. A proposal that assumes your team will write and migrate all content carries a different commitment from one that includes that work.

For ongoing care, distinguish launch corrections, routine content changes, and new development. TVA’s managed website service describes an ongoing management approach; a custom website design project starts with the job the visitor needs to complete. Discuss the responsibilities your business needs before choosing the engagement.

Bring your priority buyer journey, current site, and unresolved scope questions to a conversation with TVA. That gives us a practical starting point for deciding what the first launch should accomplish.