How to Build a Nonprofit Website Without Code in 2026

You can build a nonprofit website without code by describing the organisation in plain language, connecting Stripe for donations, and publishing to a live URL. On Zugo a multi-page site with programmes, a donate page, and a volunteer form takes a few minutes to build. After that it is short text edits.

This guide covers the nonprofit-specific parts: what a donor reads before giving, how recurring donations are set up, what transparency pages have to contain, and where a website stops and donor management begins.

What does a donor read before giving?

Less than you think, and in a fixed order: what problem you work on, who you help, what a donation actually buys, and whether you are real. A first-time donor makes that decision in under a minute, usually on a phone, often from a link someone sent them.

Which gives you the page set. Home with the mission in one sentence and a donate button that is visible without scrolling. A programmes page describing what you do in concrete terms. An impact page with real numbers from your own reporting. A donate page. A get-involved page for volunteers. An about page with the team, the board, and your registration number.

The mission sentence is the hardest thing on the site and the most valuable. "We support vulnerable communities" tells a donor nothing. "We deliver hot meals to 200 housebound people in Leeds every week" tells them what their money does. Write that sentence before you write the prompt.

The transparency pages carry more weight for a small organisation than for a large one. A donor who has not heard of you is checking that you exist: registration number, annual report, named trustees, and a real address do that job.

What should the prompt say?

Zugo builds from a description, so the description has to carry the specifics a web agency would collect in a briefing:

Build a website for a nonprofit working on [cause] in [place].
Pages:
1. Home: mission in one sentence, "Donate" button in the hero,
   three programme cards, one impact number, recent news.
2. Programmes: [list each programme with who it helps and how].
3. Impact: real figures from our reporting, with the period they cover.
4. Donate: one-off and monthly options, suggested amounts with
   what each amount buys, card checkout.
5. Get involved: volunteer signup form, current openings.
6. About: history, team, trustees, registration number, annual report link.
Tone: plain and specific, no charity clichés. Palette: [your colours].

Two lines are worth adding. "Add an appeal banner block I can edit for campaigns" saves a rebuild every time you run one. "Show a newsletter signup in the footer of every page" builds the list that funds you next year, and the mechanics are covered in the guide on adding a newsletter signup.

If a blank prompt is the hard part, Zugo ships 25 templates and a simple content or organisation template gets you closer than an empty page.

How do donations actually work on the site?

Through the Stripe connector, which handles both one-off gifts and recurring monthly donations, plus the card details, the receipt, and the failed-payment retries. You describe the donation page and the amounts; Stripe does the money.

The choices that change your income are on your side of the connector, not Stripe's:

Ask for the donate page as its own page and keep the navigation on it minimal. A donor who arrives ready to give should not be offered six other things to read. The payment side is covered in more depth in the guide on taking payments in an AI-built app.

How do volunteer signups reach a human?

A volunteer form that nobody answers costs you more than no form, because a person who offered their time and heard nothing does not offer twice.

Keep the form to name, email, phone, what they want to help with, and their availability. The Resend connector sends every submission to a real inbox the moment it arrives, and the same connector can send an automatic acknowledgement so the volunteer knows they were heard while you work out the rota.

If the volunteer list needs to be searchable and shared between coordinators rather than sitting in one person's email, the Supabase connector adds a real database and a login, so a staff-only page can hold the list. That is a small step up in complexity and it is worth it once you have more than a handful of volunteers.

One thing to decide before publishing: who is on duty for that inbox. It is an organisational question, not a technical one, and it is the reason most volunteer forms fail.

What does a nonprofit site cost to build and run?

Zugo bills per action in credits, so the spend follows what you do rather than a project quote. A simple site build is 6 credits, a multi-page platform is 12 for the first three pages and 3 for each page after, and a text edit is 3.

The Free plan gives 5 credits, which is less than one build, so it is a look around rather than a launch. Pro is $25 per month with 200 credits, which covers a six-page site plus a year of campaign changes. Business is $99 per month.

For a small organisation the relevant comparison is not against an agency quote, it is against the volunteer who built the current site in 2019 and has since moved away. The reason to build it this way is that any staff member can change the appeal banner in one sentence, without waiting for anyone.

Note that card processing fees are separate and go to Stripe, not to Zugo. Many payment processors offer nonprofit rates; that arrangement is between you and them.

What does a website not do for fundraising?

This is the honest boundary and it is worth being clear about, because the gap between a website and a fundraising operation is where small charities lose money.

A site takes donations. It does not manage donors. Tracking who gave, when, how often, which appeal moved them, and when to thank them is donor management, and it lives in a CRM built for it. You can build a simple internal record with the Supabase connector, and past a few hundred donors you will want the real thing.

Tax receipts, gift aid claims, and grant reporting are compliance work with rules specific to your country. Stripe produces payment records; turning those into a compliant annual claim is your finance person's job, not a page on the site.

And the part no builder helps with: a website does not generate donors. It converts people who already arrived. The email list, the local press, the volunteer who tells their colleagues, that is where the traffic comes from.

Where does an AI builder stop for a nonprofit?

Four limits, stated plainly.

Complex products still need a team. A grant management system, a beneficiary case-management tool, or an event platform with tickets and seating is a product, and at that scale you want engineers. Zugo does not replace a development team.

Peer-to-peer fundraising pages are not one prompt. Letting supporters create their own pages with their own totals is a real feature with real logic, and you reach it through several targeted edits or through a specialist platform.

Every build is checked in a sandbox before you receive it, so a build that did not open is not handed over. That lowers the risk of a broken page rather than removing it, and it does not check that your impact figures are accurate. That part is on you, and it is the part donors care about most.

Accessibility needs a real check. A nonprofit site is more likely than most to be read by someone using a screen reader or a phone with large text. Ask for high contrast and large text in the prompt, then test the published page rather than assuming.

For an organisation that needs a credible site with a working donate button and a volunteer form this month, none of those limits block anything. If your model is closer to paid memberships than donations, the guide on building a membership site without code is the better fit. Otherwise write the mission sentence, describe the six pages, and get the donate button live at zugo.dev.