How long should a charity website project take?

For most small and medium charities, 4 to 6 months from discovery to launch is realistic, with content as the most common slippage point. Larger or more complex sites (extensive services, multilingual, federated structure) push toward 9 to 12 months.

Do we need to change CMS?

Often no. A new design, content architecture and template set on the existing CMS can deliver most of the value at a fraction of the cost. Change CMS only when the existing one is genuinely blocking what you need to do.

How much should we spend?

Highly variable, but in 2026 a credible charity redesign typically runs £25,000 to £80,000 for small and medium charities, plus internal time. Cheaper projects are possible but tend to produce results that need replacing within a couple of years.

Charity Website Redesign Without Regret: A 2026 Guide

Most charity website redesigns deliver a prettier brochure and the same operational problems. A practical guide to running a website project that produces measurable value: scope, governance, content, architecture and decisions that avoid common regrets.

There is a familiar arc to charity website redesigns. The board signs off the project on a wave of optimism. The team picks an agency. Six months later there is a launch. Three months after launch, the numbers are unchanged, the team is exhausted, and the site is already accumulating little patches because the underlying choices were not quite right.

It does not have to be that way. The charities that get sustained value from website redesigns are not the ones with the biggest budgets. They are the ones with the clearest scope, sharpest content discipline and most pragmatic architecture decisions. What follows is a guide to running such a project.

Decide what the project is actually for

Brand vs operational performance

Some redesigns are primarily about brand: the existing site no longer represents the charity’s identity. Some are primarily about operational performance: conversion, navigation, accessibility, search visibility, content management speed. Most projects are both, but in different proportions.

Name the proportions upfront. A 70/30 operational/brand project is run differently from a 70/30 brand/operational project. Confusing the two produces a website that looks better but performs the same.

Define three success metrics

Three measurable outcomes the redesign is expected to move: e.g. online donation conversion, service enquiry completion, search visibility for priority terms. Baseline them now. Re-measure at three and six months post-launch. If you cannot name three metrics, the project is not ready.

Governance: small, decisive, paid attention

A working group of three to five people

Communications/marketing lead, fundraising lead, service lead, digital lead, and a senior sponsor. Weekly check-ins for an hour. Decisions documented. No 20-person committees.

A named senior decision-maker

One person who can break ties and approve scope changes. Usually a director or CEO. Their availability is the rate-limiter of the project; treat it that way.

Trustee oversight without trustee design-by-committee

Trustees should approve budget, sign off the brief, and review at one or two checkpoints. They should not be in the room debating font choices. The most common governance failure is trustees pulled in late and asked to weigh in on choices the team has already made.

Discovery: short and honest

Four weeks, not four months

Discovery should sharpen the brief, not become the project. Four to six weeks of: user research with real supporters and beneficiaries, content audit of the existing site, analytics review, technical audit, competitor scan. Output: a short, clear set of decisions about scope, priorities and constraints.

Content audit by use, not by enthusiasm

Most charity sites have far more content than they need. The audit should classify each page by: traffic, conversions, recency, owner. Pages with low value across all four are candidates for retirement. Going into a redesign carrying old content is one of the most reliable ways to overspend.

Information architecture and templates

Architect for the user, not the org chart

Charity websites often mirror the internal team structure: “Fundraising”, “Policy”, “Services”. Users navigate by need, not by department. Architecture should follow user intent and search behaviour, not internal reporting lines.

A small, well-built template set

Eight to twelve carefully-designed templates beats forty bespoke pages. A small template set means the team can produce new pages quickly, consistently and on-brand, without going back to the agency every time. Long-term value sits here.

Technical decisions worth getting right

CMS choice: pragmatic, not fashionable

Pick a CMS the team can use well, that the chosen agency knows, and that has a healthy ecosystem of plugins/integrations relevant to charity needs (payment, CRM, accessibility). Resist fashion-led choices.

Performance and accessibility as design constraints

Both should be baked into the design phase, not bolted on at the end. Slow pages and inaccessible designs are far more expensive to fix late. Hold the agency to performance budgets and WCAG conformance from day one.

Integration with CRM and payment

If the site does not integrate cleanly with the CRM and payment platform, supporter journeys break in the most expensive way. Specify the integrations in the brief. Test them in the build, not at UAT.

Content production: the most under-estimated risk

Plan content production as a workstream of its own

Most projects slip on content. Build content production into the plan from week one, with named owners, weekly deliverables and a sensible queue. Do not assume “the team will write the content alongside their day jobs”. They will not.

Hire help if you need it

A copywriter who knows charity sector tone can produce a tight site for a few thousand pounds and save weeks of internal grinding. Cheap relative to the project budget; usually high-value.

Launch and after

Soft launch with measurement in place

Analytics, conversion tracking, search console, accessibility audit and 301 redirects all in place at launch. Soft-launch for a week with a small cohort if you can. Catch the most painful issues before everyone sees them.

A 90-day post-launch backlog

Plan a 90-day backlog of fixes and small improvements after launch. Budget for it. Most regret-laden redesigns are projects that ran out of steam on day one of go-live.

Re-measure against the three success metrics

At three and six months post-launch, re-measure the metrics you set at the start. Share with trustees and the team honestly. If a metric has not moved, ask why and iterate. The redesign is not finished at launch; that is when it starts earning.

A website redesign is not a brand exercise dressed up as a digital project. It is a digital project that needs brand discipline. Charities that hold that line save themselves years of regret.

The most common regrets, and how to avoid them

“We migrated all the old content.” Audit ruthlessly first.
“We picked an unfamiliar CMS.” Choose pragmatically; train the team.
“The agency designed; we wrote no content.” Plan content as a workstream of its own.
“We launched and stopped.” Plan the 90-day backlog before launch.
“Trustees redesigned at the eleventh hour.” Sign off early; oversight, not co-design, at the end.
“We optimised for the homepage and nothing else.” Most traffic lands deeper in the site.

Six regrets. None inevitable. The discipline to avoid them is what separates the redesigns that pay back from the ones that need redoing in three years.

Charity Website Redesign Without Regret