How to Choose a Nonprofit Website Consultant | Socialectric

Most nonprofits choose website consultants the same way they choose restaurants: based on how things look and what other people said. They review portfolios for aesthetic quality, ask for references from previous clients, and compare day rates. None of these things reliably predict whether a consultant will build a website that holds up under institutional scrutiny, serves your specific stakeholder groups, or remains maintainable by your team after the project ends.

The RFP process, as most organisations run it, selects for the consultant who presents best. That is a different skill from the one required to diagnose an institutional website problem, navigate competing stakeholder claims, and build something that works at Board level. The best-presenting consultant and the most capable consultant are rarely the same person.

What most nonprofits get wrong in the selection process

The standard approach starts with a brief. The brief describes what the organisation wants: a new website, a refreshed design, better navigation, a donation flow that works. Consultants respond to the brief, and the organisation selects based on the quality of the response.

The problem is that the brief describes symptoms, not causes. An organisation that says it wants better navigation may actually have a stakeholder priority problem — it is trying to serve six audiences simultaneously and has never decided which three matter most. A consultant who answers the brief as written will produce better navigation. The underlying problem will resurface within twelve months.

A consultant who understands governance will question the brief. They will ask who the primary stakeholders are, what decisions the website supports for each of them, and whether the navigation problem is structural or editorial. That question changes the scope, the solution, and the outcome.

According to NCVO's UK Civil Society Almanac 2024, the voluntary sector includes over 160,000 organisations. The Communications Directors serving these organisations face a consistently reported challenge: website projects that do not resolve the underlying governance problems they were commissioned to fix. The pattern is not bad luck. It is bad selection criteria.

The five criteria that actually predict outcomes

1. Sector-specific experience

General web experience is not the same as nonprofit web experience. The governance complexity, multi-stakeholder navigation, accessibility obligations, and credibility requirements of an established NGO are materially different from a commercial website.

Ask specifically about nonprofit sector experience. Ask for examples of sites built for organisations with your scale, stakeholder complexity, and regulatory environment. If the examples are primarily small charities, community groups, or early-stage nonprofits, that experience does not transfer directly to an established organisation under institutional scrutiny. A consultant who has not previously navigated the intersection of Charity Commission disclosure obligations, institutional funder due diligence requirements, and WCAG AA compliance will learn these on your engagement.

2. A diagnostic approach before a build approach

The right consultant will not produce a quote based on your brief. They will ask questions first. What has been tried before? Who are the primary stakeholders? What does success look like in twelve months? What does failure look like?

A consultant who produces a quote and a timeline within 48 hours of receiving your brief has not done any diagnosis. They have read the brief and priced the work as described. A good consultant challenges the brief before any build begins. This is not the same as being difficult or adding unnecessary process. It is the difference between a contractor who builds what they are asked to build and an adviser who helps the organisation understand what it actually needs.

3. Evidence of accessibility expertise

WCAG 2.1 AA compliance is not optional for most established nonprofits. Organisations receiving public funding, serving beneficiaries with disabilities, or operating under the Equality Act 2010 have legal obligations that a website consultant needs to understand as a governance requirement rather than a technical checkbox.

The WebAIM Million 2025 report found that 95.9% of the top one million websites have detectable WCAG failures. For nonprofits specifically, the failure rate on sites built without accessibility governance is significantly higher. Ask whether the consultant can provide an accessibility audit alongside a build. Ask how they ensure WCAG compliance is maintained after launch, when your team starts making content changes independently.

4. Clarity on what happens after handover

Most website problems for nonprofits do not begin at launch. They begin six months after launch, when the consultant has moved on, the comms team is making content changes independently, and nobody is monitoring what is happening to the site's structure, performance, or compliance.

A consultant who does not have a clear answer to what happens after handover is not the right partner for an established nonprofit. The answer can take different forms: an ongoing retainer, a subscription model, a documented handover process that genuinely equips the internal team. What it cannot be is silence, or a vague statement about being available if problems arise. This is directly connected to the handover planning requirements that protect the organisation's investment.

5. Accountability structure

