Separating donor from beneficiary
The first architectural decision, and the one most sites skip. Which pages speak to funders, which speak to the people you serve, and where the two paths are allowed to meet. Everything downstream follows from it.
Nonprofit website design for two audiences at once.
A nonprofit site has to convince a donor to give and help a beneficiary find real help, usually on the same page. Most try to do it with one voice and end up doing neither. Norml designs and builds the structure, the system and the site behind it — and hands it over so a two-person team can run it.
A few clients we’ve worked with
The site was built by a volunteer three years ago, and nobody can change it.
The homepage asks for money and explains the mission in the same breath, so a donor and someone in need read the same paragraph and neither is served.
Programme pages were written for the annual report, not for the person who needs the programme tomorrow.
The donate button goes to a third-party page that looks nothing like the site, and the drop-off there is never measured.
Grant reporting needs numbers the website cannot produce, so somebody rebuilds them by hand every quarter.
The only person who knew how to edit the site left, and every change now costs a freelancer invoice the budget did not plan for.
What our nonprofit website design services include.
Seven things, in the order we do them. What separates a nonprofit web design agency from a general one is not visual style — it is designing for a team that has no developer, no marketing department, and a board that needs to see where the money went.
A page per programme, written to be found
One page per programme and per real situation someone arrives with, rather than a single Services page. That is also what earns search traffic: the person who needs help is searching for their problem, not for your organisation.
The giving path
The route from a page to a completed donation, designed as one journey rather than a button handed to a payment processor. Recurring versus one-off, the ask amounts, what happens after, and tracking on every step so you can see where people stop.
Impact told with what you actually measure
Numbers a board and a grantmaker recognise, laid out as a component you can update, not a graphic somebody has to redraw. We will not invent an impact figure — the design accommodates whatever your programme data genuinely supports.
Design system in Figma
Components, states and responsive rules, so the tenth programme page looks like the first and a new campaign does not need a designer. This is what keeps the site from degrading the year after launch.
A build a small team can run
WordPress, structured so a programme manager can add a page, swap a photo or publish a report without touching code. The Farm Soho runs a 500-plus page content system this way, managed by an editor with no developer on call.
Analytics, search and accessibility
Search Console, analytics and donation tracking configured at launch, plus accessibility treated as a build requirement rather than an audit you fail later. Public-facing organisations get held to it, and retrofitting costs more than building it in.
Nonprofit website design deliverables.
The scope follows the number of programmes and whether you are migrating an existing site. A typical engagement hands over the following:
- 01
A page map covering every URL, which audience it serves, and what it has to prove.
- 02
A Figma design system with components, states and responsive rules.
- 03
Programme, campaign, impact and report page templates.
- 04
A donation path designed end to end, with tracking on each step.
- 05
A WordPress build your programme staff edit without a developer.
- 06
Analytics and Search Console configured, with donation conversion tracked.
- 07
A redirect plan, so an existing site keeps the traffic and the grant citations it already has.
- 08
A handover session and every account and file in your name.
What we do for nonprofits.
The services an organisation usually buys together, starting with the audience split and ending with a site the team can run.
Our process
How the work runs.
Discovery
We read the analytics and the donation data, and we follow one real donor and one real beneficiary through the current site. You get the diagnosis before anything is designed.
[ 01 ]
Architecture
The audience split, the page map and the URL plan, agreed in writing. A sitemap the board can argue with.
[ 02 ]
Design
Wireframes first, then the system in Figma. Programme, campaign and impact templates, not a stack of static screens.
[ 03 ]
Build
The site, then the giving path behind it. Editable by your team without a developer.
[ 04 ]
Launch and handover
Redirects, analytics, Search Console, donation tracking, then the files and the session that make you independent.
[ 05 ]Nonprofit web design questions.
Have you built a website for a nonprofit?
Not yet, and we are not going to imply otherwise. The work shown on this page is from other sectors, chosen because it uses the mechanics a nonprofit needs: a large editorial content system an in-house editor runs alone, a content-heavy site rebuilt without losing its traffic, and a brand plus lead-acquisition build. Everything described on this page is either a technique from one of those published projects, named where it is, or ordinary design practice. If a nonprofit portfolio is what you are buying, several nonprofit website design companies specialise in exactly that and will show you one.
What does a nonprofit web design agency actually change?
Usually the architecture, not the visuals. Almost every nonprofit site we look at has one voice trying to serve donors and beneficiaries simultaneously, and a Programmes page covering work that the public experiences as separate things. Splitting those two is most of the improvement. The second change is making the site editable, because a design your team cannot update is a design that expires in eighteen months.
We are a small organisation. Can we afford this?
Maybe not, and we would rather say so early than after a discovery call. Norml publishes its rates on Clutch — $50–$99 per hour with a $5,000 project minimum. Full nonprofit website design services covering architecture, design system, content and build sit well above that minimum. If your budget is a few thousand dollars, a template on a hosted platform genuinely serves you better than a quarter of a custom build, and we will tell you that rather than scope down into something half-finished.
Can you connect the site to our donation platform?
Yes. We design the path and integrate whatever you already use rather than pushing you onto a new processor — the integration pattern is the same one we build for any system of record, and we have wired conditional forms straight into a CRM with routing and staged follow-up for Metroplex Homebuyers. What changes the numbers is usually not the processor, it is the page before it.
Can the site produce what we need for grant reporting?
It can produce the web-side numbers reliably — traffic, programme page engagement, donation conversion, campaign performance — configured at launch rather than reconstructed each quarter. It cannot produce your programme outcomes; those come from your own data. What we can do is design the impact pages so the numbers you do have go in once and appear everywhere they are cited.
Who updates the site after launch?
Your team, and that is a design constraint from the first day rather than a promise at the end. The build is structured so a programme manager adds a page or publishes a report without a developer, and the handover includes the files, the design system and a working session. When an organisation would rather not, Norml Care covers updates and monitoring monthly.
Do you handle accessibility?
We build to WCAG 2.1 AA as a matter of course: semantic structure, keyboard operation, contrast, focus states and real alternative text. What we do not do is certify you. A formal audit by an accessibility specialist is a separate exercise, and a public-facing organisation should budget for one — building it in first makes that audit cheap rather than a rebuild.
Our site already brings in donations. Can you rebuild it safely?
Yes, and it is planned work rather than a hope. We rebuild in slices and ship them one at a time, checking traffic and tracking against the old version before the next goes live. Diet vs Disease had both organic and paid traffic running through its site, so it was rebuilt header first, then footer, then homepage, then the rest, with nothing shipping unchecked.
Website 2.0 combines strategy, design, development and launch in one engagement, with the giving path treated as part of the build rather than an afterthought.