Industry Guides

A website RFP template nonprofits can actually use

A copy-and-paste nonprofit website RFP template, section by section, with a fair scoring grid, the case for publishing your budget, and a maintenance line.

Duraan AliUpdated 19 min read
A tidy stack of printed proposals with paper clips, a pen and reading glasses on a conference table

Most nonprofit website RFPs get bad proposals because they ask several vendors to price a project nobody has defined yet. The fix is not a longer document. It is a clearer one that states four things: what you are trying to accomplish, what has to exist when you launch, when you need it, and how much you have to spend. The full template is below, section by section, written so you can copy it into a document and fill it in this afternoon.

I have read a lot of these over 14 years, and the difference between an RFP that gets three good proposals and one that gets nine useless ones almost never comes down to writing quality. It comes down to whether the document contains enough information for a vendor to commit to a number without guessing.

Do you actually need an RFP?

Probably not, unless someone is making you. An RFP is a procurement tool designed for situations where you must be able to show that you ran a fair, documented competition. If your bylaws require it, if a foundation grant requires it, if you hold a government contract with procurement rules attached, run one.

If none of that applies, a shorter path usually works better. Write a one-page scope, send it to three studios whose work you have actually looked at, and ask each for a fixed-fee proposal. You will get the same information in half the calendar time.

And if your budget sits at the bottom of the market, do not run an RFP and do not hire an agency, including us. The Lonely Entrepreneur’s 2026 cost guide puts what most small organizations spend on a website at $1,500 to $5,000. At the low end of that, a procurement process eats a meaningful share of the money. A Squarespace or WordPress template plus ten to twenty hours of paid help from a freelance designer will get you a real website. If you do hire a studio at that level, buy a fixed price against a written scope, a short list of pages and features with a number attached, and nothing else. That kind of engagement does not include the discovery, stakeholder interviews, and content strategy an RFP process implies you want, and you should not pay agency overhead for template work.

In my view the RFP earns its keep somewhere around $10,000 and up, which is roughly where Clutch’s 2026 pricing data says most web design projects stop, or any time three or more people have to agree on the decision.

What goes in a nonprofit website RFP?

Thirteen sections. Four to eight pages total. Here is the whole structure and why each piece changes the proposals you get back.

Section Length Why it changes the proposals
1. Organization background 1-2 paragraphs Lets a vendor tell you whether they have done this kind of work
2. Project goals and measurable outcomes Half a page The single biggest driver of proposal quality
3. Current site and what is wrong with it Half a page Stops vendors from proposing fixes you already tried
4. Audiences Short list Determines information architecture and tone
5. Required functionality Checklist Where most cost variance actually lives
6. Content responsibility 1 paragraph The most common cause of blown timelines
7. Accessibility requirement 1 paragraph Cheap to specify up front, expensive to retrofit
8. Technical requirements, ownership, and ongoing maintenance Short list Protects you from being locked in, and prices year two
9. Timeline and key dates Table Filters out vendors who cannot actually staff it
10. Budget range 2 sentences Makes proposals comparable to each other
11. Evaluation criteria with weights Table Keeps your own committee honest
12. Submission instructions Short list Saves you a week of chasing formats
13. Questions vendors must answer 8-12 questions Turns marketing decks into real answers

The template, section by section

Copy each block. Replace anything in square brackets. Delete what does not apply to you.

1. Organization background

## 1. About [Organization Name]

[Organization Name] is a [501(c)(3) nonprofit / public charter school /
faith-based organization] based in [City, MN], founded in [year]. We
[one sentence on what you do and who you serve].

Scale: [X] staff, [X] volunteers, [X] people served annually,
annual operating budget of approximately $[X].

Primary funding sources: [grants / individual giving / government
contracts / tuition / program fees].

Vendors use this to judge fit, not to flatter you. A studio that has built for nonprofits knows the difference between a grant-funded organization with one communications staffer and a membership organization with a marketing team. Say which one you are.

2. Project goals and measurable outcomes

## 2. Goals

In priority order, this project must:

1. [Goal], measured by [metric], currently [baseline], target [number]
   within [timeframe] of launch.
2. [Goal], measured by [metric], currently [baseline], target [number].
3. [Goal], measured by [metric], currently [baseline], target [number].

Out of scope for this project: [things you are explicitly not doing].

This is the section that separates a serious RFP from a wish list. “Modernize our web presence” tells a vendor nothing. “Increase online donations from 40 per month to 100 per month within six months” tells them to spend budget on the giving flow instead of the photo gallery. If you do not have baseline numbers, open Google Analytics and your donation platform and write down monthly sessions, monthly online gifts, average gift size, and form submissions before you release the RFP. The “out of scope” line is underrated: “we are not migrating our donor database in this project” prevents three vendors from padding their number against a risk that does not exist.