Agencies create structural accountability problems for nonprofits. Projects pass between account managers, developers, and designers. The person you briefed at the start of a project is rarely the person who delivers the final site. When problems arise, accountability is diffuse.

An independent specialist offers a different structure: one person responsible for every decision, every line of code, and every recommendation. When something is wrong, there is one person to call. This does not mean agencies are always wrong for nonprofits. But the accountability question is worth asking explicitly: who will be responsible for this project from start to finish? This is one of the reasons Communications Directors at established nonprofits increasingly prefer specialist independents over large agencies.

The questions to ask during selection

Before shortlisting any consultant, get answers to these questions in writing.

What diagnostic process do you follow before producing a quote or proposal? A consultant who skips diagnosis will produce a solution to the wrong problem.

Can you provide examples of accessibility audits you have conducted alongside builds? Not templates or frameworks: actual audits with findings and remediation.

What does your engagement look like after the site launches? Who handles ongoing changes, and what does that cost?

Have you worked with organisations of our scale, with our stakeholder complexity and regulatory obligations? General nonprofit experience is not the same as experience with established, institutionally scrutinised organisations.

How do you handle stakeholder conflict during a project? If programme teams, fundraising, and the Executive Director all have competing views of what the site should do, who arbitrates, and on what basis?

What a structured diagnostic process looks like

The most reliable way to evaluate a consultant is to engage them for a structured diagnostic before committing to a build. A diagnostic that produces a Board-ready report with specific findings, stakeholder mapping, accessibility assessment, and governance recommendations gives your organisation the information it needs to make a sound decision — and gives the consultant the information they need to scope the right work.

A diagnostic is also a low-risk way to test the relationship. How the consultant conducts interviews, synthesises findings, and communicates recommendations tells you more about their approach than any portfolio or reference call.

If a consultant is unwilling to offer a diagnostic phase before a build, that is itself a signal. The organisations that are most confident in the solution they are proposing are the ones that have done the diagnosis first. The Blueprint Audit resource describes what a structured diagnostic engagement looks like in practice.

Question 1: Is it better to hire an agency or an independent consultant for a nonprofit website?

It depends on the complexity of the project and the accountability structure that works for your organisation. Agencies offer breadth: more people, more specialisms, more capacity for large simultaneous projects. Independent specialists offer accountability and continuity: one person responsible for everything, with no handoffs between departments. For most established nonprofits undergoing a website rebuild, the accountability model of a specialist independent is more appropriate than the distributed responsibility of an agency.

Question 2: Should we run a formal RFP process?

A formal RFP is useful for ensuring comparability across responses, but it selects for consultants who are good at writing proposals rather than consultants who are good at the work. If you run an RFP, structure it to require a diagnostic approach: ask consultants to describe how they would identify the real problem before proposing a solution, rather than asking them to propose a solution to the brief you have written.

Question 3: How important is it that the consultant has worked with nonprofits specifically?

Very important for established organisations. The stakeholder complexity, regulatory environment, accessibility obligations, and credibility requirements of an NGO with institutional funders are materially different from commercial web projects. A consultant who has not navigated these requirements before will learn on your engagement, at your cost.

Question 4: What should a diagnostic phase look like in practice?

A diagnostic engagement for a nonprofit website typically runs two to three weeks and produces a Board-ready report covering stakeholder salience mapping, technical audit findings, and specific recommendations prioritised by institutional consequence. The diagnostic is not a design proposal. It answers the question of what the organisation actually needs before anyone decides how to deliver it. Any consultant unwilling to offer a diagnostic phase before a build is proposing a solution before they understand the problem.

Question 5: How long should a nonprofit website project realistically take?

A well-governed nonprofit website project — from diagnostic through to launch — typically takes four to six months for an established organisation with meaningful content, multiple stakeholder groups, and WCAG compliance requirements. Projects that are compressed to eight or ten weeks almost always sacrifice the stakeholder validation and governance work that determines whether the new site actually performs better than the one it replaces.

If your organisation is at the beginning of a consultant selection process and wants a governance-grounded assessment of your website situation before briefing anyone, the Blueprint Audit is designed for exactly this stage.