When choosing a website redesign agency, ask how it will control costs, manage delivery, protect search visibility, support everyday publishing, and keep your website working after launch. A dependable long-term partner should explain these responsibilities clearly and show you how they work in practice.
For B2B marketers and website owners, the decision reaches beyond approving a new design. It affects how quickly campaigns launch, whether enquiries reach sales, how confidently your team updates content, and how easily you can explain website spending to management.
To understand what matters in that relationship, we reviewed real questions from Webgate’s clients and prospects.
Our interpretation of the recurring themes is straightforward: clients want greater control over their website, their budget, and the work ahead.
Where these questions come from
This article draws on Webgate’s internal qualitative review of client and prospect communications across email, Slack, and ClickUp between May 6, 2025 and November 6, 2026.
The review covered enquiries, project delivery, and ongoing support across our broader client base. We grouped recurring concerns into the 14 questions below and adapted the guidance for B2B marketing teams and website owners.
The questions and examples are anonymized paraphrases. They are organized around the buying decision rather than ranked by frequency. The answers are our recommendations based on those concerns.
In this article
- 1. How much will our website redesign cost, and what exactly is included?
- 2. What happens when we request changes or something needs fixing?
- 3. How long will the redesign take, and what could delay launch?
- 4. How will we know what is happening without chasing updates?
- 5. Will our marketing team be able to update the website independently?
- 6. How will you make sure the website matches our brand and works on mobile?
- 7. How will you protect our SEO during the redesign?
- 8. Will our forms, CRM, and other integrations work reliably?
- 9. How will we know whether the redesign is improving business results?
- 10. How will we manage multiple languages and ongoing content changes?
- 11. What happens if the website or a critical function stops working?
- 12. What will we pay after launch?
- 13. Can you take over our existing website, and will we retain control?
- 14. Will you help us improve the website over time?
1. How much will our website redesign cost, and what exactly is included?
A useful redesign estimate connects the price to specific deliverables, assumptions, and exclusions. Page count alone is insufficient: unique layouts, content preparation, integrations, languages, and migration work all affect the scope.
In our research, one client compared updating existing page copy with redesigning those pages completely. They also needed to clarify whether an estimate covered one page or every page using the same component.
That distinction can change a purchasing decision.
Ask agencies to identify which parts of the project they will deliver:
- Discovery, website structure, and content planning.
- Copywriting, visual design, and development.
- Content entry, migration, and translations.
- Forms, integrations, analytics, and SEO migration.
- Testing, training, launch, and initial support.
If the budget is constrained, request a smaller first phase with clearly explained trade-offs.
Ask for: An itemized proposal showing included work, exclusions, client responsibilities, and the assumptions behind the estimate.
2. What happens when we request changes or something needs fixing?
The agency should explain how it distinguishes a defect, an included revision, and a new requirement—and how each affects cost and timing.
These boundaries repeatedly created uncertainty in the research. A client may see an unfinished page, while the delivery team sees a new request added after approval.
Define acceptance criteria before work begins. If an agreed form fails to submit, that is different from adding a new routing workflow. Replacing approved messaging after a positioning change may also require additional work.
For changes that affect the budget, agree on an estimate and approval process before implementation. For defects, establish how they are reported, assessed, and resolved under the project agreement.
Ask for: A written change process with practical examples, approval thresholds, and clearly defined defect coverage.
3. How long will the redesign take, and what could delay launch?
A credible timeline includes the agency’s work and the decisions, content, access, and approvals required from your team.
For B2B organizations, a launch may depend on product marketing, sales, IT, regional teams, and management. Each dependency needs an owner.
Ask the agency to show when it needs final messaging, translations, CRM access, and consolidated feedback. Check whether the schedule includes content population and testing.
If your deadline is tied to an event or campaign, discuss a phased release. Identify which pages and journeys must work at launch and which improvements can follow.
Ask for: A milestone schedule showing dependencies, approval dates, launch criteria, and the consequences of delayed inputs.
4. How will we know what is happening without chasing updates?
Agree on a reporting rhythm, a shared view of the work, and a named person accountable for communication.
One client in our research explicitly requested the promised weekly updates or somewhere they could monitor progress independently. Their questions covered delivery status, outstanding assets, and the timing of maintenance work.
A useful update should help you make decisions. It should explain:
- What has been completed and where to review it.
- What is scheduled next.
- Which decisions or materials are needed from you.
- Whether the budget or launch date has changed.
- Who owns each unresolved issue.
This also gives the marketing lead something concrete to share internally.
Ask for: An example status report, access to the project workspace, and an escalation contact.
5. Will our marketing team be able to update the website independently?
Your team’s independence depends on how the website is built, the editing permissions provided, and the training delivered.
Clients repeatedly asked how to change content and reuse existing layouts. One request specifically called for a template that could be adapted for new products without starting from scratch.
Evaluate the CMS through everyday tasks. Ask a marketer to create a campaign page, update a customer story, replace an image, and preview the mobile layout.
Discuss where flexibility should stop. Reusable components can give marketers useful freedom while keeping typography, spacing, and branding consistent.
The agency should also explain which changes will still require a developer.
Ask for: A working editing demonstration, reusable templates, and short instructions for the tasks your team performs most often.
6. How will you make sure the website matches our brand and works on mobile?
Design quality should be assessed against agreed requirements for appearance, usability, accessibility, and performance across representative devices.
Our research included questions about whether implementation would match approved designs and how quality would be checked before handover.
For a B2B website, test the journeys visitors actually use: understanding a product, comparing solutions, reading a case study, navigating resources, and requesting a demo.
Review long headings, translated text, form errors, menu behavior, and interactive elements. These details can expose problems that a polished homepage screenshot will miss.
Agree on who signs off the work and how outstanding issues are categorized.
Ask for: A documented acceptance checklist and evidence of testing across key pages, devices, and interactions.
7. How will you protect our SEO during the redesign?
The agency should inventory valuable content and URLs, plan changes carefully, test the migration, and monitor search performance after launch.
Existing search visibility belongs in the project scope from the beginning. A redesign can change navigation, internal links, content, URLs, and indexing settings simultaneously.
Google’s migration guidance recommends preparing URL mappings, implementing appropriate redirects, and monitoring the move. It also warns that rankings can fluctuate while changes are processed. Google’s site migration guidance.
For 2026 projects, extend the discussion to AI search visibility. Ask how the agency will make your expertise, services, and supporting evidence accessible and understandable. Google says established SEO practices remain relevant and that its generative search features require no special schema markup. Google’s AI search guidance.
Ask for: A website migration plan with named owners, launch checks, and monitoring responsibilities.
8. Will our forms, CRM, and other integrations work reliably?
An integration is ready when the complete business process has been tested, including what happens when something fails.
One client asked whether form submissions were stored, where notifications were sent, and whether earlier enquiries could be traced. The concern was practical: could the business account for the contacts its website received?
For a B2B team, a demo request may need to create or update a CRM record, preserve campaign information, route to the correct owner, notify sales, and trigger the appropriate confirmation.
Test those steps together. Include relevant language versions and error scenarios.
Agree on how failures will be detected and investigated, and what submission records should be retained under your organization’s data policies.
Ask for: A test enquiry demonstrated from submission through CRM delivery, routing, notification, and measurement.
9. How will we know whether the redesign is improving business results?
Agree on a baseline, a small set of meaningful measures, and a reliable tracking setup before launch.
A client in our research asked what a new measurement setup would improve and how they could verify that it worked. That question applies equally to a redesign.
Useful B2B measures may include:
- Qualified demo requests and enquiries.
- Completion rates for important forms.
- Progression from website enquiries to sales opportunities.
- Engagement with product and customer evidence.
- Time required to publish a campaign or update content.
Interpret results in context. Changes in campaigns, traffic quality, seasonality, and tracking can influence comparisons.
A higher conversion count after a tracking fix may reflect more complete measurement. Establish what changed before attributing the difference to design.
Ask for: A measurement plan defining each metric, its source, the starting baseline, and who will review it.
10. How will we manage multiple languages and ongoing content changes?
Multilingual delivery needs clear rules for translation, shared content, local variations, and maintenance.
The research included questions about supplying existing translations, pricing an additional language, and whether author information would stay consistent across language versions.
Those are operational decisions. They should influence the content model and editing workflow.
Agree on which information is shared globally and which can vary by market. Identify who translates and approves copy, what happens when the source text changes, and how outdated translations are flagged.
Test forms, confirmation messages, navigation, and downloads in each relevant language.
Ask for: A multilingual workflow demonstrating one content update from the original language through translation, review, and publication.
11. What happens if the website or a critical function stops working?
Support should define how problems are detected, who responds, what coverage applies, and how service is restored.
In one client conversation, the team asked to receive outage alerts and explored whether they could restore a backup themselves when agency support was unavailable.
Their concern extended to internal accountability: they wanted enough information to explain the situation to colleagues and management.
Clarify the difference between acknowledging an incident and resolving it. Establish who covers absences and which systems the agency monitors.
Include commercially important functions in the discussion. A website can load successfully while a demo form or integration fails.
Ask for: A support agreement covering service hours, incident priorities, escalation, backups, restoration, and communication during an incident.
12. What will we pay after launch?
Request a complete view of recurring costs and a clear explanation of what ongoing support includes.
The research surfaced uncertainty around maintenance, software licences, available features, and additional development. These questions are easier to resolve before the relationship begins.
Your operating budget may include hosting, domains, paid tools, maintenance, monitoring, content work, and further development.
For retainers, establish how capacity is allocated and reported. Ask whether unused time carries over, how urgent work affects planned tasks, and when additional spending requires approval.
Also clarify which licences belong to your organization and which depend on the agency’s subscription.
Ask for: A first-year operating budget with renewal dates, account owners, included services, and the process for approving extra work.
13. Can you take over our existing website, and will we retain control?
An agency should assess the existing website before recommending a rebuild and document the access and assets required for a safe handover.
Requests to take over existing websites were a recurring theme. Some prospects wanted better support, clearer communication, or a more active development partner.
A handover can involve hosting, repositories, CMS access, domains, analytics, licences, documentation, and unresolved issues. Shared agency accounts may require a separate migration or replacement arrangement.
Ask what can be retained, what needs immediate attention, and what should be improved later. A full rebuild should have a clear business or technical justification.
Apply the same scrutiny to your future exit from the new agency.
Ask for: An initial assessment, an account and asset inventory, and a documented handover process.
14. Will you help us improve the website over time?
A long-term website partner should connect ongoing recommendations to your business priorities and explain what should happen next, why it matters, and what it will cost.
The research included demand for active improvement recommendations alongside technical support. Clients also asked for lower-cost alternatives and help deciding which changes could wait.
Make that advisory role concrete.
Discuss how the agency will review performance, gather feedback, prioritize improvements, and reserve delivery capacity. A proposed roadmap might address publishing bottlenecks, confusing product pages, lead quality, or unreliable integrations.
Ask for evidence from a comparable engagement. Establish what the agency owned, how it worked with the marketing team, and what happened after launch.
Where AI tools are involved, ask how the agency reviews their output and maintains the resulting website or workflow.
Ask for: An example improvement roadmap and a proposed review cadence covering priorities, evidence, costs, and outcomes.
What our client research suggests about choosing a long-term partner
The questions changed with the stage of the relationship.
Before a project, clients wanted clarity on price, scope, timing, and supplier suitability. During delivery, they needed visibility into progress, decisions, and changing requirements. After launch, attention shifted toward publishing independence, reliability, measurement, and ongoing costs.
That progression should influence how you choose an agency.
Evaluate whether the team can support the everyday work that follows launch: adding a campaign, updating product information, investigating a missing enquiry, explaining a technical recommendation, or preparing a budget for the next quarter.
Our interpretation is that predictable collaboration is a major part of the value clients seek.
Turn the answers into evidence before choosing
Give shortlisted agencies the same brief and ask them to demonstrate one realistic scenario: publishing a campaign page with an additional language, a CRM form, conversion tracking, and a deadline.
Then compare the supporting material:
- A clearly scoped proposal and change process.
- A schedule with responsibilities and dependencies.
- An example project update.
- A practical CMS demonstration.
- Migration and testing plans.
- A support agreement and operating budget.
- A handover inventory and improvement roadmap.
This gives your team a concrete basis for assessing the relationship before committing.
Planning a B2B website redesign in 2026?
Start with the problems your team needs to solve: slow publishing, unclear messaging, unreliable enquiries, difficult integrations, or uncertainty about ongoing support.
Webgate helps marketing teams with website design, development, migrations, and ongoing website work.
Bring your current website, priorities, and constraints. We can discuss what needs to change and how to structure the next stage.