3. Current site and what is wrong with it

## 3. Current site

URL: [url]
Platform: [WordPress 6.x / Squarespace 7.1 / Wix / custom / unknown]
Built: [year] by [vendor, or in-house, or unknown]
Approximate page count: [X]
Who can edit it today: [names/roles]
Hosting: [provider], $[X]/mo, [who holds the account]
Domain registrar: [provider], [who holds the account]
Current maintenance: [vendor and monthly cost / a staff member / nobody]

Known problems:
- [Specific problem, e.g. "the donate button is below the fold on mobile"]
- [Specific problem]
- [Specific problem]

What we want to keep: [what actually works]

Be blunt here. Vendors are not judging you for a dated site; they are trying to figure out how much of the existing thing survives. The hosting, registrar, and maintenance lines matter more than people expect: a migration where the previous developer is unreachable is a different project than one where you control the accounts, and vendors need to price that difference. If nobody knows who holds the domain, our guide on how to check whether you own your website walks through finding out.

4. Audiences

## 4. Audiences

Primary: [audience], who come to the site to [task].
Secondary: [audience], who come to the site to [task].
Tertiary: [audience], who come to the site to [task].

Language needs: [English only / English + Somali / English + Spanish /
other]. [Note whether translation is professional, machine, or not needed.]

Device split from analytics: [X]% mobile, [X]% desktop.

Rank them. Most sites fail because the homepage tries to speak to every group equally; a family looking for services and a funder doing due diligence need different pages, not competing halves of one. Language is a real budget line for a lot of Minnesota organizations. If your programs serve East African families in Minneapolis or Saint Paul, say whether you need Somali or Oromo content and whether you will supply the translations, because machine translation of a program eligibility page is not acceptable.

5. Required functionality checklist

## 5. Functionality

Must have at launch:
- [ ] Online donations via [platform, e.g. Givebutter, Classy, Stripe]
- [ ] Recurring gift option
- [ ] Events calendar with [registration / no registration]
- [ ] News or blog with [X] categories
- [ ] Staff and board directory
- [ ] Program pages, approximately [X]
- [ ] Contact form routing to [address]
- [ ] Volunteer application form
- [ ] Email signup connected to [Mailchimp / Constant Contact / other]
- [ ] Document library for [annual reports / 990s / policies]
- [ ] Search
- [ ] Mobile-first responsive layout

Nice to have, priced separately as options:
- [ ] Password-protected board or member area
- [ ] Multilingual content
- [ ] Job board
- [ ] Interactive impact map or dashboard
- [ ] Client/participant portal

Integrations required: [CRM name], [donation platform], [email tool],
[any state reporting system].

Separate must-have from nice-to-have and ask for the nice-to-haves to be priced as line-item options. Now you can trim to budget after you pick a vendor instead of before you know what things cost.

Integrations are where quotes diverge the most. Connecting a form to Mailchimp is an hour. Two-way syncing with a CRM like Salesforce NPSP or Neon is a project of its own. Name the actual system, not the category.

6. Content responsibility

## 6. Content

We will supply: [existing copy / photography / logo files / brand guide].
We need the vendor to supply: [copywriting for X pages / photography /
photo sourcing / editing of existing copy].

Content owner on our side: [name, title, hours available per week].
Target date for all content delivered to vendor: [date].

Late content is the single most common reason a nonprofit website launches three months behind schedule. Not development. Content.

Name one person, and be honest about their availability. If your executive director is the only one who can approve program copy and she has four hours a month, say so, and either budget for a copywriter or extend the timeline. A vendor who knows this can plan around it. A vendor who finds out in week six cannot.

7. Accessibility requirement

## 7. Accessibility

The delivered site must conform to WCAG 2.1 Level AA. The vendor will
describe in their proposal how they test for conformance, including which
manual checks they perform beyond automated scanning.

Automated scanning alone is not sufficient. Overlay or widget-based
accessibility products are not acceptable as a conformance strategy.

Write this in even if no regulation names you. WCAG 2.1 Level AA is the standard in the Department of Justice’s ADA Title II web rule for state and local governments, including public charter schools, with compliance dates of April 26, 2027 for entities serving 50,000 or more people and April 26, 2028 for smaller entities and special districts after the interim final rule published April 20, 2026. It is also the standard in the HHS Section 504 rule for recipients of federal health funding, with dates of May 11, 2027 and May 10, 2028 after a May 2026 extension. Grant agreements and settlements name the same level, and it costs very little to build in from the start compared to retrofitting later. Our accessibility guide for small organizations covers what conformance actually involves.

