How to Evaluate a Web Consultant for Your Nonprofit Without Writing an RFP

The RFP process is the default way nonprofits hire website help. It is also, for most organisations, a spectacular waste of time.

Here is what typically happens. The Board or senior leadership agrees the website needs work. The Communications Director is asked to manage the procurement. They spend weeks writing a document that attempts to define technical requirements they are not qualified to define, circulate it to agencies and freelancers, receive proposals that are impossible to compare because every respondent has proposed a different scope, and then choose based on price, presentation quality, or gut feeling. The whole process takes two to four months before any actual work begins.

The fundamental problem is that an RFP assumes you already know what you need. For most nonprofits, that is precisely the thing you do not know. What you know is that the website is not working. You do not know whether it needs a rebuild or targeted fixes, which stakeholders the architecture should prioritise, what accessibility obligations you are failing to meet, or where the actual gaps between what the site does and what the organisation needs are.

There is a better way to evaluate web consultants — one that starts with understanding the problem before defining the solution.

Why RFPs Fail Nonprofits Specifically

RFPs were designed for procurement contexts where the buyer can specify exactly what they need — a quantity of materials, a defined service with measurable outputs, a product with known specifications. Websites do not work this way. Two consultants can look at the same brief and propose fundamentally different solutions, both of which might be appropriate. The RFP format makes it impossible to evaluate which approach is better because it treats the proposals as comparable when they are not.

For nonprofits, the problem is compounded by several factors.

The person writing the RFP is rarely a technical specialist. Communications Directors are skilled at messaging, campaigns, and stakeholder management. They are not typically web architects or accessibility specialists. An RFP written without deep technical knowledge tends to either under-specify (leaving respondents guessing) or over-specify based on assumptions that may be wrong.

The best consultants often do not respond to RFPs. Experienced independent consultants and specialist agencies know that RFP processes favour the cheapest bid or the most polished presentation, neither of which correlates with project success. Many will not invest the time required to respond to a formal RFP, which means the process systematically excludes some of the people most qualified to do the work.

Price comparison is misleading. A £15,000 proposal for a rebuild and a £2,500 monthly partnership cover fundamentally different models. The RFP format forces you to compare them as if they are the same thing. They are not. One is a fixed deliverable with a defined end point. The other is ongoing capacity with iterative improvement. The right choice depends on your organisation’s situation, not on which number is smaller.

The timeline is punishing. Two to four months of procurement is two to four months where the website’s problems continue to affect your credibility with funders, your accessibility compliance exposure, your team’s capacity, and your stakeholders’ experience. For organisations facing Board scrutiny, regulatory pressure, or an upcoming funding cycle, that delay has real institutional cost.

What to Evaluate Instead

If you set aside the RFP format, the question becomes: how do you evaluate whether a web consultant is the right fit for your organisation? Here are the criteria that actually predict project success for nonprofits.

Do they specialise in your sector? Nonprofit websites fail in ways that generic web consultancy does not address — governance documents that funders expect to find, accessibility obligations under the Equality Act and increasingly the European Accessibility Act, content workflows designed for teams where one person manages everything, stakeholder journeys that serve donors, beneficiaries, regulators, and the Board simultaneously. A consultant who primarily works with e-commerce or corporate clients may build a beautiful site that misses these requirements entirely.

Do they start with diagnosis or design? If the first thing a consultant proposes is a design concept or a sitemap, they are skipping the most important step. The right first step is understanding your organisation — who your stakeholders are, what they need from the site, where the current site fails them, and what governance obligations apply. A consultant who begins with a diagnostic is one who will recommend what you actually need rather than what generates the most revenue for them.

Will they tell you if you do not need a rebuild? This is the most important test of integrity. If a consultant’s business model depends on selling rebuilds, their recommendation will always be to rebuild. Ask directly: under what circumstances would you recommend targeted fixes rather than a full rebuild? If they cannot answer that question clearly, they are not evaluating your situation — they are selling a service.

Can they explain their approach in governance language? Your Board does not care about Webflow versus WordPress, or CSS frameworks, or CMS architecture. They care about institutional risk, stakeholder credibility, regulatory compliance, and return on investment. A consultant who can only explain their work in technical terms will leave you translating for your Board. A consultant who frames recommendations in governance language makes the decision-making process simpler for everyone.

What is their model for ongoing support? A website is not a project with a start and end date. It is infrastructure that requires ongoing maintenance, content updates, accessibility monitoring, and periodic improvement. Ask what happens after launch. If the answer is ‘we hand it over and you manage it’, assess honestly whether your team has the capacity and expertise to do that. If not, the ongoing support model matters as much as the initial build.

Do they own their recommendations? Independent consultants who do the work personally have a different accountability relationship than agencies where the person who sold the project is not the person who delivers it. Neither model is inherently better, but you should know who will actually be making decisions about your website and whether you will have direct access to that person.

The Alternative to an RFP: Start With a Diagnostic

Instead of spending months defining what you think you need and asking consultants to bid on it, start with a structured diagnostic that establishes what you actually need.

A diagnostic engagement does several things an RFP cannot. It interviews your stakeholders to understand what different audiences need from the site. It assesses the current site’s technical condition, accessibility compliance, and content accuracy. It maps your stakeholder landscape to identify which audiences should drive the architecture. And it produces a report that gives your Board the information they need to make an informed decision about what comes next.

The Blueprint Audit is how I approach this. It is a £2,500 standalone engagement that produces a Board-ready report with specific findings and recommendations. It covers stakeholder interviews, technical assessment, accessibility audit, and governance review. The report belongs to the organisation — you can implement the recommendations internally, brief another provider using the findings, or return to it when timing is right.

