CannedSpinach
8 min read

How to Write a Website RFP (With a Free Template)

By , CEO & Founder

Back to Blog
Illustration of a website RFP checklist with a budget range, connected to three agency proposals with the best match highlighted and checked

Quick answer: A good website RFP explains why you're redoing the site, what success looks like, who the site serves, what it must do, a realistic budget range, your timeline, and how you'll score proposals. Include examples of sites you like and say why. Keep it to 5-10 pages, give agencies about three weeks to respond, and invite questions. The clearer your RFP, the more comparable and useful the proposals you get back.

I read a lot of RFPs. Some make me want to clear my calendar and start sketching. Others leave me guessing about the one thing that matters most: what does this organization actually need?

The difference is rarely length. It's whether the RFP tells agencies the truth about the project: the budget, the real reason for the redesign, and what success looks like to the people who'll use the site every day.

This guide walks through how to write a website RFP that gets you clear, comparable proposals, with a free downloadable template and a simple scoring rubric at the end. It's written for nonprofits and foundations and civic and economic development organizations, because that's where most of the RFPs we see for web design in Cincinnati come from.

What is a website RFP, and do you need one?

A website RFP (request for proposal) is a document that describes your project and asks agencies to propose how they'd do it, on what timeline, and for what price. It turns a vague "we need a new website" into something several firms can respond to on equal footing.

You probably need one if your board, funders, or procurement rules require competitive bids, or if more than a couple of people have a say in the decision. If you're a small team choosing between two agencies you already know, a short project brief and a few conversations may get you there faster. Either way, the thinking behind a good RFP is worth doing.

What should a website RFP template include?

Most strong RFPs share the same core sections. Here's what each one should do:

  1. About your organization. Mission, audiences, size of your team, and who will manage the site day to day.
  2. Why you're doing this now. The real trigger: a rebrand, a conversion problem, a CMS your team dreads, a capital campaign, a merger.
  3. Goals and how you'll measure them. More donations, more site-selection inquiries, more event registrations, fewer "where do I find..." phone calls.
  4. Audiences and their top tasks. List each user type and the two or three things they come to do.
  5. Scope and requirements. Approximate page count, content migration, integrations (CRM, donation platform, event tools), multilingual needs, and accessibility.
  6. Budget range. More on this below. It's the section that changes everything.
  7. Timeline. Key dates for proposals, selection, and launch, plus any hard deadlines like a gala or annual report.
  8. Sites you like, and why. Specific elements, not just links.
  9. What to include in a proposal. Approach, team, relevant work, timeline, pricing, and post-launch support.
  10. How you'll evaluate. Your criteria and weights, so agencies know what matters to you.
  11. Logistics. Question deadline, submission format, due date, and one point of contact.

Should you include a budget in your website RFP?

Yes. If I could change one thing about the RFPs we receive, it would be this. The number one thing that makes me excited to respond is when an RFP includes a price or a range.

Website projects vary enormously. Most of ours land somewhere between $5,000 and $150,000 depending on scope, and other agencies have their own ranges. Without a number, every agency is guessing at what "best" means for you, and you end up comparing a lean proposal to a lavish one. That isn't apples to apples.

When you share a ballpark, agencies can scope something that actually fits your needs and your constraints, instead of handing you a blind recommendation. There's no one-size-fits-all "best" website. It depends on your goals, your team, and your budget.

Worried a range invites everyone to bid the top number? Ask agencies to show what they'd recommend at your budget and what they'd add or cut if it moved. That tells you far more than a single figure.

Why the "why" matters more than the feature list

The second thing I love seeing is a clear reason behind the RFP. Some organizations want a fresh look. Others are trying to fix a conversions problem. Others need a modern CMS their team can actually manage without calling a developer.

Each of those leads to a different recommendation, which changes cost, timeline, and nearly everything else. A team that wants easier editing needs strong content modeling and training. A team with a conversions problem needs research, clearer paths, and analytics. If you only send a feature list, you'll get proposals that check boxes instead of solving the problem.

The same goes for example sites. Don't just list five websites you admire. Say what you like (or hate) about each: "the program finder lets parents filter by age in two clicks" or "the homepage feels crowded and we can't tell what to do first." Specifics make design less subjective and help agencies understand what matters to you.

Accessibility, hosting, and other requirements to spell out