The line about overlays is deliberate. The Overlay Fact Sheet, a public statement from accessibility professionals that I read in November 2026, carries 1,048 signatures behind the sentence that no overlay product can make a website fully compliant with any accessibility standard, and in January 2025 the Federal Trade Commission announced an order requiring the overlay vendor accessiBe to pay $1 million over claims that its widget made sites WCAG compliant. Ruling overlays out in the RFP prevents a vendor from quoting a cheap number that relies on one.

8. Technical requirements, ownership, and ongoing maintenance

## 8. Technical, ownership, and maintenance requirements

- Platform: [we prefer X / vendor to recommend with rationale]
- The site must be editable by non-technical staff without HTML.
- All code, design files, and content are owned by [Organization] on
  final payment. Vendor retains no license restrictions on our use.
- All accounts (hosting, domain, CMS, analytics) will be registered to
  [Organization] email addresses with [Organization] as owner.
- Site must load a typical page in under 3 seconds on a mobile
  connection. Vendor should state target Core Web Vitals.
- Vendor will provide written documentation and a recorded training
  session for our staff.
- Hosting recommendation with monthly cost stated separately.
- 30 days of post-launch bug fixes at no additional cost.
- Ongoing maintenance quoted as a separate fixed monthly price, stating:
  what is included (software updates, backups, uptime monitoring,
  security), how many hours of content edits per month, the response
  time for a broken form or a down site, and whether we may cancel
  without penalty. We are not required to buy maintenance from the
  vendor who builds the site.

The ownership clause is the most important paragraph in the entire RFP and it takes four lines. Plenty of small organizations discover during a redesign that their domain is registered to a former board member’s personal account. Stating who owns the accounts before the project starts prevents that permanently. Any vendor who pushes back on it is telling you something useful.

The maintenance line is the one most RFPs leave out, and it is where year-two surprises come from. A nonprofit site is not finished at launch: Give to the Max Day, which falls on November 19 in 2026, the annual report, the 990, staff changes, and a steady flow of plugin updates all land on somebody. Ask for the number now, while vendors are competing for the build, and ask for it in a form you can compare. The market is published: at the six Twin Cities agencies that print care-plan prices, read in October 2026, a plan with updates, backups, and monitoring but no content time runs $50 to $100 a month, a plan with 30 to 60 minutes of edits runs $149 to $250, and a plan with about two hours runs $349 to $474. A proposal whose maintenance line is far outside those bands, or missing, deserves a question. The full comparison is in how much website maintenance costs, and the nonprofit year is laid out on our maintenance page for nonprofits.

9. Timeline and key dates

## 9. Timeline

| Milestone | Date |
|---|---|
| RFP released | [date] |
| Written questions due | [date] |
| Answers posted to all bidders | [date] |
| Proposals due | [date, 5:00 PM Central] |
| Finalist interviews | [date range] |
| Vendor selected | [date] |
| Project kickoff | [date] |
| Content delivered to vendor | [date] |
| Target launch | [date] |

