withMission.techStart a conversation

How to Write a Nonprofit Website Redesign RFP (With a Template)

An RFP for website redesign usually gets written in the fortnight before a board meeting, by someone who has never written one, from a folder of complaints about the current site. It asks five agencies to price a site nobody has described. Five proposals come back on five sets of assumptions, and the organization picks the one that felt best in the room.

A redesign moves URLs, form data, integrations, analytics, and account ownership along with the design, and most RFPs describe only the design. This guide covers writing a nonprofit website RFP from what the current site demonstrably does, with an owner named for every piece that outlasts the agency's contract. The template is in section six.

01Why most website redesign RFPs get bids you cannot compare

Most website redesign RFPs are wishlists. They describe the site the organization imagines, in its own vocabulary, and list features someone admired on a peer's site: a modern look, an events calendar, a bigger donate button, pages staff can edit without calling anyone. Then they ask vendors to price it.

One bidder assumes you will write the content and quotes for design and build. Another assumes it is writing the content and quotes several times as much. Neither mentions redirects, because the RFP never did, and nothing on either quote says which assumption produced which number. Whoever wins, the content is still unwritten in month three because nobody agreed who was writing it, and in month seven search traffic falls and nobody can find a list of the pages the old site had.

Any competent designer can answer "the site looks dated" and leave untouched the things that decide the outcome, such as whether the donation flow keeps people. Those are missing from the RFP because nobody measured them first.

02Observed requirements: the review that comes before the RFP

Before anyone drafts the RFP, somebody spends a few weeks finding out what the current site does and writes it down in a form a stranger could check.

A wishlist says "we want a modern, mobile-friendly site with better donation conversion." An RFP built on a review says something like this: sixty-two percent of sessions are on a phone, the donation flow loses seven in ten people at the details step, eleven named URLs produce most of the search entrances and must keep working, and four forms send submissions to inboxes nobody reads. Every bidder is now pricing the same job.

What to measure first

Five measurements do most of the work. None needs a design opinion, and someone with admin access can pull each in an afternoon.

  1. 01
    The device split over twelve months, for all sessions and then for only the people who completed a donation or signup. If visitors arrive on phones and donors finish on desktops, that gap belongs in the RFP.
  2. 02
    Entrances by page, sorted by where people land first rather than by pageviews. The list will not match your navigation, and near the top you will find old pages nobody on staff would have picked.
  3. 03
    Conversion counts for each flow (donate, subscribe, register, volunteer, contact): how many started, how many finished, and the step where the rest stopped. Most donation platforms report the first two. The third means walking the flow yourself on a phone.
  4. 04
    The URLs that earn search traffic and inbound links, from Search Console and a backlink tool. A program page a funder links to has an address, and if the address changes without a redirect, the link breaks and the page's search standing goes with it.
  5. 05
    Where each form lands: what it collects, which system receives it, and who reads it. Expect a contact form still mailing someone who left two years ago.

Observed versus inferred

Then label every finding. Observed means somebody saw it happen or read it in a report. Inferred means a reasonable conclusion from what was seen. "The volunteer form sends to a shared inbox with nine hundred unread messages" is observed. "Volunteers drop out because nobody replies" is inferred. Both go in the RFP with their labels, so a bidder can price the certain work firmly and ask about the rest. The label also catches the organization's own unchecked beliefs, such as the certainty that most donors give online, before a vendor designs around them.

03Who you are actually hiring

