Website redesign RFP & procurement
Website redesign RFP: make agencies price the same problem
The purpose of a redesign RFP is not to prescribe every implementation detail. It is to give vendors the same business context, constraints and acceptance requirements so their proposals can be compared honestly.
Practitioner review
Malik Usman Awan
Project & Client Success Manager
Reviewed
2026-09-17
Meaningful update: 2026-09-17
Direct answer
Website redesign RFP: make agencies price the same problem
A useful website redesign RFP defines the business trigger, current-site constraints, page/content scope, migration risk, integrations, accessibility expectations, measurement, ownership, timeline, budget context, evaluation criteria and acceptance responsibilities. It should expose unknowns instead of forcing every vendor to guess differently.
Assumptions
- The buyer is comparing multiple providers or needs a durable internal project brief.
- The RFP can state what is known while leaving room for discovery where requirements are genuinely uncertain.
Limits
- Procurement rules and contract requirements vary by organization and jurisdiction.
- This guide is not legal advice and does not replace organization-specific procurement or accessibility obligations.
What an RFP needs to make comparable
| RFP field | What to state | Why it matters |
|---|---|---|
| Business trigger | Why the project exists and what is not working now. | Stops the exercise becoming a cosmetic feature list. |
| Page/content scope | Known pages, content owners, migration volume and approval responsibilities. | Prevents vendors from pricing different content workloads. |
| Technical/integration scope | CMS/platform constraints, forms, CRM, booking, analytics, email and other systems. | Makes integration and account dependencies visible. |
| Search migration | Existing indexed URLs, redirect expectations, canonical/indexing controls and monitoring responsibilities. | Protects against treating launch as a fresh site with no history. |
| Accessibility | Target standard/policy, critical flows, testing and responsibility boundaries. | Moves accessibility into planning and QA instead of a late add-on. |
| Performance & measurement | Performance expectations, analytics/key events and baseline continuity. | Makes launch quality and measurement part of acceptance. |
| Ownership & support | Domain/DNS, source, hosting, licences, handover, maintenance and change-control expectations. | Makes lock-in and recurring responsibility comparable. |
Ask vendors questions that reveal the delivery model
- Which assumptions in this RFP would you challenge before pricing?
- Which risks would you validate during discovery before design begins?
- How will you map existing URLs, content and redirects if structure changes?
- How are accessibility checks integrated into design, development and QA?
- Which analytics/key events will be preserved or deliberately replaced?
- What source, accounts and documentation are transferred at acceptance?
- What is a defect correction versus a new change request after approval?
Use evaluation criteria before proposals arrive
Define the comparison method before seeing the bids. A practical matrix can assess problem understanding, scope completeness, migration/accessibility/measurement controls, proof relevance, delivery ownership, handover clarity, commercial fit and the quality of assumptions raised by the vendor.
The matrix does not need a pseudo-scientific score. Its purpose is to stop the decision collapsing into the lowest headline price when the proposals include materially different work.
Keep discovery where uncertainty is real
A good RFP exposes unknowns instead of pretending they are solved. If content inventory, integration behavior, analytics history or platform constraints require investigation, state that explicitly and ask vendors to describe how they would resolve the uncertainty.
Working conclusion
The best RFP makes vendors price the same problem: scope, risk, responsibilities, acceptance and ownership should be comparable before the headline price is compared.
Evidence and further reading
Zolesco sources describe our own published scope and policies. External sources are used as decision-context evidence; they are not proof of Zolesco outcomes or endorsements.
Continue planning
Related buyer guides
Website redesign cost: what actually changes the quote?
A useful website redesign quote is not just a page-count number. It should make the work, responsibilities, exclusions and technical risk visible enough that two proposals can be compared on the same basis.
Read guide Provider selectionHow to choose a website redesign partner without relying on the sales pitch
The right provider is the one whose delivery model matches the risk and complexity of the project. A useful evaluation looks beyond portfolio aesthetics to scope clarity, who actually does the work, migration planning, acceptance, ownership and post-launch responsibility.
Read guide Redesign launch risk controlWebsite redesign launch risk control: URLs, analytics, accessibility and performance
A redesign launch is a controlled change to an existing digital property. Search migration is only one risk layer; measurement, accessibility, performance, forms, production behavior and ownership also need explicit acceptance checks.
Read guide