

How to Write a Website Redesign RFP (Free Template and Scoring Rubric)
A website redesign RFP (request for proposal) is a document that explains who your organization is, what your new website needs to accomplish, your scope of work, budget range, project timeline, and how you will choose a partner. A great website RFP is short, specific about business goals, and gives web agencies enough detail to send proposals you can compare side by side.
I have read and responded to a lot of website RFPs, from historic trail alliances to economic development partnerships to community foundations. The best ones make it easy for the right agency to say yes. The weakest ones are 40 pages of requirements with no budget, which usually means fewer strong proposals and a harder decision. A great RFP sets up the whole redesign process for success. This guide walks through the full RFP process: what to do before you write, what to include in your web design RFP, the mistakes that lead to vague proposals, how to choose a partner, and a free redesign RFP template you can copy.
What is a website redesign RFP?
A website redesign RFP is a formal request your organization sends to web agencies and developers asking them to propose how they would rebuild your site, what it would cost, and how long it would take. Nonprofits, schools, associations, foundations and public partners use RFPs because procurement rules or board policies require a fair, documented selection process.
An RFP is different from an RFQ (request for quote) or an RFI (request for information):
- RFP: asks agencies to recommend an approach, timeline and price
- RFQ: asks for a cost estimate on a scope you have already defined
- RFI: gathers information about potential vendors before you are ready to buy
For most website projects, an RFP is the right fit because you want expert recommendations on the design process, not just a price on a fixed list.
Why a good RFP matters
A website project touches almost everyone in your organization, from program staff to the board. A clear request for proposal leads to better outcomes for everyone, and it does four things for you:
- It forces internal alignment. Writing the RFP makes your team agree on goals, requirements and budget before you talk to agencies.
- It attracts strong proposals. Experienced agencies are selective about which RFPs they answer. Clear goals and a realistic budget range signal a funded, well-run project.
- It makes proposals comparable. When every agency responds to the same structure, your selection committee can make an informed decision instead of comparing apples to oranges.
- It prevents scope creep. A documented scope of work sets expectations for both sides once the project starts.
Vague RFPs lead to vague proposals. Agencies fill the gaps with assumptions, and those assumptions show up later as change orders or missed expectations.
Before you write: get your team on the same page
The strongest RFPs start with a little homework. Spend a week or two on these steps before drafting.
Identify stakeholders and a project manager
List everyone who will influence the new site: executive director, development or marketing lead, program staff, IT, and board members. Then name one internal project manager who will be the agency’s main contact and one person (or small group) with final approval. Projects with a clear decision maker move faster and cost less.
Capture a baseline
Pull 12 months of data from Google Analytics (GA4) and Google Search Console before you write. Note monthly visitors, top pages, donation or registration conversions, mobile versus desktop traffic, and the search terms people use to find you. This baseline lets you set realistic success metrics and measure the new site against the existing website after launch.
Inventory your content
Count your pages, blog posts, PDFs, forms and media. Flag what is outdated, what is missing, and what must carry over. Content migration is one of the biggest drivers of overall cost and timeline, so knowing the size of your existing site helps agencies give an accurate cost estimate.
Talk to your users
A few short conversations with donors, members, families, volunteers or prospective students will tell you more than any internal meeting. Ask what they come to the website for and what frustrates them. Those answers become your user personas and your target audience section.
What should be included in a website redesign RFP?
Every website RFP should answer the questions an agency needs to scope the web project accurately. Here are the sections to include, in the order agencies expect to see them.
1. Organization overview
Share your mission, who you serve, your service area, and your team size. Two or three paragraphs is plenty. Include the drivers behind the project: a rebrand, a new strategic plan, a failing platform, or a growth goal.
2. Project goals and success metrics
This is the most important section of your RFP. Define goals as outcomes, not features. Instead of “we want a modern website,” describe what the new website needs to do:
- Increase online donations or memberships
- Make program information easier to find
- Drive event registrations or volunteer sign ups
- Support lead generation for programs, services or sponsorships
- Reduce staff time spent updating content
- Meet accessibility requirements
Three to six success metrics is the sweet spot. Tie each one to a trackable KPI and your baseline, like “grow online donations 20% in the first year” or “cut the time to publish an event from a day to under 15 minutes.” Clear goals help agencies propose the right solution instead of guessing.
3. Your current website and what is not working
Agencies need to understand the starting point. Include:
- Your current website URL and content management system (CMS), including version
- Approximate number of pages, blog posts and documents (PDFs)
- Current web hosting provider and who maintains the site
- Integrations, such as donation platforms, CRM, email marketing, event calendars or member portals
- Analytics access and recent traffic trends
- What staff and users find frustrating today
Be honest here. If the existing website is hard to update, slow on mobile, or losing search visibility, say so. That context shapes the whole proposal.
4. Target audience and user personas
List your primary audiences (donors, members, families, partners, volunteers, current students, prospective students, the public) and what each one needs from the website. If you have user research, survey results or personas, attach them. Specifying your target audience is one of the best ways to guide agency proposals toward the right content strategy.
5. Scope of work and deliverables
Spell out the services you expect. Most website redesign projects include some or all of these:
- Discovery, stakeholder interviews and content strategy
- Information architecture and sitemap
- Custom website design (homepage plus key page templates)
- Web development on your chosen CMS
- Content migration from the existing site
- Copywriting or content editing
- Search engine optimization (SEO) setup, including 301 redirects from old URLs
- Accessibility compliance with WCAG 2.2 AA
- Analytics and conversion tracking (GA4 and Google Tag Manager)
- Staff training and documentation
- Web hosting, security and ongoing website maintenance
If something is optional, label it optional and ask agencies to price it separately. That keeps proposals comparable and lets you see the cost of each piece.
6. Technical requirements
Name your must haves. Common technical requirements include:
- CMS: a specific platform and version, or a request that agencies recommend one. WordPress is the most common choice for nonprofits because staff can update it easily and many agencies support it.
- Integrations: list every system the site must connect to, such as your donation platform, CRM, email tool, event calendar, learning platform or member database. If you need a web application, like a member portal, course platform or e-commerce store, describe it in more detail.
- Accessibility: require WCAG 2.2 AA compliance and ask how the agency tests for it.
- Security and hosting: uptime expectations, backups, SSL, and any security documentation your IT team requires. Larger organizations sometimes ask for a vendor’s SOC 2 Type 2 report.
- Content portability: ask how content can be exported from the CMS if you ever change providers.
If you do not have a platform preference, say so and ask each service provider to recommend one with reasons.
7. Budget range
Include a budget range. This is the single biggest factor in getting realistic, comparable proposals. Without one, one agency proposes a quick template build and another proposes a fully custom platform, and neither is wrong. A range lets agencies show you the best solution within what you can actually spend.
If your board will not let you publish a number, give a ceiling or a band, like “under $40,000” or “$25,000 to $50,000 including the first year of maintenance.” Transparency in budget helps vendors tailor their proposals accurately and saves everyone time.
8. Project timeline and key milestones
List your key dates so agencies can confirm availability. Separate procurement milestones from project milestones:
| Milestone | Example date |
|---|---|
| RFP released | March 1 |
| Questions due | March 10 |
| Answers shared with all bidders | March 14 |
| Submission deadline | March 28 |
| Finalist interviews | April 7 to 11 |
| Agency selected | April 18 |
| Project kickoff | May 1 |
| Design approval | June 15 |
| Content migration complete | August 15 |
| Site live | September 15 |
Most organization websites take three to six months from kickoff to launch. Content and approvals are usually what slow a project down, so build in room for them. If you have a hard deadline, like an annual gala, enrollment season or product launch, explain why it matters.
9. Proposal requirements
Tell agencies exactly what to submit so you can compare good proposals easily:
- Company overview and team bios
- Relevant experience with similar organizations
- Two or three case studies or portfolio examples with real data
- Proposed approach, design process and proposed timeline
- Itemized cost proposal, including ongoing maintenance
- Three client references
- Proof of insurance or other required documents
Set a page limit. Ten to fifteen pages is enough for a thoughtful response, and agencies prefer concise, structured RFPs over bloated ones.
10. Evaluation criteria
Share how proposals will be scored. It helps agencies focus on what matters to you, and it gives your selection committee a fair, documented process. Here is a simple rubric that scores proposals on the following criteria:
| Selection criteria | Weight |
|---|---|
| Relevant experience and portfolio | 25% |
| Proposed approach and understanding of goals | 25% |
| Cost and value | 20% |
| Team and project management | 15% |
| Client references | 15% |
11. Submission details
Include the submission deadline (with time zone), how to submit (email or portal), the contact person for questions, and whether you will accept questions by email or hold an informational call. Commit to sharing every answer with all bidders so everyone works from the same detailed information.
Questions to ask agencies in your RFP
Beyond the standard sections, a few targeted questions reveal a lot about potential partners:
- How will you protect our current search rankings during the redesign?
- How do you test for accessibility, and what happens if an issue is found after launch?
- Who will be our day to day contact, and how often will we meet?
- What do you need from our team, and when, to keep the project timeline on track?
- How do you handle requests that fall outside the agreed scope?
- What does ongoing support look like after the site is live?
- How do you use AI tools in your process, and how do you review AI-assisted work?
Add any specific requests unique to your organization, too. The answers show you how an agency thinks, not just what it charges.
Common website RFP mistakes to avoid
These are the patterns that most often lead to fewer proposals or a poor fit:
- No budget range. You get proposals that are impossible to compare.
- Designing the site inside the RFP. Describe goals and requirements, and let agencies recommend the design solution. That is what you are hiring them for.
- Very short response windows. Two weeks or less often means the best agencies are already booked. Give at least three weeks.
- Forgetting content. Someone has to write, edit and migrate content. Decide whether that is your team or the agency.
- Skipping SEO and redirects. A redesign without a redirect plan can wipe out years of search visibility. Ask agencies how they protect existing rankings.
- Ignoring maintenance. Ask for ongoing support pricing so you know the true first year cost.
- No question period. A short Q&A window, with answers shared with every bidder, produces much better proposals.
- Too many decision makers. A committee of twelve slows every approval. Keep the core team small and loop others in at set review points.
What agencies look for before they bid
From the agency side, we decide whether to respond to an RFP based on a few signals:
- A clear budget and timeline. It tells us the project is funded and real.
- Specific goals. We can show you a thoughtful approach instead of a generic one.
- A defined selection process. Knowing who decides and how proposals are scored builds trust.
- A reasonable scope for the budget. When scope and budget line up, you attract experienced firms instead of only the lowest bidder.
- Room to recommend. A strong website RFP describes the problem, not the exact solution, and gets more creative and more useful responses.
If your RFP checks those boxes, you will get strong proposals from agencies that fit your organization.
How to choose the right agency after proposals arrive
Once proposals come in, follow a simple, repeatable process:
- Score independently first. Have each committee member score every proposal against your evaluation criteria before you discuss them as a group.
- Shortlist two or three finalists. Invite them to a 60 minute interview or presentation.
- Ask finalists to walk through a similar project. Listen for how they handled challenges, not just the finished result.
- Call references. Ask about communication, timeline, budget and what the client would do differently.
- Compare total cost of ownership. Look past the build price to hosting, maintenance, licenses and future updates.
- Choose a great partner, not just a price. A website redesign is only the beginning. You will work with this team for months, and often years.
Notify every bidder of your decision. It is a small courtesy that builds goodwill for your next project.
Free website redesign RFP template
Copy this outline into your own document (Google Docs or Word work well) and fill in each section:
- Organization overview: mission, audiences, service area, project drivers, project manager and decision maker
- Project goals: three to six goals with measurable success metrics and baselines
- Current website: URL, CMS and version, page count, integrations, hosting, analytics, pain points
- Target audience: who uses the site, user personas, and what each audience needs
- Scope of work: required services and deliverables, with optional items labeled
- Technical requirements: CMS, integrations, accessibility requirements, hosting and security
- Budget range: a band or ceiling, and whether maintenance is included
- Project timeline: procurement dates, kickoff, key milestones and target launch
- Proposal requirements: what to submit and page limit
- Evaluation criteria: scoring categories and weights
- Submission details: submission deadline, format, contact and Q&A process
Have questions about your RFP before it goes out? Email us and we are happy to talk it through.
Website redesign RFP FAQs
How long should a website redesign RFP be?
Most effective website RFPs are 5 to 15 pages. That is long enough to explain goals, scope, budget and timeline, and short enough that agencies can respond thoughtfully. Attach supporting material like analytics reports or brand guidelines as appendices.
Should we include a budget in our RFP?
Yes. A budget range is the best way to get proposals you can compare. Agencies use it to recommend the right level of design, development and content support instead of guessing.
How many agencies should we send our RFP to?
Inviting five to eight qualified agencies usually produces three to five strong proposals. Posting publicly can bring in more responses, but plan time to review them.
How long does a website redesign take?
Most nonprofit and organization websites take three to six months from kickoff to launch. Larger sites with complex integrations, many stakeholders or heavy content migration can take longer.
What is the difference between an RFP and an RFQ for a website?
An RFP asks agencies to propose an approach, timeline and price. An RFQ asks for pricing on a scope you have already defined. Use an RFP when you want expert recommendations.
Should our new website be built on WordPress?
WordPress is a strong choice for most nonprofits and organizations because it is flexible, widely supported, and easy for staff to update. If you have specialized needs, ask agencies to recommend a platform and explain why.
Need a partner for your website redesign?
Aurelia Digital is a boutique web design and digital marketing agency in Durango, Colorado. We build WordPress websites for nonprofits, schools and organizations across the Four Corners and beyond, with SEO, accessibility and analytics built in from day one. If you are planning a redesign or have an RFP ready to share, send it our way or call 970-799-4911. Planning a full rebuild? See our nonprofit website design services.









Leave a Reply