Three kinds of firm answer website redesign RFPs, and each is good at real work. A proposal is shaped by what its author considers the job, so the parts a firm sees as someone else's job are usually absent rather than declined.

  1. 01

    A marketing firm

    What the proposal covers

    Brand and messaging, audience research, content strategy, a design that tells your story well, and a launch plan built around announcing the new site.

    What it usually leaves out

    The redirect map, analytics continuity, where each form's submissions go, credential handover, and the year after. The engagement is built around the announcement and ends once it has gone out.

  2. 02

    A web design studio

    What the proposal covers

    Information architecture, templates, visual design, the build on a CMS, content loading, accessibility work, and a launch checklist. Good studios raise redirects before you do.

    What it usually leaves out

    Less than a marketing firm. Credential handover and analytics on the live site still tend to go missing, along with anything past "the form sends an email" and CRM work beyond embedding a widget. The contract ends at a working site on launch day, and the year after is an optional retainer on the last page.

  3. 03

    A technology partner

    What the proposal covers

    The migration: every item the other two leave out, with a maintenance owner for the year after.

    What it usually leaves out

    Brand and design work, copywriting included, which a technology partner will subcontract or tell you to buy elsewhere. Its scope runs past launch day, since a migration is unfinished until data arrives where it should.

A marketing firm that leaves the redirect map out is working to its scope, and most will say so if you ask. Trouble starts when the organization assumes one hire covers all three.

So give every left-out item its own line in the scope, even when the bidder will not own it, and beside it write "bidder" or the staff member or partner who will do it. A bidder who reads "redirect map: bidder" and prices it has told you something. So has one who skips the line.

The migration work has its own guide, website redesign SEO, which follows the redirect map from inventory through the ninety days after launch. If nobody on staff can own the items that outlast launch day, that standing role is what a fractional CTO for nonprofits engagement is for.

04What a website redesign RFP should include

If you are working out how to write a website RFP from nothing, start from this list, in roughly the order a bidder needs it.

  1. 01
    Who you are, in two paragraphs a stranger could follow: what the organization does and what it needs a visitor to do. If staff cannot write this, the site will not say it either.
  2. 02
    What the current site does: the five measurements above, labeled.
  3. 03
    Goals as measurable outcomes. "More donations" is a hope. "Raise completion on the donation flow from its current rate, measured the same way for ninety days after launch" is a goal a bidder can design toward and you can check.
  4. 04
    Scope, with content responsibility spelled out: the number of page templates, the rough page count, and who writes the content and who edits and loads it. Unclear content ownership is the most expensive ambiguity an RFP can contain.
  5. 05
    Technical constraints and every integration: the CMS, hosting, the donation platform, the CRM, the mail platform, event registration, and whatever cannot change. If the CRM itself is about to be replaced, settle that first. The guide to choosing a nonprofit CRM covers the order.
  6. 06
    The non-negotiables in the next section, worded as contract terms.
  7. 07
    The URL inventory, attached, with every URL already marked keep, redirect, or retire and its traffic and link data beside it.
  8. 08
    A real budget range, and a timeline with the dates that cannot move, such as a gala or year-end giving.
  9. 09
    Evaluation criteria in the order you will weigh them, and who decides.
  10. 10
    How questions will be handled, with every answer sent to every bidder.
  11. 11
    The owner lines from the section above, one for every item a bidder might leave out.

05The non-negotiables, defined

Six terms belong in the RFP as requirements and in the contract in the same words.

  1. 01

    A one-to-one 301 redirect map

    A redirect map pairs every URL on the old site with its closest equivalent on the new site and serves each pair as a permanent 301 redirect. One-to-one rules out sending retired pages to the home page, which search engines read as a missing page. The bidder builds it from your inventory and checks every row on the live site in launch week.
  2. 02

    Title, description, and heading carryover

    On the named pages that earn search entrances, the new site keeps the existing page title, meta description, and heading structure, or changes them on purpose with the reason written down. A template that generates titles from page names throws away what the old ones earned.
  3. 03

    WCAG 2.2 AA, named in the contract

    The contract names the Web Content Accessibility Guidelines 2.2 at level AA as the conformance target, tested with a keyboard and a screen reader as well as an automated scan, with failures fixed before sign-off.
  4. 04

    Analytics verified on the live site

    Analytics and conversion tracking are confirmed working on the production site, flow by flow, before final sign-off. Tracking often breaks silently at launch, and without it nobody can show what the redesign changed.
  5. 05

    Full handover

    At the end of the project the organization holds, in its own name, the domain registration, DNS, hosting account, CMS administrator access, source code, and design files. Your staff log in to each one before the final invoice is paid.
  6. 06

    A maintenance owner for the year after

    The RFP names who maintains the site for twelve months after launch, what that covers (updates, security patches, broken forms, small content changes), and what it costs, as a line in the bid or an arrangement already made elsewhere.

