How to compare website redesign proposals

Write one sentence describing the change your business needs. For example: visitors should understand our four services and send a useful enquiry to the right person. Assess suggested features against that outcome.

Share the same page list, current website, integrations, languages and intended launch date. Ask each supplier to identify assumptions and dependencies. Keep an open decision marked to agree until someone has explained it.

The existing project brief gathers inputs; the migration worksheet records delivery checks. This guide addresses the decision between proposals.

Imagine a service firm needs a homepage, four service pages, an about page, a team page, three project records, a contact page and a frequently asked questions page. Both proposals below cover those twelve pages.

Four templates may help when services and project records need different structures. Two can be sufficient when flexible sections explain both clearly. Ask to see how an editor would publish a service page and project record, then count the work your team would still do.

Mark essential requirements as included, separately priced, client supplied or unresolved. List optional additions separately. Resolve each essential item in the written scope before choosing. A lower fee can fit your needs when your team has capacity for the remaining tasks.

Use the build plus twelve months after launch as the shared comparison period. Add each charge once; keep tax inclusive quotations intact. If hosting is bundled into support, identify its share or mark it as included. Count charges during development as well as after launch.

List usage charges and renewal changes separately when amounts depend on traffic, transactions or future pricing. Keep internal work beside the total: writing, image selection, language review, content entry and approval time.

Compare payment milestones with the deliverables available at each stage. Ask how scope changes are estimated, approved and added to the schedule. Keep any contingency allowance in your planning budget separate from the supplier’s agreed fee.

For this separate cost example, assume both suppliers have confirmed the same twelve page scope, content responsibilities and acceptance evidence. Proposal A bundles writing and migration into the build. Proposal B prices those tasks separately. Both include the same hosting and support responsibilities for twelve months after launch.

All figures below are fictional GBP amounts for arithmetic only. They are neither market benchmarks nor Branding Tatva prices, supplier quotations or client results. This example excludes taxes, payment or currency conversion charges, usage charges and internal staff time; it is a comparison of known charges, not the final payable amount.

For migration, ask for the agreed URL decisions and destination check results. Google’s site move guidance covers preparation, URL mapping, redirects and monitoring. The proposal should assign those tasks and the review after launch. Search rankings can fluctuate during a move; a promised position gives little help in assessing implementation scope.

For accessibility, request the evaluation scope, findings, corrections and retest record. W3C’s guidance calls for assessment throughout development and knowledgeable human evaluation alongside tools. Ask whether important journeys, such as completing a form, are covered and whether specialist assessment or participation by disabled users receives a separate scope.

First establish whether page addresses will stay the same. A visual redesign can retain its URLs; a change to the domain or page structure may need a URL migration plan. Ask each supplier to describe the actual changes before comparing the SEO line in a quotation.

Use this proposed handover record to turn delivery tasks into evidence you can review. Assign each item to a named person and agree how exceptions affect acceptance.

Ask which pages and conditions will be measured. Core Web Vitals cover loading, responsiveness and visual stability. Google distinguishes controlled lab tests from field measurements of actual visits. Ask for mobile test conditions before launch and an agreed review of visitor data when sufficient evidence becomes available. Treat a single score as one observation within that record.

These currencies describe Branding Tatva’s website quotations. Each supplier sets its own billing terms, so confirm the currency in each proposal. Website work receives a separate scope and fee from brand strategy packages.

A Canadian brief may require English and French; a UAE brief may require English and Arabic; an Indian brief may include Hindi or regional languages. Name the pages, writer, translator and approver required for your audience. Include navigation, forms, confirmation messages and future updates.

For every market, agree the meeting time zone, review window, feedback owner and launch support window. Record any required hosting or data location and who confirms it. Resolve these decisions before signing. The proposal should identify the delivery team and where its responsibilities begin and end.

Share your current website, required pages and the points you want clarified. You can discuss responsibilities without sharing another supplier’s confidential proposal. Suman Sharma leads strategy and messaging. The proposal identifies the delivery team, fee and acceptance evidence for your project.