How to Make the Case for a Website Budget Inside Your Nonprofit
Key takeaways
- Winning internal approval is hard because the website is not a programme, does not serve beneficiaries directly, and its contribution is indirect and difficult to quantify while the cost is concentrated and visible.
- The case fails when framed as a website project, which invites comparison to the last build; it should move from design to infrastructure and from cost to risk — categories the Board already understands.
- Reframe the website as operational infrastructure, like the CRM or accounting system, and change the question from "do we need a new website?" to "what is the current cost of operating on inadequate infrastructure?"
- Build the case on concrete evidence: donor conversion drop-off, staff time lost to workarounds, grant friction, compliance exposure, competitor comparison, and the compounding cost of delay.
- Structure the proposal like a governance paper — executive summary, current-state assessment, risk register, options appraisal, recommended phased approach, and a governance commitment for ownership and reporting.
- Meet objections on their own terms by quantifying the cost of inaction, using an honest audit to decide remediate versus rebuild, and showing the website directly supports priorities such as a capital campaign.
Summary
Securing Board or finance committee approval for a significant website investment is one of the harder internal communications challenges a Communications Director faces. The website is not a programme. It does not serve beneficiaries directly. Its contribution to the organisation's mission is indirect and difficult to quantify. Meanwhile, the investment is significant and visible, and leadership that is rightly cautious about overhead costs will apply scrutiny to anything that looks like infrastructure spending rather than impact spending.The internal case for website investment fails when it is made on marketing grounds — increased traffic, better conversion rates, improved brand presentation. These arguments do not resonate with Boards focused on mission and governance. The case succeeds when it is made on governance and risk grounds: the current website creates regulatory exposure, undermines funder credibility, and costs the organisation more in developer dependency and ongoing remediation than a properly built replacement would cost to build and maintain.This post provides the internal case framework for nonprofit website investment: how to translate website quality issues into governance language that a Board can evaluate on institutional grounds, how to quantify the cost of the current website's failures in terms that finance committees can assess against the investment required, how to frame the platform recommendation as a governance decision rather than a design preference, and how to present the risk of inaction alongside the investment case so that the Board is choosing between two sets of costs rather than between spending money and saving it.
You know the website needs investment. Your finance director sees a six-figure number and asks why you can't just update the existing one. Your board chair wonders if this can wait until next financial year. Meanwhile, your comms team is losing hours to workarounds, donors are bouncing from broken mobile pages, and a grant reviewer just asked why your annual report isn't on the site. The problem isn't the money. It's the framing.
Why "We Need a New Website" Always Loses
Framing the conversation as a website project invites the wrong comparison. Finance directors compare it to the last website build — whenever that was, whatever it cost — and assume this one is the same thing with a bigger price tag. Board members who don't work in digital have no reference point for what modern web infrastructure actually involves.
The conversation needs to move from design to infrastructure, and from cost to risk. These are categories your board already has frameworks for.
The Infrastructure Reframe
Your organisation has servers, accounting software, a CRM, and HR systems. You don't debate whether to maintain them — you budget for it as operational infrastructure. Your website is the same category of asset. It processes data, handles communications, supports fundraising, and represents the organisation to every external stakeholder simultaneously.
The question is not "do we need a new website?" The question is "what is the current cost of operating on inadequate web infrastructure?" When you frame it that way, the budget conversation becomes an infrastructure review, not a design proposal.
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 don't have this data — that itself is evidence of inadequate infrastructure.
2. Staff Time Spent on Workarounds
Ask your comms team to log, for two weeks, every task they do 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 as part of due diligence. Talk to your fundraising team about whether your site has ever been a point of friction in a grant application or major donor meeting. One missed £50,000 grant reframes a £25,000 website investment entirely.
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. This is uncomfortable and effective. Decision-makers respond to visual evidence in a way that spreadsheets don't produce.
6. The Cost of Delay
Every year of deferred investment adds technical debt, widens the gap with peer organisations, and compounds the eventual rebuild cost. A phased investment starting now is cheaper than a crisis-driven rebuild in three years.
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, operational risks — likelihood and impact rated | All trustees |
| Options Appraisal | Do nothing / remediate / rebuild — 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 |
Handling the Common Objections
"We don't have budget this year"
Ask what the cost of continuing as-is is. Quantify the staff time, the compliance risk, the missed fundraising. Most organisations discover the cost of inaction exceeds the cost of action within 18 months.
"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 cost both options honestly. See Rebuild vs Remediate for the framework.
"We'll do it after the capital campaign"
Your website directly supports the capital campaign. An underpowered site during your most intensive fundraising period is the worst possible timing for deferral.
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
- Blueprint Audit: Start With a Clear Picture
What Winning the Argument Actually Gets You
The organisations that get this approved — and frame it correctly — don't 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 actually for. Not a redesign. A functioning institutional asset that earns its cost every month.
Frequently asked questions
Frame it as infrastructure investment with a risk basis, not a design project with a cost. Present three things: the specific risks created by the current website (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 improvement proposals.
For an established nonprofit with complex stakeholder needs, a properly scoped rebuild typically costs between £15,000 and £35,000 depending on complexity, content volume, and integration requirements. This covers design, build, content migration, accessibility testing, CMS training, and documentation. Ongoing costs — hosting, maintenance, and governance support — add £3,000 to £8,000 annually. Projects priced significantly below this range typically exclude elements that later require additional investment.
Finance directors see a concentrated, visible cost on a budget line against diffuse, invisible returns. The £20,000 build cost is explicit; the £50,000 grant that advanced because the website provided credible due diligence is never attributed to the website. Addressing this requires making the indirect returns as concrete as possible: estimate the annual value of grant applications the website currently supports or undermines, calculate staff time spent on website workarounds, and quantify the compliance risk the current site represents.
A cost is an expenditure with no expected return. An investment is an expenditure that produces a return greater than the cost over a defined period. Nonprofit websites, when properly scoped, are investments: they reduce staff time on avoidable tasks, support fundraising more effectively, reduce compliance risk, and enable the organisation to direct stakeholders to a credible public presence. The investment case requires demonstrating the return, not just the necessity.
Calculate the three-year total cost of the current situation: direct costs (hosting, maintenance, emergency fixes), staff costs (hours spent on workarounds at day rate), compliance risk (estimate the probability and cost of an enforcement action), and opportunity cost (grants lost or delayed, donations not converted). Compare this against the three-year total cost of a properly built alternative. The comparison almost always favours investment, often significantly.
The executive director or CEO must sponsor the investment — without leadership support, finance committees will not approve significant website budgets. The fundraising or development director is a critical ally, because website investment directly affects their ability to cultivate donors and support grant applications. The operations director provides the risk and cost-of-inaction evidence. The communications team presents the specific capability gaps the current site creates. Building this coalition before approaching the finance committee significantly improves approval rates.
Where available, yes — but with caution. Some technology grants and charity discounts (Google for Nonprofits, Canva for Nonprofits, Salesforce for Nonprofits) reduce ongoing platform costs. However, building a website primarily around available discounts rather than organisational need often produces a site optimised for the discount rather than the organisation's stakeholders. The investment case should be made on the merits of the right solution, then discounts applied where applicable.
Phasing is legitimate when the full investment cannot be approved in a single cycle, but the phases must each be independently valuable — not partial implementations that don't function until later phases are funded. A sensible phasing: phase one addresses compliance, governance, and primary stakeholder journeys (the critical infrastructure); phase two addresses content depth, secondary audience journeys, and advanced features. Do not phase accessibility compliance — it must be in phase one.
Budget 15-20% of the initial build cost annually for ongoing maintenance. On a £25,000 build, that's £3,750-£5,000 per year covering platform costs, security monitoring, content governance support, and minor development. Organisations that budget zero for post-launch maintenance consistently find themselves with a deteriorating site requiring a reactive rebuild within three to four years — at higher cost and lower quality than planned investment would have produced.
Lead with the downside of inaction rather than the upside of investment. Present the Charity Commission's published enforcement actions related to digital transparency. Present the ICO's fines for data protection failures. Present the Equality Act obligations for accessible digital services. Then present the current site's specific gaps against each of these standards. Risk-averse boards are more motivated by avoiding defined negative outcomes than by achieving undefined positive ones.
