Website redesign / Procurement
How to Write a Website Redesign RFP
A useful RFP describes the business problem, current estate, constraints, and decision process while leaving room for a studio to recommend the solution.
Use an RFP when a structured comparison is necessary
An RFP is useful when procurement rules require consistent responses, several stakeholders need a documented decision, or the organization must compare multiple suppliers against shared requirements. A smaller business with a trusted shortlist may get better results from a concise brief followed by discovery calls.
Do not use an RFP to solve every design and technical choice before specialists are involved. State what is fixed, what is preferred, and what remains open. For a simpler first-contact document, use the website design brief guide.
Describe the business problem and current website estate
Explain the business, priority audiences, reason for redesign, desired customer actions, current problems, and evidence behind the project. Include the present URL, useful analytics or research, known high-value pages, content types, languages, integrations, accessibility obligations, security or legal constraints, and internal publishing needs.
List expected workstreams without assuming they are all included: discovery, information architecture, copy, design, development, content migration, redirects, analytics, testing, launch, training, and support. Name the internal owner, reviewers, content responsibilities, budget range, and real launch constraints. Unknowns should be visible rather than hidden inside a fixed-price request.
Ask for a response you can compare
Require each studio to explain its proposed approach, deliverables, assumptions, exclusions, team, responsibilities, timeline, price structure, change process, testing, ownership, and post-launch support. Ask for relevant evidence and the reasoning behind technical recommendations instead of a generic credentials deck.
Provide a response format that preserves meaningful differences. A table of compliance answers can sit beside a short narrative proposal. The proposal comparison guide can help define criteria for scope, responsibility, risk, and fit.
Publish the same process and information to every bidder
State the schedule for questions, answers, submission, presentations, decision, and anticipated start. Share material clarifications with all participating studios. Limit the shortlist to teams the organization can genuinely consider, and avoid requesting unpaid speculative design as a substitute for evaluating process and relevant work.
Score the response against the agreed business need, completeness, team fit, delivery confidence, ownership, and total responsibility—not price alone. Before appointment, resolve assumptions in a detailed proposal and contract. The RFP creates a fair starting point; the signed scope must still define exactly what will be delivered.
Turn procurement into a clear project
Preparing a website redesign RFP?
Northform can review the context, clarify open decisions, and propose a defined redesign scope with visible responsibilities.
Discuss your RFP Explore website redesign →