A nonprofit website design RFP helps your team compare how different partners would solve the same problem. Start with what visitors struggle to do today. A website could look dated and still work well enough. A site that makes it hard to find food assistance, donate on a phone, or update program hours is creating a problem your team can describe and test.
Use the sections below to write a request for proposal that is specific enough for a vendor to price and simple enough for a small committee to review. Ask whoever manages the site, donation reports, and program enquiries to contribute before the RFP goes out. Each person will see a different part of the problem.
1. Introduce the organization and the people the site serves
Give vendors a short summary of your mission, programs, geography, and team size. Identify the people who use the website and what they come to do. For a community food bank, people seeking support may need hours, eligibility and directions. Volunteers want to see upcoming shifts. Donors want to understand where their gift goes and complete it without running into confusing choices.
Share your existing website and two or three representative pages. If you have analytics, share a small, relevant summary such as common entry points or which devices people use. Frontline staff can also tell you what people call to ask. An increase in phone calls about a program's location might point to a website issue, especially if visitors give the same reason for calling.
2. Name the outcomes and how you will test them
Put your primary outcomes in priority order. For example, “A first-time visitor can find the nearest distribution location and confirm that it is open today on a phone.” Ask the vendor to describe how their team would validate the task with a representative user. For fundraising, the acceptance test could cover reaching the correct campaign form, seeing the total before donating, and getting an accurate receipt.
Include a staff task. Have a coordinator update a program schedule using their own account before handover. If the coordinator needs help finding the right setting, build time for training and retesting. Write these tasks into the scope so everyone knows what evidence counts as a completed project.
3. Separate required work from optional improvements
Be explicit about who will handle copywriting, content migration, redirects, donation integrations, accessibility tests, analytics, training and post-launch support. Give the vendor a rough count of pages, forms, documents, and templates. Include any known integrations with your donation platform, email system, or CRM. If your team can approve copy but cannot write it, state that directly.
Ask for optional work to be priced separately. A multilingual resource library could be a later phase, for example, while accessible program pages and working donation forms are launch requirements. See our nonprofit website cost guide for other costs to bring into the budget conversation. Include the budget range or the process for setting it and identify who decides whether work moves to a later phase.
4. Give every vendor the same questions
Ask each vendor who will do the work, where they expect staff input, and how the team responds when approvals slip. Request one comparable project and ask the team to explain its role, the original problem, and what the client could do after launch. A polished screenshot can give you a feel for the design. A concrete example of the handover shows how a partner thinks about your day-to-day work.
Ask for a timeline with dependencies, an itemized price, recurring expenses and a written approach to change requests. Include a deadline, a contact for bidder questions, and the format you want proposals to follow. Share answers to material questions with every bidder so everyone prices the same work.
5. Score the proposals before discussing favourites
A small team could assign 30 points to understanding the audience and goals, 25 to usability and accessibility testing, 20 to relevant delivery evidence, 15 to price and recurring cost clarity, and 10 to training and ownership. Use a different weighting if the hardest part of your project is a data migration or an immovable launch deadline. Have reviewers score independently and write a reason for each mark before they compare notes.
If two proposals are close, ask each finalist to show how they would handle one of your actual user journeys. Bring the staff member who will own that journey after launch. End by comparing the work each partner has priced, the work that still falls to your team, and the decisions that could change the cost.
If you are still deciding how much of the website to rebuild, bring us your current site and the three things it needs to do better. We can help you turn those priorities into a scope you can discuss with your board.