Website Redesign Questions Agencies Ask Before Kickoff

What should an agency settle before a client redesign?

Before your team touches a single wireframe, settle scope, success metrics, and brand assets in discovery — because a redesign your client can't measure is a redesign they'll blame you for. The questions below are the ones we run in discovery on every white-label build, reframed for agencies delivering the work rather than end businesses commissioning it.

Demand is not the problem. In a HubSpot survey of 6,000+ businesses, 57% said they planned to redesign their site within the year — roughly 3,500 redesigns from that group alone, per HubSpot's September 13, 2024 analysis. The gap is delivery quality: in that same HubSpot report, one-third of marketers said they were unhappy with their last redesign. That dissatisfaction is the wedge your agency pitches against, and it's why a disciplined discovery process is the product you're really selling.

If you deliver these projects for clients under your own brand, our white-label web design team runs this exact discovery flow inside your client relationships so you can scope with confidence.

The 8 discovery questions to run before kickoff

Run these with the client before you write the statement of work. Each one either de-risks the build or gives you a metric to report against later.

1. Are the brand assets actually ready?

Confirm the client can hand over usable logo files, fonts, and brand guidelines before design starts — missing or inconsistent assets stall more builds than scope changes do. Check for disparity between the brand's online and offline presence early, because inconsistency erodes recognition and it's your team that gets blamed when the client sees it on a mobile preview.

In our delivery, we catch this in discovery now: we ask clients to share logo files up front, flag any dimension or format variation, and set expectations before anyone reviews a first comp and has feelings about it. Align the visual direction to a documented brand story so the redesign reinforces positioning instead of quietly drifting from it.

2. Where does the client actually differ from competitors?

Audit the client's competitive set before design, so the new site expresses a real point of difference instead of matching category conventions. Note the layouts, patterns, and design elements competitors lean on — then position the client deliberately against them rather than blending in.

This is a billable discovery deliverable, not free strategy. Package it as a competitive and positioning audit inside the scope so the value is visible on the invoice.

3. What are the real conversion paths?

Map the journeys a visitor must complete before you design navigation, because a site that looks clean but buries the primary action fails the only test that matters. Every page should lead toward a specific call to action, and the client should be able to name the two or three paths that generate revenue.

Treat this as an information architecture and user-experience exercise up front — it's cheaper to move a nav item in a sitemap than to rebuild a template after launch.

4. Is mobile the primary experience, not an afterthought?

Design mobile-first and confirm it in discovery, because for most of the client's audience the phone is the primary device, not a fallback. Optimizing the mobile experience is no longer a differentiator you can charge extra for; it's the baseline the client will assume you've handled.

Build device breakpoints into the scope explicitly so there's no ambiguity later about what "responsive" covered.

5. What's the scope, and what triggers a change order?

Define the page count, the phases, and the threshold at which new work becomes a separate statement of work. Anchoring scope in discovery is how you protect margin on a fixed-fee build. In a recent phased build of 10–12 pages, our design phase ran about 2 to 2.5 weeks, with a total project timeline near 6 weeks — a concrete example you can put in front of a client instead of a vague "a few weeks."

We recommend agreeing on a change-order trigger before kickoff: anything past a defined hour threshold moves to a new statement of work. It keeps the relationship clean and keeps the redesign from silently expanding into an unpaid rebuild.

6. What problems must the redesign actually fix?

Get the client to list the specific issues the current site creates — bounce points, forms nobody completes, content nobody can find — so the redesign has a defined job. A redesign brief built on "make it modern" gives you nothing to design against and nothing to prove afterward.

Turn that list into acceptance criteria. When each fix is a checkbox the client agreed to, sign-off is faster and disputes are rarer.

7. How will you monitor whether the new design worked?

Agree on the metrics and the reporting cadence before launch, because the client's definition of success is what your renewal depends on. Set a baseline for each one now — traffic, conversion rate, time on page, bounce — so the post-launch report shows movement, not just a new coat of paint.

Give the client a benchmark for context. The average website bounce rate sits at 37%, according to HubSpot's Web Traffic and Performance report (updated May 11, 2025) — a useful client-facing reference point when you're framing whether a site is healthy or leaking visitors.

8. How will the new design serve visitors, not just the client?

Tie every new element back to a visitor outcome — engagement that leads to a conversion — rather than the client's internal preferences. Personalized, relevant experiences are what separate a redesign that lifts numbers from one that just looks current.

This is also where you protect the client from their own committee. When a stakeholder wants a design choice that helps the org chart and hurts the visitor, your discovery notes are the evidence that keeps the project on strategy.

Package the discovery, don't give it away

The eight questions above are a productized discovery phase — scope it, price it qualitatively as its own line, and let it de-risk the build that follows. For agencies without in-house design capacity, this is the moment to decide whether you're subcontracting the whole redesign or just the overflow. A white-label partner should slot into your process (your project tool, your client-facing brand) rather than force the client to learn theirs.

That's the value clients notice when a redesign runs through a seasoned delivery team. As one client put it in a Clutch review, "They ask fewer questions because they ask the right questions. The company is small enough to ramp up or down as needed, but they also have resources available when we need them." Right questions up front are what let you ramp a redesign without drama — which is the whole point of asking them before kickoff, not after.

We've delivered 11,800+ projects and 18,100+ hours as a Diamond HubSpot Solutions Partner, most of it inside other agencies' client relationships. If you want a redesign discovery process you can hand to clients under your own brand, that's exactly what our white-label web design service is built to run.