Handover raises the same custody question as a staff departure. The guide to nonprofit knowledge transfer covers keeping accounts in the organization's name between projects.

06A website redesign RFP template

The examples are for an invented organization, Anytown Literacy Project. Replace each with your own evidence. A row you cannot fill is where your review should start.

  1. 01

    About us

    Two paragraphs a stranger could follow.

    Example line

    Anytown Literacy Project runs free reading classes for adults in Anytown County. Most visitors come to enroll or to volunteer as tutors.

  2. 02

    The current site, observed

    The five measurements, labeled observed or inferred.

    Example line

    Observed: 64% of sessions are on a phone. 71% of people who start the donation form leave at the address step. Inferred: tutor applicants drop off because the form sends no confirmation.

  3. 03

    Goals

    Two to four outcomes. Give each a baseline and a time window.

    Example line

    Fewer than the current 71% leaving the donation form at the address step, measured the same way for 90 days after launch. No tutor application lost to an unread inbox.

  4. 04

    Scope

    Count the templates and, roughly, the pages. Say who writes the content and who loads it.

    Example line

    Seven templates, about 120 pages. Our staff write new program pages. The bidder edits and loads the rest.

  5. 05

    Integrations

    Every system the site touches.

    Example line

    Donation platform (embedded form), CRM (tutor applications), mail platform (newsletter), class enrollment tool.

  6. 06

    Constraints

    What cannot change, and why.

    Example line

    We keep the current donation platform through the fiscal year. Enrollment must work in English and Spanish.

  7. 07

    URL inventory

    Attach the spreadsheet. Every URL gets a decision before the RFP goes out.

    Example line

    Attached: 214 URLs. 96 keep, 81 redirect with targets named, 37 retire after checking traffic and links.

  8. 08

    Non-negotiables

    The six terms from the section above, in the contract's wording.

    Example line

    All six as written in our draft contract, with carryover applying to the 20 named pages in the inventory.

  9. 09

    Ownership after launch

    For each item a bidder may not own, who does.

    Example line

    Redirect map: bidder. Form destinations: bidder, with our CRM administrator. Year-after maintenance: bidder to price separately.

  10. 10

    Budget and timeline

    Your range, stated plainly, and the dates that matter.

    Example line

    Our budget range is [your range]. Launch after spring enrollment, well before year-end giving.

  11. 11

    Evaluation

    Criteria in the order you will weigh them. Name who decides.

    Example line

    1. Answers to the eight questions. 2. Year-two references. 3. Fit to scope. 4. Price. The executive director and board chair decide.

  12. 12

    Questions and dates

    How bidders ask questions, and when proposals are due.

    Example line

    Questions to our operations manager by the 10th. Every answer sent to every bidder by the 15th. Proposals due the 30th.

07Eight questions to ask every bidder, and the red flags

Send these to every bidder in writing and ask for written answers.

  1. 01

    Show us a nonprofit site you launched at least eighteen months ago. What happened to its traffic and conversions afterwards?

    Portfolios show launch day. Whether the firm knows how year two went is part of the answer.

  2. 02

    Who writes the content, and what happens when ours is late?

    A firm that has lived through late content can describe what it does about it.

  3. 03

    How do you handle URLs and redirects at launch?

    Listen for a mapped inventory and bulk checking on the live site. Hesitation here predicts more than anything else you will hear.

  4. 04

    How do you test accessibility?

    The answer should match the accessibility term above. An automated scan on its own does not.

  5. 05

    Which parts of our scope do you think we do not need?

    The firm worth hiring will talk you out of something. The rest will price it all.

  6. 06

    How will you confirm that analytics and every form work on the live site before we sign off?

    Ask who checks, and on which day.

  7. 07

    Who holds the accounts and files when we are done?

    Your organization, in the words of the handover term.

  8. 08

    What went wrong on your last project, and what did you change?

    Every firm has one.