Hard constraint: [e.g. "must launch before our Give to the Max Day
campaign on November 19, 2026" or "before enrollment opens [date]"]. If
your proposed schedule cannot meet this, say so directly rather than
proposing a date you cannot hold.

Give vendors two to three weeks to respond. Under ten business days and you get recycled material, because nobody can do original thinking about your organization in a week while running current projects.

Name the hard constraint explicitly. A Minnesota nonprofit that needs to launch before Give to the Max Day has a real deadline, and so does a charter school that needs enrollment pages live before the lottery opens. A typical business website takes four to eight weeks of build time after content is ready, so count backward from the constraint and check that your own dates are physically possible before you publish them.

10. Budget range

## 10. Budget

Our approved budget for this project is $[X] to $[Y], inclusive of
design, development, testing, training, and launch. Ongoing hosting and
maintenance should be quoted separately as monthly costs.

We are more interested in how you allocate this budget than in the
lowest number. Proposals that exceed the range will be considered only
if the additional scope is clearly justified.

Why does hiding your budget produce worse proposals?

Because a website is not a commodity with a fixed specification. The same list of pages can be built at the bottom of the market or at ten times that, and both are legitimate projects; they just make different tradeoffs about custom design, content strategy, integrations, and testing. The published bands show how wide the spread is: GoodFirms’ survey, cited by WebFX in 2026, puts small-organization sites anywhere from $1,000 to $15,000, and Clique Studios’ redesign FAQ puts a 10- to 20-page site from a larger agency at $15,000 to $40,000.

When you withhold the number, three things happen and none of them help you. You get non-comparable proposals: one vendor assumes the bottom of the band and proposes a template build, another assumes the top and proposes discovery workshops and a custom design system, and you are now comparing two different projects. Good vendors bid high or decline, because a lowball estimate against an ambiguous scope is how firms lose money. You lose the actual signal, which is not “who is cheapest” but “given the same money, who gets the most out of it?”

The fear behind budget secrecy is that vendors will simply quote your maximum. Some will. That is exactly why you also state the evaluation weights: if price is 15 percent of the score and approach is 25 percent, quoting the ceiling with a thin plan loses. If you cannot publish a number because of board politics, publish a not-to-exceed ceiling instead. “Proposals must not exceed $[X]” is less useful than a range but far better than silence. Our nonprofit website budget guide walks through setting one from the published market figures.

11. Evaluation criteria with weights

## 11. How proposals will be evaluated

| Criterion | Weight |
|---|---|
| Relevant experience with similar organizations | 30% |
| Proposed approach and understanding of our goals | 25% |
| Team, communication plan, and references | 20% |
| Cost and value within our stated range | 15% |
| Accessibility practice and post-launch maintenance | 10% |

Proposals will be scored by a [X]-person committee. Finalists may be
invited to a 45-minute interview. We reserve the right to request
clarification, to negotiate scope, or to select no vendor.

12. Submission instructions

## 12. How to submit

Send one PDF, no more than [12] pages plus appendices, to [email] by
[date] at 5:00 PM Central. Include:

- Firm name, primary contact, phone, email
- Answers to the questions in Section 13
- Three examples of comparable live sites you built, with URLs and a
  one-paragraph description of your role in each
- Three client references, at least one from a nonprofit
- Line-item budget and payment schedule
- Monthly maintenance price and what it includes
- Proposed project schedule with milestones
- Named team members who will do the work

Written questions may be submitted to [email] until [date]. All
questions and answers will be shared with every bidder on [date].

The shared question-and-answer step is worth the small amount of work it takes. It keeps the process fair, and the questions vendors ask will expose gaps in your own RFP while you still have time to fix them.

13. Questions vendors must answer

## 13. Questions

1. Which of your past projects is most similar to ours, and why?
2. Who specifically will work on this project, and what percentage of
   their time will it take?
3. What platform do you recommend for us, and what are the tradeoffs
   of that choice?
4. How do you handle content: do you write, edit, or only place it?
5. How do you test for WCAG 2.1 AA conformance?
6. What happens if our content is late? How does that affect the schedule?
7. What is not included in your price that we should budget for?
8. Who owns the code, design files, and accounts after launch?
9. What does maintenance cost after launch, what does it include, and
   what happens if we do not buy it from you?
10. Describe a project that went badly and what you changed afterward.
11. What do you need from us, and how many hours per week?
12. If our budget were cut by 30 percent, what would you cut first?

Questions 7, 9, 10, and 12 do the heavy lifting. Anyone can answer the first six from a template; the last ones require a vendor to think about your situation specifically. Question 9 in particular separates vendors who see maintenance as a service with a scope from vendors who see it as a retainer they would rather not define.

How do you score proposals fairly?

Use the grid you published, score independently, then meet. Have each committee member score every proposal on their own before any discussion, or the loudest person in the room sets the anchor.

Score everything except price first, with pricing pages removed if you can manage it. Then add price. A cheap proposal with a weak plan should not win on the strength of one number, and reviewing blind for the first pass is the simplest way to prevent that.

Criterion Weight Vendor A Vendor B Vendor C
Relevant experience (0-10) 30% 9 = 2.7 6 = 1.8 7 = 2.1
Approach and understanding (0-10) 25% 8 = 2.0 9 = 2.25 5 = 1.25
Team and communication (0-10) 20% 7 = 1.4 8 = 1.6 6 = 1.2
Cost and value (0-10) 15% 6 = 0.9 5 = 0.75 9 = 1.35
Accessibility and maintenance (0-10) 10% 9 = 0.9 7 = 0.7 4 = 0.4
Total 100% 7.9 7.1 6.3

The vendors in that table are made up to show the arithmetic. Vendor C is the cheapest and finishes last. That is the grid doing its job.

Two rules keep this honest. Write a one-sentence justification for every score under 5 or above 8, which forces reviewers to point at something in the document. And call every reference. Ask each one what surprised them, what they would do differently, and whether the vendor is still responsive today.

What does a good proposal look like versus boilerplate?

You can usually tell in the first two pages. The tells are consistent.

Boilerplate proposal Real proposal
Restates your RFP back to you States what it thinks your actual problem is, which may differ from what you wrote
Portfolio of unrelated work Two or three genuinely comparable projects with live URLs
“Our proven 5-phase process” with no dates A schedule with named milestones tied to your deadline
One lump-sum price Line items, with options priced separately
No questions asked during the window Asked two or three specific questions that made you think
Agrees with everything Pushes back on at least one thing in your RFP
Team described as “our experts” Named people with roles and time commitments
Accessibility mentioned once as “ADA compliant” Names WCAG 2.1 AA and describes the manual testing
Support described as “we’re here for you” A fixed monthly number, the hours it includes, and the response time

The pushback item matters most. If you asked for something that will not serve your goals, such as a homepage video carousel, or a custom donation form when your processor’s hosted form converts better, a vendor worth hiring will say so in the proposal. Total agreement in a written bid usually means the vendor plans to build whatever you ask and hand you the bill.

How many vendors should get the RFP?

Three to six, invited directly. This is my opinion from the vendor’s side of the table, not a survey: a serious response takes a small studio one to three unpaid working days, so a public call that reaches twenty firms gets back mostly recycled material from the firms that can afford to gamble, and the small studios that would have given your project senior attention decline first. Shortlist by looking at live sites built for organizations like yours. Our list of nonprofit web design companies in Minnesota and the guide to choosing a web design company are both built for that step.

What to do next

Fill in Sections 2, 5, and 10 first: goals with baselines, the must-have checklist, and the budget range. If you cannot fill in those three, you are not ready to release the RFP, and no vendor can price it. Then find out who holds your domain and hosting, and write down what maintenance costs you today, even if the answer is a staff member’s time. Before you send anything out, read the 15 questions to ask before you hire a web designer; several of them belong in Section 13.

If you want a second read on a draft RFP before it goes out, send it over. No charge, and no obligation to include us in the bid list. TayoPro designs and builds websites for nonprofits, including the sites for Bridge and Bloom and HARO, and keeps them maintained month to month, both at a fixed price quoted in writing. We will tell you plainly if you do not need either one, or if the rebuild you described is really a navigation-and-donation-flow fix on a site that is otherwise fine. A clearer RFP produces better proposals from everyone who responds, which is a fine outcome either way.

FAQ

Questions people ask about this

Should a nonprofit include the budget in a website RFP?

Yes, as a range. Without a number, each vendor guesses at a different project size, and you end up comparing a template build to a custom platform as if they were the same thing. A stated range tells vendors what tradeoffs to make and lets you judge who gets the most value out of the same money. If board politics rule out a range, publish a not-to-exceed ceiling instead.

How long should a nonprofit website RFP be?

Four to eight pages. That is enough for organization background, goals, a functionality checklist, accessibility requirements, timeline, budget, evaluation criteria, and submission instructions. Longer documents mostly add legal boilerplate that scares off small studios without improving the proposals you receive.

How many vendors should we send the RFP to?

Three to six. In my experience each serious proposal takes a vendor one to three unpaid working days, so a public call to twenty firms produces mostly recycled boilerplate from the ones who can afford to gamble. Shortlist by looking at live sites the vendor built for organizations like yours, then invite that shortlist directly.

How long should we give vendors to respond?

Two to three weeks from release to deadline, with a written question window that closes about a week before. Under ten business days you will get templated responses. Over four weeks you lose momentum, and your own committee forgets the details of what they read first.

What should the RFP say about accessibility?

Require WCAG 2.1 Level AA, ask how the vendor tests beyond automated scanning, and rule out overlay widgets as a conformance strategy. WCAG 2.1 AA is the standard in the Department of Justice's ADA Title II rule, with compliance dates of April 26, 2027 and April 26, 2028 after the April 2026 interim final rule, and in the HHS Section 504 rule for recipients of federal health funding. The Overlay Fact Sheet, read in November 2026, carries 1,048 signatures from accessibility professionals stating that no overlay can make a site fully compliant.

Do we need an RFP if the board already likes one vendor?

Only if your bylaws, a funder, or a government contract require competitive procurement. Otherwise a written scope and a fixed-fee proposal from the vendor you trust is faster and cheaper. Running a fake competition to justify a decision you already made wastes other people's unpaid labor.

Keep reading

Start a project

Ready to take your business to the next level?

Let's work together to create solutions that make a real impact. Tell us about your project and we'll come back with a clear plan.

(612) 293-0636info@tayopro.com