Website Redesign Agency Interview Questions for B2B Teams

Set the interview up to produce comparable answers

Give each finalist the same format, core questions, and time limit. Send the questions or topic areas in advance. You want considered answers from the delivery team, not theater from the fastest speaker.

Ask the agency to bring the people who would lead:

• Strategy and discovery
• UX and visual design
• Technical architecture and development
• Project delivery
• CMS, content migration, or analytics work when those areas carry material scope

Limit the credentials section. You have already read the proposal. Spend the meeting on decisions, assumptions, and working style.

Have each committee member score the interview alone before discussing it with the group. Use the same scale you used for the written proposal, but keep the interview score separate. A strong conversation should not erase a weak scope, and a dense proposal should not hide a team that cannot explain its choices.

1. What do you think the redesign needs to fix?

Start with the agency's diagnosis. Ask the team to name the commercial, user, content, and technical problems it sees from the brief and available site evidence.

A useful answer will separate known issues from hypotheses. The team may see unclear positioning, weak proof, difficult navigation, rigid content operations, missing analytics, or a platform that no longer fits the company. It should also state what it cannot know before discovery.

Listen for a direct link between the website problem and the business. If the team limits its answer to visual age, animation, or a modern look, it has not shown enough strategic depth.

Follow with:

• Which problem would you investigate first?
• What evidence would change your diagnosis?
• Which requested item might treat a symptom instead of the cause?

2. Which proposal assumptions carry the most risk?

Every proposal contains assumptions. Good agencies make them visible.

Ask the finalist to identify the assumptions that could change scope, cost, or schedule. Common examples include content volume, stakeholder availability, CRM access, localization rules, data migration, legal review, accessibility targets, product integrations, and the condition of the current codebase.

The answer should name an owner and a method for resolving each risk. “We will handle that in discovery” lacks enough detail. Ask what the team will inspect, who needs to decide, and what happens if the assumption proves wrong.

This question also tests commercial honesty. A team that claims the brief leaves no material uncertainty may have priced certainty it does not possess.

3. How will discovery turn into approved website decisions?

Discovery should produce decisions that guide design and development. Ask what the agency will deliver, who participates, and how your team approves the work.

Look for a process that connects research and stakeholder input to concrete outputs such as:

• Audience and buying-stage priorities
• Positioning and message hierarchy
• Sitemap and page requirements
• Conversion paths and proof needs
• Content model and editorial workflow
• Integration and analytics requirements
• Technical architecture and delivery plan

Ask which decisions must close before design begins and which can remain open. The agency should protect the project from endless discovery without rushing unresolved strategy into layouts.

4. How will you decide what belongs in the CMS?

CMS decisions shape marketing speed and site maintenance after launch. Ask the team to explain how it will divide structured content, reusable sections, page-level controls, and developer-owned functionality.

A credible answer should address your editors, content volume, governance, localization, preview needs, design-system rules, and campaign workflow. It should also explain the limits. Unlimited controls can let editors break the system. Too few controls can turn a landing page into a development request.

Ask the team to walk through one common publishing task. For example: marketing needs a new campaign page with a form, proof section, customer logos, and analytics events. Who can build it? Which parts use approved components? Which changes need development?

The answer tells you more than a list of CMS features.

5. How will you choose the technical approach?

Do not ask which framework the agency prefers. Ask how it will choose the architecture for your requirements.

The team should connect its recommendation to content operations, integrations, performance, accessibility, security, hosting, deployment, internal skills, and maintenance. Familiar tools can reduce delivery risk, but preference should not replace fit.

Use follow-up questions:

• Which requirement could force a different platform or architecture?
• What would our team own after launch?
• How will another developer take over the codebase?
• Which recurring costs or dependencies should we expect?
• How will you handle monitoring, updates, and rollback?

A strong technical lead can explain tradeoffs in plain language without pretending one stack solves every problem.

6. Who makes the work, and when do senior people step away?

Ask each person in the room to describe their role, decision rights, and expected involvement. Confirm whether the named team matches the proposal.

Agency pitches often feature senior staff. Delivery may move to a different group after the contract. That model can work if the agency explains it and gives the project clear oversight. The risk comes from an undisclosed handoff.

Ask:

• Who leads the work and client communication each week?
• Who approves strategy, design, and architecture inside the agency?
• Which tasks go to contractors or partner firms?
• What happens if a named team member becomes unavailable?
• How many projects will the core team run during our engagement?

You are buying access to judgment as much as production capacity. Confirm where that judgment sits.

7. Show us how you handle a difficult scope decision

Give every finalist the same realistic scenario. Choose one tied to your project.

Example: During design, the sales team requests a resource center with gated content, CRM segmentation, and account-level personalization. The RFP mentioned a basic resource library but did not define those features.

Ask the team to explain its response. It should clarify the goal, inspect dependencies, separate the requested feature from the current scope, estimate the effect, and present a recommendation. It should not promise the work on the spot or hide behind a contract clause.

