Nonprofit website redesign RFP guide and vendor scorecard
Use Salt Technologies’ nonprofit website RFP guide to scope a redesign or migration, score vendors and compare three-year costs. Download the kit or invite Salt to bid.
A nonprofit selection committee can use this scorecard to compare website proposals. Agree the criteria before opening bids, then give every eligible vendor the same tasks.
What should a nonprofit website redesign RFP include?
Give vendors enough information to price the same job. A communications director can draft the brief, but the people who run fundraising, programs and IT should each supply one task they need to keep working through launch.
Outcomes and audiences
Give each priority audience a task and a way to tell whether it succeeded. A participant can find a distribution site on a phone. A donor can complete a gift and see a receipt. An editor can correct both English and Spanish service hours before the office closes. Name the staff member who will accept each result.
Inventory and ownership
List the CMS, page and document counts, language versions, forms, payment processor, CRM and membership tools. For each, say who owns the account, who can grant test access and who will approve migrated content. Ask bidders to price any unknown volume separately.
Bid format and schedule
Give bidders the same response sheet. Request a fixed scope or stated estimate basis, exclusions, staffing locations, accessibility testing, launch support and recurring fees. Publish the question deadline, shared answers process, shortlist demonstration date and decision owner.
Launch and continuity
Name campaign dates, giving days and program deadlines that constrain cutover. Ask for a sample redirect register, a trial content import and a rollback rehearsal. Agree who checks that a donation, volunteer registration or member renewal made during the switch is reconciled.
A requirement you can put in a bid
“Our program manager must be able to update a food distribution location in both supported languages using an editor account. At the shortlist demonstration, use a sample location to show editing, preview, publication and reversal. In the proposal, identify who translates the update, which work requires a developer and whether training and licensing are included.”
Ask for a response against this clause from every bidder. Keep the demonstration notes with the price sheet so the panel can see exactly what the quoted fee includes.
Check mandatory eligibility, subcontractor disclosures, delivery location, accessibility obligations, insurance and required documents against the published RFP. Record pass, fail or clarification with a clause reference. Apply your published process before scoring.
Score each eligible proposal
Use the suggested weights below or agree your own before review. Use 0 for missing evidence, 1 for a claim, 2 for a partial response, 3 for meeting the requirement, 4 for strong supporting evidence and 5 for a demonstrated, repeatable result. Leave unreviewed criteria blank.
Weighted points = rating ÷ 5 × weight. Sum all six weighted scores for a total out of 100. Each evaluator records the evidence and scores independently before the panel reconciles differences.
Suggested vendor scorecard
Criterion
Weight
Evidence to request
Public journeys and accessibility
25%
Demonstrate the donation, meeting-finder and keyboard journeys in the acceptance tests.
Content migration and search continuity
20%
Provide a sample URL inventory, redirect map, exceptions list and post-launch check.
CMS editing and training
15%
Show a staff editor updating a meeting, previewing it and reverting a mistake.
Integrations, data and security
15%
Identify donation and membership integrations, data access, backups and incident ownership.
Delivery, handover and support
15%
Name delivery roles, milestones, acceptance owner, training and support response commitments.
Three-year cost of ownership
10%
Separate implementation from hosting, licenses, support, optional work and buyer staff time.
Run the same acceptance tests
Find a meeting — using only a keyboard, find the next meeting for a specified day and location. Verify the time, location and contact details are accessible and that focus stays visible.
Complete a mobile donation — use a test payment to donate, return to the website and see confirmation. Also test cancellation and retry. Check the transaction and receipt evidence with the finance owner.
Update a program — a staff editor changes a meeting time in staging, previews it, publishes it and corrects it without developer access. Verify the public listing reflects the correction.
Record for each test: vendor [name], environment [demo or staging], expected result [ ], observed result [ ], pass or issue [ ], evidence [ ], owner and retest date [ ]. Use sample records and test payments.
Document the decision
For each vendor record the evidence behind the score, unanswered questions, three-year cost assumptions, reference checks and any conflicts of interest. Resolve tied scores using the process published in the RFP.
Before contract award, turn the selected tests into acceptance criteria. Name the staff sign-off owner, remediation period and handover deliverables.
How do two website proposals compare in a worked example?
Suppose a nonprofit is moving a resource library and connecting donations to its CRM. Both proposals include a new website. The following fictional bids show how different deliverables change the committee’s decision.
Sample committee ratings on a five-point scale
Criterion
Weight
Bid A
Bid B
Public journeys and accessibility
25%
4/5
4/5
Content migration and search continuity
20%
3/5
5/5
CMS editing and training
15%
3/5
4/5
Integrations, data and security
15%
4/5
3/5
Delivery, handover and support
15%
3/5
4/5
Three-year cost of ownership
10%
3/5
4/5
Weighted total
100%
68/100
81/100
For migration, Bid A earns 3 ÷ 5 × 20 = 12 points. Bid B earns all 20. The downloadable CSV applies the same calculation to every row.
In this fictional evaluation, both bidders pass the mandatory conditions. Bid B earns the higher migration score by demonstrating a trial import, resolving broken document links and handing over a redirect register. Bid A earns the higher integration score because its team demonstrates payment reconciliation after a failed CRM sync. If that sync is essential for launch, ask B to demonstrate recovery under the published clarification process before award.
What will each website cost over three years?
Illustrative ownership costs in USD
Cost item
Bid A
Bid B
Implementation and training
$36,000
$45,000
Annual hosting, licenses and support
$9,000
$5,000
Three-year total
$63,000
$60,000
Bid A saves $9,000 at launch. Its additional $4,000 a year in running costs makes it $3,000 more expensive over three years. Ask finance to check the same period, included support hours and renewal assumptions for each proposal.
These sample USD figures illustrate a budget comparison. Assume three full years of recurring fees at the quoted rate, with the same scope for both vendors. Add any separately priced translation, transaction fees at your donation volume, internal staff time and exit or data-export costs before taking the recommendation to the board.
What do real nonprofit website RFPs ask for?
Manna Food Center asked for English and Spanish content, simpler access to programs, and connections to donation and volunteer tools. For a food-assistance site, give two vendors the same location update and ask a staff editor to publish it in both languages. Record who maintains translations and what a participant sees on a phone. Manna Food Center’s published website RFP (PDF)
The Friends had already developed a site blueprint. Its RFP asks a vendor to build on that work, migrate the site and price ongoing support across multiple properties. If your organization has a discovery report, attach it. Ask bidders which decisions they accept, which need validation and how they price support for each property. That makes duplicated discovery and unequal support coverage visible. The Friends of the Saint Paul Public Library’s published website RFP
What evidence should a panel request for accessibility?
Specify the standard and level your organization requires, the templates in scope and the third-party forms a visitor needs to finish a task. Ask vendors to identify who will test the handoff into the donation provider, which defects they can fix and who owns follow-up with the provider. Pair automated checks with keyboard and assistive-technology testing on agreed journeys. Ask for the findings and retest evidence at acceptance. W3C guidance on accessibility evaluation tools
Which Salt projects can a committee examine?
For a community website, the Alano Club of San Jose’s member administrator described migrating archives, updating meeting information and adding donation payment functionality. A committee with similar needs can ask vendors to demonstrate all three with a single staff account and a sample event. Read the Alano Club’s account.
For an association, Salt’s NARPM project covers the design and development of a designation portal. If your scope includes a member portal, request a separate estimate for authenticated work and ask who will own accounts, roles and member data after handover. Review the NARPM designation portal scope.
The NARPM designation portal is an example of our work on a member association’s processes. For a community website example, see the Alano Club of San Jose review linked below.
These are starting scopes. Your systems, decision owners, and delivery constraints shape the final proposal.
Website redesign and content migration
Ask us to inventory content, agree what to keep, map redirects and test priority journeys. For a donation page, that includes returning from the payment provider and confirming the next step.
Include the public RFP link, question deadline, proposal deadline with time zone, and the permitted channel for vendor questions.
02
Check eligibility
We review location restrictions, subcontractor disclosure, insurance, references and the proposed delivery team against the RFP before committing to a bid.
03
Compare the proposal
Request a requirement-by-requirement response with deliverables, assumptions, optional items and ongoing license, hosting and support costs.
04
Agree how to accept the work
Choose representative journeys. For example, a keyboard user can find a meeting, an editor can update it and an old event URL reaches the agreed destination. Record who signs off.
Delivery ownership
How to evaluate and engage Salt
Direct invitation
Invite Salt to bid under the RFP’s published process. Tell us if all correspondence must go through a portal or named procurement officer.
US agencies can ask Salt to scope a named work package when the solicitation permits subcontractors. The prime retains the buyer relationship and agrees disclosure with the issuer.
The Alano Club of San Jose describes migrating archives, updating meetings and adding donation payments. Read its review alongside the member portal case when assessing fit.
Agree time-zone overlap, communication channels, decision-makers, repository access, and review cadence before delivery begins. Scope, staffing, commercial terms, ownership, and post-launch responsibilities belong in the proposal and agreement.
Before you begin
Questions to resolve before committing.
Yes. Send the public invitation so we can check eligibility and deadlines. Salt has an engineering center in Pune, India. If the RFP requires US-only personnel, hosting, or specified contracting arrangements, identify those clauses in the invitation.
Name the required accessibility standard, pages and journeys to test, assistive technology expectations, remediation period and evidence your panel will accept. Specify who needs CMS training and which handover materials staff should receive.
A public brief, a system list and anonymized examples are enough for a fit review. Keep donor lists, credentials and confidential bid documents in your approved procurement channel.
Start with a short brief
Invite Salt to bid.
Send the public RFP link or reference number, the deadline and time zone, and your prescribed vendor contact process.