What a nonprofit website is actually for
A nonprofit website does three jobs. It converts a stranger into a donor. It converts a stakeholder into a long-term ally. It makes staff's day-to-day operations easier. Anything that does not serve one of those three is decoration.
That framing kills entire categories of spend. The 'redesign every two years' cycle. The all-singing CMS. The bespoke design system that only one freelancer can maintain. Resources are scarce. Spend them where they show up in donations, applications, or staff hours saved.
Nonprofit website budget: what to spend in 2026
For most small-to-mid nonprofits ($100k to $5M revenue), a useful website costs between $4,000 and $15,000 to build and $50 to $300 per month to run. That covers:
- A modern marketing site (5 to 12 pages) with a working donation flow
- A CMS staff can update without a developer
- Accessibility that actually passes WCAG 2.2 AA
- Analytics that respect donor privacy
- Hosting, domain, email forwarding, and backups for a year
Bigger budgets ($20k and up) buy bespoke integrations. CRM sync, member portals, multilingual content, recurring giving with custom logic. They do not buy a better-looking site. Design quality is a function of taste and constraint, not budget.
Accessibility is the donor flow
If your donation form fails for screen readers, keyboard-only users, or low-vision donors, you are turning away the people most likely to give. Accessibility is not a compliance checkbox. It is the conversion funnel.
At minimum: semantic HTML, real form labels, 4.5:1 contrast, focus states you can see, error messages tied to the field, and a donation flow that works without JavaScript loaded. Test with VoiceOver and a keyboard. If you cannot complete the donation, neither can your donor.
Test your donation form with VoiceOver and the keyboard. If you cannot finish the gift, neither can your donor.
How to pick a nonprofit CMS (Framer, Webflow, Sanity, WordPress)
For most nonprofits the real choice is between a hosted page builder, a headless CMS with a custom front end, and WordPress. Each is the right answer for someone.
- Framer or Webflow: staff edit pages; designer-built; no dev contract
- Sanity or Lovable: complex content models, auth, member-facing work
- WordPress: you already have it and staff know it well
- Squarespace for anything past a brochure site
- Custom CMSes nobody else can maintain
- Free platforms that gate donor data or skim every gift
- Switching CMS without a written reason it pays back
Donation flows that actually convert
Use a real payment processor (Stripe, Givebutter, Donorbox). Not a contact form that asks people to mail a check. Default to recurring monthly with a one-click switch to one-time. Pre-fill amounts based on what your donors actually give. Show a thank-you that feels human, not a receipt.
The single highest-ROI change I see is cutting the donation flow from five steps to two. Most nonprofits ask for too much information up front. Take the card, take the email, send the rest as a follow-up. For org-wide thinking on where tech actually pays back, see AI automation for small mission-driven teams →.
Where to start this quarter
I build nonprofit sites on Lovable, Framer, or Sanity depending on the org. Engagements range from $2,000 fixed-scope page rebuilds to $7,500 per month full tech-partner retainers. Sliding-scale rates are available; pricing should not gatekeep mission-aligned work. The full nonprofits service page → has the longer version of how I work.
We figure out what your site needs to actually do, what a realistic budget looks like, and what the next 90 days could ship. No pitch, no pressure.