These details often get left out, then show up as surprise change orders later:

  • Accessibility. Name a standard. WCAG 2.1 Level AA is the standard the U.S. Department of Justice adopted for state and local government websites under ADA Title II. An April 2026 interim rule moved the compliance dates to April 26, 2027 for entities serving 50,000 or more people, and April 26, 2028 for smaller entities and special districts. WCAG 2.2 has been the current W3C Recommendation since October 2023. We're not lawyers, but from a technical standpoint, asking for WCAG 2.1 AA at a minimum is a sensible baseline for any public-facing organization.
  • Content. Who writes and migrates it? How many pages, documents, and news posts are coming over?
  • Hosting, security, and maintenance. Ask for post-launch support, hosting, and update plans to be priced separately so you can compare them.
  • Training. If your team will edit the site, ask how agencies train staff and what happens when someone new joins.
  • Search and AI visibility. Ask how they'll protect existing rankings during the move (redirects, metadata) and help your organization show up in Google and AI answers.

Free website RFP template (copy and fill in)

Download it: Website RFP Template (Word document). It opens in Microsoft Word or Google Docs and has fill-in tables for your goals, audiences, budget, timeline and scoring, so you can edit it and send it out as your own.

Prefer to start from scratch? Copy the outline below into a document and answer each prompt in plain language. Most organizations land at 5-10 pages.

  1. Organization overview. Who we are, who we serve, and who will manage the site after launch.
  2. Why now. "We're replacing our website because..." (one honest paragraph).
  3. Goals. Three to five goals, each with how we'll measure it.
  4. Audiences. Each user type and their top tasks on our site.
  5. Current site. URL, platform, what works, what doesn't, and rough page count.
  6. Requirements. Must-haves vs. nice-to-haves, integrations, accessibility standard, languages.
  7. Examples. Three to five sites, with what we like or dislike about each.
  8. Budget. "Our budget for design and build is $X-$Y. Please price hosting and support separately."
  9. Timeline. RFP issued, questions due, answers posted, proposals due, interviews, decision, target launch.
  10. Proposal contents. Approach, team, two or three relevant projects, timeline, itemized pricing, references.
  11. Evaluation criteria. The rubric below, with your weights.
  12. Submission details. Format, due date and time, and one contact for questions.

How to score website proposals fairly

Decide your weights before proposals arrive, so the shiniest presentation doesn't win by default. Here's a simple starting rubric you can adjust:

  • Understanding of our goals (25%). Did they respond to our "why," or just repeat our feature list?
  • Relevant experience (20%). Similar organizations, audiences, or complexity.
  • Approach and process (20%). Research, content, design, development, testing, and launch.
  • Value for the budget (15%). Clear, itemized pricing that fits our range.
  • Post-launch support and training (10%). Hosting, maintenance, and how our team will run the site.
  • Team and fit (10%). Who we'll actually work with, and how communication works.

Give agencies about three weeks to respond, and publish answers to questions for everyone. Then shortlist two or three for a conversation. Our honest guide to choosing a web design company has more questions worth asking at that stage.

If you're in Greater Cincinnati, Northern Kentucky, or elsewhere in the Tri-State, it's worth including at least one regional firm on your list - someone who already knows the funders, partners and communities your site needs to speak to.

Want a second set of eyes on your RFP?

Canned Spinach is a Cincinnati web design agency. We build custom websites, keep them maintained and secure, and handle SEO / AI visibility and graphic design for nonprofits, foundations, civic and economic development organizations, and mid-market companies. If you're drafting an RFP and want a quick, no-pressure gut check on scope or budget before it goes out, book a short call.

Sources

Frequently Asked Questions

Most effective website RFPs are 5-10 pages. That's enough room to explain your organization, goals, audiences, requirements, budget, and timeline without burying agencies in boilerplate. If your procurement office requires standard legal language, put it in an appendix so the project details stay easy to find. Clarity matters far more than length.

About three weeks is a reasonable window for a typical website RFP. It gives agencies time to ask questions, review your current site, and put together a thoughtful approach and accurate pricing. Rushed deadlines tend to produce generic proposals. Build a question deadline into the first week and share every answer with all bidders.

Yes. Sharing a budget range is the single best way to get proposals you can compare. Website projects vary widely in cost, so without a range each agency guesses at your expectations. A range lets agencies recommend what fits your needs and constraints. You can also ask them to explain what they'd add or cut at different budget levels.

Most organizations should ask for WCAG 2.1 Level AA at a minimum. It's the standard the U.S. Department of Justice adopted for state and local government websites under ADA Title II. WCAG 2.2 is the latest W3C version, so asking agencies how they handle it is reasonable too. For legal questions about your own obligations, check with your counsel.

An RFI (request for information) gathers general information about potential vendors. An RFQ (request for qualifications or quotation) focuses on credentials or price for a well-defined job. An RFP (request for proposal) asks agencies how they'd solve your problem, along with timeline and cost. For most website redesigns, an RFP is the best fit.

Share

Keep Reading

View All Posts

Ready to grow?
Let's talk.

Bring us your idea. We'd love to hear what's on your mind.

Get started