Skip to content
Copied to clipboard
All industries

Non-Profit

Three audiences, one site.

Donors, partners, and participants all arrive at the same pages wanting different things, and writing for all three at once is how a site ends up speaking to none of them. We give each one its own path — then hand the whole thing to a team that usually has no developer on staff.

Written from your side

What we hear, and what we do about it.

The problem

What we hear from buyers

  • Copy written for donors that participants have to read around
  • A site nobody on staff can update without outside help
  • Programme information buried under organisational history
  • Design that reads either corporate or homemade, and never quite right

The response

How we approach the work

  • Information architecture that gives each audience its own route
  • An editing surface built for the people who will actually use it, and documented on handover
  • Programme and impact content structured to be updated rather than rebuilt
  • Identity that holds up to a funder and still welcomes a family

Liability vs. force multiplier

Same mission. Two different websites.

A programme officer reviewing two organisations. Both do real work. One of them makes it easy to fund.

Organisation A — a reason to fund elsewhere

The site they find

  • Copy written for donors that participants read around
  • Programme detail buried under organisational history
  • Impact numbers from a report two years old
  • Design that reads either corporate or homemade
Organisation B — a reason to fund you

The site we build

  • Each audience given its own route through the site
  • What you do, before the story of how you started
  • Impact content structured to be updated, not rebuilt
  • Holds up to a funder and still welcomes a family

Why JMG

What holds up under scrutiny.

Why JMG / 01

Three audiences, one site

Donors, partners, and participants want different things from the same pages. We structure the site so each finds their path without the others being watered down.

Why JMG / 02

Built to be handed over

Your team runs the site after launch, often with no developer on staff. That's a constraint from the first component, not a plugin added at the end — and we document what we hand over.

Why JMG / 03

Support that isn't sold back to you

Every launch includes 30 days of post-launch support. Ongoing care sits inside Platforms rather than being priced as a separate service.

Services that lead

Where we start the engagement.

Most non-profit engagements open on one of these and grow into the others.

Service / 02

Brand

Design that earns trust — and doesn't look like government software.

Common questions

The questions we hear first.

We serve donors, partners, and participants. How do you avoid a site that speaks to nobody?

By giving each one its own path rather than its own paragraph. The information architecture does the work — a donor and a programme participant should each be one click from what they came for, without reading copy written for the other.

Our team has no developer. Can we run the site ourselves?

Yes. We build the editing surface for the people who'll actually use it, and we document the handover.

What happens after launch?

Every launch carries a 30-day warranty — we fix anything that breaks in what we delivered. Beyond that, ongoing care covers uptime and security monitoring, backups, and maintenance, handled inside Platforms.

Can you help with campaigns and email?

Yes — content strategy, campaigns, and email sit inside Brand, in the same engagement with one point of contact.

What does a project like this cost?

Scope drives price. Tell us the budget you're working with and we'll tell you honestly what fits it. The free Project Estimator gives a ballpark in about a minute.

Ready to get started?

Building for Non-Profit?

We've shipped across this industry. Tell us about your project and we'll reply within one business day with a senior point of contact.