B2B Website Redesign Agency Selection Criteria

Define the project before you search for an agency

Most agency searches start with a list of names. Start with the operating problem.

Write down why the current website has become a constraint. Your sales team may struggle to send buyers to useful pages. Marketing may depend on developers for routine publishing. The CMS may allow inconsistent layouts. Analytics may miss the actions that matter. The design system may exist in Figma but not in production code.

Turn those constraints into a one-page selection brief. Include:

• the business goals the website must support
• the primary audiences and conversion actions
• the expected scope across strategy, content, design, development, and migration
• the systems the site must connect to
• the people who will publish and maintain it
• the launch window and approval constraints
• the budget range your company can support

This brief gives you a common standard for the shortlist. Without it, one agency may look strong because it specializes in visual identity while another looks strong because it handles complex development. You cannot compare them until you name the work.

Use ten agency selection criteria

A credible redesign partner should cover the full path from a commercial problem to a maintained website. Score candidates against ten criteria before you request a proposal.

Use these criteria as gates first. A weighted proposal scorecard comes later. The shortlist should remove agencies that cannot cover a required part of the project.

Check whether strategy reaches production

Many agencies sell strategy as a discovery phase. Ask what the strategy changes.

A useful answer should connect research to concrete deliverables: positioning decisions, sitemap changes, buyer paths, page priorities, content requirements, wireframes, component needs, CMS structures, tracking events, and test criteria.

Ask the agency to walk through one decision from a past project without requesting confidential client information. You want to hear the original constraint, the evidence the team gathered, the decision it made, and where that decision appeared in the final website.

A deck alone does not prove that strategy governed the build. The agency should show a chain from research to production.

Inspect the content and UX process

Your website cannot wait for polished copy to make structural decisions. The agency needs a process for working with incomplete content while preventing placeholder text from driving the design.

Ask who owns:

• stakeholder and customer input
• sitemap and page hierarchy
• content briefs and source collection
• copywriting or editing
• legal and subject-matter review
• content entry and migration
• final page approval

Then ask how the team tests navigation and page structure before visual design. Look for working sessions, wireframes, content models, and review criteria tied to buyer tasks.

If the agency says “the client provides content,” press for boundaries. Your team may need to supply raw expertise, finished copy, or every CMS entry. Those are different commitments.

Test the design-system claim

A design system should connect visual decisions, coded components, and CMS controls. A component library that ends in Figma leaves your production site exposed to drift.

Ask candidates to explain:

• how they define typography, color, spacing, and interaction rules
• how they design responsive and error states
• how design components map to code
• how coded components map to CMS fields
• how they handle one-off requests after launch
• who maintains the system when new page patterns appear

Review a comparable live site across desktop and mobile. Check whether the system holds together beyond the homepage. Repeated sections should feel related without making every page identical.

Put developers in the selection meeting

Meet the people who will make architecture decisions. A salesperson cannot answer for the development team.

Ask a developer to explain the proposed approach in plain language. Cover hosting, frontend architecture, CMS, preview workflow, forms, integrations, analytics, accessibility, performance, testing, deployment, monitoring, and maintenance.

The strongest answer will name tradeoffs. A flexible CMS can increase editor responsibility. A strict component model can protect quality while limiting campaign layouts. Third-party scripts can add business value and hurt performance. You need a team that can manage those tensions instead of selling every feature as a free benefit.

Confirm whether the agency uses employees, long-term partners, or rotating subcontractors. The staffing model matters less than clear ownership and continuity.

Evaluate the CMS as an operating system

Do not choose a CMS from a logo in a proposal. Choose the publishing model your team needs.

Give each agency three real publishing scenarios:

1. Launch a campaign page using approved components.
2. Update a product or service message across several pages.
3. Add a new content type with its own fields, filters, and SEO requirements.

Ask how marketers, designers, and developers handle each scenario. The answer should cover previews, roles, approvals, reusable content, validation, page composition, releases, and rollback.

A blank canvas can turn every editor into a designer. A rigid schema can send minor changes back to development. The agency should recommend a balance based on your team, not its preferred software stack.

Require conversion tracking in the build scope

Treat measurement as part of the website architecture. Adding tags after launch produces gaps when nobody defined the events, data fields, consent behavior, or CRM handoffs during development.

Ask how the agency will:

