How Monarch Park Community Trust Made the Case to Their Board

The Meeting Nobody Wants to Have

Sarah had been at Monarch Park Community Trust for eight months when she finally asked James to put the website on the board agenda.

She had spent three of those months documenting everything. The accessibility audit. The PageSpeed scores. The plugin conflicts. The two days she lost last October when a WooCommerce update broke the donation page and nobody noticed for 72 hours. She had a spreadsheet. She had screenshots. She had a quote from a local agency for a WordPress refresh that came in at $28,000 and would, in her estimation, solve approximately none of the underlying problems.

What she did not have was confidence that the board would understand any of it.

Non-profit boards are not technology committees. They are lawyers, retired educators, community advocates, and accountants who give their Saturday mornings to an organization they believe in. They are not thinking about plugin dependency or content modelling or WCAG 2.1 AA compliance. They are thinking about program delivery, donor relationships, and whether the organization is going to meet payroll.

Getting a website rebuild approved means speaking their language, not yours.

Here is how Sarah did it.

Start With Risk, Not Technology

The single most effective thing Sarah did was reframe the conversation from a technology decision to a risk management decision.

Boards understand risk. They think about it constantly: reputational risk, financial risk, legal risk, operational risk. A website rebuild pitched as a technology upgrade gets filed under discretionary spending. The same rebuild pitched as risk mitigation gets a different kind of attention.

Sarah led with three risks.

None of this required Sarah to explain what a plugin was.

What the Data Says About Slow, Inaccessible Nonprofit Websites

Monarch Park's site was loading in eleven seconds on mobile. That is not a minor inconvenience. According to research from the BBC, every additional second a page takes to load causes 10% of visitors to leave. At eleven seconds, the math is brutal.

The wider picture is sobering. Only 19% of nonprofits raised more than half of their revenue online in 2024, while 11% raised nothing digitally at all. (NonProfit PRO 2025) The gap between organizations investing in their digital presence and those running on neglected WordPress installs is not closing. It is widening.

Then Talk About True Cost

Once the board was thinking about risk, Sarah introduced cost. Not the cost of rebuilding. The cost of not rebuilding.

She broke it down simply.

The agency that maintained the site charged $150 an hour. In the past 12 months Monarch Park had spent $4,200 on maintenance calls, most of them related to plugin updates, broken integrations, and content changes that should have been simple. That number did not include the two days of staff time lost during the donation page outage, or the ongoing hours Sarah herself spent navigating a CMS that was not designed for the way the organization worked.

The board stopped thinking about the rebuild as an expense and started thinking about it as an investment with a measurable return.

The Hidden Cost of Plugin Dependency

WordPress powers a significant share of the web, but its plugin ecosystem comes with a cost that rarely appears in any budget line. Plugins need updating. Updates conflict. Conflicts break things. Fixing broken things costs money.

For a nonprofit whose donor conversion rate is already razor thin, those seconds are not a technical problem. They are a revenue problem. Neither of these is a problem that a visual refresh solves.

Address the "Why Not Just Update WordPress" Question

It came up, as it always does.

One board member, a retired educator who had been with the organization since 2014, asked why they could not simply update the existing WordPress site rather than rebuilding from scratch. It was a fair question and Sarah had prepared for it.

Her answer had three parts.

First, the current site's problems were structural, not cosmetic. A new theme and updated plugins would not fix the accessibility violations baked into the content. It would not reduce plugin dependency. It would not give the communications team the flexibility they needed to manage content without developer help. It would be new wallpaper on a crumbling wall.

Second, the quote for a WordPress refresh was $28,000. The quote for a rebuild on a modern platform was not dramatically higher when you factored in the reduced ongoing maintenance costs. The gap between the two options was smaller than it appeared.

Third, and most importantly, they had already done the WordPress refresh. The site had been refreshed in 2019. They were back in the same conversation seven years later. At some point the organization needed to make a different decision.

The board member nodded. Sarah moved on.

The Mobile Reality Nonprofits Cannot Ignore

More than half of all web traffic now comes from mobile devices, and nonprofit websites are failing that audience at a striking rate.

Monarch Park's mobile PageSpeed score was 43 out of 100. Their load time on mobile was eleven seconds. By the time most visitors saw the homepage, more than half had already left.

Give Them a Decision, Not a Discussion

One of the most common mistakes in board presentations is leaving the room open for a conversation that the board is not equipped to have. If you present the technology options and ask the board to weigh in on platforms and vendors, you will be in that meeting for three hours and leave with nothing decided.

Sarah did not ask the board to choose a platform. She asked the board to approve a budget for a discovery process.

The board was not being asked to approve a rebuild. They were being asked to approve the process of understanding what a rebuild would cost and what it would deliver.

What This Looks Like for Your Organization

If you are a Communications Manager or Executive Director reading this with a sense of recognition, here are the three things worth taking from Monarch Park's experience.

What's Next

In Part 3 we will follow Monarch Park through the vendor evaluation process: what questions they asked, what red flags they spotted, and how they separated vendors who could talk about websites from vendors who actually understood how non-profits work.