The audit is not a sales mechanism for a larger engagement. If the finding is that your current site needs targeted fixes rather than a rebuild, the report will say so. If it identifies specific gaps that require professional implementation, it will specify what those are and what they would involve.

What Comes After the Diagnostic

For organisations that proceed with implementation, the Monthly Partnership replaces both the fixed-scope project and the guaranteed-hours retainer.

A fixed-scope project assumes the scope will not change. For nonprofits, it always changes — a new programme launches, a funder requests specific content, a campaign creates urgent landing page needs, leadership transitions require messaging updates. A fixed scope either constrains the organisation or triggers expensive change orders.

A guaranteed-hours retainer incentivises filling time rather than solving problems. If you pay for 40 hours, the provider has an incentive to use 40 hours whether the work requires it or not. And if a task takes 45 hours, you are negotiating overages.

The Monthly Partnership works differently. It is a rolling subscription at £2,500 per month with a 2–4 day turnaround on tasks. The work is prioritised together based on what the organisation actually needs. Tasks queue in priority order and are worked through methodically. If priorities shift — because they always do — the queue is reordered. There is no minimum commitment period and 30 days’ notice to pause or cancel.

This model works because it aligns the consultant’s incentive with the organisation’s interest: solve problems efficiently, maintain the site as institutional infrastructure, and respond to organisational needs as they emerge rather than as they were predicted months earlier in a scope document.

What If Your Board Requires an RFP?

Some boards have procurement policies that mandate competitive bidding above a certain threshold. If that applies to your organisation, you can still improve the process significantly.

Keep the RFP focused on your organisation’s situation, not on technical specifications. Describe your stakeholders, your challenges, and what success looks like — not what CMS you want or how many pages you think you need. Let respondents propose their own approach rather than bidding on a predefined scope. Evaluate based on understanding of your sector, diagnostic methodology, and ongoing support model rather than on price alone.

And consider whether the diagnostic phase — at £2,500 — falls below your procurement threshold entirely. If it does, you can engage a diagnostic without RFP, then use the findings to inform a more targeted procurement if a larger engagement is needed.

For the governance context behind these decisions, see Why Your NGO Website Is a Governance Problem. For how stakeholder priorities should drive your website architecture, see Nonprofit Website Stakeholder Mapping. For the practical question of whether to fix or rebuild, see When to Rebuild vs. Fix Your Nonprofit Website.

Frequently Asked Questions

Q1: Should a nonprofit use an RFP to hire a web developer?

For most nonprofits, no. RFPs assume you already know what you need, which is rarely the case. They take two to four months, exclude strong consultants who do not respond to formal bids, and produce proposals that are impossible to compare. A structured diagnostic is more effective because it establishes what you actually need before you commit resources.

Q2: How much should a nonprofit expect to pay for a website?

Fixed-price rebuilds from agencies range from £10,000 to £50,000 or more depending on scope. A subscription model at £2,500 per month provides ongoing design and development with iterative delivery. The right model depends on whether you need a one-off project or continuous infrastructure support.

Q3: What should a nonprofit look for when hiring a web consultant?

Sector specialisation, a diagnostic-first approach rather than jumping to design, willingness to recommend fixes over rebuilds when appropriate, ability to explain work in governance language your Board understands, a clear model for ongoing support, and personal accountability for recommendations.

Q4: What is a website diagnostic or audit for nonprofits?

A structured assessment of your current website covering stakeholder needs, technical condition, accessibility compliance, content accuracy, and governance alignment. It produces a Board-ready report with specific findings and recommendations. The diagnostic establishes what the organisation needs before any design or development commitment.

Q5: Why do the best web consultants not respond to RFPs?

Because RFP processes favour the cheapest bid or most polished presentation, neither of which predicts project success. Experienced consultants know that the time required to respond to a formal RFP is better spent on actual client work. The RFP process systematically excludes people who are busy delivering results for existing clients.

Q6: Is a fixed-price project or monthly subscription better for a nonprofit website?

A fixed-price project works when scope is genuinely defined and unlikely to change. For most nonprofits, scope changes constantly as programmes evolve, campaigns launch, and leadership transitions occur. A monthly subscription provides ongoing capacity that adapts to organisational needs without change orders or scope negotiations.

Q7: How do I get my Board to approve website investment without an RFP?

Frame the investment as governance infrastructure, not a marketing expense. Present the institutional risks of the current site, the compliance obligations it fails to meet, and the specific stakeholder needs it does not serve. A diagnostic report at £2,500 often falls below procurement thresholds and provides the evidence base for the Board to make an informed decision about larger investment.

Q8: What questions should I ask a web developer before hiring them for a nonprofit project?

Ask: what nonprofits have you worked with and what were the governance challenges? Under what circumstances would you recommend fixes rather than a rebuild? How do you handle accessibility compliance? What happens to our site and credentials if the engagement ends? Who will actually be doing the work? How do you communicate with Boards and senior leadership?

Q9: Can we skip the diagnostic and go straight to a website rebuild?

You can, but you risk building the wrong thing. Without a diagnostic, the rebuild brief is based on assumptions about what the organisation needs rather than evidence. This frequently leads to scope changes mid-project, stakeholder disagreements about priorities, and a final result that does not address the actual governance gaps.

Q10: What is the difference between a website audit and a website redesign proposal?

An audit is a diagnostic that assesses the current state and recommends what should happen next. A redesign proposal is a plan to implement a specific solution. The audit should come first because it determines whether a redesign is even necessary. Many organisations discover that targeted fixes address their actual problems more efficiently than a full rebuild.