• map conversion actions to business questions
• define event names and required properties
• implement a data layer
• configure tag management and consent behavior
• preserve campaign parameters
• test forms and CRM routing
• validate production data after launch
• document the measurement plan

The agency does not need to manage your analytics program forever. It should leave the new site capable of producing trustworthy data from its first release.

Ask for a migration and launch plan

A redesign changes more than page layouts. URLs, metadata, internal links, structured content, forms, scripts, media, and tracking all move through the project.

Ask candidates to outline their migration inventory and launch checks. The plan should name owners for redirect mapping, metadata, canonical URLs, sitemaps, robots rules, content entry, accessibility, responsive testing, browser coverage, forms, integrations, analytics, performance, deployment, and rollback.

Production verification matters. A passing staging review cannot prove that live forms, redirects, caching, consent, or third-party services work.

Verify team ownership before you shortlist

Agency credentials can hide the people who will deliver your project. Request a working-team call before the proposal stage.

Confirm who owns strategy, content, UX, visual design, development, QA, and project delivery. Ask how much senior involvement continues after kickoff and who makes decisions when a technical or scope risk appears.

Review relevant work with the person who helped deliver it. Ask which parts that person owned. This keeps the conversation grounded in experience instead of a borrowed portfolio.

Check capacity, too. Ask what else the proposed team will handle during your project and how the agency covers absences. You need a credible allocation, not a promise that your project will receive attention.

Check ownership, handoff, and maintenance

Your contract should leave your company able to operate the website and change partners.

Before you shortlist an agency, ask who will own:

• source code and repositories
• design files and component documentation
• domains, hosting, analytics, tag management, and CMS accounts
• licensed fonts, plugins, and software
• content and media assets
• deployment settings and environment documentation
• integration credentials and vendor relationships

Ask what training, warranty, documentation, and maintenance the agency provides. A maintainable website still needs updates, monitoring, dependency work, and clear escalation paths. The agency should define those responsibilities before launch pressure arrives.

Run a structured qualification call

Give every candidate the same 45-minute agenda:

1. Restate our business problem and the website’s job.
2. Name the two largest delivery risks in this scope.
3. Explain how research changes content, UX, design, and development.
4. Show how design components connect to code and CMS controls.
5. Walk through one real publishing workflow.
6. Explain the migration and production verification plan.
7. Introduce the people who would deliver the work.
8. Define what our team will own and maintain.

Record evidence against the ten criteria. Remove candidates that avoid required areas, assign them to an unnamed future partner, or cannot explain who owns the decision.

Build a shortlist of qualified differences

Three agencies with the same surface pitch do not create a useful shortlist. Choose candidates that meet the gates and offer credible differences in approach, team, specialization, or operating model.

Document why each agency made the list. Name the evidence, open questions, and risks. Send the same brief to each finalist, then compare proposals against normalized scope rather than presentation quality.

The shortlist stage should answer one question: can this team own the full redesign problem your company needs solved? The proposal stage can then answer how it will do the work, what it will cost, and which terms control the risk.

Frequently asked questions

How many website redesign agencies should we shortlist?

Shortlist three qualified agencies when possible. That gives your team enough contrast to test different approaches without creating an evaluation process that rewards shallow sales work. Use capability gates before the shortlist so each finalist can cover the required scope.

Should we choose a specialist or a full-service web agency?

Choose the team that matches the work. A specialist fits a narrow problem with strong internal support. A full-stack agency fits a redesign that requires connected strategy, content, UX, design, development, CMS, analytics, migration, and maintenance. Verify who handles every required area.

Should we ask for speculative design work before selecting an agency?

No. Speculative concepts reward presentation speed before the agency understands your buyers, content, constraints, and systems. Ask for relevant work, process evidence, working-team access, and a clear explanation of how research changes production decisions.

When should we discuss the website redesign budget?

Share a credible range during qualification. The range helps agencies identify whether your requirements fit the available investment and prevents proposals for different projects. Ask each candidate to flag the requirements that create the most cost or schedule risk.

Select for the website you need to operate

Virdis plans, designs, and develops custom B2B websites as connected systems. We align strategy, content, conversion paths, design systems, custom development, CMS architecture, analytics, testing, and maintenance in one scope. If your team is building an agency shortlist, Virdis can help define the requirements and show how we would carry them into production.