The red flags

  1. 01

    No questions in the proposal

    A bid priced from the RFP alone, with nothing to clarify, is a bid for a template. Serious responses arrive with awkward questions about content and integrations.
  2. 02

    They run discovery and bid on the build

    The firm that will quote the build has a stake in what discovery finds. That is ordinary commerce, and it is why your own evidence comes first and their discovery stays short.
  3. 03

    Redirects and analytics left out

    A proposal without them shows you where the firm thinks its job stops.
  4. 04

    An all-visual nonprofit portfolio

    Handsome mission sites are easy to show. Ask about the donation flow, the CRM connection, the program directory, and the translated pages, which are what make nonprofit sites hard.
  5. 05

    A rebuild before anyone looked

    Sometimes a rebuild is right. A firm that recommends one in the first meeting got there without looking at your site.
  6. 06

    Vague ownership

    Hosting on their account, the domain at their registrar, no source handover, and a retainer that is really the fee for access. Settle ownership now, while leaving is hypothetical.

08How to run the evaluation

Lay the proposals side by side against the RFP's scope and ownership lines and mark each one included, excluded, or silent. Treat silent as excluded. A bid that says nothing about the redirect map does not include one, whatever is said on the call, and a bid far below the others has usually skipped a line this way.

Score the answers to the eight questions before anyone sees price. Two or three people score alone on a simple scale, then compare. Where scorers disagree there is usually an answer worth a follow-up call.

For references, ask for a site that launched at least eighteen months ago and ask about year two. Did traffic hold? Did the forms keep working? Could staff make changes without calling the firm? How did maintenance cost compare with the estimate?

With two finalists left, a paid discovery of a week or two shows how each works on your own problem. Put your review document at the center of it so neither starts from scratch at your expense. Then decide in the order you said you would, and tell the bidders you did not choose why.

09Questions we get asked

What should a website redesign RFP include?
Who you are, written for a stranger. What the current site does, measured and labeled observed or inferred. Goals as measurable outcomes. Scope, including who writes the content. Every integration. The non-negotiables: a one-to-one 301 redirect map, metadata carryover, WCAG 2.2 AA, analytics verified on the live site, full handover, and a named maintenance owner. The URL inventory with decisions made. A real budget range and timeline. Evaluation criteria in order. How questions will be handled.
How long should a website RFP be?
Six to ten pages covers most nonprofits, plus the URL inventory as a spreadsheet. The test is whether two bidders reading it would price the same job. Long RFPs are usually long because of adjectives and procurement boilerplate borrowed from a larger organization. Cut those before you cut a measurement.
Should we share our budget in the RFP?
Yes. Without a range, bidders scope for organizations of different sizes, some too small to do the work and some far past what you can spend, and you lose weeks sorting them. With a range, every bidder proposes the best project that fits it.
Do we need an RFP for a small website?
Not a formal one, but you still need the document. A small organization hiring one freelancer can skip the scoring panel. It should not skip the short written version of an RFP for website design: what the current site does, who writes the content, the URL inventory with redirect decisions, the integrations, and who owns the accounts at the end.
Can our marketing agency write the RFP?
It can help, and a good one will write the audience and messaging sections well. An agency drafting an RFP it may bid on has an interest in where the scope lines fall, and marketing agencies tend to draw them around marketing work. If yours drafts it, have someone with no stake in the build review the redirect, form, analytics, and handover lines before it goes out.
Who should own the website after launch?
The organization should hold every account and file in its own name, the domain and hosting included. Maintenance is a separate question. Someone has to be named for the year after launch, whether that is the agency on a retainer, a staff member with real hours set aside, or a technology partner. If the RFP does not ask, the answer defaults to nobody.

Start with the evidence the RFP needs

A Mission Surface Review produces the observed requirements this guide keeps asking for, every finding labeled, in a document you own and can attach to any RFP. We do not bid on the build that follows. If you are still deciding whether you need a redesign at all, the guide to planning one starts a step earlier.