Your website redesign RFP should define your business goals, project scope, vendor requirements, priced deliverables, submission rules, and weighted evaluation criteria so you receive comparable agency proposals. With those details agreed on internally, you give agencies a consistent basis for estimating the work and give your selection team a defensible way to choose a partner.
You also need to expose the uncertainties: unfinished content, undocumented integrations, approval bottlenecks, and migration risks. Through Sacramento Web Design Group’s strategy-led WordPress approach and more than 30 years of local experience, you get a practical perspective on connecting procurement requirements with a website your team can maintain after launch.
Your website redesign RFP should give every bidder the same business context and scope assumptions. Include enough detail to price the project while leaving room for vendors to explain their recommended approach. For procurement planning, consult the Federal Acquisition Regulation’s solicitation structure as an example of how formal proposals organize requirements.
Use the following structure as your procurement document, replacing each bracketed prompt with your project details. Keep supporting inventories and technical documentation in appendices so your core requirements remain easy to review.
Assign requirement IDs such as TECH-01 or SEO-03 wherever you need a direct vendor response.
Connect your redesign to measurable business outcomes. Specify your priority audiences and the actions you want them to complete, such as requesting a consultation or purchasing a product.
Replace “improve lead generation” with a defined target: “Increase qualified consultation requests from [baseline] to [target] within [measurement period].” Identify who determines lead quality and where you record conversions.
Document your current problems with evidence:
Separate launch acceptance from post-launch business results. Your vendor controls implementation quality; your conversion results also depend on traffic quality, offers, and follow-up.
Quantify your scope using page templates, content records, and functional requirements. A 200-page website with six reusable layouts presents a different workload from 200 individually designed pages.
State who supplies your copy, photography, product data, and legal notices. Assign a named decision-maker and a review turnaround for each approval stage.
For your eCommerce requirements, identify product variations, payment gateways, shipping rules, tax services, and account functionality. List excluded systems explicitly, including any application portal that only needs an outbound link.
Ask vendors to identify assumptions and describe how they will price changes when your inventory differs from the supplied estimate.
Use your RFP to manage competitive procurement: bidder eligibility, pricing consistency, response requirements, and selection. Use your website design brief to communicate creative direction and audience needs during project delivery.
Include enough brand context for an agency to assess the assignment. Save detailed visual exploration and final layout decisions for paid discovery and design work.
When you include inspirational websites, explain the specific feature you value. A useful note identifies navigation behavior or content hierarchy without implying permission to reproduce another company’s design.
Use your website redesign RFP to require evidence of relevant delivery experience and written commitments about how your project will operate. Your vendor requirements should reveal who will perform the work and how you will retain control of your website. For accessibility requirements, reference the W3C Web Content Accessibility Guidelines (WCAG 2.2) and specify which success criteria vendors must meet.
Request two or three comparable projects, including each agency’s precise role. Ask for scope, implementation challenges, launch timing, and outcomes with measurement periods.
For custom WordPress design, request an explanation of the proposed theme architecture, editing experience, and plugin selection process. Ask how your staff will create new pages without disrupting approved layouts.
Require names or clearly defined roles for your project manager, designer, developer, and quality assurance lead. Request disclosure of subcontractors and identify who remains accountable for their work.
Collect references during shortlisting, then verify that the people presented in the proposal will participate in your engagement.
Ask vendors to connect their discovery activities to specific decisions. Your proposal should explain how audience research influences navigation and how keyword research informs your content plan.
If you need brand messaging and visual identity work, specify whether your scope includes positioning, logo refinement, or a full identity system. Require separate pricing for substantial brand development.
Define your website copywriting requirements by page count, approximate length, interviews, and revision rounds. For SEO, request responsibility for technical audits, metadata, internal linking, and migration monitoring.
If vendors propose AI-assisted work, require disclosure of permitted uses, human review, and restrictions on uploading confidential information.
Specify your accessibility target, such as WCAG 2.2 Level AA, and define the pages and user journeys covered by testing. Ask for automated checks plus manual keyboard and assistive-technology testing.
Have your legal adviser confirm the obligations that apply to your organization. Keep the technical accessibility target and legal review responsibilities explicit.
For security, require:
Request a quality assurance plan covering supported browsers, devices, integrations, and defect reporting. Require written test results before launch approval.
Require your proposal to distinguish ownership of custom work from third-party licenses. State your expectations for source files, repositories, content, and administrator credentials.
Keep your domain registration and critical business accounts under your organization’s control. Ask vendors to disclose hosting restrictions, migration fees, premium plugin renewals, and any license that ends when your support agreement ends.
Define your support coverage by service hours, response targets, and escalation process. Distinguish a defect warranty from paid maintenance and new feature development.
Require an exit procedure covering your database export, media files, credentials, and handover assistance.
In your website redesign RFP, define each deliverable by quantity, format, review allowance, and acceptance condition. You will receive more useful bids when agencies price the same outputs and identify optional work separately.
Request a written discovery summary documenting your audiences, project risks, and unresolved decisions. Include an approved sitemap and a template inventory with a clear relationship between page types and layouts.
Specify which pages require wireframes and which require full visual designs. For each website design draft, define your review participants and included revision rounds.
Set approval gates before development begins. Your acceptance criteria might require approved desktop and mobile layouts for every unique template, with navigation behavior and reusable components documented.
If discovery will determine final scope, ask for a priced discovery phase and a defined method for approving the subsequent build estimate.
Translate your functional needs into testable behavior. For a lead form, specify required fields, routing, spam protection, confirmation messages, and CRM synchronization.
Identify each integration’s system owner, access requirements, and testing environment. Ask vendors to separate standard configuration from custom API development.
For migration, provide counts for pages, posts, products, documents, and media assets. State whether each category needs direct transfer, formatting cleanup, rewriting, or archival.
Include your mobile-responsive design requirements for navigation, forms, tables, and embedded content. Define your supported screen sizes and devices in the test plan, with attention to primary conversion paths.
Require a current URL inventory and an approved old-to-new URL map. Assign responsibility for implementing permanent redirects and checking for redirect chains, broken links, and missing destinations.
Your launch checklist should cover:
For performance, specify the test method and representative pages. If you use Core Web Vitals targets, identify LCP, INP, and CLS thresholds and distinguish laboratory checks from field data.
Account for third-party scripts in your performance assumptions. Require a rollback plan and a named launch decision-maker.
Define training by audience and task. Your editors need practice updating content, while your administrators need guidance on permissions and maintenance responsibilities.
Request recorded training, a concise editing guide, and instructions for common workflows. Include your backup restoration procedure and integration configuration notes in the handoff package.
Set a defined user acceptance testing period, such as ten business days, as a contractual proposal requirement. Specify how your team reports defects and what constitutes a launch-blocking issue.
Tie acceptance to documented completion: approved deliverables, working integrations, transferred access, completed training, and resolution of defects at the agreed severity levels.
Publish your website redesign RFP budget parameters and response instructions before agencies begin estimating. You give bidders a fair opportunity to respond when your deadlines, pricing assumptions, and required documents are consistent.
State your approved investment range and whether it includes content production, licensing, hosting, and post-launch support. If funding remains provisional, identify the approval dependency.
Request itemized fees for discovery, design, development, migration, testing, and training. Require separate totals for the base scope and optional enhancements, plus estimated recurring costs over a consistent period.
Ask for hourly rates and authorization rules for out-of-scope work. For a concrete pricing reference, Sacramento Web Design Group lists Project design / outside-of-scope piecework: $130 per hour. Treat that as a change-work rate; request a tailored proposal for your complete redesign.
Require vendors to disclose taxes, payment processing charges, and travel costs where applicable.
Publish dates for your RFP release, questions, shared answers, proposals, interviews, and intended selection. Identify your time zone and distinguish fixed deadlines from planning targets.
For delivery, request a dependency-based schedule. Your milestones should show when your team must supply content and approve work.
Ask each vendor to explain its project process through scheduled review points and deliverables. Confirm availability around your launch window before selection.
Document dependencies such as DNS access, payment provider approval, CRM credentials, and legal review. If your deadline is fixed, ask vendors to identify a feasible launch scope and separately priced later phases.
Give vendors a response order that matches your evaluation process. Require an executive summary, approach, deliverables, team, schedule, pricing, assumptions, exceptions, and relevant project examples.
For easy comparison, include a response matrix with these columns:
Specify your submission email or portal, file formats, size limits, and naming convention. Include an exact deadline with time zone, a procurement contact, and a proposal validity period.
State your policy for late submissions and whether you reserve the right to request clarifications or discontinue procurement, subject to your organization’s purchasing rules.
Use one written channel for vendor questions and publish a firm question deadline. Share substantive answers with every invited bidder so each proposal reflects the same information.
Remove identifying or confidential details from shared questions. If you hold a vendor briefing, distribute the same notes or recording to all participants.
Issue numbered addenda when your requirements change. Identify the affected requirement IDs and require acknowledgment in each proposal.
Extend the submission deadline when a material scope change requires additional estimation. Preserve your original RFP, addenda, and final responses as the procurement record.
Use a weighted scorecard in your website redesign RFP after checking mandatory eligibility requirements. Your selection should reflect documented evidence, delivery risk, and total cost across the same scope.
Set your weights before reviewing proposals. For a strategy-led WordPress redesign, you could adopt the following example and adjust it to your organization’s priorities.
| Evaluation criterion | Weight | Evidence you should assess |
|---|---|---|
| Business strategy and understanding of your needs | 25% | Discovery approach, audience insight, measurable objectives |
| Technical fit and implementation quality | 25% | WordPress architecture, integrations, migration plan |
| Relevant experience and assigned team | 15% | Comparable projects, individual roles, references |
| Delivery plan and project governance | 15% | Milestones, dependencies, risk management |
| Value and total cost of ownership | 15% | Complete scope, recurring fees, commercial clarity |
| Training and ongoing support | 5% | Handoff quality, service terms, editor enablement |
| Total | 100% |
Score each criterion from 0 to 5, then calculate score ÷ 5 × weight. Define your scale in advance: 0 for no response, 3 for meeting your requirements, and 5 for strong supporting evidence plus relevant additional value.
Have evaluators score independently before discussing differences.
Use pass/fail criteria for requirements your organization cannot waive. Examples include required insurance, acceptance of essential data protection terms, or support for a business-critical integration.
Reserve weighted scoring for differences in quality or approach. A preferred design style or local meeting availability belongs in this category unless your procurement rules make it mandatory.
Require vendors to identify exceptions explicitly. Determine whether you permit remediation before disqualifying a bidder, and apply that policy consistently.
Keep your mandatory list focused. Every additional gate reduces your eligible vendor pool and should connect to a documented business requirement.
Invite your shortlisted agencies to structured interviews with the proposed delivery team. Use the same core questions to ask a web designer so your comparisons remain consistent.
Ask how each team would address your highest-risk integration or incomplete content inventory. Request clarification of estimates and assumptions without soliciting unpaid speculative design work.
For reference checks, ask about budget changes, communication, editor usability, and post-launch responsiveness. Confirm what caused any schedule changes and how the agency handled them.
Record written clarifications and reconcile them with pricing before final scoring. If you change a shared requirement, communicate that change to every remaining bidder.
Convert your selected proposal into a statement of work with defined deliverables and acceptance criteria. Establish which document controls when your contract, RFP, and proposal contain conflicting language.
Tie payment milestones to observable progress, such as discovery approval, design approval, staging delivery, and handoff. Define your review obligations alongside the vendor’s delivery obligations.
Confirm intellectual property terms, license transfers, confidentiality, termination rights, and change-order approval. Have qualified counsel review terms with legal consequences.
Before awarding the contract, resolve open assumptions and verify the team’s start date. Notify unsuccessful bidders according to your procurement policy and retain your scoring record.
A successful website redesign RFP starts with a shared scope, measurable acceptance conditions, and a scoring method approved before bids arrive. Check that every requested deliverable has an owner and that every recurring cost has a place in your comparison.
Before issuing your website redesign RFP, discuss your project with Sacramento Web Design Group through a free 30-minute strategy and design consultation. Bring your draft scope, budget range, and launch constraints so you can discuss practical next steps and budget requirements.
Use your organization’s procurement rules to settle publication and document-control decisions before distributing your RFP. Keep the same official requirements available to every participating agency.
Post your RFP on your organization’s procurement page or required purchasing portal, then send it directly to a curated list of qualified agencies. If you use professional associations or vendor directories to broaden distribution, direct respondents to one official location for documents and addenda.
Yes, you can use a free template as a starting structure after replacing generic language with your scope and evaluation criteria. Remove irrelevant requirements and verify that your template covers migration, ownership, recurring fees, and acceptance.
Send your official RFP as an accessible, version-controlled PDF and provide editable response forms or pricing spreadsheets separately. Keep one authoritative copy and issue numbered addenda whenever you change its requirements.
Allow three to four weeks as a planning starting point for a moderately complex redesign, subject to your procurement rules. Give agencies more time when your response requires extensive technical analysis, partner coordination, or a mandatory briefing, and schedule shared answers before the submission deadline.
Yes, disclose your approved budget range and explain what it must cover. Require vendors to price your base requirements separately from optional work so you can compare complete proposals within that range.
