What Trustees Ask Before Approving Website Investment
Key takeaways
- Website spending is a use of charitable funds, which makes approval a trustee decision rather than a communications one, and the Charity Governance Code published in November 2025 gives managing resources and risks a principle of its own.
- The case fails when it is framed as a website project, because that invites comparison with the last build; it has to move from design to infrastructure and from cost to risk, which are categories the board already has frameworks for.
- Change the question from whether a new website is needed to what the current one costs to operate, and the budget conversation becomes an infrastructure review rather than a design proposal.
- Build the case on evidence a board can test: donation drop-off, staff time lost to workarounds, grant friction, compliance exposure, peer comparison, and the compounding cost of delay.
- In the Charity Digital Skills Report 2026, Zoe Amar and Nissa Ramsay found that 17% of charities accessed funding for digital costs from trusts and foundations, down from 30% the year before, so the money is more likely to come from reserves than from a grant.
- Structure the paper as a governance document: executive summary, current state assessment, risk register, options appraisal, recommended phased approach, and a named owner with a reporting line back to the board.
Summary
Website spending stops being a communications matter the moment it reaches the board, and becomes a use of charitable funds that trustees are accountable for approving. The case fails when it is framed as a website project, because that invites comparison with the last build and a debate about design. It succeeds when it is framed as infrastructure and risk: what the current site costs the organisation every month, what regulatory exposure it carries, and what the board is actually choosing between. This post covers the reframe, the six evidence points that support it, how to structure the paper so it reads as a governance decision, and how to answer the objections trustees and finance directors raise in the room.
The problem isn't the money. It's the framing.
You know the website needs investment. But:
- your finance director asks why you can't just update the existing one;
- your board chair wonders if it can wait until next financial year;
- meanwhile your comms team loses hours to workarounds, donors bounce from broken mobile pages, and a grant reviewer just asked why your annual report isn't on the site.
Why "We Need a New Website" Always Loses
A website project invites the wrong comparison. Finance directors compare it to the last build and assume this is the same thing with a bigger price tag. Board members outside digital have no reference point for what modern web infrastructure involves.
The conversation needs to move from design to infrastructure, and from cost to risk. Your board already has frameworks for both.
The Infrastructure Reframe
Your website is infrastructure, like your servers, accounting software, CRM and HR systems. You do not debate whether to maintain those; you budget for them. The website processes data, handles communications, supports fundraising, and represents the organisation to every external stakeholder at once.
So the question is not "do we need a new website?" It is "what is the current cost of operating on inadequate web infrastructure?" Asked that way, the budget conversation becomes an infrastructure review.
Why This Is a Trustee Decision
Once the number is large enough to reach the board, website spending stops being a communications matter. It becomes a use of charitable funds, and the people signing it off carry a duty for it.
That duty is not a matter of taste:
- The Charity Commission expects trustees to manage their charity's resources responsibly. Its guidance on decision-making for charity trustees (CC27) asks them to act within their powers, in good faith, and sufficiently informed.
- The Charity Governance Code, published on 10 November 2025, gives managing resources and risks a principle of its own among its eight, alongside a new foundation principle on trustees understanding their legal duties. It runs on apply or explain, so a board that declines a recommendation is expected to be able to say why.
A trustee reading a request for a significant sum is not asking whether the site could look better. They are asking:
- Is this a responsible use of the charity's funds?
- What happens if it is not spent?
- Who is accountable for the outcome?
- How will the board know in twelve months whether the decision was sound?
Answer those four and you have written a governance paper. Leave them out and you have written a design proposal with a price on it.
The funding context makes this harder. In the Charity Digital Skills Report 2026, which drew 807 responses, Zoe Amar and Nissa Ramsay found that 17% of charities had received funding for digital from grantmaking trusts and foundations, compared with 30% in 2025. They also found that 63% said squeezed finances were the biggest barrier to their digital progress.
So this money is more likely to come out of reserves or unrestricted income than a grant, and a trustee is right to test it harder. Anticipate that test rather than resent it.
Building the Business Case: Six Evidence Points
1. Donor Conversion Data
If you have Google Analytics, pull the data on your donation journey:
- Where do people drop off?
- What percentage of mobile visitors complete a donation?
If you do not have this data, that is itself evidence of inadequate infrastructure.
2. Staff Time Spent on Workarounds
Ask your comms team to log, for two weeks, every task that exists only because the website can't do it automatically:
- manual PDF updates;
- fielding calls about information that should be on the site;
- rebuilding pages in the wrong tool because the CMS is too complex.
Annualise that time and cost it at their day rate.
3. Grant Opportunities Affected
Many institutional funders now include website review in due diligence. Ask your fundraising team whether the site has ever caused friction in a grant application or a major donor meeting.
A single grant lost on a due diligence question reframes the whole conversation in the currency your finance director thinks in. What a programme officer checks, and what they conclude when they cannot find something, is set out in what funders see when they visit your website.
4. Compliance Exposure
GDPR, WCAG, Charity Commission reporting requirements: cost out what a regulatory penalty or legal challenge would represent. This is not scaremongering; it's quantified risk.
5. Competitor Positioning
Show your board three comparable organisations' websites alongside yours. It is uncomfortable and effective: decision-makers respond to visual evidence in a way spreadsheets don't produce.
6. The Cost of Delay
Every year of deferral adds technical debt, widens the gap with peers, and compounds the eventual rebuild cost. A phased investment now is cheaper than a crisis-driven rebuild later.
How to Structure the Proposal
| Section | Content | Audience |
|---|---|---|
| Executive Summary | Risk identified, recommended action, cost, expected outcome | Board chair, trustees |
| Current State Assessment | Specific failures: accessibility score, compliance gaps, conversion data | Finance director, COO |
| Risk Register | Legal, reputational and operational risks, with likelihood and impact rated | All trustees |
| Options Appraisal | Do nothing, remediate or rebuild, with costs and outcomes for each | Board, ED |
| Recommended Approach | Phased plan with milestones, costs, and success measures | Finance, operations |
| Governance Commitment | Who owns this, how it will be reported to the board | All trustees |
A Template You Can Fill In
Most people stall writing that paper from a blank page, so I have written the version you fill in. It is free, with no email capture and no form, and it downloads directly.
The first half turns everything above into sections you complete:
- the problem in your organisation's own words;
- what has forced the decision now;
- the cost of another twelve months of doing nothing;
- accessibility as legal exposure rather than best practice;
- a budget range with a written justification instead of a blank field;
- who signs off what before the project starts.
Each section notes why it matters and what a weak entry looks like.
The second half is the vendor specification you write once the money is agreed, including how WCAG 2.2 AA conformance gets verified at handover rather than promised. More on that in the piece on selecting a consultant who understands governance.
The second half looks like an RFP, and I have argued that an RFP is a poor way to choose a consultant. I still think so: for selection, a structured diagnostic identifies the right person more reliably than a written response.
This template does a different job. It gets internal agreement that the project should happen at all, and records what was agreed so the decision survives the months that follow. Those are governance outcomes, and a written specification is the right instrument for them.
Take your own copy in Google Docs.
Handling the Common Objections
"We don't have budget this year"
Ask what continuing as things are actually costs. Quantify the staff time, compliance risk and missed fundraising, and set that annual figure beside the one-off project cost.
One number does not always beat the other. The point is that the board is then choosing between two costs, not between spending and saving. That is a different decision, and usually a shorter conversation.
"Can't we just update the existing site?"
Sometimes yes. A good audit will tell you whether remediation or rebuild is the right call, and will cost both options honestly. See Rebuild vs Remediate for the framework.
"We'll do it after the capital campaign"
Your website supports the capital campaign. An underpowered site during your most intensive fundraising period is the worst time to defer.
"Isn't this a management decision?"
Partly. Running the website day to day is management. A capital sum, a multi-year commitment, or a change that affects how the charity meets its publication duties is a board decision.
Treating it as operational is how charities end up with a website nobody at board level has formally accepted responsibility for. Put it on the agenda as a decision item with a recommendation, not as an update. If the board would rather delegate it, ask them to minute the delegation and the spending limit.
Further Reading
- Why Your Nonprofit Website Is a Governance Liability
- Affordable Nonprofit Websites: Hidden Compliance & Governance Costs
- The Real Cost of 'Good Enough' Nonprofit Websites
- Nonprofit Website RFP: Selecting Consultants Who Understand Governance
- Blueprint Audit: Start With a Clear Picture
What Winning the Argument Actually Gets You
Organisations that frame this correctly and get it approved do not just get a new website. They get a reset:
- Content governance that was entirely informal becomes documented.
- Vendor relationships that were dangerously opaque get renegotiated with clear ownership terms.
- The comms team stops losing hours to workarounds.
- The board starts referencing the website in funder conversations rather than avoiding the subject.
That is what the budget argument is for. Not a redesign. A functioning institutional asset that earns its cost every month.
The template is free and ungated. If you want the evidence that fills in the first half before you write it, the Blueprint Audit is a £2,500 assessment of where your site currently stands on accessibility, governance and credibility. Standalone, no obligation.
Two clicks. Three things.
Send the address of your website. Within two working days you get a short email naming the three things a funder would hold against it, including what AI assistants like ChatGPT and Google’s AI Overviews currently say about you. No report, no call, no follow-up unless you ask.
Received. Your three things arrive within two working days.
That did not send. Email hello@socialectric.com with your website address and I will reply from there.
Frequently asked questions
- How do you justify a website budget to a nonprofit board?
Frame it as infrastructure investment with a risk basis, not a design project with a cost. Present three things: the specific risks the current site creates (compliance exposure, fundraising friction, governance gaps), the operational cost of the current situation (staff time on workarounds, missed grant opportunities, accessibility complaints), and the return on a properly scoped investment. Boards respond to risk-framed infrastructure arguments more reliably than to design proposals. It helps to know the questions a board will actually ask before you are in the room.
- What budget range should a nonprofit expect for a website rebuild?
For an established nonprofit with complex stakeholder needs, a rebuild is scoped and priced from the audit's findings, not from a published range: complexity, content volume and integration requirements move the number too far for one figure to be honest. The scope has to cover design, build, content migration, accessibility testing, CMS training and documentation, plus an ongoing line for hosting, maintenance and governance support. A quote well below its peers usually excludes one of those, and the omission surfaces later as extra cost. That pattern is set out in the hidden compliance and governance costs of an affordable site.
- Why do nonprofit finance directors resist website investment?
Because they see a concentrated, visible cost on a budget line against diffuse, invisible returns. The build cost is explicit; a grant that advanced because the website provided credible due diligence is never attributed to the website. Make the indirect returns as concrete as possible: estimate the annual value of grant applications the website supports or undermines, calculate staff time spent on workarounds, and quantify the compliance risk the current site represents.
- What is the difference between a website cost and a website investment?
A cost is an expenditure with no expected return; an investment produces a return greater than the cost over a defined period. A properly scoped nonprofit website is an investment: it reduces staff time on avoidable tasks, supports fundraising, reduces compliance risk, and gives stakeholders a credible public presence. The case has to demonstrate the return, not just the necessity. The counterpart is what a good enough website costs an institution while nobody is counting.
- How do you calculate the return on a nonprofit website investment?
Compare the three-year total cost of the current situation with that of a properly built alternative. The current situation includes direct costs (hosting, maintenance, emergency fixes), staff costs (hours spent on workarounds at day rate), compliance risk (estimated probability and cost of an enforcement action), and opportunity cost (grants lost or delayed, donations not converted). The comparison almost always favours investment.
- What internal stakeholders need to support a nonprofit website budget?
The executive director or CEO must sponsor it: without leadership support, finance committees will not approve significant website budgets. The fundraising or development director is a key ally, because the website affects their ability to cultivate donors and support grant applications. The operations director provides the risk and cost-of-inaction evidence, and the communications team presents the capability gaps the current site creates. Building this coalition before approaching the finance committee improves the chances of approval.
- Should a nonprofit use a charity discount or grant for website investment?
Where available, yes, but with caution. Some technology grants and charity discounts (Google for Nonprofits, Canva Nonprofits, Salesforce's Power of Us Program) reduce ongoing platform costs. But a site built around available discounts rather than organisational need is often optimised for the discount, not the organisation's stakeholders. Make the case on the merits of the right solution, then apply discounts where they fit.
- How should a nonprofit phase a website investment to manage budget impact?
Make each phase independently valuable, not a partial implementation that only works once later phases are funded. Phasing is legitimate when the full investment cannot be approved in a single cycle. A sensible split: phase one covers compliance, governance and primary stakeholder journeys (the critical infrastructure); phase two covers content depth, secondary audience journeys and advanced features. Do not phase accessibility compliance: it must be in phase one.
- What is a reasonable annual website maintenance budget for a nonprofit?
Budget for it annually, as a percentage of the initial build cost. That line covers platform costs, security monitoring, content governance support and minor development. Organisations that budget nothing for post-launch maintenance consistently end up with a deteriorating site and a reactive rebuild, at higher cost and lower quality than planned investment would have produced.
- How do you make the website budget case to a risk-averse nonprofit board?
Lead with the downside of inaction rather than the upside of investment. Present the Charity Commission's published inquiry reports and regulatory alerts, the ICO's fines for data protection failures, and the Equality Act obligations for accessible digital services. Then show the current site's specific gaps against each. Risk-averse boards are more motivated by avoiding defined negative outcomes than by achieving undefined positive ones.
- Is a website business case the same as an RFP?
No, and conflating them is why website projects stall. A business case argues that the organisation should spend the money; it is decided internally, usually by an Executive Director or a board, before any vendor sees anything. An RFP specifies what the money buys and asks vendors to price it. The template on this page covers both because the same person writes them in sequence, but different audiences read them in different rooms. Writing the second before the first is the most common sequencing mistake, and it hands the scoping decision to the vendors.
- Do UK charities have a legal obligation to make their website accessible?
Almost always yes, though not usually through the route people expect. The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 exclude non-governmental organisations at regulation 4(1)(b), so most charities sit outside them. That exclusion has exactly two carve-outs, both about what the organisation does: it falls away where the services provided are essential to the public, or where they specifically address the needs of, or are meant for, persons with disabilities.
Being mostly financed by public money is a separate and earlier question. It sits in the regulation 3 definition of a body governed by public law, which decides whether you are a public sector body in the first place, not whether the NGO exclusion applies to you.
The Equality Act 2010 applies broadly, including to free services, with no size or income threshold. Its duty to make reasonable adjustments is anticipatory for service providers: foreseeable barriers are expected to have been addressed before a disabled person encounters one. Waiting for a complaint is not compliance. If the organisation sells to consumers in the EU, the European Accessibility Act may also apply. None of this is legal advice.
- Is approving website spending a trustee decision or a management one?
Running the website day to day is management. A capital sum, a multi-year commitment, or a change that affects how the charity meets its publication duties is a board decision, because it is a use of charitable funds and carries institutional risk.
The Charity Governance Code published in November 2025 treats managing resources and risks as a principle in its own right and runs on apply or explain, so a board that turns a recommendation down is expected to explain the alternative approach it is taking. If your board prefers to delegate the decision, ask for the delegation and the spending limit to be minuted.