Your Donation Page Is a Checkout Form
I’ve been looking at open source donation pages as part of a case study on the FreeBSD Foundation. What I found applies to most projects, not just FreeBSD.
The typical open source donation page has: a “Donate” heading, a payment form, a tax ID, maybe a mailing address for checks, and a note about employer matching. That’s it.
It answers “how do I give?” but never “why should I give?” or “what happens when I give?”
That’s a checkout page, not a fundraising page. It converts people who already decided to donate. It does nothing to create or increase motivation.
The behavioral research on charitable giving is pretty clear on what works. Most of it has been studied for decades. And most of it is absent from open source donation pages.
What’s missing (and what the research says)
1. Suggested amounts with impact framing
Most donation pages show an empty field. No presets, no context.
Tversky and Kahneman’s anchoring research (1974) showed that the first number people see shapes their decision. Fundraising professionals have known this forever: preset amounts with a “most popular” nudge increase average donation size.
But the bigger problem is the lack of context. “$50” means nothing. “$50 funds one day of CI infrastructure” gives the donor a concrete picture of what their money buys.
The “most chosen” label is social proof and anchoring combined. The impact descriptions make the donation feel concrete.
2. Progress toward a goal
Most open source projects have a fundraising target. Almost none show it on the donation page.
A progress bar does two things: it shows the donor their contribution matters (the bar moves), and it creates urgency when the gap is visible.
All of our work is funded by donations.
The reserve context note is important. It turns “we need money” into “here’s specifically what’s at stake.” People give more when they understand the consequence of NOT giving (loss aversion, Kahneman & Tversky, 1979).
3. Financial transparency on the page
Foundations publish financial reports. Almost nobody reads them. But if you put three key numbers on the donation page itself, the donor sees them at the moment of decision.
(Financial reports linked somewhere in the footer)
Two scenarios, side by side. The “without” scenario is what actually happens when nonprofits run deficits for 4 years.
4. Social proof
When you donate to a cause and you’re the only one, it feels uncertain. When you can see that 214 other people donated this year, and someone gave $500 twelve minutes ago, it feels normal.
(nothing)
This is the bystander effect in reverse. Instead of “someone else will donate,” you see that real people already did.
5. The headline
This one is small but it matters.
The first is a transaction. The second is an appeal. Research on prosocial behavior consistently shows that appeals framed around the recipient’s need outperform transactional framing.
A concept mockup
I built a concept redesign to show what this looks like when you put it all together. Zero JavaScript, pure HTML and CSS, using real financial data from public reports. A proof of concept for the Foundation or anyone else to adapt.
The mockup includes a campaign progress bar, preset donation amounts with impact framing, a revenue vs. expenses chart, budget allocation breakdown, corporate sponsor tiers, a value gap table showing companies that use the project vs. what they donate, and a recent donor feed for social proof.
All of this built with numbers already public. No new data collection needed.
This is not a criticism
The foundations and projects with bare-bones donation pages are not doing anything wrong. They’re engineering organizations run by engineers. Fundraising UX is not their expertise, and they have a hundred other things competing for their time.
That’s exactly why this matters. These are small changes. A volunteer with UX experience could implement most of them in a weekend. The behavioral research behind them is well-established. And for projects running persistent fundraising shortfalls, even a modest increase in conversion rate or average donation size compounds over time.
If you maintain an open source project, look at your donation page. Ask yourself: does it answer “why should I give?” or just “how do I give?”
If you have UX skills and want to contribute to an open source project, this is one of the highest-impact things you can do that doesn’t involve writing code.
The concept mockup uses FreeBSD Foundation data because that’s the case study I’m working on. The principles apply to any project. This post is part of the simbiosi.org open source sustainability research.