← Case studies
Case study · Storytelling sites

A storytelling website that turned readers into recurring donors.

Program impact was buried three clicks deep, inside PDFs no one opened. We rebuilt the site around the people served — and the monthly giving line moved for the first time in three years.

Youth-serving nonprofit · 18 staff · Serving 1,400 kids annually

+62%
Recurring monthly gifts in first 6 months
2.1×
Average time on program pages
−41%
Bounce rate on the new donation page
The challenge

The old site treated stories as an afterthought — a blog category no one visited. The homepage led with a mission statement, a three-column "What We Do" block, and a donate button that landed on a generic form.

Meanwhile, the program team had a folder full of remarkable stories from the kids they served. None of them made it to the pages donors actually read.

The approach
01

Content audit driven by the donor journey

We mapped every page against three donor types: someone who just heard the org's name, someone deciding whether to give once, and someone considering a monthly commitment. Every page needed to earn its place in that journey — or come off the map.

02

Story-first architecture

Program pages now open with one specific young person's story, told in their own words when possible. Impact numbers appear below the fold, as evidence for the story — not as a wall of stats readers scroll past.

Every story ends with a purpose-built ask: sponsor a semester, cover a summer program week, fund a mentor's training.

03

A donation page that matches the promise

We rebuilt the donation flow around monthly giving as the default option. Preset amounts tied to specific outcomes. Suggested monthly gift shown alongside the one-time amount at equal weight. One-page checkout. No surprise ask on the thank- you screen.

04

A story cadence the team could sustain

We shipped the site with a simple submission template program staff use after each week of programming. New stories rotate in every three weeks. No writing marathons. No begging the ED for approval every time.

The outcome

Six months after launch, recurring monthly gifts were up 62% year over year — the first meaningful movement on that line in three years. Average time on program pages more than doubled. Bounce rate on the new donation page dropped 41%.

The development director now sends the site's story pages as her first touch with major-gift prospects — something she never did with the old site.

The site finally sounds like the room feels when you visit our program.

Director of Development, client organization
Common questions

What teams ask before starting one of these.

What makes a nonprofit storytelling website different from a normal one?
A storytelling website is structured around the people and moments your work exists for — not around your org chart. Program pages open with a specific person or place, impact data supports the story instead of leading it, and every page ends with a next step tied to what the reader just felt.
Do we need professional photography and video to do this?
No. Some of the strongest storytelling sites we've built use phone-captured photos and written first-person stories from program participants. What matters is that the story is real, specific, and attached to a clear next step.
How do you decide which stories go on the site?
We map stories to donor journeys. A first-time visitor needs a different story than a monthly donor considering an upgrade. We prioritize the three or four stories that do the most fundraising work, then build a simple system so your team can rotate in new ones every quarter.
Does story-driven design actually move donations?
In our experience, yes — but only when the story leads to a specific, low-friction next step. A great story with a generic 'Donate' button underperforms a good story with a purpose-built ask ('Sponsor a week of meals for one family').

Your best stories deserve a site that actually shows them.