A good answer protects the outcome and the scope. It gives your project owner a clear decision with cost, timing, and system consequences.

8. How will you run content, migration, and redirects?

Website teams often underestimate content work because the tasks sit across marketing, SEO, design, development, and legal review.

Ask who owns the content inventory, page decisions, writing, approvals, CMS entry, asset cleanup, redirect map, metadata, and final QA. Confirm whether the proposal prices those responsibilities or assigns them to your team.

Then ask how content readiness affects the schedule. The agency should define deadlines and escalation paths. It should also explain how it will build templates with representative content instead of designing around neat placeholder copy.

If your site has many pages, products, regions, or legacy assets, ask how the team will test migration completeness and redirect coverage before launch.

9. What does your QA and launch plan cover?

Ask for the planned test areas, environments, owners, and acceptance method. A website launch involves more than checking pages in a browser.

The answer should fit your scope and may include:

• Responsive behavior and supported browsers
• Accessibility checks
• Forms, CRM routing, and email notifications
• Analytics events and consent behavior
• Metadata, canonicals, sitemap, robots rules, and redirects
• CMS roles, preview, and publishing workflow
• Performance and error monitoring
• Security review and account ownership
• Content and integration checks
• Launch rollback and post-launch support

Ask which checks the agency performs and which your team must accept. “We test everything” gives you no ownership model.

10. How do you manage feedback and approvals?

A redesign can collect contradictory feedback from executives, marketing, sales, product, and legal. Ask how the agency turns that input into decisions.

Look for one client owner, defined review windows, consolidated feedback, and clear approval records. The agency should know how to challenge feedback that conflicts with the brief while respecting the client's decision rights.

Ask what happens when stakeholders miss a review date or reopen approved work. The response should describe the schedule and scope effect without sounding punitive. Mature delivery teams make consequences visible before frustration builds.

11. What will our team own at handoff?

Ask for a precise handoff list. It may include source code, repositories, design files, CMS accounts, hosting, domains, analytics properties, tag-manager containers, documentation, component guidance, training, warranties, and support terms.

Confirm who owns third-party accounts and which subscriptions continue after launch. Ask how the agency will transfer knowledge to an internal team or another vendor.

A custom website should not depend on hidden access, undocumented decisions, or one developer's memory. The agency should describe how it will leave a maintainable system and a clear operating boundary.

12. Which part of our brief would you challenge?

End with a question that tests judgment. A capable agency should have a reasoned concern, tradeoff, or missing decision after studying the brief.

It may challenge the launch date, platform mandate, page count, personalization plan, review structure, migration assumption, or separation between brand and website work. The point is not disagreement. You want to hear whether the team can identify risk, explain it, and recommend a path.

Be cautious when every answer mirrors your stated preference. Agreement makes for an easy pitch and a weak advisory relationship.

Score evidence, not chemistry

A good working relationship matters, but interview energy can distort selection. Charismatic presenters can win points for commitments that never reached the proposal. Quiet technical leads can surface the risk that protects the project.

Score each answer against four factors:

Record proposal changes that come out of the interview. Ask the finalist to confirm material clarifications in writing before selection. The contract and statement of work should carry the commitments your committee relied on.

Avoid interview exercises that reward pitch production

Do not ask finalists for unpaid homepage concepts or a free strategy sprint. The agency lacks the discovery needed to make responsible choices, and the exercise favors teams with spare pitch resources.

Use a shared scenario, proposal critique, or requirements discussion instead. If collaboration on real work will determine the decision, run a paid workshop with a defined output.

The interview should test thinking and working style without extracting project work before the contract.

Frequently asked questions

Who should attend a website redesign agency interview?

Include the internal project owner and the leaders responsible for marketing, content, technology, and procurement decisions. Ask each agency to bring the people who would lead strategy, design, development, and project delivery.

How many website redesign agencies should we interview?

Interview the smallest finalist group that gives you a credible comparison. Three finalists often give a committee enough contrast without creating a long process, but your procurement rules and proposal quality should set the number.

Should we ask agencies to create a design concept for the interview?

Do not use unpaid speculative design as the main test. It rewards pitch production before discovery. Ask the team to critique a scenario, explain tradeoffs, or run a paid workshop if you need to test collaboration on real work.

Should every finalist receive the same interview questions?

Give each finalist the same core questions, time limits, and scoring criteria. Add proposal-specific questions where needed. This structure makes answers easier to compare and keeps one bidder from receiving a softer interview.

Carry the interview answers into the scope

The interview has value when it changes the decision or sharpens the contract. Capture assumptions, exclusions, named-team commitments, client responsibilities, technical decisions, handoff terms, and unresolved risks.

Virdis helps B2B teams plan and deliver custom website redesigns across strategy, design, development, CMS architecture, integrations, analytics, migration, and launch. If your finalist interviews expose gaps between the brief and the proposals, resolve those gaps before you choose the agency.